hello@sterling-grc.com +1 201 263 4443 New York ISO & GRC consulting in 60+ countries
SterlingInternational Consulting Talk to a consultantTalk to us
Control A.7.4ISO/IEC 27001:2022 · Physical controls

ISO 27001 A.7.4: Make physical security monitoring effective

Physical security monitoring should make unauthorised access detectable and connect that detection with an appropriate response. ISO 27001 Annex A.7.4 concerns continuing monitoring of premises for that purpose. A camera that records unusable images, an alarm nobody receives or a monitoring service with outdated contacts can create reassurance without dependable protection.

Part ofA.7 · Physical controls|Reading time 6 min

What A.7.4 requires in practice

Annex A control 7.4 asks the organisation to monitor its premises continuously for physical access that has not been approved. The important word is monitor: the aim is to notice an unauthorised entry or attempt, and to be able to act on it. That may involve cameras, alarms, guards or a combination, depending on the premises and risks. The control has three practical parts. Decide which areas and situations need watching, including out-of-hours periods. Make sure the monitoring produces usable signals, such as clear images or alarms that reach a person. Define what happens next, meaning who assesses the signal and how it is escalated. The outputs are a monitoring arrangement that fits the premises, a response routine, and evidence that the equipment and people involved are working. The standard does not name a supplier, technology or recording period.

Specify what the monitoring must establish

Begin with the protected areas and the access scenarios that matter. Decide what a meaningful event looks like, which parts of the premises need coverage and how operating hours affect the arrangement. Monitoring a busy entrance and detecting unexpected access to an unoccupied equipment room can require different decisions.

Be explicit about the expected outcome. Is the arrangement intended to detect access while it occurs, support later investigation, or both? A recording-only setup may contribute evidence but does not automatically deliver timely detection and response. Consider how alarms, personnel and recording capabilities work together rather than counting devices as the measure of success.

ISO/IEC 27001 consulting & certification support

Get clause A.7.4 right the first time — with a global leader in ISO/IEC 27001 implementation

A Sterling consultant works the requirement through with your team, links it to the rest of the system and carries it to certification readiness. Expert and experienced consultants, 8,100+ client engagements in 60+ countries.

Treat response as part of the monitoring design

For each relevant signal, identify who receives it, how they assess it and where they escalate uncertainty. The responder needs enough context to distinguish an authorised maintenance visit from an unexplained event. Working instructions should also address unavailable contacts, a failed monitoring connection and recurring nuisance alarms.

A contracted service can provide part of the arrangement, but responsibilities still need to be agreed. Confirm coverage hours, notification routes, fault handling and the information the provider requires when the site changes. Do not assume that a contract labelled “24-hour monitoring” means every event produces the response your organisation expects.

Why physical monitoring matters to the business

Locks and badges delay an intruder, but monitoring tells you that something is happening, and that is what allows a timely response. Without it, an unauthorised visit to an equipment room might only be discovered when something is missing or fails. Monitoring also supports investigation: usable records help establish what happened, protect innocent staff from suspicion and support insurance or legal processes. Customers with strict requirements may ask about site surveillance. During audit, the difference between monitoring that exists and monitoring that works becomes clear when alarms and recordings are tested, so a response-minded arrangement stands out.

How to implement A.7.4

Define the purpose of the monitoring first, then choose the means. Keep the scope realistic for the size of the site, because a small office needs a proportionate arrangement and not a copy of a large facility. Record why the chosen coverage is considered sufficient.

  1. Identify the protected areas and the situations that matter, such as entry to an unoccupied equipment room at night.
  2. State whether the aim is to detect while it happens, to support later investigation, or both.
  3. Choose monitoring arrangements that suit each area, and confirm that images or alarm signals are usable in practice.
  4. Define who receives each type of signal, how they assess it and where they escalate if unsure.
  5. Give responders enough context, such as expected maintenance visits, to tell routine from unusual events.
  6. Test the arrangement on a regular basis, including alarm delivery, recording quality and the responder's contact details.
  7. Where a provider supplies monitoring, agree what it covers, how you receive information and who maintains the equipment.

Illustrative construction example: monitoring a temporary records office

Illustrative example 1

A hypothetical construction project keeps confidential commercial records in a temporary office after normal working hours. An alarm service is active, but its notification list names a former project manager. When the team conducts an authorised test, the service receives the signal while nobody responsible for the current site receives the call.

