Home / How to audit ISO 27001 / ISO 27001 Annex A 5.7 Audit Checklist

ISO 27001 Annex A 5.7 Audit Checklist

Stuart And Fay High Table

In this ultimate how to audit guide to ISO 27001 Annex A 5.7 Threat Intelligence, you will learn directly from an ISO 27001 Lead Auditor:

  • 10 Key Audit Steps
  • Verification Criteria
  • Required Evidence
  • The Pass / Fail Test

I am Stuart Barker, the ISO 27001 Lead Auditor and author of the Ultimate ISO 27001 Toolkit.

Using over 30 years of industry experience across hundreds of audits, I’m giving you the exact templates, walkthroughs, and practical examples you need to achieve ISO 27001 certification.

Auditing ISO 27001 Annex A 5.7 Threat Intelligence validates the systematic collection and analysis of data regarding potential security attacks. This process confirms the Primary Implementation Requirement of contextualizing threat data to inform risk decisions and defensive actions. The Business Benefit empowers proactive defense strategies, reducing incident impact by anticipating adversary tactics rather than just reacting to them.

1. Threat Intelligence Process Formalisation Verified

Verification Criteria: A documented process or procedure exists that defines how threat intelligence is collected, processed, and disseminated across the organisation.

Required Evidence: Approved Threat Intelligence Policy or Standard Operating Procedure (SOP) detailing the intelligence lifecycle.

Pass/Fail Test: If the organisation cannot produce a documented methodology for handling threat data, mark as Non-Compliant.

2. Identification of Diverse Intelligence Sources Confirmed

Verification Criteria: The organisation has identified and formalised both internal and external sources of threat data, encompassing tactical, operational, and strategic levels.

Required Evidence: A register of intelligence sources, including subscription records to ISACs, commercial feeds, or government alerts (e.g., NCSC).

Pass/Fail Test: If the organisation relies solely on a single, generic news feed without technical or sector-specific sources, mark as Non-Compliant.

3. Tactical Intelligence Implementation (IoCs) Validated

Verification Criteria: Evidence exists that Indicators of Compromise (IoCs) such as malicious IPs, file hashes, and URLs are actively ingested and used for detection.

Required Evidence: Configuration logs from SIEM, EDR, or Firewall showing the automated or manual ingestion of threat feeds.

Pass/Fail Test: If IoCs are collected but not actively applied to blocking or monitoring tools, mark as Non-Compliant.

High Table Fay and Stuart 3
Shopping Basket
Scroll to Top