A.8 Technological controls

A.8.3 Information access restriction

Not mandatory by default – decided in your SoA

What it means in plain language

Restrict access to information and application functions according to the access control policy.

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 should turn access control rules into concrete restrictions on folders, application functions, records, and data views. The main failure mode is over-broad access that accumulates through projects, role changes, and one-off exceptions, then persists because no owner periodically checks it. Teams should connect business roles to access groups and show how request, approval, testing, and review records prove the restriction is working.

Common auditor findings to check for

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

  • Folder or application permissions are assigned by default to broad groups, exposing customer or internal records to users who do not need them for daily work.
  • Role design is inconsistent across systems, so the same job function has different visibility in CRM, ticketing, and file storage without documented justification.
  • Temporary access granted for support or project work is not removed, leaving accumulated access rights that no longer match current responsibilities or data ownership.

How you can implement it

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

  • Maintain an access matrix for key information sets and application functions, showing the business role, permission level, approver, and data owner. The procedure should require each new access request to reference that matrix, so reviewers can compare requested rights with the minimum needed for the task and reject broad default access.
  • Use named access groups rather than individual folder grants wherever practical, and have application owners review them on a scheduled cadence such as quarterly or after major staffing changes. When exceptions are needed, record the reason, start and end dates, and compensating controls such as supervision or masked views.
  • Test restricted views after implementation by using a standard user account from the affected role. The system owner or delegated tester should confirm that prohibited folders, fields, or functions remain hidden, then retain screenshots or configuration extracts as evidence. Failed tests should trigger rework before the access change is closed.
  • Link termination and role-change procedures to access removal so that business managers confirm what the person no longer needs. For high-value datasets, add periodic entitlement recertification by data owners and compare current rights with job descriptions, active projects, and incident tickets. Escalate discrepancies through corrective action when access is excessive or unclear.

What an auditor will ask to see

  • Access matrix mapping roles to folders, apps, functions, and owners.
  • Quarterly entitlement review with removed rights and open exceptions.
  • Role-based test evidence showing hidden fields or denied functions for a standard account.

Baseline documents in the kit

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

Connect this work to your ISMS

Review the dependencies with A.5.15 — Access control and A.5.18 — Access rights. Keep the ownership and evidence consistent across these activities.

ISO/IEC 27001 vs SOC 2: evidence you can reuse 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.