Threat Monitoring (ARC-003-R007) - ARC-003

Requirement Details & Guidance

ARC-003-R007 · ARC-003

Why This Requirement Exists

This requirement exists to keep threat information current and identify emerging threats using intelligence and ongoing monitoring and to ensure security architecture decisions are consistent, risk-informed, and traceable.

Implementation Guidance

Establish a documented process for keep threat information current and identify emerging threats using intelligence and ongoing monitoring. Define accountable roles, required inputs and outputs, approval or validation points, criteria, review frequency, exception handling, monitoring, and evidence requirements. Integrate the activity with architecture governance, risk management, security requirements, engineering, and change processes as applicable. Retain records sufficient to demonstrate that the control operates.

Practical Application & Audit Readiness

ARC-003-R007 · Field Guidance

Business Examples

Common Audit Findings

Common Mistakes

Best Practices & Ownership

ARC-003 · Recommended Approach

Recommended Practices

Typical Owner

Cross-Mapped Regulatory Frameworks

Harmonized Control Mappings

FRAMEWORK CODE	FRAMEWORK NAME & DETAILS	FAMILY / CATEGORY	VERSION	ACTION
ISO27001	ISO/IEC 27001 ISO/IEC 27001 specifies auditable requirements for... Clause: 9.1 – Monitoring, measurement, analysis and evaluation	ISO Standard	v2022	View →
IRDAI	IRDAI Information & Cyber Security Guidelines IRDAI information and cyber-security requirements... Clause: §2.18-3.1 – Identification of Potential Threats; §2.18-3.2 – Threat Intelligence Process; §2.5-3.2.2 – Technology risk assessment Process	India Guideline	vLatest	View →
RBI-CSF	RBI Cyber Security Framework / Master Directions RBI cyber-security requirements and directions set... Clause: 6) Application Security Life Cycle (ASLC) – 6.6 Threat modelling, secure coding, security testing and secure rollout; Circular §5 – Identification/assessment of inherent cyber risks and controls	India Regulation	vLatest	View →
SEBI-CSCRF	SEBI Cyber Security & Cyber Resilience Framework SEBI’s Cybersecurity and Cyber Resilience Framewor... Clause: 2.2 ID.RA: Risk Assessment	India Regulation	vLatest	View →
DORA	Digital Operational Resilience Act The EU Digital Operational Resilience Act establis... Clause: Article 8(2) – Continuous identification of ICT risk sources, cyber threats and ICT vulnerabilities Article 6(8)(d) – ICT reference architecture and changes needed for business objectives	EU Regulation	vCurrent	View →
ISO27002	ISO/IEC 27002 ISO/IEC 27002 is a guidance standard containing a... Clause: 5.7 – Threat intelligence	ISO Standard	v2022	View →
NIS2	NIS2 Directive The NIS2 Directive establishes EU-wide cybersecuri... Clause: Article 21(2)(a) – Policies on risk analysis and information system security	EU Directive	vCurrent	View →
PCI-DSS	PCI DSS PCI DSS is an industry security standard maintaine... Clause: 6.2.4 – Software engineering techniques or other; 11.4.1 – A penetration testing methodology is defined,	PCI Standard	v4	View →
NIST-CSF	NIST Cybersecurity Framework (CSF) The NIST Cybersecurity Framework provides high-lev... Clause: PR.IR – Technology Infrastructure Resilience \| PR.IR-01 – Networks and environments are protected from unauthorized logical access and usage ID.AM – Asset Management \| ID.AM-08 – Systems, hardware, software, services, and data are managed throughout their life cycles GV.OC – Organizational Context \| GV.OC-04 – Critical objectives, capabilities, and services that external stakeholders depend on or expect from the organization are understood and communicated	NIST Framework	v2	View →
NIST80053	NIST SP 800-53 NIST SP 800-53 Rev. 5 presents control families, i... Clause: 3.16 – RISK ASSESSMENT; RA-3 – RISK ASSESSMENT, RA-10 – THREAT HUNTING	NIST Control Catalog	vRev. 5	View →
SOC2	SOC 2 Trust Services Criteria SOC 2 is an independent examination and reporting... Clause: CC3.2 – Risk Assessment – COSO Principle 7: The entity identifies risks to the achievement of its objectives across the entity and analyzes risks as a basis for determining how the risks should be managed. CC6.6 – Logical and Physical Access Controls – The entity implements logical access security measures to protect against threats from sources outside its system boundaries. CC7.2 – System Operations – The entity monitors system components and the operation of those components for anomalies that are indicative of malicious acts, natural disasters, and errors affecting the entity's ability to meet its objectives; anomalies are analyzed to determine whether they represent security events.	AICPA Audit Framework	vLatest	View →

Parent Domain Context

Governance Domain Baseline

Domain Name:

Security Architecture (ARC)

Purpose:

To design secure systems and ensure security is built into the architecture.

Scope:

Enterprise

View

Parent Control Context

Control Baseline

Control Name:

Threat Modeling (ARC-003)

Summary:

Establishes threat modeling including threat identification, attack surface analysis, risk assessment, mitigation planning, validation, monitoring, reporting, review, and continuous improvement.

Business Description:

Establish and maintain threat modeling processes to identify, assess, prioritize, and mitigate security threats during the design of systems, applications, infrastructure, APIs, and cloud services.

View