IM-5 Use single sign-on (SSO) for application access
Use single sign-on so users authenticate once to reach applications and data across cloud and on-premises environments rather than maintaining separate credentials per application.
4
artefacts
0
held by a system
0
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Application inventory showing which are integrated with single sign-on · Policy repository / GRC workspace
- Onboarding standard requiring single sign-on for new applications · HR system / LMS
- Exception register for applications that cannot integrate · Policy repository / GRC workspace
- Count of standalone application credentials remaining · Policy repository / GRC workspace
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- single sign-on adopted for new applications only, legacy left standalone
- exceptions granted permanently
- shared local accounts persisting alongside single sign-on
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-4 Authenticate server and services · IM-6 Use strong authentication controls