ISO 27001:2022 Annex A 7.1 – Physical Security Perimeters Explained

Cyber security starts with where people can physically go.

Annex A 7.1 exists to ensure organisations define and protect physical security perimeters, so information and associated assets are shielded from unauthorised physical access, damage, or interference.

This control is about establishing clear physical boundaries — and controlling what crosses them.

ISO 27001

Quick Guide: Annex A 7.1 at a Glance

Annex A 7.1 of ISO 27001:2022 focuses on physical security perimeters.

At a practical level, this means:

  • Identifying physical boundaries that protect information and assets
  • Preventing unauthorised physical access
  • Reducing opportunities for theft, tampering, or damage
  • Supporting layered physical and information security controls
  • Aligning physical protection with information risk

The control does not prescribe specific technologies or layouts. It expects organisations to apply appropriate, risk-based physical boundaries.

In-Depth Guide to Annex A 7.1

What Is Annex A 7.1 and Why Does It Matter?

Information security is not purely digital.

Many serious security incidents begin with:

  • Unauthorised access to offices or facilities
  • Theft of devices or documents
  • Tampering with systems or infrastructure
  • Physical access enabling logical compromise

Annex A 7.1 ensures organisations establish physical barriers and boundaries that reduce these risks before technical controls are even tested.

This control applies to:

  • Buildings and sites
  • Rooms and secure areas
  • Locations housing information processing facilities
  • Areas where sensitive information is handled or stored

If information can be accessed physically, physical security matters.

How to Implement Annex A 7.1 Effectively

A pragmatic approach to Annex A 7.1 typically includes the following elements.

1. Define Physical Security Perimeters

Organisations should identify where physical boundaries are required, based on:

  • The sensitivity of information
  • The criticality of systems or assets
  • The likelihood and impact of unauthorised access

Perimeters may exist at multiple levels, including:

  • Site or building boundaries
  • Floor or zone boundaries
  • Individual rooms or secure areas

Clear definition supports consistent protection.

2. Use Physical Barriers to Control Access

Physical security perimeters are commonly implemented using:

  • Walls, doors, and partitions
  • Fences, gates, or barriers
  • Secure entry points

Barriers should be appropriate to the environment and the level of risk being managed.

3. Reduce Weak Points in the Perimeter

Perimeters are only as effective as their weakest point.

Organisations should consider:

  • External doors and access points
  • Windows, ceilings, and raised floors
  • Shared spaces or adjoining premises
  • Areas used infrequently or outside normal hours

Overlooked access points are a common cause of perimeter failure.

4. Support Perimeters with Monitoring and Deterrence

Physical perimeters are often supported by additional measures, such as:

  • CCTV or surveillance
  • Intruder alarms
  • Lighting and visibility controls

These measures act as both deterrents and detection mechanisms.

5. Protect Assets Within the Perimeter

Annex A 7.1 is not limited to buildings.

Organisations should also consider:

  • Physical protection of servers, network equipment, and endpoints
  • Secure positioning of devices to prevent casual access or tampering
  • Protection of paper records and removable media

Perimeter controls should align with what is being protected inside them.

6. Align Physical Security with Other Controls

Physical security perimeters work best as part of a layered approach.

They typically support:

  • Physical access control (Annex A 7.2)
  • Asset management and handling controls
  • Environmental and equipment protection
  • Logical access and monitoring controls

No single control is effective in isolation.

In-Depth Guide to Annex A 5.1

What is Annex A 5.1 and Why Does It Matter?

  • What the organisation values
  • How security decisions are approached
  • Where accountability sits
  • Aligns security with business objectives
  • Supports proportionate, risk-based decisions
  • Provides a reference point during incidents and disputes
  • Creates consistency without bureaucracy

How to Implement Annex A 5.1 Effectively

1. Define a Comprehensive Information Security Policy
  • Scope: What the policy applies to (systems, data, people).
  • Objectives: Why security is important for the business.
  • Roles & Responsibilities: Who is accountable for security.
  • Key Principles: Risk management, access control, and data protection.
2. Secure Senior Management Approval
  • Review and approve policies.
  • Ensure resources are allocated for implementation.
  • Lead by example in enforcing security policies.
