03.11.02E — Threat Hunting | Bare Metal Cyber

Official NIST requirement content

Security requirement

a.Establish and maintain a cyber threat-hunting capability to:
1. a-1.Search for indicators of compromise in organizational systems and
2. a-2.Detect, track, and disrupt threats that evade existing safeguards.
b.Employ the threat-hunting capability [Organization-defined: frequency].

Official NIST discussion

Discussion

Threat hunting is an active means of cyber defense in contrast to traditional protection measures, such as firewalls, intrusion detection and prevention systems, quarantining malicious code in sandboxes, and Security Information and Event Management (SIEM) technologies and systems. Cyber threat hunting involves proactively searching organizational systems, networks, and infrastructure for advanced threats. The objective is to track and disrupt adversaries as early as possible in the attack sequence and to measurably improve the speed and accuracy of responses. Indications of compromise include unusual network traffic, unusual file changes, and the presence of malicious code. Threat-hunting teams leverage existing threat intelligence and may create new threat intelligence that is shared with peer organizations, Information Sharing and Analysis Organizations (ISAO), Information Sharing and Analysis Centers (ISAC), and relevant government departments and agencies. This requirement does not enhance a specific requirement in SP 800-171 but can be used to strengthen the protection of CUI associated with critical programs or high value assets.

Official organization-defined parameters

Tailoring decisions required

Resolve these values through the governing organization’s approved tailoring and risk-management process before declaring the requirement implemented.

frequencyorganization-defined frequencythe frequency at which to implement the threat-hunting capability is defined.

Official protection strategy classifications

Protection strategies supported

These classifications are carried from the official SP 800-172 OSCAL record and help explain the enhanced requirement’s defensive purpose.

PS-DLODamage-Limiting Operations

Bare Metal Cyber interpretation

Implementation perspective

Treat Threat Hunting as an enhanced CUI protection outcome for elevated threat conditions that must be reflected in the system boundary, documented implementation, operational behavior, and assessment evidence. Pay particular attention to threat, vulnerability, likelihood, impact, criticality, and risk-response decisions for the CUI environment.

Confirm the federal agency selected this enhanced requirement for the critical program or high-value asset and identify the CUI system components, services, users, and external connections in scope.
Resolve every organization-defined parameter through an approved governance and tailoring process.
Map each clause of the requirement to an accountable owner, implementation mechanism, and evidence source.
Verify that inherited and shared implementations are supported by current provider evidence and responsibility boundaries.
Collect evidence during normal operation and review changes, exceptions, and deficiencies on a risk-based cadence.

Questions to ask

Which critical-program or high-value-asset CUI, data flows, users, and services are protected by this enhanced requirement?
Which portions are implemented locally, inherited, shared, or not applicable, and what evidence supports that determination?
Do the system security plan, deployed configuration, operating process, and assessment evidence tell the same story?
What change, incident, or threshold should trigger reassessment?

Evidence and validation

risk assessments and threat models
vulnerability findings and prioritization records
supply-chain risk assessments
risk response and acceptance decisions

Common failure patterns

risk registers detached from technical evidence
vulnerability severity treated as business impact
assessments not updated after material change
accepted risks without owners or expiration

Official NIST SP 800-172A content

Assessment objectives and methods

Assessment objectives (5)

a.1.
a cyber threat-hunting capability is established to search for indicators of compromise in organizational systems.
a.1.
a cyber threat-hunting capability is maintained to search for indicators of compromise in organizational systems.
a.2.
a cyber threat-hunting capability is established to detect, track, and disrupt threats that evade existing safeguards.
a.2.
a cyber threat-hunting capability is maintained to detect, track, and disrupt threats that evade existing safeguards.
b.
the threat-hunting capability is employed [Organization-defined: frequency].

Examine

Risk assessment policy
assessment reports
audit records and/or event logs
threat-hunting capability
system security plan
other relevant documents or records

Interview

Personnel with threat-hunting responsibilities
system/network administrators
personnel with information security responsibilities

Test

Processes for assessments and audits
mechanisms or tools supporting and/or implementing threat-hunting capabilities

Official source-control relationships

Source NIST SP 800-53 controls

These controls are referenced by the official SP 800-172 Rev. 3 OSCAL record. Open the corresponding control pages for complete control text, enhancements, D3FEND mappings, and related learning.

Source controlRA-10Open SP 800-53 control →

Source record

Authoritative sources

Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by NIST. The official publications, the responsible federal agency, and the governing contract or agreement determine applicability, tailoring, assessment depth, and required implementation.