Compliance Made Simple

Database compliance, automated

Meet regulatory requirements with comprehensive audit logging, real-time threat detection, and automated compliance reporting for 20+ frameworks.

55+
Compliance Frameworks
100%
Audit Coverage
<72hr
Breach Detection
1-Click
Evidence Reports
GDPR European Union All Industries

EU General Data Protection Regulation

Comprehensive data protection regulation governing how organizations collect, store, and process personal data of EU residents. Non-compliance can result in fines up to 4% of global annual revenue.

Why You Need Database Auditing

Article 30 Records of Processing Activities

Organizations MUST maintain detailed records of all personal data processing activities, including access logs.

Article 32 Security of Processing

REQUIRES appropriate technical measures including the ability to ensure ongoing confidentiality and integrity of processing systems.

Article 33 Breach Notification

Data breaches MUST be reported to authorities within 72 hours. Requires real-time detection capabilities.

Article 35 Data Protection Impact Assessment

High-risk processing REQUIRES documented impact assessments with evidence of security measures.

DB Audit Accelerators

Policy Template

Personal Data Access Monitoring

Pre-built policy to track all access to tables containing EU resident data

Report

DPIA Evidence Report

Automated report documenting all data access patterns for impact assessments

Classification

EU PII Patterns

Auto-detect EU-specific identifiers: national IDs, IBAN, VAT numbers

Alert

72-Hour Breach Detection

Real-time alerting ensures you detect breaches within notification window

CCPA/CPRA California, USA All Industries

California Consumer Privacy Act / California Privacy Rights Act

California privacy law granting consumers rights over their personal information. Applies to businesses with >$25M revenue, data on 100k+ consumers, or 50%+ revenue from selling data.

Why You Need Database Auditing

Section 1798.100 Right to Know

Consumers can request disclosure of specific personal information collected. REQUIRES ability to locate and report all consumer data.

Section 1798.105 Right to Delete

MUST delete consumer data upon request and verify deletion across all systems.

Section 1798.150 Security Requirements

Businesses MUST implement reasonable security procedures. Failure creates private right of action.

CPRA Addition Sensitive Personal Information

Enhanced protections REQUIRED for sensitive data including precise geolocation and financial information.

DB Audit Accelerators

Policy Template

Consumer Data Access Tracking

Track all queries accessing California consumer records

Report

Data Subject Request Report

Generate complete access history for any consumer within minutes

Classification

CA Consumer PII

Identify California-specific data: CA driver license, state IDs

Alert

Bulk Data Export Detection

Alert when large volumes of consumer data are accessed or exported

LGPD Brazil All Industries

Lei Geral de Proteção de Dados

Brazil comprehensive data protection law modeled after GDPR. Applies to any processing of personal data of individuals located in Brazil, regardless of where the processor is located.

Why You Need Database Auditing

Article 37 Processing Records

Controllers and processors MUST maintain records of personal data processing operations.

Article 46 Security Measures

REQUIRES technical and administrative measures to protect personal data from unauthorized access.

Article 48 Incident Communication

Security incidents MUST be communicated to the national authority and data subjects in reasonable time.

Article 18 Data Subject Rights

MUST provide access to data, correction, deletion, and portability upon request.

DB Audit Accelerators

Policy Template

Brazil Personal Data Monitoring

Track access to CPF, RG, and other Brazilian identifiers

Report

LGPD Compliance Report

Document processing activities and security measures

Classification

Brazilian PII Patterns

Auto-detect CPF, CNPJ, RG, and Brazilian address formats

Alert

Incident Detection

Real-time detection of potential data breaches

PIPEDA Canada All Industries

Personal Information Protection and Electronic Documents Act

Canadian federal privacy law governing how private sector organizations collect, use, and disclose personal information in commercial activities.

Why You Need Database Auditing

Principle 4.7 Safeguards

Personal information MUST be protected by security safeguards appropriate to the sensitivity of the information.

Principle 4.9 Individual Access

Upon request, individuals MUST be informed of the existence, use, and disclosure of their personal information.

PIPEDA Breach Breach Reporting

Organizations MUST report breaches that pose real risk of significant harm to the Privacy Commissioner and affected individuals.

Principle 4.1 Accountability

Organizations are ACCOUNTABLE for personal information under their control.

DB Audit Accelerators

Policy Template

Canadian PII Access Monitoring

Track access to SIN, health card numbers, and Canadian identifiers

Report

Access Request Response

Generate complete data access history for individual requests

Classification

Canadian PII Patterns

Detect SIN, provincial health numbers, Canadian postal codes

Alert

Breach Risk Detection

Identify access patterns that may constitute reportable breaches

PDPA Singapore All Industries

Singapore Personal Data Protection Act

Singapore data protection law governing collection, use, and disclosure of personal data by private organizations in Singapore.

Why You Need Database Auditing

Section 24 Protection Obligation

Organizations MUST protect personal data with reasonable security arrangements.

Section 21 Access Obligation

Upon request, organizations MUST provide individuals access to their personal data and information about its use.

Section 26B Data Breach Notification

Notifiable breaches MUST be reported to PDPC within 3 calendar days of assessment.

Section 25 Retention Limitation

Organizations MUST cease retention when no longer necessary for legal or business purposes.

DB Audit Accelerators

Policy Template

Singapore Data Protection

Monitor access to NRIC, FIN, and Singapore-specific identifiers

Report

PDPA Compliance Report

Document data protection measures and access controls

Classification

Singapore PII Patterns

Detect NRIC, FIN, Singapore phone formats, postal codes

Alert

3-Day Breach Alert

Rapid breach detection to meet 3-day notification requirement

PIPL China All Industries

Personal Information Protection Law of China

China comprehensive data protection law with strict requirements for processing personal information of individuals in China, including data localization requirements.

Why You Need Database Auditing

Article 51 Security Measures

Personal information handlers MUST adopt necessary measures to ensure processing activities comply with laws and prevent unauthorized access.

Article 55 Impact Assessment

REQUIRES personal information protection impact assessment before processing sensitive personal information.

Article 57 Incident Response

In case of data breach, handlers MUST immediately take remedial measures and notify authorities and individuals.

Article 40 Cross-Border Transfer

Cross-border data transfers REQUIRE security assessment, certification, or standard contracts.

DB Audit Accelerators

Policy Template

China Data Processing Monitor

Track all processing of Chinese resident personal information

Report

PIPL Impact Assessment

Document processing activities for impact assessment requirements

Classification

Chinese PII Patterns

Detect Chinese ID numbers, phone formats, and sensitive categories

Alert

Cross-Border Transfer Detection

Alert when data matching Chinese residents is accessed from outside China

SOX United States Public Companies

Sarbanes-Oxley Act

U.S. federal law mandating internal controls and audit trails for financial reporting systems in publicly traded companies. Criminal penalties for executives who certify false statements.

Why You Need Database Auditing

Section 302 Corporate Responsibility

CEO and CFO MUST personally certify financial reports. REQUIRES verifiable audit trails proving data integrity.

Section 404 Internal Controls

Companies MUST assess and report on internal control effectiveness. REQUIRES documented evidence of controls over financial data.

Section 802 Criminal Penalties

Knowingly altering or destroying records is a federal crime. REQUIRES tamper-evident audit logging.

Section 103 Audit Documentation

Audit records MUST be retained for 7 years. REQUIRES long-term, immutable log storage.

DB Audit Accelerators

Policy Template

Financial Data Change Tracking

Monitor all INSERT, UPDATE, DELETE on financial tables

Policy Template

Privileged User Monitoring

Track DBA and admin access to financial systems

Report

SOX Audit Evidence Report

