Design Review (ARC-004-R002) - ARC-004

Requirement Details & Guidance

ARC-004-R002 · ARC-004

Why This Requirement Exists

This requirement exists to evaluate security requirements, controls, and design vulnerabilities before implementation and to ensure security architecture decisions are consistent, risk-informed, and traceable.

Implementation Guidance

Establish a documented process for evaluate security requirements, controls, and design vulnerabilities before implementation. 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-004-R002 · Field Guidance

Business Examples

Common Audit Findings

Common Mistakes

Best Practices & Ownership

ARC-004 · Recommended Approach

Recommended Practices

Typical Owner

Cross-Mapped Regulatory Frameworks

Harmonized Control Mappings

FRAMEWORK CODE	FRAMEWORK NAME & DETAILS	FAMILY / CATEGORY	VERSION	ACTION
IRDAI	IRDAI Information & Cyber Security Guidelines IRDAI information and cyber-security requirements... Clause: §2.5-3.1.2.1 – Security requirement analysis and specifications; §2.5-3.1.2.2 – Application development	India Guideline	vLatest	View →
RBI-CSF	RBI Cyber Security Framework / Master Directions RBI cyber-security requirements and directions set... Clause: 5) Secure Configuration – 5.1 Baseline security requirements/configurations across device categories and lifecycle, with periodic review; 6) Application Security Life Cycle (ASLC) – 6.1 Information security across all application lifecycle stages	India Regulation	vLatest	View →
SEBI-CSCRF	SEBI Cyber Security & Cyber Resilience Framework SEBI’s Cybersecurity and Cyber Resilience Framewor... Clause: 3.4 PR.IP: Information Protection Processes and Procedures; 1.1 GV.OC: Organizational Context	India Regulation	vLatest	View →
DORA	Digital Operational Resilience Act The EU Digital Operational Resilience Act establis... Clause: Article 6(8)(d) – ICT reference architecture and changes needed for business objectives Article 7 – ICT systems, protocols and tools	EU Regulation	vCurrent	View →
NIS2	NIS2 Directive The NIS2 Directive establishes EU-wide cybersecuri... Clause: Article 21(2)(f) – Policies and procedures to assess the effectiveness of cybersecurity risk-management measures	EU Directive	vCurrent	View →
PCI-DSS	PCI DSS PCI DSS is an industry security standard maintaine... Clause: 2.2.1 – Configuration standards are developed,; 6.5.2 – Upon completion of a significant change, all	PCI Standard	v4	View →
COBIT2019	COBIT COBIT is an enterprise governance and management f... Clause: 4.3 – Build, Acquire and Implement (BAI) > BAI03 – Managed Solutions Identification and Build > BAI03.10 – Maintain solutions. 4.3 – Build, Acquire and Implement (BAI) > BAI03 – Managed Solutions Identification and Build > BAI03.02 – Design detailed solution components.	COBIT Governance Framework	v2019	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	NIST Framework	v2	View →
NIST80053	NIST SP 800-53 NIST SP 800-53 Rev. 5 presents control families, i... Clause: 3.17 – SYSTEM AND SERVICES ACQUISITION, 3.4 – ASSESSMENT, AUTHORIZATION, AND MONITORING; SA-17 – DEVELOPER SECURITY AND PRIVACY ARCHITECTURE AND DESIGN, CA-2 – CONTROL ASSESSMENTS	NIST Control Catalog	vRev. 5	View →
NPCI-ISR	NPCI Information Security Requirements NPCI information-security requirements define cont... Clause: Operational Review; Review – Architectural Review	India Standard	vLatest	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. CC5.1 – Control Activities – COSO Principle 10: The entity selects and develops control activities that contribute to the mitigation of risks to the achievement of objectives to acceptable levels. CC4.1 – Monitoring of Controls – COSO Principle 16: The entity selects, develops, and performs ongoing and/or separate evaluations to ascertain whether the components of internal control are present and functioning.	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:

Security Design & Architecture Reviews (ARC-004)

Summary:

Establishes security design and architecture reviews including design review, architecture review, requirement validation, risk assessment, approval, reporting, monitoring, follow-up, and continuous improvement.

Business Description:

Establish and maintain formal security design and architecture review processes for new systems, applications, infrastructure, cloud services, and significant technology changes.

View