PM-12 Insider Threat Program. Implement an insider threat program that includes a cross-discipline insider threat incident handling team
Insider Threat Program. Implement an insider threat program that includes a cross-discipline insider threat incident handling team.
5
artefacts
0
held by a system
2
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
- Records of cases handled, with the disciplines actually engaged in each · Document repository
- Evidence of the legal and privacy safeguards governing what the programme may collect and access · Data governance / DLP tooling
governing documentDocuments that govern the control
- The insider threat programme charter, its scope and its authority · Policy repository / GRC workspace
- Membership of the cross discipline incident handling team, showing security, legal, human resources and management representation · Document repository
- Procedures for referral, triage and handling of a potential insider concern · 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
- Team exists on paper as a security function only, with no human resources or legal participation
- No referral route from managers and colleagues, so the programme sees only what monitoring tools surface
- Data collection safeguards undefined, exposing the programme itself as a privacy risk
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 sheetPM-11 Mission and Business Process Definition. Define organizational mission and business processes with consideration for information security and privacy and the resulting risk to organizational operations, organizational assets, individuals, other organizations, and the Nation; and · PM-13 Security and Privacy Workforce. Establish a security and privacy workforce development and improvement program