Skip to content

Threat Detection

What is Threat Detection?

The process and technology used to identify malicious activity, policy violations, and other security threats within an organization's environment.

Information Security

Each of these is named in at least one of the same controls as threat detection. The number is how many controls name both.

What the standards actually require on threat detection

Requirements naming threat detection across 6 standards, quoted from the control text.

Define and implement a logging, threat detection and incident response strategy so threats are detected and remediated rapidly and compliance requirements for logging are met.

ASBv3-GS-7 · Define and implement logging, threat detection and incident response strategy →

Deploy runtime threat detection that monitors process activity, file changes, and network behavior inside containers. Tune detections to the workload baseline and integrate alerts with the SOC.

SP800-190-3.17 · Runtime Threat Detection →

Article 32 establishes the ADVANCED CYBERSECURITY CONTROLS that critical-impact entities must implement IN ADDITION TO the Article 30 minimum controls.

NCCS-Art.32_33_34 · Advanced cybersecurity controls (NCCS Articles 32-34) - for critical-impact entities →
HKMA TM-G-11 control

HKMA TM-G-1 Cyber + Audit + Outsourcing + Cloud. (1) SECURITY MONITORING AND SIEM (TM-G-1.7.1) - SIEM + SOC + 24x7 monitoring + log management + correlation + use cases + alert handling + escalation + UEBA + behavior analytics + SOAR automation + threat detect...

HKMA-TMG1-Cyber-Monitoring-Threat-Intel-IR-Audit-Outsource-Cloud · TM-G-1 Security Monitoring + SIEM + Threat Intel + Cyber IR + Audit + Outsourcing + Cloud Computing Risk →

HL7 FHIR Audit + Provenance + Digital Signatures. AUDITEVENT LOGGING (FHIR-SEC-07 + FHIR-SEC-4.1) - FHIR AuditEvent Resource for structured audit logging + IETF RFC 3881 + IHE ATNA + DICOM Audit + comprehensive audit trail of: (a) authentication events;

HL7-FHIR-Audit-Provenance-DigitalSignatures-Integrity · HL7 FHIR Audit + Provenance + Digital Signatures + AuditEvent Resource + Audit Log Integrity + Retention →

Questions people ask about threat detection

What is Threat Detection?
The process and technology used to identify malicious activity, policy violations, and other security threats within an organization's environment.
Why is Threat Detection important for compliance?
Threat Detection is a key concept in Information Security. Understanding threat detection helps organizations meet regulatory requirements, reduce risk, and demonstrate due diligence during audits. Our compliance platform maps 1,016 frameworks with 316K cross-framework control mappings.
Which compliance frameworks address Threat Detection?
Threat Detection appears in the requirement text of Azure Security Benchmark, NIST SP 800-190, DORA RTS on ICT Risk Management Framework (Commission Delegated Regulation (EU) 2024/1774), EU Network Code on Cybersecurity for the Electricity Sector, HKMA TM-G-1. Across these standards we have identified 9 controls that name it directly, each linked to the control text on the compliance platform.
Where can I learn more about Threat Detection?
Explore our compliance framework pages to see how threat detection applies across different standards and regulations. Our implementation guides provide step-by-step guidance, and the compliance platform offers AI-powered analysis of how this concept maps across 1,016 frameworks.

See how Threat Detection applies across compliance frameworks

Our platform maps 1,016 frameworks with 316K cross-framework control mappings. Explore how this concept is addressed across standards.

Written and maintained by Gerard Blokdyk, The Art of Service.