Best Compliance Software

Practical guide · November 16, 2026

ISO 27001 scope: a worked example for a small company

A small company can define an information security management system around a particular service, but the boundary needs to reflect how that service actually operates. A useful scope names the service, people, locations and supporting systems—and explains the dependencies that cross its boundary. “Our production application” is a starting point, not a complete description.

ISO describes ISO/IEC 27001 as a standard for managing information security risks across people, processes and technology. A server list alone does not describe that management system. ISO’s overview

A scope statement you can challenge

Hypothetical example: Northbridge Scheduling is a 24-person company with one cloud-hosted appointment service, remote employees and a small office. This is a drafting exercise, not an auditor-approved scope.

The ISMS covers the development, operation and customer support of Northbridge Scheduling’s hosted appointment service. It includes the employees and contractors performing those activities, their managed work devices, the company office, remote working arrangements, production and development environments, and the identity, source-control and support systems used to deliver the service. External hosting and other suppliers are managed through the company’s supplier and access-control processes.

The statement creates questions that someone can answer with evidence:

Boundary Evidence to attach Question to resolve
Hosted service Architecture and data-flow diagrams Do exports and backups appear?
Development Repository and deployment access lists Can a contractor change production code?
Customer support Support-tool access and handling procedure Can support tickets contain customer data?
Remote work Device inventory and remote-work procedure Do personal devices access covered information?
Suppliers Responsibility assignments and supplier records Which safeguards does the company still operate?

The table is an editorial review tool. It helps turn a scope sentence into an operational boundary; it is not a substitute for the standard or an audit.

The paragraph above is a working ISMS boundary description. Certificate wording may be shorter; retain the detailed boundary, interfaces and dependencies behind it and agree the certification wording with the certification body. A concise certificate cannot replace the operational scope record.

Three exclusions to challenge

“The cloud provider is outside our scope, so hosting is excluded.” Separate the provider’s facilities from your own responsibilities for configuration, permissions, data and supplier oversight. Outsourcing a function does not make its relationship to the service disappear. NQA’s practitioner presentation discusses scoping and the role of outsourced services. NQA presentation and publisher transcript

“HR is excluded because it does not develop the product.” Ask who authorizes new employees, changes roles and tells IT that someone has left. You may need the relevant HR process inside your management arrangements even if other HR activities sit outside the chosen service boundary.

“The office is excluded because production runs elsewhere.” Check what actually happens there. If staff administer production from that office, explain how their access and equipment are controlled. A location’s role matters more than whether it contains a server.

These are challenges to investigate, not universal rulings that every department or location must appear identically in every certificate.

Scope and control selection answer different questions

The scope describes what the ISMS covers. The Statement of Applicability records the organization’s control-selection decisions. Do not use a narrow scope sentence to hide a dependency that still affects the covered service. For a practical discussion of boundaries and dependencies, see Advisera’s scope guide.

Before sending a draft to a certification body, ask the service owner, IT lead and people-operations owner to trace one customer record and one employee’s access through the boundary. Record every unexplained handoff. Resolve those handoffs before polishing the certificate wording.

Research basis: public standards overview and practitioner guidance, including a publisher-provided webinar transcript; no audit or certification assessment performed. Evidence reviewed November 16, 2026.