SC-22 Architecture and provisioning for name/address resolution service
Requires the set of systems that together provide name resolution for the organization to be fault tolerant and to implement separation between internal and external resolution roles.
4
artefacts
0
held by a system
3
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 of internal and external role separation in the resolution design · Identity provider / directory
- Failover test results for name resolution services · Backup / DR tooling
- Diversity evidence such as separate networks or providers · Document repository
governing documentDocuments that govern the control
- Architecture documentation showing redundant name resolution servers · 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
- Two servers presented as redundant while sharing one host, network or provider
- Internal and external resolution served by the same instances
- Failover never tested, so redundancy is assumed rather than proven
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 sheetSC-21 Secure name/address resolution service (recursive) · SC-23 Session authenticity