7-year audit trail with tamper-evident verification

Alert

Schema Change Detection

Immediate alerts on DDL changes to financial database objects

PCI-DSS Global Payment Card Processing

Payment Card Industry Data Security Standard

Security standard for organizations handling credit card data. Required for all merchants and service providers that store, process, or transmit cardholder data.

Why You Need Database Auditing

Requirement 10.1 Audit Trail Implementation

MUST implement audit trails to link all access to system components to each individual user.

Requirement 10.2 Automated Audit Trails

MUST implement automated audit trails for all system components to reconstruct events.

Requirement 10.4 Time Synchronization

All critical system clocks MUST be synchronized. Audit logs MUST have accurate timestamps.

Requirement 10.7 Audit Trail Retention

Audit trail history MUST be retained for at least one year, with minimum 3 months immediately available.

DB Audit Accelerators

Policy Template

Cardholder Data Access Monitoring

Track all SELECT/UPDATE/DELETE on cardholder data tables

Report

PCI Compliance Scorecard

Requirement 10 compliance evidence with gap analysis

Classification

PCI Data Patterns

Detect PANs, CVVs, expiration dates, cardholder names

Alert

Bulk Card Data Access

Alert on queries returning large volumes of card data

GLBA United States Financial Services

Gramm-Leach-Bliley Act

U.S. law requiring financial institutions to protect customer financial information and explain data sharing practices. Enforced by FTC, SEC, and banking regulators.

Why You Need Database Auditing

Safeguards Rule Information Security Program

Financial institutions MUST develop, implement, and maintain a comprehensive security program.

314.4(c) Access Controls

MUST implement access controls on customer information systems, including monitoring of access.

314.4(d) Activity Monitoring

MUST monitor systems and procedures to detect actual and attempted attacks or intrusions.

Safeguards Rule Incident Response

MUST implement procedures to respond to security incidents affecting customer information.

DB Audit Accelerators

Policy Template

Customer Financial Data Monitoring

Track access to account numbers, balances, transaction histories

Report

GLBA Safeguards Report

Evidence of security program implementation

Classification

Financial Account Patterns

Detect account numbers, routing numbers, financial identifiers

Alert

Unauthorized Access Detection

Detect attempts to access customer data without authorization

DORA European Union Financial Services

EU Digital Operational Resilience Act

EU regulation ensuring financial entities can withstand, respond to, and recover from ICT-related disruptions. Effective January 2025 for all EU financial institutions.

Why You Need Database Auditing

Article 6 ICT Risk Management

Financial entities MUST have ICT risk management framework including monitoring of ICT systems.

Article 17 ICT Incident Classification

MUST classify ICT-related incidents and report major incidents to competent authorities.

Article 19 Incident Reporting

Major ICT incidents MUST be reported within specified timeframes with root cause analysis.

Article 28 Third-Party Risk

MUST maintain register of third-party ICT service providers and monitor their access.

DB Audit Accelerators

Policy Template

ICT System Monitoring

Comprehensive monitoring of all database access and changes

Report

DORA Incident Report

Incident classification and timeline for regulatory reporting

Classification

Critical Data Assets

Identify and classify critical financial data assets

Alert

Third-Party Access Monitoring

Track and alert on third-party service provider database access

HIPAA United States Healthcare

Health Insurance Portability and Accountability Act

U.S. law protecting sensitive patient health information. Applies to healthcare providers, health plans, and healthcare clearinghouses. Civil penalties up to $1.5M per violation category per year.

Why You Need Database Auditing

164.312(b) Audit Controls

Covered entities MUST implement hardware, software, and/or procedural mechanisms that record and examine activity in systems containing ePHI.

164.308(a)(1)(ii)(D) Activity Review

MUST implement procedures to regularly review records of information system activity, such as audit logs, access reports, and security incident tracking.

164.312(c)(1) Integrity Controls

MUST implement policies and procedures to protect ePHI from improper alteration or destruction.

164.308(a)(6) Security Incident Procedures

MUST implement policies and procedures to identify, respond to, and mitigate security incidents.

DB Audit Accelerators

Policy Template

PHI Access Audit Policy

Track all access to tables containing patient health information

Policy Template

Minimum Necessary Monitoring

Detect access patterns exceeding minimum necessary standard

Report

HIPAA Audit Trail Report

164.312(b) compliant audit evidence with examiner notes

Classification

PHI Data Patterns

Detect MRN, diagnosis codes, medications, insurance IDs

Alert

PHI Breach Detection

Real-time detection of unauthorized PHI access

FedRAMP United States Government & Cloud Providers

Federal Risk and Authorization Management Program

U.S. government program providing standardized security assessment for cloud products serving federal agencies. Mandatory for cloud service providers working with federal government.

Why You Need Database Auditing

AU-2 Audit Events

Organization MUST determine auditable events and ensure the system generates audit records for defined events.

AU-3 Content of Audit Records

Audit records MUST contain: what type of event, when it occurred, where it occurred, source, outcome, and identity of individuals/subjects.

AU-6 Audit Review, Analysis, and Reporting

Organization MUST review and analyze audit records for indications of inappropriate or unusual activity.

AU-9 Protection of Audit Information

System MUST protect audit information and audit tools from unauthorized access, modification, and deletion.

DB Audit Accelerators

Policy Template

NIST 800-53 AU Family

Complete implementation of all AU (Audit) controls

Report

FedRAMP Evidence Package

Pre-formatted evidence for 3PAO assessments

Classification

CUI Patterns

Detect Controlled Unclassified Information categories

Alert

Audit System Health

Monitor and alert on audit logging system availability

FISMA United States Federal Government

Federal Information Security Management Act

U.S. law requiring federal agencies to develop, document, and implement information security programs. Mandates NIST standards for all federal information systems.

Why You Need Database Auditing

NIST 800-53 AU-2 Audit Events

Federal systems MUST audit: successful/failed account logons, account management, object access, policy changes, privilege functions.

Continuous Monitoring Ongoing Assessment

Agencies MUST implement continuous monitoring programs for security controls.

NIST 800-53 SI-4 System Monitoring

Organizations MUST monitor systems to detect attacks and indicators of potential attacks.

Annual Assessment Security Reviews

Systems MUST undergo annual security assessments with documented evidence.

DB Audit Accelerators

Policy Template

Federal System Audit Policy

All NIST 800-53 required audit events pre-configured

Report

FISMA Annual Assessment Report

Audit control evidence for annual security reviews

Dashboard

Continuous Monitoring Dashboard

Real-time security posture visibility

Alert

Attack Pattern Detection

SI-4 compliant monitoring with threat detection

StateRAMP United States (State Level) State Government

State Risk and Authorization Management Program

Standardized security framework for state and local governments to assess cloud service providers. Based on FedRAMP with state-specific adaptations.

Why You Need Database Auditing

AU Controls FedRAMP-Aligned Audit

Cloud services MUST implement audit controls based on FedRAMP baseline requirements.

Continuous Monitoring Ongoing Compliance

Providers MUST maintain continuous monitoring and submit monthly/annual reports.

3PAO Assessment Independent Verification

Security posture MUST be verified by approved third-party assessment organizations.

Annual Review Reassessment

Authorization MUST be renewed annually with evidence of maintained compliance.

DB Audit Accelerators

Policy Template

StateRAMP Audit Controls

FedRAMP-aligned audit policy templates

Report

StateRAMP Evidence Package

Monthly and annual compliance evidence reports

Dashboard

Compliance Status Dashboard

Real-time view of control implementation status

Alert

Compliance Drift Detection

Alert when audit controls deviate from baseline

CMMC United States Defense Industrial Base

Cybersecurity Maturity Model Certification

