This requirement exists to define security requirements, technology selection criteria, and implementation guidance for engineering and to ensure security architecture decisions are consistent, risk-informed, and traceable.
Establish a documented process for define security requirements, technology selection criteria, and implementation guidance for engineering. 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.
| 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.2.5 – Technical review of applications |
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; 6) Application Security Life Cycle (ASLC) – 6.9 Security evaluation and maturity assessment before adopting new technologies for critical systems |
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 7 – ICT systems, protocols and tools Article 9(2) – ICT security policies, procedures, protocols and tools for resilience and data security |
EU
Regulation
|
vCurrent | View → |
| NIS2 | NIS2 Directive The NIS2 Directive establishes EU-wide cybersecuri... Clause: Article 21(2)(e) – Security in network and information systems acquisition, development and maintenance, including vulnerability handling and disclosure |
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.2.4 – Software engineering techniques or other |
PCI
Standard
|
v4 | View → |
| COBIT2019 | COBIT COBIT is an enterprise governance and management f... Clause: 4.2 – Align, Plan and Organize (APO) > APO03 – Managed Enterprise Architecture > APO03.05 – Provide enterprise architecture services. 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 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.17 – SYSTEM AND SERVICES ACQUISITION; SA-8 – SECURITY AND PRIVACY ENGINEERING PRINCIPLES, SA-17 – DEVELOPER SECURITY AND PRIVACY ARCHITECTURE AND DESIGN |
NIST
Control Catalog
|
vRev. 5 | View → |
| SOC2 | SOC 2 Trust Services Criteria SOC 2 is an independent examination and reporting... Clause: CC5.2 – Control Activities – COSO Principle 11: The entity also selects and develops general control activities over technology to support the achievement of objectives. 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. CC5.3 – Control Activities – COSO Principle 12: The entity deploys control activities through policies that establish what is expected and in procedures that put policies into action. |
AICPA
Audit Framework
|
vLatest | View → |