Skip to content
Technological controls
ISO 27001A.8.27

ISO 27001 Annex A 8.27 Secure system architecture and engineering principles

What it says

Principles for engineering secure systems shall be established, documented, maintained and applied to any information system development activities.

Quoted as published. Everything else on this page is written by Control Stack.

What it means

In plain English

Establish, document and maintain principles for engineering secure systems, and apply them to any information system development activities, in-house or outsourced.

Your organisation must establish, document and maintain principles for engineering secure systems, and apply them to any information system development activities. That takes in new systems, changes, infrastructure and integrations, including work a supplier does for you. The principles are design rules that systems are built to, such as least privilege (only the access needed) and default deny (refused unless allowed). Maintaining means keeping them current. A document alone falls short: each design must actually use them.

Why it matters

A weakness designed into a system, such as trusting everything inside the network, is slow and costly to fix once the system is live, and later testing may miss it. Shared principles mean each project starts from the same secure design choices.

How to implement

  1. Name an owner and write the principles down.

    Keep them short, specific and versioned. For example: access is refused unless a rule allows it, every request is authenticated, input from outside is never trusted, and systems fail into a safe state. Apply them at every architecture layer: business processes, data, applications and technology. Annex A 8.28 covers coding rules.

  2. Build the principles into design work.

    Add them to the project or design template, and hold a security design review before building. Record how the design meets each principle and where in the system each security control applies. If a control falls short of a requirement, record the gap, the reason and who accepted it.

  3. Use the principles for every kind of development activity.

    Include new applications, changes to existing systems, infrastructure and cloud builds, integrations and automations. If you buy software instead of building it, apply them to the integrations and configuration you design. Annex A 8.26 covers security requirements when acquiring applications.

  4. Pass the principles on to anyone developing for you.

    Write the principles that apply into the contract or statement of work, and ask for design documents that show them in use. If the terms are fixed, compare the supplier's design information with your principles and record the gaps before you commit. Annex A 8.30 covers directing that work.

Keep it running

Revisit the principles when you adopt new technology, when a new attack pattern affects systems like yours, or after an incident traces back to design. Repeated exceptions to the same principle suggest it needs rewriting, or teams need a template or tool to meet it.

Evidence and audit

  1. Check 1 of 4What an auditor asks for

    Ask for

    The documented engineering principles and their version history, with project and incident records for the same period, up to today.

    Look at

    Whether each principle is specific enough to judge a design against, and whether the changes line up with the technology adopted and the threats faced in those records.

    Good evidence

    The principles are written down, a design can pass or fail against them, and any relevant change, such as adopting new technology, led to an update.

  2. Check 2 of 4What an auditor asks for

    Ask for

    A list of recent development activities from project, change and supplier records, matched to design records.

    Look at

    Whether infrastructure, integration and outsourced work appear as well as new applications, and whether each has a record showing the principles were used.

    Good evidence

    Every sampled activity, of any type, has a record showing how the principles were applied or why a departure was accepted.

  3. Check 3 of 4What an auditor asks for

    Ask for

    One recently built system, walked through against its design and the principles.

    Look at

    Live settings that test a principle, such as whether a new account starts with no access and unmatched network traffic is refused, and whether departures were recorded.

    Good evidence

    The system behaves as the principles say, and each departure is recorded with a reason and who accepted it.

  4. Check 4 of 4What an auditor asks for

    Ask for

    A contract or statement of work for outsourced development, with the supplier's design evidence.

    Look at

    Whether the principles that apply were passed on, and whether the evidence shows them used in the delivered design.

    Good evidence

    The agreement carries the principles that apply and the evidence shows them in use, or, where the terms were fixed, the supplier's design information was compared with the principles and the gaps recorded before commitment.

Mappings

Closest match in ASD Information Security Manual: ISM-0938, Use Secure by Design and Secure by Default vendors for user applications, which this control covers in full and more.

ISO 42001

ISO/IEC 42001: 1 mapping

ASD ISM

ASD Information Security Manual: 25 mappings

ASD Essentials

ASD Essentials for enterprise IT: 1 mapping

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.

Get help with this control

ISO 27001 training

Mindset Cyber, a PECB Authorised Titanium Partner, sells official PECB ISO/IEC 27001 courses that map directly to the controls in this library.