# Software Development Security Policy - Source: https://support.icompaas.com/compliance/policy-docs/software-development-security-policy - Section: [Compliance](https://support.icompaas.com/compliance) › [Policy Documents](https://support.icompaas.com/compliance/policy-docs) › All policy documents - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **Policy Document**·8 mapped controls ## What this policy is The secure-SDLC policy — requirements for threat modelling, secure-coding training, SAST/DAST coverage, dependency-scanning, secrets-management, and pre-production security testing. ## Why every organization needs one Most exploitable application vulnerabilities are introduced during development. Shifting security left through SDLC controls is far cheaper than fixing in production. ## What a competent Software Development Security Policy typically contains - Purpose and scope - Roles and responsibilities - Definitions - Threat-modelling trigger and template - SAST/DAST coverage requirements - Dependency-scanning cadence - Secret-management standards - Review cadence (typically annual) and version control - Approval, sign-off and effective date ## How iCompaas tracks this policy The icompaas policy-doc producer manages this document through an 8-state lifecycle: `draft` → `generated` → `internal_qa` → `customer_review` → `in_review` → `approved` → `signed` (with `rejected` as a terminal side-state). The producer publishes a `policy_doc_software_development_security_policy_signed` compliance finding once at least one document of this kind reaches the `signed` state for the account being assessed; the finding then rolls up into every compliance framework that references this policy (see the table below). ## Compliance frameworks that reference this policy The icompaas [compliance controls library](https://support.icompaas.com/compliance) links every policy document to the controls in each framework that require, evidence, or otherwise rely on it. Below: every control across every framework in the iCompaas catalogue that names this policy as part of its evidence base. Each control links to its own dedicated page with auditor-view content + implementation guidance. | Framework | Control | Title | Component | | --- | --- | --- | --- | | ISO/IEC 27001:2022 | [A.5.8](https://support.icompaas.com/compliance/iso-27001-2022/a-5-8-information-security-in-project-management) | [Information security in project management](https://support.icompaas.com/compliance/iso-27001-2022/a-5-8-information-security-in-project-management) | Organizational controls | | ISO/IEC 27001:2022 | [A.8.4](https://support.icompaas.com/compliance/iso-27001-2022/a-8-4-access-to-source-code) | [Access to source code](https://support.icompaas.com/compliance/iso-27001-2022/a-8-4-access-to-source-code) | Technological controls | | ISO/IEC 27001:2022 | [A.8.25](https://support.icompaas.com/compliance/iso-27001-2022/a-8-25-secure-development-life-cycle) | [Secure development life cycle](https://support.icompaas.com/compliance/iso-27001-2022/a-8-25-secure-development-life-cycle) | Technological controls | | ISO/IEC 27001:2022 | [A.8.26](https://support.icompaas.com/compliance/iso-27001-2022/a-8-26-application-security-requirements) | [Application security requirements](https://support.icompaas.com/compliance/iso-27001-2022/a-8-26-application-security-requirements) | Technological controls | | ISO/IEC 27001:2022 | [A.8.29](https://support.icompaas.com/compliance/iso-27001-2022/a-8-29-security-testing-in-development-and-acceptance) | [Security testing in development and acceptance](https://support.icompaas.com/compliance/iso-27001-2022/a-8-29-security-testing-in-development-and-acceptance) | Technological controls | | ISO/IEC 27001:2022 | [A.8.31](https://support.icompaas.com/compliance/iso-27001-2022/a-8-31-separation-of-development-test-and-production-environments) | [Separation of development, test and production environments](https://support.icompaas.com/compliance/iso-27001-2022/a-8-31-separation-of-development-test-and-production-environments) | Technological controls | | ISO/IEC 27701:2025 | [A.3.27](https://support.icompaas.com/compliance/iso-27701-2025/a-3-27-secure-development-life-cycle) | [Secure development life cycle](https://support.icompaas.com/compliance/iso-27701-2025/a-3-27-secure-development-life-cycle) | Security considerations | | ISO/IEC 27701:2025 | [A.3.28](https://support.icompaas.com/compliance/iso-27701-2025/a-3-28-application-security-requirements) | [Application security requirements](https://support.icompaas.com/compliance/iso-27701-2025/a-3-28-application-security-requirements) | Security considerations | 8 controls across 2 frameworks reference this policy. ## About this page This article is part of the iCompaas [Policy Documents](https://support.icompaas.com/compliance/policy-docs) library — one page per signed-document type the icompaas policy-doc producer tracks for customer accounts. The article is intentionally framework-agnostic: a customer signing a policy of this kind gets the same regulatory benefit across every framework that references it. ## Related compliance guidance - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): SOC 2 auditors test that policies like this one exist, are approved, and are reviewed on schedule; the guide lists the full set. - [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 clause 5.2 and Annex A.5.1 require a documented, approved policy set; the guide shows how it fits the ISMS.