EvidenceSheet

5.6 Contact with special interest groups

Requires ongoing contact to be maintained with special interest groups, with forums that specialise in security and with professional bodies, giving the organisation a route to current expertise and early warning of deve

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

none for this control

periodic reviewEvidence produced at each review

  • Membership records, subscriptions or attendance evidence for the period · HR system / LMS
  • Records of information received through these channels and what was done with it, such as advisories fed into vulnerability management · Vulnerability scanner / patch tooling
  • Evidence that participation is assigned to a role rather than to an individual's personal interest · Identity provider / directory
  • Any confidentiality assessment governing what the organisation shares in those forums · Policy repository / GRC workspace

governing documentDocuments that govern the control

  • The list of special interest groups, security forums and professional bodies the organisation participates in · Policy repository / GRC workspace

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

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

5.5 Contact with authorities · 5.7 Threat intelligence