Azure Security Benchmark ASBv3-IM-8: Restrict the exposure of credential and secrets

What else in your programme already covers this

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

PCI DSS 4.0 · 4 controls

6.2.4 6.2.4 Engineering techniques against common software attacks
8.3.2 8.3.2 Authentication factors unreadable with strong cryptography
8.6.2 8.6.2 No hard-coded passwords for interactive system accounts
8.6.3 8.6.3 System account passwords protected against misuse

C5 (Germany) · 3 controls

C5-CRY-04 Secure key management
C5-IDM-08 Confidentiality of authentication information
C5-PSS-07 Confidentiality of Authentication Information

FedRAMP High · 3 controls

IA-5 Authenticator Management
IA-5(6) Protection of Authenticators
IA-5(7) Authenticator Management | No Embedded Unencrypted Static Authenticators (IA-5(7))

FedRAMP Moderate · 3 controls

IA-5 Authenticator Management
IA-5(6) Protection of Authenticators
IA-5(7) Authenticator Management | No Embedded Unencrypted Static Authenticators (IA-5(7))

AWS Well-Architected Security Pillar · 2 controls

SEC02-BP03 Store and use secrets securely
SEC11-BP07 Regularly assess security properties of the pipelines

ISO 27001:2022 · 2 controls

5.17 Authentication information
8.28 Secure coding

ISO 27002:2022 · 2 controls

5.17 Authentication information
8.28 Secure coding

NIST SP 800-171 Rev 3 · 2 controls

03.05.07 Password Management
03.05.12 Authenticator Management

ACSC Essential Eight · 1 control

E8-ADMIN-ML2 Restrict Administrative Privileges (ML2)

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

ANSSI-HYG-11 Protect Passwords Stored on Systems

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

ASD37-23 Protect authentication credentials (Excellent)

CIS Controls v8 · 1 control

CIS-16.12 Implement Code-Level Security Checks

CMMC 2.0 · 1 control

IA.L2-3.5.10 Cryptographically-Protected Passwords

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

CCM-IAM-15 Passwords Management

HIPAA Security Rule · 1 control

164.308(a)(5)(ii)(D) Password Management (Addressable)

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization

NIST SP 800-161 Rev 1 · 1 control

161R1-IA-5 Authenticator Management

NIST SP 800-218 · 1 control

SP800-218-PW.5.1 Secure Coding Practices

NIST SP 800-53 Rev 5 · 1 control

NIST800-IA-5 IA-5 Authenticator Management

NIST SP 800-66 Rev 2 · 1 control

164.308(a)(5)(ii)(D) Password Management (Addressable)

SOC 2 · 1 control

SOC2-CC6.1 CC6.1 Logical access security over protected information assets

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