RA-10 Threat Hunting
Hunts for adversary activity introduced through the supply chain rather than waiting for an alert.
3
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
- Hunt records and findings · Document repository
governing documentDocuments that govern the control
- Hunt plans including supply chain hypotheses · Policy repository / GRC workspace
- Use of supplier and component intelligence in hunts · Vendor register / contract repository
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 focuses on perimeter intrusion only
- supplier compromise indicators never hunted for
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