Azure Security Benchmark IM-4: Authenticate server and services

What else in your programme already covers this

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

CMMC 2.0 · 4 controls

IA.L2-3.5.1 Identification
IA.L2-3.5.2 Authentication
IA.L2-3.5.4 Replay-Resistant Authentication
SC.L2-3.13.15 Communications Authenticity

FedRAMP High · 3 controls

IA-3 Device Identification and Authentication
IA-5(2) Public Key-Based Authentication
SC-23 Session Authenticity

FedRAMP Moderate · 3 controls

IA-3 Device Identification and Authentication
IA-5(2) Public Key-Based Authentication
SC-23 Session Authenticity

NIST SP 800-53 Rev 5 · 3 controls

NIST800-IA-3 IA-3 Device Identification and Authentication
NIST800-IA-9 IA-9 Service Identification and Authentication
NIST800-SC-23 SC-23 Session Authenticity

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

CCM-DCS-08 Equipment Identification
CCM-IAM-14 Strong Authentication

ISO 27002:2022 · 2 controls

8.24 Use of cryptography
8.5 Secure authentication

NIST Cybersecurity Framework 2.0 · 2 controls

NIST-CSF-PR.AA-02 Identities are proofed and bound to credentials based on the context of interactions
NIST-CSF-PR.AA-03 Users, services, and hardware are authenticated

NIST SP 800-161 Rev 1 · 2 controls

161R1-IA-3 Device Identification and Authentication
161R1-IA-9 Service Identification and Authentication

NIST SP 800-171 Rev 3 · 2 controls

03.05.02 Device Identification and Authentication
03.13.15 Session Authenticity

NIST SP 800-172 · 2 controls

3.5.1e Identification of Systems, Components, and Devices
3.5.3e Prohibit Connection of Unknown or Unverified System Components

AWS Well-Architected Security Pillar · 1 control

SEC09-BP03 Authenticate network communications

C5 (Germany) · 1 control

C5-PSS-05 Authentication Mechanisms

HIPAA Security Rule · 1 control

164.312(d) Person or Entity Authentication (Standard)

NIST SP 800-66 Rev 2 · 1 control

164.312(d) Person or Entity Authentication (Standard)

SOC 2 · 1 control

SOC2-CC6.7 CC6.7 Restricting and protecting information in transmission, movement and removal

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