What this policy is
Defines how the organization consumes external threat intelligence (commercial feeds, ISACs, government advisories) and converts it into detection and prevention actions.
Why every organization needs one
Generic security controls miss threats targeted at a specific industry or technology stack. Threat intel is what makes detection adaptive.
What a competent Threat Intelligence Policy typically contains
- Purpose and scope
- Roles and responsibilities
- Definitions
- Subscribed-source inventory
- Intel-to-detection workflow
- Intel-to-vulnerability-prioritisation workflow
- Sharing obligations (ISAC, customer disclosure)
- Review cadence (typically annual) and version control
- Approval, sign-off and effective date
How iCompaas tracks this policy
The icompaas policy-doc producer manages this document through an 8-state lifecycle: draft → generated → internal_qa → customer_review → in_review → approved → signed (with rejected as a terminal side-state). The producer publishes a policy_doc_threat_intelligence_policy_signed compliance finding once at least one document of this kind reaches the signed state for the account being assessed; the finding then rolls up into every compliance framework that references this policy (see the table below).
Compliance frameworks that reference this policy
The icompaas compliance controls library links every policy document to the controls in each framework that require, evidence, or otherwise rely on it. Below: every control across every framework in the iCompaas catalogue that names this policy as part of its evidence base. Each control links to its own dedicated page with auditor-view content + implementation guidance.
| Framework | Control | Title | Component |
|---|---|---|---|
| ISO/IEC 27001:2022 | A.5.6 | Contact with special interest groups | Organizational controls |
| ISO/IEC 27001:2022 | A.5.7 | Threat intelligence | Organizational controls |
| ISO/IEC 27701:2025 | A.3.28 | Application security requirements | Security considerations |
3 controls across 2 frameworks reference this policy.
About this page
This article is part of the iCompaas Policy Documents library — one page per signed-document type the icompaas policy-doc producer tracks for customer accounts. The article is intentionally framework-agnostic: a customer signing a policy of this kind gets the same regulatory benefit across every framework that references it.