3. Communicate and Train Employees
  • Include security policies in onboarding and ongoing training.
  • Ensure policies are easily accessible to all employees.
  • Encourage acknowledgment and acceptance of security responsibilities.
4. Regular Review & Continuous Improvement
  • Set a schedule for periodic policy reviews (at least annually).
  • Update policies based on business changes, new threats, or regulatory updates.
  • Conduct audits to ensure compliance and effectiveness.
5. Integrate Policies into the ISMS
  • Use it to develop more detailed security procedures.
  • Ensure policies align with other Annex A controls and broader risk management practices.
Key Differences: ISO 27001:2013 vs ISO 27001:2022
AspectISO 27001:2013ISO 27001:2022
Control StructureTwo separate controls: 5.1.1 & 5.1.2Merged into one control (5.1)
Implementation GuidanceLess prescriptiveMore detailed guidance for policy creation and alignment
Awareness & TrainingNot explicitly mentionedExplicitly requires policies to be part of training programmes
Attributes TableNot includedew attributes table for mapping policies to industry terms
Common Challenges & How to Overcome Them
  • Challenge: Employees don’t follow security policies.
  • Solution: Make policies practical and relevant to daily work. Use real-world examples in training.
  • Challenge: Policies are outdated or too generic.
  • Solution: Schedule annual reviews and update policies based on real threats and business changes.
  • Challenge: Policies are written in technical jargon.
  • Solution: Use plain language that all employees can understand.
  • Challenge: Lack of leadership buy-in.
  • Solution: Show how weak security affects business objectives—costs of breaches, loss of client trust, and legal penalties.
Final Recommendations
  • Make security policies living documents—review, refine, and update regularly.
  • Use policy training and awareness to create a security-conscious workforce.
  • Ensure policies are accessible, relevant, and easy to understand.
  • Keep policies aligned with business strategy and regulatory requirements.
  • Engage leadership in driving security culture from the top down.

Practical Considerations

Annex A 7.1 does not require:

  • Military-grade physical security
  • Identical controls at every location
  • Constant staffing or supervision

It does require organisations to:

  • Understand where physical access creates information risk
  • Define boundaries deliberately
  • Apply protection proportionate to risk

Physical security should be visible, consistent, and maintained.

Common Challenges and How to Overcome Them

  • Assuming office space is inherently secure
  • Define and protect physical boundaries explicitly
  • Ignoring secondary access points
  • Review windows, ceilings, and shared areas
  • Over-reliance on technical controls
  • Treat physical security as a foundational layer
  • Perimeters degrading over time
  • Review and maintain barriers as environments change

Physical breaches are often silent — prevention is critical.

In-Depth Guide to Annex A 5.1

What is Annex A 5.1 and Why Does It Matter?

  • What the organisation values
  • How security decisions are approached
  • Where accountability sits
  • Aligns security with business objectives
  • Supports proportionate, risk-based decisions
  • Provides a reference point during incidents and disputes
  • Creates consistency without bureaucracy

How to Implement Annex A 5.1 Effectively

1. Define a Comprehensive Information Security Policy
  • Scope: What the policy applies to (systems, data, people).
  • Objectives: Why security is important for the business.
  • Roles & Responsibilities: Who is accountable for security.
  • Key Principles: Risk management, access control, and data protection.
2. Secure Senior Management Approval
  • Review and approve policies.
  • Ensure resources are allocated for implementation.
  • Lead by example in enforcing security policies.
3. Communicate and Train Employees
  • Include security policies in onboarding and ongoing training.
  • Ensure policies are easily accessible to all employees.
  • Encourage acknowledgment and acceptance of security responsibilities.
4. Regular Review & Continuous Improvement
  • Set a schedule for periodic policy reviews (at least annually).
  • Update policies based on business changes, new threats, or regulatory updates.
  • Conduct audits to ensure compliance and effectiveness.
5. Integrate Policies into the ISMS
  • Use it to develop more detailed security procedures.
  • Ensure policies align with other Annex A controls and broader risk management practices.
