ISO 27001:2022
Technological controls – ISO 27001:2022

ISO 27001:2022 8.27: Secure system architecture and engineering principles

Principles for engineering secure systems are to be set, written down, kept current and applied to every information system development activity. Purpose (stated in ISO/IEC 27002:2022): ensures that information systems are designed, implemented and operated securely at every stage of their 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.27.

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

What else in your programme already covers this

This control maps to 87 controls across 26 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

FedRAMP High · 8 controls

  • PL-8 Security and Privacy Architectures
  • SA-11(2) Developer Testing and Evaluation | Threat Modeling and Vulnerability Analyses (SA-11(2))
  • SA-15 Development Process, Standards, and Tools (SA-15)
  • SA-4(2) Acquisition Process | Design and Implementation Information for Controls (SA-4(2))
  • SA-4(9) Acquisition Process | Functions, Ports, Protocols, and Services in Use (SA-4(9))
  • SA-8 Security and Privacy Engineering Principles
  • SA-9(2) Identification of Functions, Ports, Protocols, and Services
  • SC-22 Architecture and Provisioning for Name/Address Resolution Service

FedRAMP Moderate · 8 controls

  • PL-8 Security and Privacy Architectures
  • SA-11(2) Developer Testing and Evaluation | Threat Modeling and Vulnerability Analyses (SA-11(2))
  • SA-15 Development Process, Standards, and Tools (SA-15)
  • SA-4(2) Acquisition Process | Design and Implementation Information for Controls (SA-4(2))
  • SA-4(9) Acquisition Process | Functions, Ports, Protocols, and Services in Use (SA-4(9))
  • SA-8 Security and Privacy Engineering Principles
  • SA-9(2) Identification of Functions, Ports, Protocols, and Services
  • SC-22 Architecture and Provisioning for Name/Address Resolution Service

PCI DSS 4.0 · 8 controls

  • 1.2.3 1.2.3 Accurate network diagram of CDE connections
  • 2.2.1 2.2.1 System configuration standards maintained
  • 2.2.4 2.2.4 Only necessary functionality enabled
  • 2.2.6 2.2.6 System security parameters configured against misuse
  • 3.6.1.1 3.6.1.1 Service provider cryptographic architecture documented
  • 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

CIS Controls v8 · 7 controls

  • CIS-10.5 Enable Anti-Exploitation Features
  • CIS-12.2 Establish and Maintain a Secure Network Architecture
  • CIS-12.4 Establish and Maintain Architecture Diagram(s)
  • CIS-16.10 Apply Secure Design Principles in Application Architectures
  • CIS-16.14 Conduct Threat Modeling
  • CIS-16.7 Use Standard Hardening Configuration Templates for Application Infrastructure
  • CIS-4.8 Uninstall or Disable Unnecessary Services on Enterprise Assets and Software

ISO 27002:2022 · 5 controls

  • 8.25 Secure development life cycle
  • 8.26 Application security requirements
  • 8.27 Secure system architecture and engineering principles
  • 8.28 Secure coding
  • 8.31 Separation of development, test and production environments

SOC 2 · 5 controls

  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

NIST SP 800-218 · 4 controls

AWS Well-Architected Security Pillar · 3 controls

  • SEC01-BP06 Automate deployment of standard security controls
  • SEC01-BP07 Identify threats and prioritize mitigations using a threat model
  • SEC05-BP01 Create network layers

CMMC 2.0 · 3 controls

COBIT 2019 · 3 controls

  • APO03.02 APO03.02 Define reference architecture
  • BAI03.01 BAI03.01 Design high-level solutions
  • BAI03.02 BAI03.02 Design detailed solution components

ISO 27701:2019 · 3 controls

  • 6.11.1 Security requirements of information systems
  • 6.11.2 Security in development and support processes
  • 8.4 Privacy by design and privacy by default

NIST SP 800-161 Rev 1 · 3 controls

  • 161R1-PL-8 Security and Privacy Architectures
  • 161R1-SA-17 Developer Security and Privacy Architecture and Design
  • 161R1-SA-8 Security and Privacy Engineering Principles

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

  • CCM-AIS-04 Secure Application Design and Development
  • CCM-DSP-07 Data Protection by Design and Default

HIPAA Security Rule · 2 controls

NIST SP 800-172 · 2 controls

  • 3.13.2e Introduce Unpredictability into System Operations
  • 3.13.3e Confuse and Mislead Adversaries

NIST SP 800-66 Rev 2 · 2 controls

Azure Security Benchmark · 1 control

C5 (Germany) · 1 control

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

DORA · 1 control

EU AI Act · 1 control

ISO 27001:2013 · 1 control

  • A.14.2.5 Secure system engineering principles

ISO/IEC 42001:2023 · 1 control

  • 8.3 AI risk treatment

NIS2 Directive · 1 control

  • Art.21.2.e Security in acquisition, development and maintenance, including vulnerability handling and disclosure

NIST Cybersecurity Framework 2.0 · 1 control

  • 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-171 Rev 3 · 1 control

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

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

ISO 27001:2022 8.27 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 87 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll ISO 27001:2022 controls