Azure Security Benchmark
Logging and Threat Detection

Azure Security Benchmark ASBv3-LT-2: Enable threat detection for identity and access management

Detect identity and access threats by monitoring user and application sign-in and access anomalies, alerting on patterns such as excessive failed logins and deprecated accounts.

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

What else in your programme already covers this

This control maps to 44 controls across 21 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 · 5 controls

  • AC-17(1) Monitoring and Control
  • AC-2(12) Account Monitoring for Atypical Usage
  • AC-7 Unsuccessful Logon Attempts
  • AU-6 Audit Record Review, Analysis, and Reporting
  • SI-4 System Monitoring

FedRAMP Moderate · 5 controls

  • AC-17(1) Monitoring and Control
  • AC-2(12) Account Monitoring for Atypical Usage
  • AC-7 Unsuccessful Logon Attempts
  • AU-6 Audit Record Review, Analysis, and Reporting
  • SI-4 System Monitoring

PCI DSS 4.0 · 4 controls

  • 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
  • 8.2.6 8.2.6 Inactive accounts removed within 90 days
  • 8.3.4 8.3.4 Lockout after 10 attempts for 30 minutes

CIS Controls v8 · 3 controls

  • CIS-13.1 Centralize Security Event Alerting
  • CIS-5.3 Disable Dormant Accounts
  • CIS-8.5 Collect Detailed Audit Logs

CMMC 2.0 · 3 controls

NIST SP 800-171 Rev 3 · 3 controls

NIST SP 800-53 Rev 5 · 3 controls

C5 (Germany) · 2 controls

  • C5-IDM-03 Locking and withdrawal of user accounts in the event of inactivity or multiple failed logins
  • C5-OPS-15 Logging and Monitoring - Accountability

ISO 27002:2022 · 2 controls

  • 5.16 Identity management
  • 8.16 Monitoring activities
  • E8-MFA-ML3 Multi-Factor Authentication - Maturity Level 3

APPI · 1 control

  • SEC02-BP05 Audit and rotate credentials periodically

HIPAA Security Rule · 1 control

ISO 27001:2022 · 1 control

  • 8.16 Monitoring activities
  • NIST-CSF-DE.CM-03 Personnel activity and technology usage are monitored to find potentially adverse events

NIST SP 800-172 · 1 control

  • 3.14.2e Monitor Organizational Systems with Specialized Capabilities

SOC 2 · 1 control

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

UK Cyber Essentials · 1 control

  • CE-SC.8 Process for Compromised Passwords

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 Logging and Threat Detection

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

Azure Security Benchmark ASBv3-LT-2 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.

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 44 it maps to, and the evidence behind each claim, over MCP and REST.