# ISO/IEC 27001:2022 A.8.30 — Outsourced development - Source: https://support.icompaas.com/compliance/iso-27001-2022/a-8-30-outsourced-development - Section: [Compliance](https://support.icompaas.com/compliance) › [ISO/IEC 27001:2022 Annex A Controls](https://support.icompaas.com/compliance/iso-27001-2022) › Technological controls - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **ISO/IEC 27001:2022**·Annex A `A.8.30`·medium·Component: **Technological controls** ## What this control requires > The organization shall direct, monitor and review the activities related to outsourced system development. > > — ISO/IEC 27001:2022, Annex A A.8.30 ### In plain English The organization shall direct, monitor and review the activities related to outsourced system development. In practice, this means you can prove you management management-level controls on a defined cadence. ## Why it matters ISO 27001 certification depends on showing each Annex A control is either implemented or explicitly justified for exclusion in the Statement of Applicability (SoA). Certification bodies sample controls during surveillance audits, and a missing SoA entry — or implementation that doesn't match the SoA wording — is a finding. ## What an auditor looks for An ISO 27001 lead auditor looks for: (1) an SoA entry covering the control with justification, (2) a documented procedure or policy implementing it, (3) records that prove the procedure runs (logs, tickets, training records) and (4) management-review evidence that effectiveness is monitored. Within **Technological controls**, the assessor will trace your implementation back to the catalogue reference (Annex A A.8.30) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Logging Monitoring **AWS.** Org-trail CloudTrail to a central log archive account, GuardDuty in every region, and Security Hub for cross-source correlation. **Azure.** Pipe every diagnostic setting into a central Log Analytics workspace; onboard Microsoft Sentinel for SIEM/SOAR. **GCP.** Aggregate audit logs in a dedicated logging project with sink to BigQuery; enable Security Command Center Premium and route findings to Chronicle SIEM. #### Secure Development **Pipeline.** Require code review, SAST (Semgrep / Snyk Code), SCA (Dependabot / Renovate), secret-scanning and IaC scanning in the merge pipeline. **Branch protection.** Protected branches enforce reviews, signed commits and passing CI before merge; document the protection rules as the control evidence. ### Operational checklist - **Management.** Document the trigger, the owner and the cadence. - **Secure.** Document the trigger, the owner and the cadence. - **Security.** Document the trigger, the owner and the cadence. - **Monitor.** Document the trigger, the owner and the cadence. - **Scope:** management, security, development. ## Evidence to collect - **Ticketing Workflow.** `ticketing_workflow` evidence - **Vendor Risk Management.** `vendor_risk_management` evidence - **Infra Scan.** Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings. Vendor assessments and tracked deliverables demonstrate oversight of outsourced development. ## Common pitfalls - Per-account logging that nobody stitches together at the org level — incidents that cross accounts go undetected for days. - CI security checks set to warn-only; the merge button is faster than the security feedback. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**NIST SP 800-171 Rev. 3 3.16.2** — Unsupported System Components](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-16-2-unsupported-system-components) - [**CIS Controls v8 16.4** — Establish and Manage an Inventory of Third-Party Software Components](https://support.icompaas.com/compliance/cis-controls-v8/16-4-establish-and-manage-an-inventory-of-third-party-software-components) - [**SOC 2 (2017 TSC) CC9.2** — Vendor Risk Management](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc9-2-vendor-risk-management) - [**BSI C5:2020 COS-02** — Security requirements for connections in the Cloud Service Provider's network](https://support.icompaas.com/compliance/bsi-c5-2020/cos-02-security-requirements-for-connections-in-the-cloud-service-provider-s-network) - [**ISO/IEC 27701:2025 A.3.30** — Outsourced development](https://support.icompaas.com/compliance/iso-27701-2025/a-3-30-outsourced-development) ## Related controls in ISO/IEC 27001:2022 - [**Annex A A.5.20** — Addressing information security within supplier agreements](https://support.icompaas.com/compliance/iso-27001-2022/a-5-20-addressing-information-security-within-supplier-agreements) - [**Annex A A.8.29** — Security testing in development and acceptance](https://support.icompaas.com/compliance/iso-27001-2022/a-8-29-security-testing-in-development-and-acceptance) - [**Annex A A.5.19** — Information security in supplier relationships](https://support.icompaas.com/compliance/iso-27001-2022/a-5-19-information-security-in-supplier-relationships) - [**Annex A A.5.22** — Monitoring, review and change management of supplier services](https://support.icompaas.com/compliance/iso-27001-2022/a-5-22-monitoring-review-and-change-management-of-supplier-services) - [**Annex A A.8.27** — Secure system architecture and engineering principles](https://support.icompaas.com/compliance/iso-27001-2022/a-8-27-secure-system-architecture-and-engineering-principles) - [**Annex A A.8.28** — Secure coding](https://support.icompaas.com/compliance/iso-27001-2022/a-8-28-secure-coding) ## References - [ISO/IEC JTC 1/SC 27 — ISO/IEC 27001:2022](https://www.iso.org/standard/27001) - Catalogue identifier: `Annex A A.8.30` Topics: vendor riskvendor managementsupply chain securitylogging monitoringsecure development ## Related compliance guidance - [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): Start with the full ISO 27001 implementation guide — scope, roadmap, evidence and how the assessment runs. - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most companies that hold ISO 27001 also need a SOC 2 report for North American customers, and the two share most of their technical controls.