Sekit CSF · Application Security · Technical
RCF-0117Secure SDLC policy
Technical gates enforce security checks before code can progress through the development pipeline
Mapping at a glance
RCF-0117Secure SDLC policyApplication Security · Technical
RCF-0117 maps to 6 controls across the published frameworks. +1 more in the table below. Open in the full graph →
Maps to ISO/IEC 27001:2022
Curated mapping with the reasoning, not just the codes.
A.8.25Secure development life cyclesupportsThe technical facet configures the pipeline so automated security checks must pass before code reaches production, enforcing A.8.25's lifecycle discipline mechanically.A.8.29Security testing in development and acceptancesupportsThis Sekit technical control gates the pipeline so automated security checks must pass before production, the enforcement mechanism this ISO control requires for testing before acceptance.A.8.31Separation of development, test and production environmentssupportsThis Sekit technical control gates the pipeline so code cannot reach production without passing checks, reinforcing the separation between development and production this ISO control requires.
Maps to NIST CSF 2.0
Curated mapping with the reasoning, not just the codes.
PR.PS-01Configuration management appliedPR.PS-03Hardware maintainedPR.PS-04Logs generated for monitoring
Evidence that proves this control
What an auditor, or Sekit's evidence engine, asks for.
Secure development policy
The rules the development team follows to build software securely: security requirements, code review and threat modeling.
From the Sekit evidence catalog
This topic through the other lenses
All Application Security controls
Ask Sekura: “What evidence proves RCF-0117?”
Also via MCP, free with account