Azure Security Benchmark LT-3: Enable logging for security investigation

What else in your programme already covers this

This control maps to 62 controls across 26 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 · 7 controls

AC-2(4) Automated Audit Actions
AC-6(9) Log Use of Privileged Functions
AU-11 Audit Record Retention
AU-12 Audit Record Generation
AU-2 Event Logging
AU-3 Content of Audit Records
CM-5(1) Access Restrictions for Change | Automated Access Enforcement and Audit Records (CM-5(1))

FedRAMP Moderate · 7 controls

AC-2(4) Automated Audit Actions
AC-6(9) Log Use of Privileged Functions
AU-11 Audit Record Retention
AU-12 Audit Record Generation
AU-2 Event Logging
AU-3 Content of Audit Records
CM-5(1) Access Restrictions for Change | Automated Access Enforcement and Audit Records (CM-5(1))

CIS Controls v8 · 5 controls

CIS-3.14 Log Sensitive Data Access
CIS-8.10 Retain Audit Logs
CIS-8.12 Collect Service Provider Logs
CIS-8.2 Collect Audit Logs
CIS-8.5 Collect Detailed Audit Logs

PCI DSS 4.0 · 5 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.2 10.2.2 Required details recorded for each auditable event
5.3.4 5.3.4 Anti-malware audit logs enabled and retained

NIST SP 800-171 Rev 3 · 4 controls

03.01.07 Least Privilege - Privileged Functions
03.03.01 Event Logging
03.03.02 Audit Record Content
03.03.03 Audit Record Generation

NIST SP 800-53 Rev 5 · 4 controls

NIST800-AU-11 AU-11 Audit Record Retention
NIST800-AU-12 AU-12 Audit Record Generation
NIST800-AU-2 AU-2 Event Logging
NIST800-AU-3 AU-3 Content of Audit Records

ACSC Essential Eight · 3 controls

E8-ADMIN-ML2 Restrict Administrative Privileges (ML2)
E8-APP-ML2 Application Control (ML2)
E8-UAH-ML3 User Application Hardening - Maturity Level 3

CMMC 2.0 · 3 controls

AC.L2-3.1.7 Privileged Functions
AU.L2-3.3.1 System Auditing
AU.L2-3.3.2 User Accountability

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 3 controls

CCM-LOG-07 Logging Scope
CCM-LOG-08 Log Records
CCM-LOG-11 Transaction/Activity Logging

NIST Cybersecurity Framework 2.0 · 3 controls

NIST-CSF-DE.CM-01 Networks and network services 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-07 Incident data and metadata are collected, and their integrity and provenance are preserved

C5 (Germany) · 2 controls

C5-OPS-10 Logging and Monitoring - Concept
C5-PSS-04 Error handling and Logging Mechanisms

NIST SP 800-161 Rev 1 · 2 controls

161R1-AU-12 Audit Record Generation
161R1-AU-2 Event Logging

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

ANSSI-HYG-36 Enable and Configure Logging on the Most Important Components

APEC Cross-Border Privacy Rules (CBPR) System · 1 control

CBPR-PR-30 Specific proportional safeguards in place

APPI · 1 control

APPI-A23 Security Control Measures

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

ASD37-33 Capture network traffic (Limited)

AWS Well-Architected Security Pillar · 1 control

SEC04-BP01 Configure service and application logging

Australia Consumer Data Right - Banking (CDR) · 1 control

AUCDR-IS-1 Limit risk of unauthorised access to the CDR data environment

Australia My Health Records Act 2012 · 1 control

MYHR-SEC-3 Audit logging and access monitoring

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

CFTC-SS-3 Information Security Category

HIPAA Security Rule · 1 control

164.312(b) Audit Controls (Standard)

NIST SP 800-66 Rev 2 · 1 control

164.312(b) Audit Controls (Standard)

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.

You are reading one control. How much of Azure Security Benchmark have you already done?

Azure Security Benchmark LT-3 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Azure Security Benchmark your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 71 of 85 Azure Security Benchmark controls already carry evidence.

If you hold NIST SP 800-53 Rev 583.5% covered · 14 gaps If you hold FedRAMP Moderate78.8% covered · 18 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.172.9% covered · 23 gaps If you hold ISO 27002:202269.4% covered · 26 gaps If you hold C5 (Germany)65.9% covered · 29 gaps If you hold ISO 27001:202261.2% covered · 33 gaps

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.

See the released pairs, $299 each Browse the graph free