2.2.3 Primary functions isolated or secured to highest level
Primary functions requiring different security levels are managed so that only one primary function exists per component, or different security levels are isolated, or all are secured to the highest level.
5
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
- Container or VM isolation evidence · Document repository
- Configuration review · Cloud console / configuration management
governing documentDocuments that govern the control
- System role inventory · Policy repository / GRC workspace
- Architecture diagram showing function separation · Policy repository / GRC workspace
- Approved exceptions with controls · Document repository
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
- Mixed roles on single host
- No isolation between dev and prod functions
- No documented rationale
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 sheet2.2.2 Vendor default accounts are managed as follows: • If the vendor default account(s) will be used, the default password is changed per Requirement 8.3.6. • If the vendor default account(s) will not be used, · 2.2.4 Only necessary services enabled