DoD framework verifying cybersecurity practices of contractors handling Federal Contract Information (FCI) and Controlled Unclassified Information (CUI).

Why You Need Database Auditing

AU.L2-3.3.1 Create Audit Records

Organizations MUST create system audit logs and records to enable monitoring, analysis, and investigation.

AU.L2-3.3.2 User Accountability

MUST ensure actions can be traced to individual users uniquely.

AU.L2-3.3.4 Audit Process Failure

MUST alert in the event of an audit logging process failure.

SI.L2-3.14.6 Monitor Communications

MUST monitor organizational systems including inbound/outbound communications for attacks.

DB Audit Accelerators

Policy Template

CUI Protection Policy

Monitor all access to Controlled Unclassified Information

Report

CMMC Assessment Evidence

Practice-by-practice evidence documentation

Classification

CUI Data Patterns

Identify and classify CUI categories in databases

Alert

Audit Health Monitoring

Alert on audit system failures per AU.L2-3.3.4

SOC 2 Global Service Providers

Service Organization Control 2

Trust service criteria framework for evaluating controls related to security, availability, processing integrity, confidentiality, and privacy. Required by enterprise customers for vendor assessment.

Why You Need Database Auditing

CC6.1 Logical Access Security

Entity MUST implement logical access security software, infrastructure, and architectures to protect against threats.

CC7.2 System Monitoring

Entity MUST monitor system components for anomalies indicative of malicious acts or system failures.

CC7.3 Security Event Evaluation

Entity MUST evaluate security events to determine whether they could impact ability to meet objectives.

CC8.1 Change Management

Entity MUST authorize, design, develop, configure, test, approve, and implement changes to meet objectives.

DB Audit Accelerators

Policy Template

Trust Services Monitoring

Policies aligned to all five trust service criteria

Report

SOC 2 Control Evidence

Auditor-ready evidence for Type I and Type II reports

Dashboard

Security Event Dashboard

Real-time visibility into CC7.2 and CC7.3 events

Alert

Anomaly Detection

AI-powered detection of unusual system behavior

ISO 27001 Global All Industries

ISO/IEC 27001 Information Security Management

International standard for information security management systems (ISMS). Certification demonstrates commitment to security and is often required for international business.

Why You Need Database Auditing

A.12.4.1 Event Logging

Event logs recording user activities, exceptions, faults and information security events MUST be produced, kept and regularly reviewed.

A.12.4.3 Administrator Logs

System administrator and operator activities MUST be logged and the logs protected and regularly reviewed.

A.9.2.1 User Registration

Formal user registration and de-registration process MUST be implemented to enable assignment of access rights.

A.16.1.2 Reporting Security Events

Information security events MUST be reported through appropriate management channels as quickly as possible.

DB Audit Accelerators

Policy Template

A.12.4 Logging Policy

Complete implementation of ISO 27001 logging controls

Report

ISMS Audit Report

Evidence package for ISO 27001 certification audits

Dashboard

Security Event Review

Regular review interface for A.12.4.1 compliance

Alert

Privileged User Monitoring

A.12.4.3 compliant administrator activity tracking

NIST CSF United States / Global All Industries

NIST Cybersecurity Framework

Voluntary framework providing guidance for organizations to manage and reduce cybersecurity risk. Widely adopted as a baseline for security programs worldwide.

Why You Need Database Auditing

DE.CM-1 Network Monitoring

The network is monitored to detect potential cybersecurity events.

DE.CM-3 Personnel Activity Monitoring

Personnel activity is monitored to detect potential cybersecurity events.

DE.CM-7 Unauthorized Activity Monitoring

Monitoring for unauthorized personnel, connections, devices, and software is performed.

PR.DS-1 Data-at-Rest Protection

Data-at-rest is protected with appropriate controls.

DB Audit Accelerators

Policy Template

DE.CM Monitoring Policy

Detect function controls for database activity

Report

Framework Alignment Report

Map database controls to CSF categories and subcategories

Dashboard

Detect Function Dashboard

Real-time view of DE.CM control effectiveness

Alert

Unauthorized Access Detection

DE.CM-7 compliant unauthorized activity alerts

CIS Controls Global All Industries

Center for Internet Security Critical Security Controls

Prioritized set of actions to protect organizations from known cyber attack vectors. Adopted by numerous organizations as a practical security framework.

Why You Need Database Auditing

Control 3 Data Protection

Develop processes and technical controls to identify, classify, securely handle, retain, and dispose of data.

Control 6 Access Control Management

Use processes and tools to create, assign, manage, and revoke access credentials and privileges.

Control 8 Audit Log Management

Collect, alert, review, and retain audit logs of events that could help detect, understand, or recover from an attack.

Control 13 Network Monitoring

Operate processes and tools to establish and maintain comprehensive network monitoring and defense.

DB Audit Accelerators

Policy Template

Control 8 Implementation

Complete audit log management per CIS requirements

Report

CIS Controls Assessment

Control-by-control implementation evidence

Classification

Data Classification Rules

Control 3 compliant data identification and classification

Alert

Attack Pattern Detection

Alerts based on known attack signatures and behaviors

NIS2 European Union Essential & Important Entities

EU Network and Information Security Directive 2

EU directive establishing cybersecurity obligations for entities operating essential and important services. Effective October 2024 with significant penalties for non-compliance.

Why You Need Database Auditing

Article 21(1) Risk Management Measures

Essential and important entities MUST take appropriate technical and organizational measures to manage security risks.

Article 21(2)(g) Policies on Use of Cryptography

Entities MUST have policies and procedures regarding use of cryptography and encryption.

Article 23 Incident Reporting

Significant incidents MUST be reported to CSIRT within 24 hours, with full report within 72 hours.

Article 21(2)(d) Supply Chain Security

Entities MUST address security in supplier relationships and direct suppliers.

DB Audit Accelerators

Policy Template

NIS2 Database Security Policy

Technical measures for database security per Article 21

Report

NIS2 Incident Report

24/72-hour incident report templates with required fields

Classification

Essential Service Data

Identify and classify data supporting essential services

Alert

Significant Incident Detection

Real-time detection to enable 24-hour initial notification

21 CFR Part 11 United States / Global Pharmaceuticals & Life Sciences

FDA Electronic Records and Electronic Signatures

FDA regulation establishing criteria for electronic records and signatures to be considered trustworthy and equivalent to paper records. Required for any company manufacturing or distributing FDA-regulated products.

Why You Need Database Auditing

§11.10(e) Audit Trail

Systems MUST use secure, computer-generated, time-stamped audit trails to independently record the date and time of operator entries and actions.

§11.10(k)(2) Authority Checks

REQUIRES use of authority checks to ensure only authorized individuals can use the system, access operations, or sign records.

§11.10(g) Operational System Checks

Systems MUST enforce permitted sequencing of steps and events, as appropriate.

§11.50 Signature Manifestations

Electronic signatures MUST be linked to their respective electronic records to ensure signatures cannot be removed or transferred.

DB Audit Accelerators

Policy Template

GxP Data Integrity Monitoring

Track all access to validation data, batch records, and quality systems

Report

21 CFR Part 11 Audit Trail Report

Timestamped audit trail with operator identification for FDA inspections

Alert

Unauthorized Access Detection

Real-time alerts when users attempt unauthorized system access

Classification

GxP Data Patterns

Identify batch records, COAs, validation data, and LIMS entries

CMS United States Healthcare / Medicare & Medicaid

Centers for Medicare & Medicaid Services Requirements

CMS security and privacy requirements for organizations handling Medicare and Medicaid data. Includes Minimum Acceptable Risk Standards (MARS-E) and Acceptable Risk Safeguards (ARS).

