EvidenceSheet

SC-40 Wireless Link Protection. Protect external and internal [organization-defined] from the following signal parameter attacks: [organization-defined]

Wireless Link Protection. Protect external and internal [organization-defined] from the following signal parameter attacks: [organization-defined].

5
artefacts
1
held by a system
1
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

  • Configuration and design evidence of the protections applied to each link · Cloud console / configuration management

periodic reviewEvidence produced at each review

  • Test or measurement records confirming the protection performs as intended · Document repository

governing documentDocuments that govern the control

  • Identification of the external and internal wireless links in scope · Policy repository / GRC workspace
  • The defined signal parameter attacks the links are protected from, such as jamming, direction finding or exploitation of signal characteristics · Document repository
  • Wireless network diagrams showing which links carry the protection · 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

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

SC-39 Process isolation · SC-41 Port and I/O Device Access. [organization-defined] disable or remove [organization-defined] on the following systems or system components: [organization-defined]