IM-3 Manage application identities securely and automatically
Use managed identities, service principals, or federated credentials for application authentication instead of stored secrets.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), IM-3. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark) in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Service principal credential rotation log · Identity provider / directory
- Workload identity federation configuration · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Managed identity inventory · Policy repository / GRC workspace
First move
Common gaps auditors find
- Service principal secrets unrotated
- Credentials in code repositories
- Over-permissioned managed identities
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetIM-2 Protect identity and authentication systems · IM-4 Authenticate server and services