Why You Need Database Auditing

MARS-E 2.0 AU-2 Audit Events

Systems MUST be capable of auditing successful and unsuccessful account logon events, account management, and object access.

MARS-E 2.0 AU-3 Content of Audit Records

Audit records MUST contain type of event, when occurred, where occurred, source, outcome, and identity of individuals.

ARS 3.1 AC-2 Account Management

Organizations MUST manage information system accounts including identifying account types and establishing conditions for membership.

MARS-E 2.0 AU-6 Audit Review

Organizations MUST review and analyze system audit records for indications of inappropriate or unusual activity.

DB Audit Accelerators

Policy Template

Medicare/Medicaid Data Monitoring

Track all access to beneficiary data and claims information

Report

CMS MARS-E Compliance Report

Evidence package for CMS security assessments

Classification

CMS Data Patterns

Detect Medicare IDs, Medicaid IDs, and beneficiary information

Alert

Unusual Access Pattern Detection

Alert on anomalous access to Medicare/Medicaid data

ISO 13485 Global Medical Devices

Medical Devices Quality Management Systems

International standard specifying requirements for quality management systems for medical device manufacturers. Required for CE marking and FDA approval processes.

Why You Need Database Auditing

§4.2.5 Control of Documents

Organizations MUST establish documented procedures to define controls needed for approval, review, updating, and identification of documents.

§4.2.4 Control of Records

Records MUST remain legible, readily identifiable, and retrievable. Retention times MUST be established.

§7.5.1 Control of Production

Production processes MUST be validated and controlled with documented procedures and traceability.

§8.2.4 Monitoring and Measurement

Organization MUST monitor and measure product characteristics to verify requirements have been met.

DB Audit Accelerators

Policy Template

Medical Device Data Traceability

Track all software-driven medical device database outputs

Report

ISO 13485 Audit Evidence

Full lifecycle auditability documentation for certification

Classification

Device Master Records

Identify DMR, DHR, and device-related production data

Alert

Quality Record Modification

Alert on changes to quality management records

EU EHDS European Union Healthcare / Research

European Health Data Space

EU regulation establishing a common framework for health data sharing across member states. Effective 2026, enables secondary use of health data for research while maintaining patient privacy.

Why You Need Database Auditing

Article 33 Secondary Use Logging

Health data access bodies MUST log all queries and data access for secondary use purposes.

Article 35 Data Provenance

REQUIRES complete provenance tracking of health data from source through all processing stages.

Article 37 Access Control

Organizations MUST implement technical measures to ensure only authorized researchers access data.

Article 41 Security Requirements

REQUIRES appropriate technical and organizational measures to protect health data during secondary use.

DB Audit Accelerators

Policy Template

Research Data Access Monitoring

Track all secondary use data queries for medical research

Report

EHDS Provenance Report

Complete data lineage and access history for compliance

Classification

EU Health Data Patterns

Identify health records across EU member state formats

Alert

Unauthorized Research Access

Alert on access outside approved research protocols

NIST 800-53 United States Federal Government / Contractors

NIST Special Publication 800-53 Revision 5

Comprehensive catalog of security and privacy controls for federal information systems. Required for all US federal agencies and their contractors. The gold standard for government security.

Why You Need Database Auditing

AU-2 Event Logging

Organization MUST identify events requiring logging and establish frequency of audit log reviews.

AU-3 Content of Audit Records

Audit records MUST contain what type of event, when occurred, where occurred, source, outcome, and user identity.

AU-6 Audit Record Review

Organization MUST review and analyze audit records for indications of inappropriate or unusual activity.

AU-9 Protection of Audit Information

System MUST protect audit information and audit tools from unauthorized access, modification, and deletion.

DB Audit Accelerators

Policy Template

NIST AU Family Implementation

Complete implementation of all AU (Audit) controls

Report

NIST 800-53 Evidence Package

Control-by-control compliance documentation

Dashboard

Continuous Monitoring Dashboard

Real-time security posture visibility per AU-6

Alert

Security Event Detection

AU-6 compliant monitoring with threat detection

IRS Pub 1075 United States Taxation / Government

IRS Publication 1075 - Tax Information Security Guidelines

IRS requirements for safeguarding Federal Tax Information (FTI). Applies to all agencies, contractors, and agents receiving FTI from the IRS.

Why You Need Database Auditing

9.3.3.2 Audit Events

Systems processing FTI MUST audit successful and unsuccessful system access attempts and account management events.

9.3.3.3 Content of Audit Records

Audit records MUST contain: type of event, when occurred, where occurred, source of event, outcome, and identity.

9.3.3.6 Audit Review and Reporting

Organization MUST review and analyze audit records weekly for unusual, unexpected, or suspicious activity.

9.3.3.9 Protection of Audit Information

Audit records containing FTI MUST be protected from unauthorized access and retained for 7 years.

DB Audit Accelerators

Policy Template

Federal Tax Information Monitoring

Track all access to databases containing FTI

Report

IRS 1075 Audit Report

7-year compliant audit trail with weekly review evidence

Classification

FTI Data Patterns

Detect SSN, EIN, and federal tax information

Alert

FTI Access Anomaly Detection

Alert on suspicious access patterns to tax data

CJIS United States Law Enforcement

FBI Criminal Justice Information Services Security Policy

Security policy for all entities accessing FBI Criminal Justice Information (CJI). Applies to law enforcement agencies, contractors, and any organization with CJI access.

Why You Need Database Auditing

5.4.1.1 Auditable Events

Systems MUST generate audit records for successful and unsuccessful access attempts to CJI.

5.4.1.2 Content of Audit Records

Audit records MUST contain date/time, component, type of event, user identity, and outcome.

5.4.3 Audit Monitoring and Review

Agency MUST implement procedures for monitoring and analyzing audit records to detect inappropriate activity.

5.4.6 Audit Record Retention

Audit records MUST be retained for a minimum of one year and available for review.

DB Audit Accelerators

Policy Template

CJI Access Monitoring

Track all access to Criminal Justice Information databases

Report

CJIS Audit Trail Report

Complete access history with success/failure status

Classification

CJI Data Patterns

Identify criminal history, warrants, and law enforcement data

Alert

Unauthorized CJI Access

Alert on access attempts outside authorized parameters

UK DPA United Kingdom All Industries

UK Data Protection Act 2018

UK implementation of data protection principles post-Brexit. Supplements UK GDPR and applies to all organizations processing personal data of UK residents.

Why You Need Database Auditing

Section 57 Logging Requirements

Controllers MUST keep logs of collection, alteration, consultation, disclosure, combination, or erasure of personal data.

Section 59 Data Protection by Design

Controllers MUST implement appropriate technical measures including access logging from the outset.

Section 66 Breach Notification

Personal data breaches MUST be reported to the ICO within 72 hours of becoming aware.

Section 107 Subject Access Rights

Organizations MUST provide individuals with access to their personal data and processing information.

DB Audit Accelerators

Policy Template

UK Citizen Data Monitoring

Track access to UK resident personal data to prevent insider snooping

Report

UK DPA Compliance Report

2-year retention compliant access log documentation

Classification

UK PII Patterns

Detect NI numbers, NHS numbers, and UK-specific identifiers

Alert

Insider Threat Detection

Alert on unusual internal access to citizen service data

SEC 17a-4 United States Securities / Broker-Dealers

SEC Rule 17a-4 - Records to be Preserved

SEC regulation requiring broker-dealers to preserve records in non-rewritable, non-erasable format (WORM). Critical for trading firms, investment advisors, and financial institutions.

Why You Need Database Auditing

17a-4(b)(4) Trade Records

