EvidenceSheet

CC6.6 Measures against threats outside system boundaries are implemented

Implements logical access security measures to protect against threats from sources outside its system boundaries.

5
artefacts
2
held by a system
2
at each review
moderate
to go live
Identity provider / directory
where the evidence lives
teal = a system already holds it · olive = produced at each review

system holds itEvidence a system already holds

  • Configuration of boundary protections, such as firewalls, intrusion prevention, denial of service protection and web application firewalls · Identity provider / directory
  • Evidence of monitoring for and response to external attack attempts · Identity provider / directory

periodic reviewEvidence produced at each review

  • Evidence of controls over remote access, including multi factor authentication and restriction of the routes available · Identity provider / directory
  • Evidence of encryption or other protection of credentials and data crossing the boundary · Identity provider / directory

governing documentDocuments that govern the control

  • Identification of the system boundaries and of the points at which external access is possible · Policy repository / GRC workspace

First move

Start with the 2 of 5 artefacts that already live in a system (Identity provider / directory); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

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

CC6.5 Discontinues logical and physical protections over physical assets only after the ability to read or recover data and software from those assets has been diminished and is no longer required to meet the entity's · CC6.7 Transmission of data is restricted to authorized users