Database Auditing Essentials.Pdf
Total Page:16
File Type:pdf, Size:1020Kb
Database Auditing Who did what to which data when and how? INTELLIGENCE. INNOVATION. INTEGRITY Authors This presentation was prepared by: Craig S. Mullins Corporate Technologist NEON Enterprise Software, Inc. 14100 Southwest Freeway Sugar Land, TX 77479 Tel: 888.338.6366 Fax: 281.207.4973 E-mail: [email protected] This document is protected under the copyright laws of the United States and other countries as an unpublished work. This document contains information that is proprietary and confidential to NEON Enterprise Software, which shall not be disclosed outside or duplicated, used, or disclosed in whole or in part for any purpose other than to evaluate NEON Enterprise Software products. Any use or disclosure in whole or in part of this information without the express written permission of NEON Enterprise Software is prohibited. © 2006 NEON Enterprise Software (Unpublished). All rights reserved. INTELLIGENCE. INNOVATION. INTEGRITY Agenda Emergence of Enterprise Data Protection Regulatory Compliance and Auditing Database Auditing Capabilities INTELLIGENCE. INNOVATION. INTEGRITY DBA versus Data Management Database Administration Data Management — Database Security — Data Protection — Backup/Recovery — Data Privacy Protection — Disaster Recovery — Data Quality Improvement — Reorganization — Data Quality Monitoring — Performance Monitoring — Application Call Level Tuning — Database Archiving — Data Structure Tuning — Data Extraction — Capacity Planning — Metadata Management Managing the database environment Managing the content and uses of data INTELLIGENCE. INNOVATION. INTEGRITY Top Data Protection Challenges Where is my sensitive data located & who is using it? How can I enforce access & change control policies for critical databases? How do I simplify & automate compliance? INTELLIGENCE. INNOVATION. INTEGRITY Security By the Numbers (per TechTarget) 54% of companies say security budgets are growing 69% of security pros said their job will be more strategic in 2008 75% of security pros said their job will involve more compliance work 62% of security pros said their company’s top IT person will care more about security in 2008 52% said their top priority will have something to do with network/security integration 80% said they would “prefer to purchase best of breed products and integrate them into my network so I have the strongest security possible for my budget.” INTELLIGENCE. INNOVATION. INTEGRITY Database Security By the Numbers (per TechTarget) 67% of 1,100 security pros said securing databases was an important or very important challenge for 2008 — #1 in a list of 13 data protection initiatives 45% of security pros will spend more time on data protection in 2008 vs. 2007. — #3 on a list of 19 security activities 41% will spend more time on database security specifically INTELLIGENCE. INNOVATION. INTEGRITY Data Breaches According to the Privacy Rights Clearinghouse, the total number of records containing sensitive personal information involved in security breaches in the U.S. since January 2005 is: 218,198,364 As of February 5, 2008 http://www.privacyrights.org/ar/ChronDataBreaches.htm INTELLIGENCE. INNOVATION. INTEGRITY How Prevalent is this Problem? 68% of companies are losing sensitive data or having it stolen out from under them six times a year An additional 20% are losing sensitive data 22 times or more per year. Sources: eWeek, March 3, 2007 IT Policy Compliance Group http://www.eweek.com/c/a/Desktops-and-Notebooks/Report-Some-Companies-Lose-Data-Six-Times-a-Year/ INTELLIGENCE. INNOVATION. INTEGRITY Regulations Impacting Security Governance vs. Privacy Governance Privacy 1.1. Basel Basel IIII 1.1. EU EU DPDDPD 2.2. Sarbanes Sarbanes OxleyOxley 2.2. AU/NZ AU/NZ NPPNPP 3.3. OFAC OFAC 3.3. SB SB 1386/AB1386/AB 19501950 4.4. Turnbull Turnbull ReportReport 4.4. GLBA GLBA 5.5. HIPAA HIPAA 6.6. PCI PCI 7.7. FCRA FCRA ---- “Red “Red Flag”Flag” Protect and control the process Protect the data INTELLIGENCE. INNOVATION. INTEGRITY FCRA: “Red Flag” Rules All federally regulated financial institutions must be in full compliance by Nov. 1, 2008, with the so-called "Red Flag" provisions of the Fair and Accurate Credit Transactions Act of 2003 (FACTA). Part of FCRA – the Fair Credit Reporting Act. Requires that financial institutions and creditors develop and deploy an Identity Theft Prevention Program for combating ID theft on new and existing accounts. Each institution must develop a program that will: Identify relevant patterns, practices, and specific forms of activity that are "red flags" signaling possible ID theft. Include a mechanism to detect red flags identified by the program. Quickly respond to detected red flags in a way to both prevent and mitigate ID theft. Be updated regularly to reflect changes in real world risks from ID theft. INTELLIGENCE. INNOVATION. INTEGRITY Top Regulations Impacting DB Security ISO NIST CobiT PCI CMS HIPAA GLBA 17799 NERC 800-53 Audit Requirements (SOX) DSS ARS (Basel II) (FISMA) 1. Access to Sensitive Data (Successful/Failed SELECTs) 9999 9 9 2. Schema Changes (DDL) (Create/Drop/Alter Tables, etc.) 999 9 9 9 9 3. Data Changes (DML) (Insert, Update, Delete) 999 4. Security Exceptions (Failed logins, SQL errors, etc.) 99999 9 9 9 5. Accounts, Roles & Permissions (DCL) 99999 9 9 9 (GRANT, REVOKE) DDL = Data Definition Language (aka schema changes) DML = Data Manipulation Language (data value changes) DCL = Data Control Language INTELLIGENCE. INNOVATION. INTEGRITY Enterprise Data Protection Cost associated with Non-Compliance Loss/Out of Business & Breach of Data Increased Staff Fines Simplify & automate Protect enterprise data Rapidly address auditors’ compliance process requirements Tactical Strategic Need Need INTELLIGENCE. INNOVATION. INTEGRITY Regulatory Compliance and… Impact: upper-level management is keenly aware of the need to comply, if not all of the details that involves. Prosecution: prosecution can result in huge fines and even imprisonment. Cost: the cost of complete compliance can be significant. Durability: although there have been discussions about scaling back some laws (e.g. SOX), increasing regulations and therefore increasing time, effort, and capital will be spent on compliance. That is, the issue will not just disappear if you ignore it long enough! INTELLIGENCE. INNOVATION. INTEGRITY Why Audit & Secure Databases Cost of Breach Identity theft, credit cards etc. Regulatory Compliance Database monitoring is key requirement Database Leak Prevention Sensitive data needs protection Open Accessability Web 2.0 applications dissolving traditional perimeter controls INTELLIGENCE. INNOVATION. INTEGRITY Data and Database Protection, Security, and Auditing Trends ta a D f o t n u o m A Compliance Protection 0 Data Protection Issues: Accessibility Volume of data Increased accessibility of data Regulatory compliance Increased number and type of threats INTELLIGENCE. INNOVATION. INTEGRITY Database Auditing In a world replete with regulations and threats, organizations have to go well beyond securing their data. Essentially, they have to perpetually monitor their data in order to know who or what did exactly what, when and how – to all their data. Source: Audit the Data – or Else: Un-audited Data Access Puts Business at High Risk. Baroudi-Bloor, 2004. HIPAA, for example, requires patients to be informed any time someone has even looked at their data. INTELLIGENCE. INNOVATION. INTEGRITY What is Database Auditing? There are many names used for basically the same thing. I’ll call it database auditing, but you may also know it as: Data Access Auditing Data Monitoring Data Activity Monitoring (DAM) INTELLIGENCE. INNOVATION. INTEGRITY Database Auditing definition Database Auditing: The process of monitoring access to and modification of selected database objects and resources within operational databases and retaining a detailed record of the access where said record can be used to proactively trigger actions and can be retrieved and analyzed as needed. INTELLIGENCE. INNOVATION. INTEGRITY Key Stakeholder Requirements SECURITY OPERATIONS 9 Real-time policies 9 Separation of duties 9 Minimal impact 9 Secure audit trail 9 Best practices reports 9 Change management 9 Data mining & 9 Automated controls 9 Performance optimization forensics 100% Visibility & Unified View INTELLIGENCE. INNOVATION. INTEGRITY Database Auditing Types of Database Auditing Database Auditing Requirements Database Auditing Challenges Native DBMS Database Auditing? Reporting and Analyzing the Audit Data INTELLIGENCE. INNOVATION. INTEGRITY Types of Database Auditing Authorization Auditing Who can do what. Access Auditing Who did do what. Modifications: INSERT, UPDATE, DELETE Reads: SELECT Other: DDL (CREATE / DROP/ALTER), DCL (GRANT / REVOKE), Utilities, SQL errors, failed logins, etc. Replication Auditing Who copied which data where. INTELLIGENCE. INNOVATION. INTEGRITY Database Auditing Approaches What methods are available? Audit within the DBMS (traces) — Must start performance trace – Overhead as trace records are written by the DBMS — DDL changes required to traced tables? Audit from the database transaction log files — Modifications are on the log anyway so… Audit over the network — Capture SQL requests as they are sent over the network — What about non-network requests? (e.g. CICS w/DB2) Audit directly against the DBMS server (software tap) INTELLIGENCE. INNOVATION. INTEGRITY Native DBMS Audit The native DBMS audit capability may not be optimal: Separation of duties