PR.DS-02 The confidentiality, integrity, and availability of data-in-transit are protected
The confidentiality, integrity, and availability of data-in-transit are protected. Control from NIST Cybersecurity Framework 2.0 framework, domain: PR - Protect.
5
artefacts
1
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
- Email transport encryption configuration · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- TLS configuration standards and scan results · Policy repository / GRC workspace
- VPN and zero trust network access policy · Policy repository / GRC workspace
- API security policy with mutual authentication · Policy repository / GRC workspace
- Network traffic encryption audit · Policy repository / GRC workspace
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
- Weak ciphers still permitted for legacy clients
- Internal traffic unencrypted
- API mutual authentication absent
- Email encryption opportunistic only
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 sheetPR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected · PR.DS-10 The confidentiality, integrity, and availability of data-in-use are protected