A.8 Technological controls

A.8.26 Application security requirements

Not mandatory by default – decided in your SoA

What it means in plain language

Identify and approve security requirements when developing or acquiring applications.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

Teams need to turn business needs into explicit application security requirements before development or procurement starts. Stakeholders should approve requirements, challenge missing protections and check suppliers against the agreed acceptance criteria. The objective is to avoid late surprises by tying authentication, logging, encryption, and privacy expectations to the request, contract, and acceptance process.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Security requirements are vague or bundled into general functionality, so teams later discover missing logging, weak authentication, or weak encryption expectations.
  • Procurement decisions rely on vendor brochures rather than documented security criteria, leaving no trace of who approved accepted gaps or compensating controls.
  • Acceptance criteria exist for features, but not for security; testing therefore confirms function while overlooking access restriction, retention, or evidence needs.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Create a standard requirements template with security prompts for authentication, authorization, logging, encryption, session management, backup, privacy, and third-party access. Require the business owner and information security reviewer to approve applicable items before build or contract award. Make the template easy to use in user stories, statements of work, or SaaS evaluations.
  • Map requirement sources to legal, regulatory, customer, and internal risk drivers. For example, if personal data is processed, specify minimization, masking, retention, and deletion needs; if privileged users are involved, specify stronger authentication and logging. This helps justify why controls apply without assuming every requirement is universal.
  • Use practical checks during selection and delivery: vendor questionnaire, architecture review, proof of concept, and acceptance test scripts. Record where a supplier control is inherited, where a compensating control is needed, and where the business accepts residual risk. Keep decisions linked to the application record and change log.
  • Review a sample of active projects or SaaS renewals on an illustrative monthly or quarterly basis. Missing or contradictory requirements should become nonconformities or corrective actions so future requests improve. Where rework is needed, update the template, reviewer checklist, and approval workflow rather than relying on verbal reminders.

What an auditor will ask to see

  • Approved security requirements section in a user story set, procurement pack, or SaaS checklist with named approvers.
  • Acceptance test cases covering authentication, logging, encryption, privacy, or access restriction for the application.
  • Vendor security assessment, contract addendum, or risk acceptance note showing how control gaps were addressed.
  • Traceability matrix linking business need, security requirement, implementation owner, and test outcome.

Baseline documents in the kit

These free kit documents help you document or evidence A.8.26. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.8.25 — Secure development life cycle and A.8.27 — Secure system architecture and engineering principles. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.