Skip to main content

💼 11.5.2 A change-detection mechanism (for example, file integrity monitoring tools) is deployed.

  • ID: /frameworks/pci-dss-v4.0.1/11/05/02

Description​

As follows:

  • To alert personnel to unauthorized modification (including changes, additions, and deletions) of critical files.
  • To perform critical file comparisons at least once weekly.

Similar​

  • Sections
    • /frameworks/pci-dss-v4.0/11/05/02
    • /frameworks/aws-fsbp-v1.0.0/rds/20
    • /frameworks/aws-fsbp-v1.0.0/rds/21
    • /frameworks/aws-fsbp-v1.0.0/rds/22

Similar Sections (Take Policies From)​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [RDS.20] Existing RDS event notification subscriptions should be configured for critical database instance events1no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [RDS.21] An RDS event notifications subscription should be configured for critical database parameter group events1no data
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [RDS.22] An RDS event notifications subscription should be configured for critical database security group events1no data
💼 PCI DSS v4.0 → 💼 11.5.2 A change-detection mechanism (for example, file integrity monitoring tools) is deployed.4no data

Similar Sections (Give Policies To)​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 PCI DSS v4.0 → 💼 11.5.2 A change-detection mechanism (for example, file integrity monitoring tools) is deployed.4no data

Sub Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance

Policies (4)​

PolicyLogic CountFlagsCompliance
🛡️ AWS Account Config is not enabled in all regions🟢1🟢 x6no data
🛡️ AWS RDS Instance Event Subscription for critical events is not configured🟢1🟢 x6no data
🛡️ AWS RDS Parameter Group Event Subscription for critical events is not configured🟢1🟢 x6no data
🛡️ AWS RDS Security Group Event Subscription for critical events is not configured🟢1🟢 x6no data