Illustrative example 2

The project corrects the contacts, defines a fallback and checks responsibility during leave and demobilisation. The repeated test follows the signal from the site through acknowledgement and the agreed response decision. Evidence includes the test conditions, time of notification and corrective action. The exercise tests management reliability without staging an unauthorised intrusion or exposing live security details.

Automate™ on Effivity · included in every Sterling engagement

Keep clause A.7.4 alive in Effivity

Record what you decided under clause A.7.4, link it to the records and controls it affects, and let the review date trigger the next look. Effivity is the ISO & GRC software used in 50+ countries — and part of every Sterling ISO/IEC 27001 programme.

Illustrative BPO example: a camera that observes the wrong area

A fictional BPO centre rearranges reception furniture and moves the entrance to a restricted processing area. Its camera still operates, but the new layout prevents the monitoring team from seeing the relevant access point clearly. The system dashboard reports normal device status, which staff mistake for effective coverage.

Facilities and security review the new arrangement using a harmless, authorised walkthrough. They adjust the monitoring design after considering the purpose and applicable privacy requirements, then confirm that the intended event can be detected and understood. They also check that confidential information on staff screens is not captured unnecessarily. Device health and useful coverage are recorded as separate checks.

Protect the monitoring system and the information it creates

Monitoring equipment and services can themselves become security dependencies. Restrict administration, protect access to recordings and review who can disable or change the system. Technical maintenance should include relevant power, communication and fault conditions. Sensitive coverage information should be available to those who need it rather than casually distributed.

Monitoring people and retaining footage can engage privacy and employment obligations. Determine the applicable requirements, purpose, access and retention before introducing the arrangement. The control is not permission for unlimited observation. Use appropriate specialist advice for jurisdiction-specific decisions; neither an ISO certificate nor a generic policy establishes lawful surveillance in every country.

Evidence, tests and failure patterns

What counts as evidence

A reviewer can examine the coverage rationale, responsibility arrangements, authorised tests, fault records and evidence that reported events receive attention. Retained information should explain the selected control and its operation without exposing unnecessary personal data. These evidence methods are examples; the standard does not demand one particular monitoring spreadsheet or vendor report.

Common weaknesses

Test representative conditions rather than repeating the easiest daytime check. Consider an unavailable primary responder, a legitimate out-of-hours visit or a reported equipment fault. Define safe test boundaries and avoid disrupting emergency systems. Follow failures through to repair and retest. A growing list of acknowledged faults is not the same as restored monitoring.

Connect monitoring with entry arrangements, security-event assessment and privacy responsibilities. ISMS performance evaluation should examine whether the arrangement remains effective, including after changes in premises or providers.

Frequently asked questions

Does this control require cameras everywhere?

No universal camera layout is prescribed. Select appropriate monitoring methods for the premises and risk, while addressing relevant legal and privacy requirements.

Is continuous recording the same as continuous monitoring?

Not necessarily. Recording preserves information; effective monitoring also needs the intended detection and evaluation arrangements. Explain how your chosen combination achieves the control's purpose.

How long must recordings be retained?

There is no single ISO 27001 period for all recordings. Determine a justified period using the purpose, applicable obligations and information risks, then apply deletion and access controls consistently.

Build monitoring that can be demonstrated

Discuss monitoring governance and ISMS support with Sterling. A scoped programme can combine implementation, staff learning, documentation and agreed Effivity ISO & GRC automation software, with authorised vulnerability scanning and findings review where included. Continued support helps the organisation prepare credible evidence; certification is decided independently. Enrol in ISO/IEC 27002 Information Security Controls to strengthen the link between control intent and practical verification. See the physical controls overview for related premises decisions.

Source basis and reading note. This is original practical guidance for ISO/IEC 27001:2022. Use an authorised copy for definitive requirements. Illustrative examples describe hypothetical situations, not client results. Implementation methods are distinguished from requirements; independent bodies decide certification outcomes. Issuer standard record Issuer standard record: iso.org.
Disclaimer. This guide is provided for general information only. It is not the text of the standard, not legal or professional advice, and not a representation of how any certification body will assess your organisation. Sterling International Consulting accepts no liability for any loss arising from reliance on it. Requirements are applied to each organisation's own context through an engagement; contact us to implement ISO/IEC 27001 in your organisation.