Records of every trade and trade-related database modification MUST be preserved for at least 6 years.

17a-4(f) Electronic Storage

Electronic records MUST be preserved in WORM (Write Once Read Many) format with audit trail.

17a-4(f)(2)(ii) Verification

Broker-dealers MUST verify automatically the quality and accuracy of electronic storage.

17a-4(f)(3) Audit System

MUST maintain a separate audit system that accounts for input and preserves entries with timestamps.

DB Audit Accelerators

Policy Template

Trade Data Immutability

Monitor all modifications to trade and order databases

Report

SEC 17a-4 WORM Compliance

7-year immutable audit trail for regulatory examination

Classification

Trade Record Patterns

Identify orders, executions, and trade-related data

Alert

Record Modification Attempt

Alert on any attempt to modify preserved records

NAIC MDL-668 United States (State) Insurance

NAIC Insurance Data Security Model Law

Model law adopted by most US states requiring insurance companies to implement comprehensive information security programs with annual certification requirements.

Why You Need Database Auditing

Section 4D Risk Assessment

Licensees MUST design information security program to identify risks to nonpublic information and assess safeguards.

Section 4F Access Controls

REQUIRES implementation of access controls including monitoring of access to nonpublic information.

Section 6 Investigation

Licensees MUST conduct investigation of cybersecurity events and determine scope, affected individuals, and root cause.

Section 8 Annual Certification

Insurers MUST annually certify in writing that they maintain a compliant information security program.

DB Audit Accelerators

Policy Template

Insurance Data Monitoring

Track access to policyholder nonpublic information

Report

NAIC Annual Certification Report

DAM system evidence for annual certification filing

Classification

Insurance Data Patterns

Detect policy numbers, claims data, and beneficiary information

Alert

Cybersecurity Event Detection

Alert on events requiring investigation per Section 6

MiCA European Union Crypto / Web3 / Digital Assets

EU Markets in Crypto-Assets Regulation

EU regulation establishing uniform rules for crypto-asset service providers. Effective 2024, requires comprehensive audit trails for distributed ledger operations.

Why You Need Database Auditing

Article 68 Record Keeping

Crypto-asset service providers MUST keep records of all services, orders, and transactions for 5 years.

Article 76 Custody Safeguards

Custodians MUST maintain audit trails for wallet-custody databases with complete transaction history.

Article 78 Transfer Traceability

REQUIRES complete traceability of crypto-asset transfers including originator and beneficiary information.

Article 83 Operational Resilience

Providers MUST implement systems to ensure business continuity and access to transaction records.

DB Audit Accelerators

Policy Template

Crypto Transaction Monitoring

Track all distributed ledger entry points and wallet operations

Report

MiCA Compliance Report

5-year transaction history with complete audit trail

Classification

Crypto Asset Patterns

Identify wallet addresses, transaction hashes, and digital asset data

Alert

Suspicious Transaction Detection

Alert on unusual crypto-asset movements

DPDP Act India All Industries

India Digital Personal Data Protection Act 2023

India comprehensive data protection law governing processing of digital personal data. Applies to organizations processing data of individuals in India with penalties up to ₹250 crore.

Why You Need Database Auditing

Section 8(7) Security Safeguards

Data Fiduciaries MUST implement appropriate technical and organizational measures to protect personal data.

Section 8(6) Breach Notification

Personal data breaches MUST be reported to the Board and affected individuals without delay.

Section 11 Data Principal Rights

Organizations MUST provide data principals with access to their personal data and processing information.

Section 8(9) Retention Limitation

Personal data MUST be erased when purpose is achieved or upon data principal request. Logs retained for 180 days minimum.

DB Audit Accelerators

Policy Template

India Personal Data Monitoring

Track access to Aadhaar, PAN, and Indian personal data

Report

DPDP Compliance Report

180-day minimum retention with security safeguard evidence

Classification

Indian PII Patterns

Detect Aadhaar numbers, PAN, and Indian identifiers

Alert

Breach Detection for DPDP

Real-time detection for rapid breach notification

APPI Japan All Industries

Japan Act on Protection of Personal Information

Japan primary data protection law governing handling of personal information. Updated 2022 with stricter requirements for cross-border transfers and breach notification.

Why You Need Database Auditing

Article 23 Security Control

Business operators MUST take necessary and appropriate measures to prevent leakage, loss, or damage of personal data.

Article 26 Breach Notification

Significant data breaches MUST be reported to the PPC and affected individuals without delay.

Article 33 Disclosure Request

Business operators MUST disclose retained personal data to individuals upon request.

Article 28 Cross-Border Transfer

Transfer of personal data outside Japan REQUIRES consent or equivalent protection confirmation.

DB Audit Accelerators

Policy Template

Japan Personal Data Monitoring

Track access to My Number and Japanese personal data

Report

APPI Compliance Report

Security measure documentation for PPC assessment

Classification

Japanese PII Patterns

Detect My Number, Japanese names, and address formats

Alert

Cross-Border Transfer Detection

Alert when Japanese personal data accessed from outside Japan

Quebec Law 25 Quebec, Canada All Industries

Quebec Law 25 - An Act to Modernize Legislative Provisions Respecting Personal Information

Quebec comprehensive privacy law with strict requirements for logging personal information access. Fully effective September 2024 with significant penalties.

Why You Need Database Auditing

Section 3.1 Access Logging

Organizations MUST log every single instance a staff member accesses or shares customer personal information.

Section 3.3 Privacy Impact Assessment

REQUIRES Privacy Impact Assessment for any project involving personal information.

Section 3.5 Breach Notification

Confidentiality incidents MUST be reported to the CAI and affected individuals.

Section 8 Anonymization

Organizations MUST implement and audit anonymization techniques for personal information.

DB Audit Accelerators

Policy Template

Quebec PII Access Tracking

Log every instance of personal information access or sharing

Report

Law 25 PIA Evidence

Privacy Impact Assessment documentation with access logs

Classification

Quebec Resident Patterns

Identify Quebec-specific identifiers and resident data

Alert

PII Access Notification

Real-time logging of all personal information access

ISO 27701 Global All Industries

ISO/IEC 27701 Privacy Information Management System

International standard extending ISO 27001 to include privacy management. Provides framework for PII controllers and processors to demonstrate compliance with privacy regulations.

Why You Need Database Auditing

7.2.2 Purpose Limitation

PII controllers MUST ensure processing is limited to identified purposes with audit trail evidence.

7.2.6 Access Recording

Organizations MUST record access to PII including who accessed, when, and for what purpose.

8.2.2 Processor Obligations

PII processors MUST ensure personnel are bound by confidentiality and log all processing activities.

7.3.6 Breach Response

Organizations MUST have procedures to notify authorities and data subjects of PII breaches.

DB Audit Accelerators

Policy Template

PIMS Access Control

Track all access to PII with purpose limitation verification

Report

ISO 27701 Audit Evidence

Certification-ready documentation of privacy controls

Classification

PII Processing Patterns

Identify and categorize personal information processing

Alert

Purpose Limitation Violation

Alert when PII accessed outside identified purposes

SOCI Act Australia Critical Infrastructure

Australia Security of Critical Infrastructure Act 2018

Australian law protecting critical infrastructure assets. Requires mandatory incident reporting within 72 hours and comprehensive risk management programs.

Why You Need Database Auditing

Part 2A Critical Infrastructure Risk Management

Responsible entities MUST adopt and maintain a critical infrastructure risk management program.

Section 30BC Cyber Security Incidents

Critical cyber security incidents MUST be reported to the Australian Signals Directorate within 72 hours.

Part 3 System of Records

Entities MUST maintain records of access to critical infrastructure systems for forensic investigation.

