IM-4 Authenticate server and services
Use strong authentication methods including mutual TLS, certificates, and federated trust for server-to-server communication.
3
artefacts
1
held by a system
0
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- MTLS configuration · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Certificate inventory and expiry tracking · Policy repository / GRC workspace
- Server authentication design documentation · Policy repository / GRC workspace
First move
Start with the 1 of 3 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Self-signed certificates in production
- Expiry not monitored
- Anonymous service-to-service calls
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-3 Manage application identities securely and automatically · IM-5 Use single sign-on (SSO) for application access