PA-6 Use privileged access workstations
Provide secured, isolated workstations for sensitive roles such as administrators, developers and critical service operators, so administrative sessions do not originate from general-purpose endpoints.
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
- Privileged access workstation build standard · Policy repository / GRC workspace
- List of roles required to use them and the enforcement mechanism · Policy repository / GRC workspace
- Conditional access or network policy restricting administration to those devices · Policy repository / GRC workspace
- Compliance reporting on workstation state · 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
- administration performed from the same laptop used for mail and browsing
- workstation standard defined but not enforced at sign-in
- contractors administering from unmanaged devices
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 sheetPA-5 Set up emergency access · PA-7 Follow just enough administration (least privilege) principle