RA-10 Threat hunting
Requires a cyber threat hunting capability to be established and maintained to search for indicators of compromise and to detect, track and disrupt threats that have evaded existing controls, and requires that capability
4
artefacts
0
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
none for this control
periodic reviewEvidence produced at each review
- Evidence hunts are informed by current threat intelligence · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Documented threat hunting capability including scope, tooling and data sources · Policy repository / GRC workspace
- Hunt plans and completed hunt reports at the defined frequency · Policy repository / GRC workspace
- Findings and the disruption or remediation actions they produced · 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
- Hunting equated with reviewing alerts already generated by existing tools
- Capability exists on paper but no hunts have been performed at the stated frequency
- Hunt findings never fed back into detection rules
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 sheetRA-9 Criticality analysis · SA-1 Policy and procedures for system and services acquisition