Section 30BF Ransomware Reporting

Ransomware payments MUST be reported within 72 hours of making or becoming aware of the payment.

DB Audit Accelerators

Policy Template

Critical Infrastructure Monitoring

Comprehensive logging for Australian critical infrastructure databases

Report

SOCI Incident Report

72-hour compliant incident documentation for ASD reporting

Classification

Critical Asset Data

Identify data supporting critical infrastructure operations

Alert

Cyber Incident Detection

Real-time detection for 72-hour reporting compliance

BSIMM12 Global Software Development

Building Security In Maturity Model

Framework for measuring and improving software security practices. Measures activities across governance, intelligence, SSDL touchpoints, and deployment.

Why You Need Database Auditing

SE2.4 Code Repository Protection

Organizations MUST audit access to source code repositories and development databases.

SE3.2 Software Inventory

REQUIRES maintaining software inventory including binary and code provenance logs.

CMVM2.1 Configuration Monitoring

Organizations MUST track and monitor changes to development and deployment configurations.

SM2.2 Security Metrics

REQUIRES collecting and publishing security metrics including audit log analysis.

DB Audit Accelerators

Policy Template

DevSecOps Audit Policy

Monitor development lifecycle and source-code database access

Report

BSIMM Assessment Evidence

Binary and code provenance logs for security assessment

Classification

Development Data Patterns

Identify source code, build artifacts, and secrets

Alert

Unauthorized Code Access

Alert on access to code repositories outside authorized patterns

NERC CIP-007-6 North America Power / Utilities

NERC Critical Infrastructure Protection - Systems Security Management

NERC reliability standard requiring security management for Bulk Electric System (BES) Cyber Systems. Mandatory for all electric utilities in North America.

Why You Need Database Auditing

R4.1 Security Event Monitoring

Responsible entities MUST log events at BES Cyber System level including login attempts.

R4.2 Event Log Retention

Security event logs MUST be retained for at least 90 days and available for immediate review.

R4.3 Log Review

Responsible entities MUST review logs of BES Cyber Systems at least once every 15 days.

R5.6 Administrative Access

MUST log all administrative actions and configuration changes on BES databases.

DB Audit Accelerators

Policy Template

BES Cyber System Monitoring

Track all access and changes to bulk electric system databases

Report

NERC CIP Audit Report

Immutable 90-day logs with 15-day review evidence

Classification

BES Data Patterns

Identify SCADA, EMS, and grid control system data

Alert

BES Configuration Change

Alert on administrative actions to critical grid systems

TSA SD 1580/82 United States Rail / Transit

TSA Security Directives for Surface Transportation

TSA security directives requiring rail and transit operators to implement cybersecurity measures including 24/7 monitoring of critical systems.

Why You Need Database Auditing

SD 1580-21-01 Continuous Monitoring

Operators MUST implement 24/7 monitoring of signaling and interlocking databases for operational anomalies.

SD 1580-21-01 §4 Incident Reporting

Cybersecurity incidents MUST be reported to CISA within 24 hours of discovery.

SD 1582-21-01 Access Control

REQUIRES implementation of access controls for critical operational technology systems.

SD 1580-21-01 §3 Log Retention

Security logs MUST be retained for at least 1 year and available for TSA review.

DB Audit Accelerators

Policy Template

Rail OT System Monitoring

Monitor signaling, interlocking, and train control databases 24/7

Report

TSA SD Compliance Report

1-year log retention with immediate anomaly reporting

Classification

Rail System Data

Identify signaling, dispatch, and safety system data

Alert

OT Anomaly Detection

Real-time alerting for operational anomalies requiring 24hr reporting

IATA IOSA Global Aviation

IATA Operational Safety Audit (ISM v16)

International standard for airline operational safety management. Required for IATA membership and accepted by aviation authorities worldwide.

Why You Need Database Auditing

ORG 3.1.1 Safety Data Protection

Operators MUST implement measures to protect safety databases from unauthorized access or modification.

FLT 3.11.1 Flight Data Monitoring

REQUIRES audit trails for flight manifest, weight/balance, and operational databases.

MNT 1.10.3 Maintenance Records

Maintenance databases MUST have complete audit trails to reconstruct any safety-data change.

SEC 3.1.1 Security Management

Security-related data MUST be protected with access logging and monitoring.

DB Audit Accelerators

Policy Template

Aviation Safety Data Monitoring

Track access to flight, maintenance, and safety databases

Report

IOSA Audit Evidence

Safety data reconstruction capability for IOSA audits

Classification

Aviation Data Patterns

Identify flight manifests, MEL, and airworthiness data

Alert

Safety Data Modification

Alert on changes to safety-critical aviation data

IMO MSC.428(98) Global Maritime

IMO Maritime Cyber Risk Management

International Maritime Organization resolution requiring cyber risk management in safety management systems. Applies to all ships subject to ISM Code.

Why You Need Database Auditing

Resolution §2 Cyber Risk Management

Maritime operators MUST address cyber risks in their Safety Management Systems.

ISM Code 12.1 SMS Audit

Safety Management System including cyber controls MUST be verified annually by auditors.

Resolution §4 Bridge System Logging

REQUIRES logging of bridge navigation, ballast control, and engine room data access.

Resolution §5 Incident Response

Organizations MUST have procedures for responding to and recovering from cyber incidents.

DB Audit Accelerators

Policy Template

Maritime OT Monitoring

Log access to navigation, ECDIS, and vessel control databases

Report

IMO Cyber Compliance Report

Annual SMS verification evidence for cyber controls

Classification

Maritime System Data

Identify AIS, ECDIS, and vessel operational data

Alert

Bridge System Access Alert

Alert on unauthorized access to navigation systems

CER Directive European Union Water / Waste / Energy

EU Critical Entities Resilience Directive

EU directive requiring critical infrastructure operators to implement resilience measures. Covers water, waste management, energy, and digital infrastructure sectors.

Why You Need Database Auditing

Article 12 Risk Assessment

Critical entities MUST carry out risk assessments including cyber threats to operational systems.

Article 13 Resilience Measures

Entities MUST implement measures to ensure resilience including access control and logging.

Article 15 Incident Notification

Significant incidents MUST be notified to competent authorities within 24 hours.

Article 14 Background Checks

Critical roles MUST be subject to background verification with access logging.

DB Audit Accelerators

Policy Template

Critical Entity Monitoring

Audit access to SCADA and chemical treatment databases

Report

CER Resilience Report

Risk-based forensic-ready log documentation

Classification

Utility System Data

Identify SCADA, water treatment, and waste management data

Alert

Critical System Access Alert

24-hour incident notification capability

SPD-5 United States Space / Satellite

US Space Policy Directive 5 - Cybersecurity Principles for Space Systems

US policy establishing cybersecurity principles for space systems. Requires Zero-Trust architecture and comprehensive logging for ground and space operations.

Why You Need Database Auditing

Principle 1 Zero Trust Architecture

Space systems MUST implement Zero-Trust logging for all ground and space operations.

Principle 3 Command and Control Security

REQUIRES traceability of command-and-control (C2) database telemetry and access.

Principle 4 Ground System Protection

Ground segment operations MUST implement comprehensive access logging and monitoring.

Principle 5 Incident Response

Operators MUST maintain incident response capabilities with forensic-ready logging.

DB Audit Accelerators

Policy Template

Space Ground Ops Monitoring

Zero-Trust logging for satellite command and control

Report

SPD-5 Compliance Report

Traceability evidence for C2 operations

Classification

Space System Data

Identify telemetry, C2 commands, and orbital data

Alert

C2 Access Alert

Alert on command and control database access