Key Differences: ISO 27001:2013 vs ISO 27001:2022
AspectISO 27001:2013ISO 27001:2022
Control StructureTwo separate controls: 5.1.1 & 5.1.2Merged into one control (5.1)
Implementation GuidanceLess prescriptiveMore detailed guidance for policy creation and alignment
Awareness & TrainingNot explicitly mentionedExplicitly requires policies to be part of training programmes
Attributes TableNot includedew attributes table for mapping policies to industry terms
Common Challenges & How to Overcome Them
  • Challenge: Employees don’t follow security policies.
  • Solution: Make policies practical and relevant to daily work. Use real-world examples in training.
  • Challenge: Policies are outdated or too generic.
  • Solution: Schedule annual reviews and update policies based on real threats and business changes.
  • Challenge: Policies are written in technical jargon.
  • Solution: Use plain language that all employees can understand.
  • Challenge: Lack of leadership buy-in.
  • Solution: Show how weak security affects business objectives—costs of breaches, loss of client trust, and legal penalties.
Final Recommendations
  • Make security policies living documents—review, refine, and update regularly.
  • Use policy training and awareness to create a security-conscious workforce.
  • Ensure policies are accessible, relevant, and easy to understand.
  • Keep policies aligned with business strategy and regulatory requirements.
  • Engage leadership in driving security culture from the top down.

Final Recommendations

Annex A 7.1 is about controlling physical access before digital controls are tested.

When physical security perimeters are implemented effectively:

  • Opportunities for unauthorised access are reduced
  • Theft and tampering risks decrease
  • Other security controls operate more effectively
  • Information assets are better protected by design

Information security does not start at the firewall.
It starts at the front door, boundary, and barrier.

That is exactly what Annex A 7.1 is designed to reinforce.

In-Depth Guide to Annex A 5.1

What is Annex A 5.1 and Why Does It Matter?

  • What the organisation values
  • How security decisions are approached
  • Where accountability sits
  • Aligns security with business objectives
  • Supports proportionate, risk-based decisions
  • Provides a reference point during incidents and disputes
  • Creates consistency without bureaucracy

How to Implement Annex A 5.1 Effectively

1. Define a Comprehensive Information Security Policy
  • Scope: What the policy applies to (systems, data, people).
  • Objectives: Why security is important for the business.
  • Roles & Responsibilities: Who is accountable for security.
  • Key Principles: Risk management, access control, and data protection.
2. Secure Senior Management Approval
  • Review and approve policies.
  • Ensure resources are allocated for implementation.
  • Lead by example in enforcing security policies.
3. Communicate and Train Employees
  • Include security policies in onboarding and ongoing training.
  • Ensure policies are easily accessible to all employees.
  • Encourage acknowledgment and acceptance of security responsibilities.
4. Regular Review & Continuous Improvement
  • Set a schedule for periodic policy reviews (at least annually).
  • Update policies based on business changes, new threats, or regulatory updates.
  • Conduct audits to ensure compliance and effectiveness.
5. Integrate Policies into the ISMS
  • Use it to develop more detailed security procedures.
  • Ensure policies align with other Annex A controls and broader risk management practices.
Key Differences: ISO 27001:2013 vs ISO 27001:2022
AspectISO 27001:2013ISO 27001:2022
Control StructureTwo separate controls: 5.1.1 & 5.1.2Merged into one control (5.1)
Implementation GuidanceLess prescriptiveMore detailed guidance for policy creation and alignment
Awareness & TrainingNot explicitly mentionedExplicitly requires policies to be part of training programmes
Attributes TableNot includedew attributes table for mapping policies to industry terms
Common Challenges & How to Overcome Them
  • Challenge: Employees don’t follow security policies.
  • Solution: Make policies practical and relevant to daily work. Use real-world examples in training.
  • Challenge: Policies are outdated or too generic.
  • Solution: Schedule annual reviews and update policies based on real threats and business changes.
  • Challenge: Policies are written in technical jargon.
  • Solution: Use plain language that all employees can understand.
  • Challenge: Lack of leadership buy-in.
  • Solution: Show how weak security affects business objectives—costs of breaches, loss of client trust, and legal penalties.
Final Recommendations
  • Make security policies living documents—review, refine, and update regularly.
  • Use policy training and awareness to create a security-conscious workforce.
  • Ensure policies are accessible, relevant, and easy to understand.
  • Keep policies aligned with business strategy and regulatory requirements.
  • Engage leadership in driving security culture from the top down.

The Annex Control Table

ISO 27001:2022 Organisational Controls
ISO 27001:2022 Technological Controls