WithPCI Logo
WithPCI.com

10.3 Audit logs are protected from destruction and unauthorized modifications.

This requirement focuses on ensuring that audit logs are properly protected from unauthorized access, modification, and destruction. Proper protection of audit logs is essential for maintaining their integrity and usefulness in detecting and investigating security incidents.

Sub-requirements

10.3. Audit logs capture all required elements and are protected.

Ensure audit logs include all necessary information, are synchronized for accurate timestamps, and are protected against unauthorized modification.

https://WithPCI.com
4
Sub-requirements
4
Test Points
Moderate (3.0)
Implementation Difficulty

Control Types

Technical
Technical: 4

Key Risks

Incomplete log details
Unsynchronized timestamps
Log tampering

Frequently Asked Questions

What elements must be included in audit logs?

User ID, event type, date/time, success/failure, origin, and affected data/system.

Why is time synchronization important for logs?

It ensures logs from different systems can be correlated accurately during investigations.

How are logs protected from modification?

By using immutable storage, access controls, and regular monitoring.

How often should logs be backed up?

Promptly and regularly, to a secure, centralized location.

What are the risks of incomplete or unprotected logs?

Inability to investigate incidents, undetected tampering, and compliance failures.

Common QSA Questions

Can you show evidence of log synchronization and protection?

Yes, we use NTP for time sync and store logs on secure, access-controlled servers.

How do you ensure all required log elements are captured?

We configure log settings according to PCI DSS and review log samples regularly.

How are audit logs backed up and retained?

We use automated log forwarding and retention policies to ensure logs are available for at least 12 months.

Your perspective on this PCI DSS requirement matters! Share your implementation experiences, challenges, or questions below. Your insights help other organizations improve their compliance journey and build a stronger security community.Comment Policy