ECC-1:2018 Saudi Arabia Government / Critical Infrastructure

Saudi Arabia Essential Cybersecurity Controls (NCA)

Saudi National Cybersecurity Authority mandatory controls for government entities and critical infrastructure. Requires protected logs for all national infrastructure.

Why You Need Database Auditing

3-1-1 Event Logging

Organizations MUST enable and protect logs for systems processing sensitive information.

3-1-2 Log Protection

Audit logs MUST be protected from unauthorized access, modification, and deletion.

3-1-3 Log Review

Organizations MUST regularly review logs and generate reports on security events.

3-1-4 Time Synchronization

All systems MUST be synchronized to authoritative time sources for accurate logging.

DB Audit Accelerators

Policy Template

NCA Logging Policy

Mandatory protected logs for national infrastructure databases

Report

ECC-1 Compliance Report

Tamper-proof centralized log documentation for NCA

Classification

Sensitive Data Patterns

Identify Saudi government and infrastructure data

Alert

Security Event Notification

Per NCA guidelines alert and review capability

EU AI Act European Union / Global AI Systems / All Industries

EU Artificial Intelligence Act

EU regulation establishing harmonized rules for AI systems. Requires immutable "Black Box" logging for high-risk AI with complete traceability of inputs, outputs, and agentic actions.

Why You Need Database Auditing

Article 12 Record-Keeping

High-risk AI systems MUST automatically log inputs, outputs, and agentic actions with immutable audit trails.

Article 13 Transparency

REQUIRES traceability enabling human understanding of AI system decision-making.

Article 14 Human Oversight

Systems MUST enable human monitoring and intervention with complete audit trails.

Article 17 Quality Management

Providers MUST implement quality management with documented procedures and logging.

DB Audit Accelerators

Policy Template

AI Black Box Logging

Immutable logging of all AI inputs, outputs, and agentic actions

Report

EU AI Act Compliance Report

Complete traceability documentation for high-risk AI

Classification

AI Training Data

Identify model inputs, training data, and inference logs

Alert

AI Drift Detection

Alert on anomalous AI behavior requiring investigation

ISO/IEC 42001 Global AI Systems

ISO/IEC 42001 Artificial Intelligence Management System

International standard for AI management systems. Provides framework for responsible AI development with continuous monitoring of model-data interactions.

Why You Need Database Auditing

6.1.4 AI Risk Assessment

Organizations MUST assess AI system risks including bias, drift, and data quality issues.

8.4 AI System Monitoring

REQUIRES continuous monitoring of AI model performance and data interactions.

9.1 Performance Evaluation

Organizations MUST monitor, measure, analyze, and evaluate AI system performance.

10.1 Nonconformity Management

AI failures MUST be documented, investigated, and corrected with audit trail.

DB Audit Accelerators

Policy Template

AIMS Monitoring Policy

Continuous monitoring of AI model-data interactions

Report

ISO 42001 Audit Evidence

Documented bias and drift audits for certification

Classification

AI System Data

Identify model parameters, training data, and outputs

Alert

Model Drift Alert

Alert on AI performance degradation or bias detection

DSA European Union Digital Platforms / Social Media

EU Digital Services Act

EU regulation establishing obligations for digital platforms including audit trails for content moderation and algorithmic transparency.

Why You Need Database Auditing

Article 15 Transparency Reporting

Platforms MUST report on content moderation activities with supporting audit data.

Article 27 Recommender System Transparency

REQUIRES audit trails for algorithm training data and recommendation decisions.

Article 37 Data Access

Very large platforms MUST provide vetted researchers access to data with usage logging.

Article 40 Audit Requirements

Annual independent audits MUST verify platform compliance including audit log integrity.

DB Audit Accelerators

Policy Template

Platform Content Monitoring

Track content moderation and algorithm training data access

Report

DSA Transparency Report

Annual compliance evidence for independent audits

Classification

Platform Data Patterns

Identify content decisions, algorithm inputs, and user data

Alert

Algorithm Change Alert

Alert on modifications to recommendation systems

SOC 2 + AI Global AI Service Providers

SOC 2 Trust Services Criteria for AI Systems

Extended SOC 2 framework addressing AI-specific risks. Covers model governance, data provenance, and algorithmic accountability for AI service providers.

Why You Need Database Auditing

CC7.2 AI AI System Monitoring

Entity MUST monitor AI system components for anomalies including model performance and data drift.

CC6.7 AI AI Input Validation

REQUIRES validation and logging of all AI system inputs to prevent adversarial attacks.

CC8.1 AI Model Change Management

AI model updates MUST be authorized, tested, and documented with complete audit trails.

PI1.4 AI AI Output Integrity

Entity MUST implement controls to ensure AI output integrity and detect manipulation.

DB Audit Accelerators

Policy Template

AI Trust Services Monitoring

SOC 2 controls extended for AI system components

Report

SOC 2 + AI Evidence Package

AI-specific trust service criteria documentation

Classification

AI Service Data

Identify model endpoints, training pipelines, and outputs

Alert

AI Anomaly Detection

AI-powered detection of unusual AI system behavior

ISA/IEC 62443 Global Manufacturing / Industrial

ISA/IEC 62443 Industrial Automation and Control Systems Security

International standard series for industrial automation security. Covers security lifecycle for industrial control systems and Industry 4.0 environments.

Why You Need Database Auditing

SR 2.8 Auditable Events

Control systems MUST generate audit records for security-relevant events.

SR 2.9 Audit Storage Capacity

REQUIRES sufficient storage and protection for audit logs from PLCs and SCADA systems.

SR 2.10 Response to Audit Failures

Systems MUST alert upon audit processing failure and protect audit integrity.

SR 6.1 Audit Log Accessibility

Authorized personnel MUST be able to access and review audit logs.

DB Audit Accelerators

Policy Template

ICS/SCADA Monitoring

Audit PLCs and SCADA databases in automated factories

Report

IEC 62443 Compliance Report

Real-time OT security log documentation

Classification

Industrial Data Patterns

Identify PLC programming, HMI data, and process control

Alert

ICS Security Event

Alert on unauthorized access to industrial control systems

IACS UR E26/E27 Global Maritime Industrial / Mining

IACS Unified Requirements for Cyber Resilience

International Association of Classification Societies requirements for cyber security of ships and offshore units. Applies to computer-based systems in heavy equipment and maritime operations.

Why You Need Database Auditing

E26 §5.1 Security Event Logging

Computer-based systems MUST log security-relevant events for forensic investigation.

E27 §4.3 Access Control

REQUIRES implementation of access controls with audit logging for OT systems.

E26 §5.3 Log Integrity

Log integrity MUST be verified by classification society surveyor during inspections.

E27 §5.1 Incident Response

Organizations MUST have incident response procedures with forensic evidence preservation.

DB Audit Accelerators

Policy Template

Maritime Industrial Monitoring

Log access to vessel and offshore unit control systems

Report

IACS Survey Evidence

Log integrity documentation for class surveyor verification

Classification

Maritime OT Data

Identify DP systems, cargo handling, and industrial control data

Alert

OT System Access Alert

Alert on unauthorized access to maritime industrial systems

UN R155 Global Automotive

UN Regulation 155 - Cyber Security and Cyber Security Management System

UN regulation requiring cybersecurity management systems for vehicle manufacturers. Mandatory for type approval in UNECE countries including EU, UK, Japan, and Korea.

Why You Need Database Auditing

7.2.2.2(g) Forensic Capability

Manufacturers MUST have capability to analyze attempted or successful cyber attacks with data collection.

7.2.2.2(h) Logging Requirements

REQUIRES audit logs for Over-the-Air (OTA) update databases and vehicle telemetry.

