SEC10-BP05 Pre-provision access
Pre-provision the access incident responders need, using temporary credentials and prepared elevation paths so investigation is not delayed by access requests during an event.
4
artefacts
0
held by a system
2
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
- Evidence that responder access uses temporary rather than long-lived credentials · Identity provider / directory
- Access test records confirming responders can reach the needed accounts · Identity provider / directory
governing documentDocuments that govern the control
- Responder role definitions and their permission sets · Policy repository / GRC workspace
- Pre-provisioned break-glass access procedure and approval path · 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
- root account used for incident response
- permissions edited by hand during an incident
- responder access never tested so gaps surface mid-incident
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 sheetSEC10-BP04 Develop and test security incident response playbooks · SEC10-BP06 Pre-deploy tools