Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
Set rules for working in secure areas (e.g. no photos, no unattended visitors).
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
Working in secure areas fails when people treat a protected room like an ordinary office and rules stay informal. Teams should turn the procedure into practical access expectations for staff, contractors, and escorts, especially where sensitive media, systems, or conversations are present. Record exceptions, because unmanaged one-off access is a common source of avoidable exposure and weak accountability.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Unescorted visitor access was allowed in a server room without a logged escort, room entry record, or manager approval for the exception.
Photography and screen-capture restrictions were not posted or briefed, so contractors could use phones in areas handling sensitive assets.
A two-person rule for sensitive work existed informally but had no task log, making it impossible to prove who witnessed or verified the operation.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Define secure-area entry conditions in the procedure: authorised roles, escort duties, badge rules, visitor sign-in, and when a second person must be present for sensitive operations. Tie each condition to the asset type in the room, such as servers, backup media, prototypes, or confidential discussions, so staff understand why a restriction exists and when it changes.
Use practical tools that fit the site: a visitor register, temporary badges, door access logs, CCTV where permitted, and a room checklist for end-of-day checks. For higher-risk rooms, keep a simple operations log naming the activity, people present, start and finish time, and any deviation that was approved by the facilities or information security owner.
Assign accountability clearly. Facilities can maintain the physical controls, the department manager can approve special access, and the asset owner can define what is sensitive enough to require escorts or dual control. Train reception, cleaners, and maintenance teams too, because secure-area breaches often happen through trusted support roles rather than core users.
Review the rules after incidents, renovations, or changes in occupancy. If a room starts hosting new information types, update signage, escort rules, and access lists promptly. Keep evidence of periodic walkthroughs, exception approvals, and any follow-up where a breach was observed, then use that record to improve the procedure and reinforce behaviour.
What an auditor will ask to see
Signed visitor logs showing date, time, host, escort, and room visited for secure-area access.
A secure-area checklist or end-of-day inspection record confirming screens, papers, and media were controlled.
Approved exception request or sensitive-operation log documenting a two-person activity and the named witnesses.
Baseline documents in the kit
These free kit documents help you document or evidence A.7.6. Each one is tailored to your organization when you build your kit.
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.