AWS Well-Architected Security Pillar
Detection

AWS Well-Architected Security Pillar SEC04-BP01: Configure service and application logging

Enable CloudTrail across all accounts and regions, VPC Flow Logs, application logs and service-specific logs, centralised to a dedicated log archive account.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 85 controls across 22 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

FedRAMP High · 9 controls

  • AC-17(1) Monitoring and Control
  • AC-2(4) Automated Audit Actions
  • AC-6(9) Log Use of Privileged Functions
  • AU-12 Audit Record Generation
  • AU-2 Event Logging
  • AU-3 Content of Audit Records
  • AU-9 Protection of Audit Information
  • SI-4 System Monitoring
  • SI-4(4) Inbound and Outbound Communications Traffic

FedRAMP Moderate · 9 controls

  • AC-17(1) Monitoring and Control
  • AC-2(4) Automated Audit Actions
  • AC-6(9) Log Use of Privileged Functions
  • AU-12 Audit Record Generation
  • AU-2 Event Logging
  • AU-3 Content of Audit Records
  • AU-9 Protection of Audit Information
  • SI-4 System Monitoring
  • SI-4(4) Inbound and Outbound Communications Traffic

CIS Controls v8 · 8 controls

  • CIS-12.5 Centralize Network Authentication, Authorization, and Auditing (AAA)
  • CIS-13.6 Collect Network Traffic Flow Logs
  • CIS-3.14 Log Sensitive Data Access
  • CIS-8.1 Establish and Maintain an Audit Log Management Process
  • CIS-8.12 Collect Service Provider Logs
  • CIS-8.2 Collect Audit Logs
  • CIS-8.5 Collect Detailed Audit Logs
  • CIS-8.6 Collect DNS Query Audit Logs

PCI DSS 4.0 · 7 controls

  • 10.2.1 10.2.1 Audit logging enabled on all system components
  • 10.2.1.1 10.2.1.1 Logs capture individual user access to cardholder data
  • 10.2.1.2 10.2.1.2 Logs capture all administrative actions
  • 10.2.1.4 10.2.1.4 Logs capture invalid logical access attempts
  • 10.2.1.5 10.2.1.5 Logs capture changes to identification and authentication credentials
  • 10.2.1.6 10.2.1.6 Logs capture initialization and stopping of audit logs
  • 10.2.2 10.2.2 Required details recorded for each auditable event

C5 (Germany) · 6 controls

  • C5-IDM-06 Privileged access rights
  • C5-OPS-10 Logging and Monitoring - Concept
  • C5-OPS-13 Logging and Monitoring - Identification of Events
  • C5-OPS-14 Logging and Monitoring - Storage of the Logging Data
  • C5-OPS-15 Logging and Monitoring - Accountability
  • C5-OPS-16 Logging and Monitoring - Configuration

CMMC 2.0 · 5 controls

NIST SP 800-171 Rev 3 · 5 controls

ACSC Essential Eight · 4 controls

  • E8-ADMIN-ML2 Restrict Administrative Privileges (ML2)
  • E8-APP-ML2 Application Control (ML2)
  • E8-MFA-ML3 Multi-Factor Authentication - Maturity Level 3
  • E8-UAH-ML3 User Application Hardening - Maturity Level 3
  • ASBv3-DS-7 Enable logging and monitoring in DevOps
  • ASBv3-IR-4 Detection and analysis - investigate an incident
  • LT-3 Enable logging for security investigation
  • LT-4 Enable network logging for security investigation
  • NIST-CSF-DE.CM-01 Networks and network services are monitored to find potentially adverse events
  • NIST-CSF-DE.CM-03 Personnel activity and technology usage are monitored to find potentially adverse events
  • NIST-CSF-PR.PS-04 Log records are generated and made available for continuous monitoring
  • NIST-CSF-RS.AN-06 Actions performed during an investigation are recorded, and the records' integrity and provenance are preserved

NIST SP 800-53 Rev 5 · 4 controls

NIST SP 800-161 Rev 1 · 3 controls

HIPAA Security Rule · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

  • ANSSI-HYG-36 Enable and Configure Logging on the Most Important Components
  • ASD37-33 Capture network traffic (Limited)
  • AUCDR-IS-1 Limit risk of unauthorised access to the CDR data environment

ISO 27001:2022 · 1 control

ISO 27002:2022 · 1 control

ISO 27701:2019 · 1 control

  • 6.9.4 Logging and monitoring

SOC 2 · 1 control

  • SOC2-CC7.2 CC7.2 Monitoring system components for anomalies

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Detection

You are reading one control. How much of AWS Well-Architected Security Pillar have you already done?

AWS Well-Architected Security Pillar SEC04-BP01 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of AWS Well-Architected Security Pillar your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 52 of 63 AWS Well-Architected Security Pillar controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

The graph holds this control, the 85 it maps to, and the evidence behind each claim, over MCP and REST.