Security risk must be understood before deployment so material vulnerabilities are not introduced into production without informed decisions.
Perform risk assessments for applications and significant releases, define security acceptance criteria, document residual risk, and require appropriate approval for unresolved high-risk issues.
| FRAMEWORK CODE | FRAMEWORK NAME & DETAILS | FAMILY / CATEGORY | VERSION | ACTION |
|---|---|---|---|---|
| IRDAI | IRDAI Information & Cyber Security Guidelines IRDAI information and cyber-security requirements... Clause: §2.9-3.4 – Release Management; §2.5-3.2.4 – System changes control |
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.1 Information security across all application lifecycle stages; 6) Application Security Life Cycle (ASLC) – 6.6 Threat modelling, secure coding, security testing and secure rollout |
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 |
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 25 – Testing of ICT tools and systems |
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: 6.5.1 – Changes to all system components in the; 6.5.2 – Upon completion of a significant change, all; 6.5.3 – Pre-production environments are separated; 6.5.4 – Roles and functions are separated between |
PCI
Standard
|
v4 | View → |
| COBIT2019 | COBIT COBIT is an enterprise governance and management f... Clause: 4.3 – Build, Acquire and Implement (BAI) > BAI07 – Managed IT Change Acceptance and Transitioning > BAI07.01 – Establish an implementation plan. |
COBIT
Governance Framework
|
v2019 | View → |
| NIST-CSF | NIST Cybersecurity Framework (CSF) The NIST Cybersecurity Framework provides high-lev... Clause: PR.PS – Platform Security | PR.PS-06 – Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle PR.PS – Platform Security | PR.PS-01 – Configuration management practices are established and applied DE.CM – Continuous Monitoring | DE.CM-09 – Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events |
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.5 – CONFIGURATION MANAGEMENT; SA-10 – DEVELOPER CONFIGURATION MANAGEMENT, CM-3 – CONFIGURATION CHANGE CONTROL |
NIST
Control Catalog
|
vRev. 5 | View → |
| CIS-V8 | CIS Controls CIS Controls are a prioritized set of cybersecurit... Clause: Control 16 – Application Software Security: 16.1 – Establish and Maintain a Secure Application Development Process |
CIS
Best Practice
|
vv8 | View → |
| NPCI-ISR | NPCI Information Security Requirements NPCI information-security requirements define cont... Clause: Security Measures / Controls; Application Security Life Cycle |
India
Standard
|
vLatest | View → |
| SOC2 | SOC 2 Trust Services Criteria SOC 2 is an independent examination and reporting... Clause: CC8.1 – Change Management – The entity authorizes, designs, develops or acquires, configures, documents, tests, approves, and implements changes to infrastructure, data, software, and procedures to meet its objectives. |
AICPA
Audit Framework
|
vLatest | View → |