A.7 Physical controls

A.7.2 Physical entry

Not mandatory by default – decided in your SoA

What it means in plain language

Control who can enter secure areas using entry controls and access points.

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

A.7.2 focuses on controlling entry to secure areas, so only authorized people can cross the perimeter and visitors remain visible and supervised. Problems usually arise when access lists are not reviewed, temporary passes are reused, or escorts do not know their responsibilities. Teams should connect badge issuance, visitor handling, and periodic review of who still needs access.

Common auditor findings to check for

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

  • Badge access is issued informally by managers, but removals after role changes are not timely, so former staff or contractors retain entry rights longer than intended.
  • Visitors are signed in, yet there is no consistent escort expectation or badge return step, leaving secure areas exposed when host staff are distracted.
  • Quarterly access list reviews are claimed, but there is no retained evidence of review decisions, exceptions, or follow-up on dormant credentials.

How you can implement it

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

  • Set a clear entry control method for each secure area: personal badge, PIN plus badge, reception-issued temporary pass, or guarded access. Document who approves access, who can issue temporary credentials, how lost or stolen badges are disabled, and how contractors are handled when their work window ends.
  • Use the Visitor Access Log as part of a complete flow: identity verified at reception, purpose recorded, host named, escort assigned, start and end times captured, and pass returned or invalidated on exit. For recurring visitors, require periodic re-validation rather than indefinite reuse of the same visitor record.
  • Review badge and access rights at a cadence based on risk, such as after role changes, project completion, contractor offboarding, or a quarterly list review for sensitive rooms. The reviewer should be someone with authority to question business need, and the output should be a dated decision list.
  • For exceptions such as emergency maintenance or delivery access, use a controlled temporary process with start/end time, named approver, and post-visit reconciliation. Retain CCTV references where used, turnstile or door logs, and incident notes when entry controls were bypassed or challenged.

What an auditor will ask to see

  • Visitor Access Log showing identity, host, escort, times, and badge return.
  • Physical Entry Controls Procedure defining approval, temporary access, and badge revocation steps.
  • Quarterly access review record with approvals, removals, and unresolved exceptions.
  • Door access system export showing active badges matched to current staff or contractors.

Baseline documents in the kit

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

Connect this work to your ISMS

Review the dependencies with A.7.1 — Physical security perimeters and A.5.18 — Access rights. 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.