ISO 27001 A.7.2: Control entry to secure areas
Physical entry control should allow the right person into the right area for an authorised purpose, while preventing a valid invitation or staff badge from becoming unlimited access. ISO 27001 Annex A.7.2 helps organisations protect secure areas at the points where people and materials cross their boundaries. The business value is a more dependable relationship between access permission and the work actually being performed.
What A.7.2 requires in practice
Annex A control 7.2 asks that secure areas are protected by suitable entry controls and access points. The control covers everyone and everything that crosses the boundary: staff, regular suppliers, visitors and deliveries. Several ideas sit inside it. Entry should depend on an authorised purpose rather than on simply having a badge or an invitation. Keys, cards and codes need controlled issue, return and action when lost. Visitors need identification, a host and an appropriate level of supervision. Delivery points should let goods in without giving delivery staff a route to sensitive areas. The outputs are rules for who may enter which area, working entry mechanisms, and records showing that entry decisions are made and reviewed. The standard does not require biometric readers, a specific visitor system or any named technology; the controls must suit the site and its risks.
Separate identity, permission and the entry decision
Knowing who someone is does not establish where they may go. Define who can approve access to each protected area, what business need supports it and how the decision reaches the person or system controlling entry. A receptionist should not have to infer technical-room access from the fact that a visitor has an appointment with someone in the building.
For staff and regular suppliers, connect permissions with joining, role changes and departure. Consider time-limited or area-limited access where appropriate. Physical keys need the same management attention as electronic credentials: ownership, authorised issue, return and action when a key is missing. A record of issued keys is useful only if it reflects the keys still in circulation.
Design visitor and delivery handling around real journeys
Decide how a visitor's identity and purpose are confirmed, who receives them and what supervision is appropriate. Give them relevant entry and emergency information without exposing unnecessary security detail. An exception to normal escort arrangements needs an accountable decision; familiarity with a returning visitor is not itself authorisation.
Deliveries create a different interface. Goods may need to enter while the delivery person has no reason to access workstations, records or processing rooms. Review the physical route, reception responsibility and handover. Inspection arrangements should suit the goods and risks, and any inspection of personal belongings must respect applicable legal and ethical requirements. Do not copy an intrusive practice into every site simply because another business uses it.
Why controlling physical entry matters to the business
Most physical breaches do not involve forced doors; they involve a plausible person being let in. A dependable entry process stops a valid invitation or a staff badge from turning into unlimited access. For the business this protects customer records, equipment and staff, and it limits the time spent investigating where a missing item went. It also gives clients confidence when they visit or review your premises. At audit, entry control is usually tested by observation: auditors watch how visitors are received, check who holds keys and ask about former staff. A site where the practice matches the stated rules rarely generates findings.
How to implement A.7.2
Design entry around the actual journeys people and goods take through your site. Keep the arrangements workable for busy reception staff, because a rule that slows every visitor excessively will be quietly bypassed. Involve the people who operate the door in designing it.
- List the secure areas and decide who may approve access to each, and on what business grounds.
- Connect access permissions to joining, role changes and leaving, so that rights follow the person's real position.
- Set rules for keys, cards and codes, covering issue, return, loss and the update of any shared codes.
- Define how visitors are identified, received, escorted and recorded, and who may authorise an exception.
- Review delivery routes and handover points so that couriers do not pass through sensitive areas.
- Train reception, security and host staff on the rules and on what to do when someone cannot be verified.
- Review entry records and key lists on a regular basis and correct any mismatch with current staff and suppliers.
Illustrative BPO example: an engineer's recurring visits
A fictional BPO centre permits a printer engineer to enter its client-processing area whenever reception recognises the engineer. The service contract is current, but the visit is not matched to a particular work request and staff screens contain sensitive information.
The centre introduces a confirmed appointment and responsible host for each visit, with access limited to the relevant equipment area. Reception verifies the approval rather than relying on recognition. The host confirms completion and departure. An authorised review samples a service request, the entry record and the handover to the host. It also checks how an unplanned arrival is handled when the usual contact is absent.
Illustrative manufacturing example: temporary access that outlives the job
A hypothetical manufacturer gives a facilities contractor electronic access for a refurbishment. After completion, the contractor's credential still opens a room containing production records and network equipment. Procurement has closed the purchase order, but no one has communicated that the physical access should end.
The organisation links temporary permission to an owner and an end condition, then checks expiry in the access system. The review also examines whether another contractor requires replacement access for follow-up work. Evidence connects the authorised purpose, permitted area, actual expiry and any approved extension. The remedy is a working lifecycle, not merely adding another signature to the original request.
Test the decisions and exceptions
Useful checks include comparing a sample of active permissions with current roles, confirming that expired access no longer works through an authorised test, and following a visitor from approval to departure. Examine arrangements during shift changes, reception absence and emergency maintenance. A process that works only when one experienced person is present is vulnerable to ordinary staffing changes.
Entry records can support investigation and review, but they may contain personal information. Decide access, protection and retention based on purpose and applicable requirements. ISO 27001 does not supply one universal retention period for every visitor log. Avoid collecting information simply because a digital form makes additional fields easy to add.
Evidence and neighbouring controls
The Statement of Applicability explains selection and implementation status; operating evidence should support the actual arrangement. Approval records, permission extracts, key inventories and visitor records are possible methods rather than universally mandated document titles. Compare these with staff explanations and observations at the entry point. A polished procedure cannot compensate for an unattended door routinely held open.
Connect entry decisions with physical perimeters, the lifecycle of access rights and working within secure areas. Returning a badge does not necessarily end logical access, and admission to an area does not authorise every activity inside it. Operational planning should make those handovers clear.
Common nonconformities with A.7.2
Auditors who observe entry practice tend to find the following. Many of these come from convenience overriding the rules, and are visible to an auditor within minutes of arriving at reception.
- Visitors admitted on a staff member's word with no identification or record.
- Former employees or suppliers whose cards or keys still work.
- Key registers that do not match the keys actually in circulation.
- Shared access codes that have not changed for years despite staff turnover.
- Delivery staff able to walk unaccompanied into working areas.
Frequently asked questions
Are biometrics required for secure-area entry?
No particular technology is universally required. Assess the protection needed, reliability, accessibility and applicable privacy obligations before selecting an authentication method.
Can visitors enter without an escort?
The arrangement should follow the risk and authorised purpose. Where an exception is justified, define its limits and responsibility rather than allowing unrestricted access by default.
Does a visitor signature prove entry was controlled?
No. It may record attendance, but approval, identity checks, permitted movement and actual supervision are separate matters. Test the complete journey.
Improve access decisions with Sterling
Request support for physical access governance and its connection to ISMS implementation, staff learning and agreed Effivity ISO & GRC automation software. Sterling can include scoped authorised vulnerability scanning and findings review within the wider engagement, with continued support through agreed preparation work; certification remains independent. For practitioners designing these interfaces, enrol in ISO/IEC 27002 Information Security Controls. Continue through the physical control guides to examine protection after entry.