Skip to content
Technological controls
ISO 27001A.8.26

ISO 27001 Annex A 8.26 Application security requirements

What it says

Information security requirements shall be identified, specified and approved when developing or acquiring applications.

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

What it means

In plain English

Identify, specify and approve information security requirements when developing or acquiring applications, including bought cloud services, not after they go live.

Your organisation must identify, specify and approve information security requirements when developing or acquiring applications, including bought cloud services. All three are required, while the work or purchase is under way rather than after go-live:

  • Identify: work out what security the application needs, given its purpose and the information it handles.
  • Specify: state those needs clearly enough to build, buy or test against.
  • Approve: someone with authority accepts them, along with any gaps.

Why it matters

An application chosen or built with no agreed requirements can go live without the sign-on, logging or encryption your information needs, and by then the contract is signed or the design fixed. Agreeing requirements first shows those gaps while they can still be closed.

How to implement

  1. Add a security requirements step to new application requests.

    Put it in project start-up (Annex A 5.8) and the purchase request, so it runs before a build starts or a contract is signed. Include free trials and app store sign-ups that connect to company information or accounts; these can use a short checklist with one approver.

  2. Identify requirements from a risk assessment.

    Record what information the application handles and its classification (Annex A 5.12), who uses it, what it connects to and what laws apply (Annex A 5.31). Work through sign-on, access levels, encryption, input checks, logging and error handling, and keep those that apply.

  3. Specify each requirement so it can be tested.

    Write 'administrators sign in with multi-factor authentication', not 'strong security'. For payments or transactions with partners, add the identity checks, transaction integrity and proof of receipt each side needs.

  4. Get the requirements approved and keep the record.

    Decide who approves, usually whoever is accountable for the application and its risks. Record the decision before the design is fixed or you approach suppliers, then put the requirements in the design document, user stories or tender, and approve again if the scope changes.

  5. Compare bought products with the requirements before you commit.

    Use product documentation, a vendor questionnaire, an independent assurance report and a trial. Where a product falls short and its terms cannot change, add your own control, choose differently or have the approver accept the gap before the contract is signed. Annex A 5.20 covers agreeing requirements with suppliers.

Keep it running

Keep the requirements with the application's record. Reopen them on a major change, such as new types of information, new integrations or new groups of users, and when a bought service's renewal gives you a chance to address open gaps.

Evidence and audit

  1. Check 1 of 4What an auditor asks for

    Ask for

    A list of recent new applications, from purchase records, development project records and single sign-on logs, matched to requirements records.

    Look at

    Applications with no record, including free or low-cost tools connected to company accounts.

    Good evidence

    Every application developed or acquired in the period has requirements that were identified, specified and approved.

  2. Check 2 of 4What an auditor asks for

    Ask for

    The requirements record for a sampled application, with the risk assessment behind it.

    Look at

    Whether the requirements reflect that application's information and risks, and whether each one can be tested.

    Good evidence

    Each requirement is specific to the application and testable, with no generic wording such as 'must be secure'.

  3. Check 3 of 4What an auditor asks for

    Ask for

    The approval record, with its date compared with the contract signature or the development start and release dates.

    Look at

    Who approved, when, and what gaps they accepted.

    Good evidence

    A person with authority approved the requirements during development or before the contract was signed, not after go-live, and any accepted gap is named.

  4. Check 4 of 4What an auditor asks for

    Ask for

    The contract, tender or design document for the same application.

    Look at

    Whether the approved requirements appear in what the supplier or developers were given.

    Good evidence

    The approved requirements appear in that document, or the record explains why a standard contract could not carry them.

Mappings

Closest match in ASD Information Security Manual: ISM-0971, Use OWASP standards in web application development, which this control covers in full and more.

ISO 42001

ISO/IEC 42001: 1 mapping

ASD ISM

ASD Information Security Manual: 23 mappings

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.