ISO 27001:2022
Technological controls – ISO 27001:2022

ISO 27001:2022 8.30: Outsourced development

When another party develops systems for the organization, the organization is to steer that work, watch it and review it. Purpose (stated in ISO/IEC 27002:2022): ensures the organization's required security measures are implemented in outsourced system development. As an Annex A reference control, it is compared with the controls determined in risk treatment (6.1.3 c) and recorded in the Statement of Applicability as included or excluded, with the justification and implementation status (6.1.3 d); implementation guidance is ISO/IEC 27002:2022 8.30.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 54 controls across 22 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 · 8 controls

ISO 27002:2022 · 5 controls

  • 5.20 Addressing information security within supplier agreements
  • 5.22 Monitoring, review and change management of supplier services
  • 8.25 Secure development life cycle
  • 8.30 Outsourced development
  • 8.31 Separation of development, test and production environments

HIPAA Security Rule · 4 controls

NIST Cybersecurity Framework 2.0 · 4 controls

  • NIST-CSF-GV.SC-04 Suppliers are known and prioritized by criticality
  • NIST-CSF-GV.SC-05 Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties
  • NIST-CSF-GV.SC-07 The risks posed by a supplier, their products and services, and other third parties are understood, recorded, prioritized, assessed, responded to, and monitored over the course of the relationship
  • NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

NIST SP 800-161 Rev 1 · 4 controls

SOC 2 · 4 controls

  • SOC2-CC5.1 CC5.1 Selecting control activities that mitigate risk (COSO principle 10)
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure
  • SOC2-CC9.2 CC9.2 Assessing and managing vendor and business partner risk
  • SOC2-P6.4 P6.4 Privacy commitments from vendors and third parties

ISO 27701:2019 · 3 controls

  • 6.11.2 Security in development and support processes
  • 6.12.1 Information security in supplier relationships
  • 8.5.7 Engagement of a subcontractor to process PII

CIS Controls v8 · 2 controls

  • CIS-15.4 Ensure Service Provider Contracts Include Security Requirements
  • CIS-16.1 Establish and Maintain a Secure Application Development Process

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

FedRAMP High · 2 controls

  • SA-10 Developer Configuration Management
  • SA-4 Acquisition Process

FedRAMP Moderate · 2 controls

  • SA-10 Developer Configuration Management
  • SA-4 Acquisition Process

ISO/IEC 42001:2023 · 2 controls

  • A.10 Third-party and customer relationships
  • A.10.3 Suppliers

NIST SP 800-218 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

C5 (Germany) · 1 control

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

  • CFTC-SS-5 Systems Development and Quality Assurance Category

DORA · 1 control

EU AI Act · 1 control

ISO 27001:2013 · 1 control

NIS2 Directive · 1 control

  • Art.21.3 Take account of supplier-specific vulnerabilities and of Union coordinated supply chain risk assessments

NIST SP 800-172 · 1 control

  • 3.11.7e Supply Chain Risk Management Plan

PCI DSS 4.0 · 1 control

  • 12.8.2 12.8.2 TPSP contracts acknowledging account data responsibility

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 Technological controls – ISO 27001:2022

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

ISO 27001:2022 8.30 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27001:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27001:2022 controls already carry evidence.

If you hold NIST SP 800-53 Rev 584.9% covered · 14 gapsIf you hold ISO 27001:201383.9% covered · 15 gapsIf you hold FedRAMP Moderate80.6% covered · 18 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.174.2% covered · 24 gapsIf you hold C5 (Germany)69.9% covered · 28 gapsIf you hold NIST Cybersecurity Framework 2.063.4% covered · 34 gaps

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. 170 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll ISO 27001:2022 controls