ISO 27701:2019
PIMS-specific guidance related to ISO/IEC 27002, ISO 27701:2019

ISO 27701:2019 6.11.2: Security in development and support processes

System development and design policies must give guidance on the organization's processing needs based on its obligations to individuals and applicable law, covering privacy principles in the development lifecycle, privacy requirements at the design phase informed by risk or impact assessment, protection checkpoints at project milestones, the knowledge developers need, and minimising processing by default; systems and components processing personal data must be designed with privacy built in from the start and protective settings as the default so collection and processing are limited to what the identified purposes need and so that later obligations such as timely disposal are facilitated; change control, technical review, package change restrictions, secure development environments, outsourced development and system and acceptance testing apply as the base guidance requires.

Maintained by Gerard Blokdyk

What else in your programme already covers this

This control maps to 74 controls across 19 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST SP 800-53 Rev 5 · 10 controls

  • NIST800-SA-10 SA-10 Developer Configuration Management
  • NIST800-SA-11 SA-11 Developer Testing and Evaluation
  • NIST800-SA-15 SA-15 Development Process, Standards, and Tools
  • NIST800-SA-17 SA-17 Developer Security and Privacy Architecture and Design
  • NIST800-SA-22 SA-22 Unsupported System Components
  • NIST800-SA-3 SA-3 System Development Life Cycle
  • NIST800-SA-8 SA-8 Security and Privacy Engineering Principles
  • NIST800-SC-38 SC-38 Operations Security
  • SP800-53-CM Configuration Management Family
  • SP800-53-SA System and Services Acquisition Family

PCI DSS 4.0 · 10 controls

  • 6.2.1 6.2.1 Secure development of bespoke and custom software
  • 6.2.2 6.2.2 Annual secure software training for developers
  • 6.2.3 6.2.3 Code review before release
  • 6.2.3.1 6.2.3.1 Manual code review independence and approval
  • 6.2.4 6.2.4 Engineering techniques against common software attacks
  • 6.3.1 6.3.1 Vulnerability identification and risk ranking
  • 6.5.1 6.5.1 Change control procedure for production
  • 6.5.3 6.5.3 Separate pre-production from production
  • 6.5.4 6.5.4 Separate roles between production and pre-production
  • 8.6.2 8.6.2 No hard-coded passwords for interactive system accounts

CIS Controls v8 · 8 controls

  • CIS-16.1 Establish and Maintain a Secure Application Development Process
  • CIS-16.10 Apply Secure Design Principles in Application Architectures
  • CIS-16.11 Leverage Vetted Modules or Services for Application Security Components
  • CIS-16.12 Implement Code-Level Security Checks
  • CIS-16.4 Establish and Manage an Inventory of Third-Party Software Components
  • CIS-16.5 Use Up-to-Date and Trusted Third-Party Software Components
  • CIS-16.8 Separate Production and Non-Production Systems
  • CIS-16.9 Train Developers in Application Security Concepts and Secure Coding

ISO 27001:2022 · 5 controls

  • 8.25 Secure development life cycle
  • 8.27 Secure system architecture and engineering principles
  • 8.28 Secure coding
  • 8.29 Security testing in development and acceptance
  • 8.30 Outsourced development

ISO 27002:2022 · 5 controls

  • 8.25 Secure development life cycle
  • 8.27 Secure system architecture and engineering principles
  • 8.28 Secure coding
  • 8.29 Security testing in development and acceptance
  • 8.32 Change management
  • NIST-CSF-ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles
  • NIST-CSF-ID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked
  • NIST-CSF-PR.PS-01 Configuration management practices are established and applied
  • NIST-CSF-PR.PS-02 Software is maintained, replaced, and removed commensurate with risk
  • NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

SOC 2 · 5 controls

  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC6.8 CC6.8 Preventing and detecting unauthorised or malicious software
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure
  • SOC2-P6.4 P6.4 Privacy commitments from vendors and third parties
  • SOC2-PI1.3 PI1.3 Controls over system processing

FedRAMP High · 4 controls

  • SA-10 Developer Configuration Management
  • SA-11 Developer Testing and Evaluation
  • SA-15 Development Process, Standards, and Tools (SA-15)
  • SA-3 System Development Life Cycle

FedRAMP Moderate · 4 controls

  • SA-10 Developer Configuration Management
  • SA-11 Developer Testing and Evaluation
  • SA-15 Development Process, Standards, and Tools (SA-15)
  • SA-3 System Development Life Cycle
  • ASBv3-DS-4 Integrate static application security testing into DevOps pipeline
  • ASBv3-DS-5 Integrate dynamic application security testing into DevOps pipeline
  • ASBv3-GS-10 Define and implement DevOps security strategy

CMMC 2.0 · 3 controls

NIST SP 800-161 Rev 1 · 3 controls

  • SEC11-BP02 Automate testing throughout the development and release lifecycle
  • AUCDR-IS-4 Formal vulnerability management program

C5 (Germany) · 1 control

  • C5-DEV-01 Policies for the development/procurement of information systems

GDPR · 1 control

ISO 27017:2015 · 1 control

  • 14.2 Security in development and support processes
  • 03.16.01 Security Engineering Principles

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in PIMS-specific guidance related to ISO/IEC 27002, ISO 27701:2019

You are reading one control. How much of ISO 27701:2019 have you already done?

ISO 27701:2019 6.11.2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27701:2019 your existing evidence covers. Hold SOC 2 and 58 of 108 ISO 27701:2019 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 289 were rejected on the SOC 2 pair alone.

Query this from an agent

The graph holds this control, the 74 it maps to, and the evidence behind each claim, over MCP and REST.