6.11.1 Security requirements of information systems
Security requirements analysis and specification and the protection of application services transactions apply as the base guidance requires, and personal data transmitted over untrusted networks, including the public in
4
artefacts
0
held by a system
2
at each review
hard
to go live
Document repository
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 encryption for personal data crossing untrusted networks · Data governance / DLP tooling
- Transaction protection evidence for application services · Document repository
governing documentDocuments that govern the control
- Requirements specifications covering privacy for new and changed systems · Policy repository / GRC workspace
- Definition of which networks the organization treats as untrusted · 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
- Untrusted defined as the public internet only, leaving partner and third party links unencrypted
- Encryption terminated at a load balancer with the internal hop left in clear
- Requirements captured for security and silent on privacy obligations
- Legacy interfaces exempted indefinitely
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 sheet6.10.2 Information transfer · 6.11.2 Security in development and support processes