7.2.2.5 Incident Response

Organizations MUST detect and respond to cyber attacks with evidence preservation.

Annex 5 Part C Data Retention

Forensic data MUST be retained for 10 years to support post-incident analysis.

DB Audit Accelerators

Policy Template

Automotive CSMS Monitoring

Track OTA updates, telematics, and vehicle diagnostic data

Report

UN R155 Compliance Report

10-year forensic retention for type approval

Classification

Automotive Data Patterns

Identify VIN, ECU data, and vehicle telemetry

Alert

Vehicle Cyber Attack Detection

Alert on attempted or successful vehicle cyber attacks

Bill C-27 CPPA Canada All Industries / Agriculture

Canada Consumer Privacy Protection Act (Digital Charter)

Proposed Canadian federal privacy law replacing PIPEDA. Includes specific requirements for traceability of farm-to-table data and supply chain personal information.

Why You Need Database Auditing

Section 57 Security Safeguards

Organizations MUST implement appropriate physical, organizational, and technological security safeguards.

Section 72 Breach Records

REQUIRES maintaining records of every breach of security safeguards involving personal information.

Section 63 Access Rights

Individuals MUST be able to request and receive their personal information and processing details.

Section 59 Traceability

Organizations MUST be able to reconstruct the journey of personal data from ingestion to deletion.

DB Audit Accelerators

Policy Template

Canadian Data Traceability

Track farm-to-table and supply chain PII with automated consent logging

Report

CPPA Compliance Report

Breach record and data journey documentation

Classification

Canadian Industry Patterns

Identify agricultural, supply chain, and consumer data

Alert

Data Journey Alert

Track personal data across processing stages

HMS OHIP Canada Healthcare Billing

Health Management System Billing (OHIP/Alberta)

Canadian provincial requirements for health management system billing auditing. Requires correlation of billing codes with clinical access records to prevent fraud.

Why You Need Database Auditing

PHIPA Section 12 Audit Trail

Organizations MUST maintain audit logs of access to personal health information.

HIA Section 60 Billing Verification

REQUIRES auditing of billing codes versus clinical access records for fraud prevention.

PHIPA Section 10 Access Controls

Organizations MUST implement technical safeguards to protect health information.

Billing Audit Requirements Correlation Analysis

Systems MUST enable correlation of billing submissions with clinical record access patterns.

DB Audit Accelerators

Policy Template

Healthcare Billing Audit

Correlate billing codes with clinical database access

Report

HMS Billing Audit Report

10-year audit window for billing fraud detection

Classification

Canadian Healthcare Patterns

Identify OHIP, Alberta Health, and provincial billing codes

Alert

Billing Anomaly Detection

Alert on billing patterns inconsistent with access records

FERPA United States Education

Family Educational Rights and Privacy Act

US federal law protecting the privacy of student education records. Applies to all schools receiving federal funding and requires comprehensive access logging.

Why You Need Database Auditing

34 CFR 99.32 Record of Disclosures

Educational agencies MUST maintain records of each disclosure of personally identifiable information.

34 CFR 99.31 Consent Requirements

REQUIRES prior written consent for disclosure with exceptions requiring disclosure logging.

34 CFR 99.10 Right to Inspect

Parents and eligible students MUST be able to inspect and review education records.

34 CFR 99.35 Record Maintenance

Disclosure records MUST be maintained for the life of the education record.

DB Audit Accelerators

Policy Template

Student Record Monitoring

Track all access to student education databases

Report

FERPA Disclosure Log

Lifetime disclosure records for education records

Classification

Student Data Patterns

Identify student IDs, grades, disciplinary records, and PII

Alert

Unauthorized Student Data Access

Alert on access outside FERPA authorized purposes

Dubai ISR v2 United Arab Emirates Government / Real Estate / Services

Dubai Information Security Regulation Version 2

Dubai mandatory information security requirements for government and service entities. Requires detailed CRUD logging for property registry and citizen service databases.

Why You Need Database Auditing

ISR-AO-02 Access Control

Organizations MUST implement access control with detailed logging of all access events.

ISR-SM-04 Security Monitoring

REQUIRES detailed CRUD (Create/Read/Update/Delete) logs for sensitive government data.

ISR-IM-01 Incident Management

Security incidents MUST be logged, investigated, and reported to relevant authorities.

ISR-AO-04 Audit Trail

Tamper-proof logs MUST be stored centrally and protected from modification.

DB Audit Accelerators

Policy Template

Dubai Government Data Monitoring

Detailed CRUD logs for property registry and citizen services

Report

ISR v2 Compliance Report

Tamper-proof centralized log documentation

Classification

UAE Data Patterns

Identify Emirates ID, property records, and government data

Alert

Sensitive Data Access Alert

Alert on access to government and citizen data

NIS2 (Logistics) European Union Logistics / Supply Chain

NIS2 Directive Article 21 - Supply Chain Security

NIS2 requirements specifically for logistics and supply chain operators. Requires data integrity auditing and proof of business continuity.

Why You Need Database Auditing

Article 21(2)(d) Supply Chain Security

Entities MUST address security risks in supplier relationships with auditing of logistics databases.

Article 21(2)(c) Business Continuity

REQUIRES proof of business continuity logs and data integrity verification.

Article 21(2)(e) Acquisition Security

Security in network and information system acquisition MUST be documented and audited.

Article 23 Incident Reporting

Supply chain incidents MUST be reported within 24 hours with supporting audit data.

DB Audit Accelerators

Policy Template

Supply Chain Data Integrity

Audit logistics and routing database modifications

Report

NIS2 Supply Chain Report

Business continuity and data integrity evidence

Classification

Logistics Data Patterns

Identify shipment, routing, and supply chain data

Alert

Supply Chain Incident Alert

24-hour notification capability for supply chain incidents

GDPR (Gaming) European Union / Global Gaming / Entertainment

GDPR Article 32 - Gaming Industry Application

GDPR requirements as applied to gaming industry including user account data protection and micro-transaction integrity. 5-year retention for financial data.

Why You Need Database Auditing

Article 32 Security of Processing

Gaming operators MUST implement secure logging of user account data and payment information.

Article 17 Right to Erasure

REQUIRES ability to erase player data while maintaining financial audit trails.

Article 25 Data Protection by Design

Game systems MUST be designed with privacy controls and access logging from inception.

Article 33 Breach Notification

Data breaches affecting player data MUST be reported within 72 hours.

DB Audit Accelerators

Policy Template

Gaming User Data Monitoring

Track player account and micro-transaction database access

Report

Gaming GDPR Compliance

5-year financial integrity retention with user audit trails

Classification

Gaming Data Patterns

Identify player IDs, payment data, and in-game transactions

Alert

Gaming Data Breach Detection

72-hour breach notification for player data

One platform, all frameworks

DB Audit provides the foundation for compliance across every regulation.

Comprehensive Audit Logging

Every query, access event, and modification is captured with full context: who, what, when, where, and outcome.

Real-Time Threat Detection

AI-powered anomaly detection identifies suspicious activity within milliseconds, enabling rapid incident response.

Automatic Data Classification

Automatically identify and classify PII, PHI, PCI data, and more. Know exactly where your sensitive data lives.

Pre-Built Policy Templates

Start monitoring in minutes with regulation-specific policy templates. No need to build from scratch.

Audit-Ready Reports

Generate compliance evidence reports with one click. Formatted for auditors and ready for regulatory review.

SIEM Integration

Forward security events to Splunk, Sentinel, QRadar, and more. Unified monitoring across your security stack.

Ready to simplify compliance?

Start your free trial and see how DB Audit accelerates your path to compliance.