Threat Identification
What is Threat Identification?
The process of recognizing and documenting potential threats that could exploit vulnerabilities and adversely affect organizational assets.
Terms that appear alongside threat identification
Each of these is named in at least one of the same controls as threat identification. The number is how many controls name both.
- vulnerability 2 shared controls
- risk assessment 2 shared controls
- cybersecurity 2 shared controls
Frameworks that govern threat identification
What the standards actually require on threat identification
Requirements naming threat identification across 3 standards, quoted from the control text.
The vendor must establish processes to identify threats to the software, assess associated risks, and mitigate or accept those risks through documented decisions.
SSLC-4.1 · Threat Identification and Risk Mitigation →FSSC 22000 v6 Additional Requirements - FSSC-specific scheme additions beyond ISO 22000 + ISO/TS 22002-x (publicly available + downloadable from fssc.com).
FSSC-Additional-Requirements-v6 · FSSC 22000 Additional Requirements v6 (Food Defense + Food Fraud + Allergen + Environmental + Culture) →Identify is the first of five functional elements per MSC-FAL.1/Circ.3/Rev.2 (aligned with NIST CSF Identify). Activities include: (1) Asset Inventory of vulnerable systems organisationally + onboard ship - Operational Technology (OT) systems including Bridge...
IMO-MSC-FAL-Identify-AssetInventory-ThreatsVulnerabilities-CyberRiskAssessment-RolesResponsibilities · IMO MSC-FAL Identify Function - OT/IT Asset Inventory + Threats + Vulnerabilities + Cyber Risk Assessment + Roles and Responsibilities + Crew + CSO + DPA →Questions people ask about threat identification
What is Threat Identification?
Why is Threat Identification important for compliance?
Which compliance frameworks address Threat Identification?
Where can I learn more about Threat Identification?
See how Threat Identification applies across compliance frameworks
Our platform maps 686 frameworks with 311K cross-framework control mappings. Explore how this concept is addressed across standards.