1.1.1 NSC policies and procedures documented
All security policies and operational procedures for Requirement 1 are documented, kept current, in use, and known to affected parties.
5
artefacts
1
held by a system
2
at each review
hard
to go live
HR system / LMS
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Network security control policy document with version history · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Annual review attestation signed by control owner · Vendor register / contract repository
- Distribution list and acknowledgement records · HR system / LMS
governing documentDocuments that govern the control
- Procedures for firewall and router management · Policy repository / GRC workspace
- Training material referencing the policy · HR system / LMS
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Cloud console / configuration management on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Policies older than 12 months
- No evidence of distribution
- Procedures missing operational detail
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 sheet