BeyondTrust

Security in Context: The BeyondTrust Blog

Welcome to Security in Context

Bringing you news and commentary on solutions and strategies for protecting critical IT infrastructure in the context of your business.

3 Reasons POS Should Give A DAM

Posted August 1, 2011    Peter McCalister

Just when you thought we exceeded our TLA (three letter acronym) quota for the year, up pops this idea for a blog based on a recent discussion with a national retailer, and I couldn’t resist the play on acronyms and the potential for multiple interpretations. But don’t let the TLAs scare you. This is actually a serious topic that does effect any of you who are responsible for compliance across remote sales locations.
If you haven’t figured out the TLAs for todays’s discussion, then don’t feel lost, as I can think of about five variations on each. For today’s purpose though:
POS stands for Point of Sale and refers to systems that handle local sales transactions and report back to corporate for accounting and audit purposes

DAM stands for Database Activity Monitoring and refers to the security software responsible for monitoring those transactions to ensure compliance as well as assist with security
Most POS projects involve backoffice applications specific to the type of retail organization you are (i.e. grocery vs clothing, vs consumer goods, vs whatever you sell in a physically remote location). These apps typically run on SQL Server or some other database like Oracle or IBM DB2. If you only have one or two stores, then DAM may be overkill but if you have 50+ stores then you will find it is mandatory for compliance purposes.

Any good DAM solution is going to be able to configure audit sources and set up notifications for events. Audit policies and rules define conditions for activity and exceptions. Collection and publishing schedules facilitate processes to monitor activity and status. A strong console administration and various report packs also facilitate easier and faster deployment for immediate discovery and reporting of compliance issues especially with exporting and scheduling report distribution.

So, back to the title of today’s blog; What are the 3 reasons POS should give a DAM?
PCI DSS compliance or for those of you tired of acronyms, Payment Card Industry Data Security Standards compliance. This is the primary regulation all retailers need to be most mindful of as it sets the requirements for transaction data integrity and privacy.

Remediation for any security breach that may inadvertently occur at the database level of your POS. Know exactly who did what, when and where will allow your security teams to handle the situations that present themselves.

Business intelligence on what types of database admin activities are occuring at specific POS sites relative to other locations.

Leave a Reply

Additional articles

pbps-blog2

10 Ways to Ensure Your Privileged Password Management Strategy Will Succeed

Posted April 27, 2015    Scott Lang

Leveraging complex, frequently updated passwords is a basic security best practice for protecting privileged accounts in your organisation. But if passwords are such a no-brainer, why do so many data breaches tie back to poor password management?

Tags:
, , , , , , , ,
beyond-trust

PowerBroker for Windows – Most Innovative IAM Solution by Cyber Defense Magazine

Posted April 21, 2015    Scott Lang

PowerBroker for Windows has been selected as a winner by the 2015 Cyber Defense Magazine Awards Program in the category of “Most Innovative Identity and Access Management Solution”.

Tags:
, , ,
pbps-customer-campaign-image

Are you changing your passwords as often as the weather changes?

Posted April 20, 2015    Scott Lang

There is one thing that should change more frequently than the weather: Your privileged passwords. Why? If you’re like more than 25% of companies out there, then your current IT environment contains unmanaged accounts putting you at risk of data breaches and compliance violations, and you don’t have a process to control those accounts.

Tags:
, , , ,