RA-10 Threat Hunting
Hunts for adversary activity introduced through the supply chain rather than waiting for an alert.
Source: NIST SP 800-161 Rev 1 (supply chain), RA-10. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open NIST SP 800-161 Rev 1 (supply chain) in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
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
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