Azure Security Benchmark LT-4: Enable network logging for security investigation

What else in your programme already covers this

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

CIS Controls v8 · 3 controls

CIS-13.6 Collect Network Traffic Flow Logs
CIS-8.6 Collect DNS Query Audit Logs
CIS-8.7 Collect URL Request Audit Logs

FedRAMP High · 3 controls

AU-2 Event Logging
SI-4(18) System Monitoring | Analyze Traffic and Covert Exfiltration (SI-4(18))
SI-4(4) Inbound and Outbound Communications Traffic

FedRAMP Moderate · 3 controls

AU-2 Event Logging
SI-4(18) System Monitoring | Analyze Traffic and Covert Exfiltration (SI-4(18))
SI-4(4) Inbound and Outbound Communications Traffic

CMMC 2.0 · 2 controls

SC.L2-3.13.1 Boundary Protection
SI.L2-3.14.6 Monitor Communications for Attacks

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

CCM-IVS-08 Network Architecture Documentation
CCM-LOG-07 Logging Scope

ISO 27701:2019 · 2 controls

7.4.9 PII transmission controls
8.4.3 PII transmission controls

NIST SP 800-171 Rev 3 · 2 controls

03.03.01 Event Logging
03.13.01 Boundary Protection

NIST SP 800-53 Rev 5 · 2 controls

NIST800-AU-12 AU-12 Audit Record Generation
NIST800-AU-2 AU-2 Event Logging

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

ANSSI-HYG-22 Put in Place a Secure Internet Access Gateway

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

C5 (Germany) · 1 control

C5-COS-03 Monitoring of connections in the Cloud Service Provider's network

HIPAA Security Rule · 1 control

164.312(b) Audit Controls (Standard)

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-DE.CM-01 Networks and network services are monitored to find potentially adverse events

NIST SP 800-161 Rev 1 · 1 control

161R1-SI-4 System Monitoring

NIST SP 800-66 Rev 2 · 1 control

164.312(b) Audit Controls (Standard)

SOC 2 · 1 control

SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary

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-4 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