ISO/IEC 27001 certification assesses an information security management system, commonly called an ISMS. It concerns how an organisation manages risks to information through people, processes and technology. A useful assessment starts with the information and services that matter. A certificate with an impressive corporate name can still cover a narrower activity than a prospective customer expects.
The current published edition is ISO/IEC 27001:2022, with a 2024 amendment addressing climate considerations in management system context. Check ISO’s current record for the edition and amendments. This guide explains the practical decisions behind the scope, risk treatment and evidence. It does not claim that certification prevents all breaches or establishes compliance with every privacy or cybersecurity law.
Begin with a service a customer can recognise
Choose a concrete starting point: the payroll service, hosted application, research platform or internal information service being managed. Describe what it does, who relies on it and what could happen if information were disclosed, altered or unavailable. That description makes security priorities understandable to commercial and operational managers, rather than leaving them solely with the IT team.
Then follow the information. Identify where it enters, where it is stored, who accesses it, which suppliers handle it and how it is removed. Include paper records and conversations where relevant. A business may protect its production database carefully while overlooking exported spreadsheets, support attachments or information shared with an external implementation partner. Those handovers deserve deliberate decisions.
Read the scope before interpreting the certificate
Identify the legal entity, services, organisational units, locations and boundaries proposed for certification. Establish how dependencies outside the boundary are managed. If one subsidiary operates a platform and another provides customer support, the relationship needs explanation. A narrow scope is not automatically improper, but its public description should allow a buyer to understand what was assessed.
For a supplier review, compare the certificate with the actual service in your contract. Ask whether the relevant product operations, support teams and hosting arrangements are included. Do not infer that every subsidiary, cloud region or product is covered because the parent company displays a certificate. Request a clear explanation where a schedule or scope description is ambiguous.
Put ownership beside each important information flow
This original planning table helps a team expose decisions before selecting controls. It is not a mandatory ISO template.
|
Information flow |
Business question |
Evidence to investigate |
|
Customer onboarding |
Who may collect which information? |
Agreed requirements and access decisions |
|
Privileged administration |
Who can make a sensitive change? |
Authorisation and activity records |
|
Supplier processing |
What is the provider responsible for? |
Contract, assurance and service boundaries |
|
Incident handling |
Who decides and communicates? |
Escalation arrangements and exercised roles |
|
Service termination |
What happens to access and data? |
Offboarding and retention decisions |
Choose one flow and ask the business owner to explain the risk. If everyone assumes another department owns the decision, resolve that ambiguity first. A security product cannot compensate for an unassigned responsibility.
Distinguish risk assessment from a catalogue of threats
A useful risk assessment connects information, threats, vulnerabilities and consequences within the organisation’s circumstances. The purpose is to support decisions about treatment and acceptance. A list containing every possible attack but no explanation of the business consequence is difficult to prioritise. Equally, a low score is unhelpful when nobody can explain its basis.
Agree an approach that different assessors can apply consistently enough for meaningful decisions. Identify risk owners, treatment actions and acceptance authority. Revisit assumptions after material changes or incidents. A practical challenge is to ask what evidence would make management change its view. That question helps distinguish a considered risk decision from a number chosen merely to close a spreadsheet entry.
Understand the Statement of Applicability
The Statement of Applicability explains the controls determined necessary and the relevant inclusion, implementation and exclusion reasoning required by the standard. Annex A is a reference set for checking that necessary controls have not been overlooked. It is not a rule that every listed control must be implemented identically in every organisation. Additional controls may be necessary for particular risks or obligations.
Do not confuse ISO/IEC 27001 with ISO/IEC 27002. The former provides ISMS requirements; the latter offers information security control guidance. ISO’s record for ISO/IEC 27002 explains this relationship. A buyer may request information about applicable controls through an appropriate confidentiality arrangement, but should not assume that every supplier will publish sensitive implementation detail openly.
Evaluate controls through ordinary operating events
Select evidence showing how controls work when people join, change roles, release software, investigate alerts or leave the organisation. Ask whether access decisions are reviewed, critical changes receive appropriate scrutiny and backups can support the required recovery. The exact checks depend on the service and risk. Avoid reducing the system to screenshots taken just before the audit.
Look at exceptions. Who may authorise an urgent change? What happens when a supplier cannot meet the security requirement? How is a temporary access arrangement removed? Exceptions are often where formal rules and practical work diverge. Record the decision, limits and follow-up needed so that a temporary solution does not quietly become an uncontrolled permanent arrangement.
Examine suppliers and cloud boundaries carefully
A cloud provider’s certificate can support assurance, but it does not automatically certify its customer’s configuration, access decisions or application. Map the division of responsibilities. Determine who manages identities, encryption choices, logging, incident communications and deletion. Ask for assurance relevant to the service being used rather than collecting unrelated certificates.
NIST’s supply chain risk management guidance provides a complementary framework for understanding supplier dependencies. It is not a substitute for ISO/IEC 27001 requirements. In purchasing, translate important dependencies into contract and oversight questions: notification of significant changes, access to relevant evidence, support during an incident and workable arrangements when the service ends.
A fictional example: the support export outside the platform
Imagine a fictional software company with strong controls around its hosted application. Support staff export customer records into a shared spreadsheet to investigate service problems. The spreadsheet is kept longer than intended, and access is broader than the application’s normal permissions. The security boundary described in sales material does not explain this supporting process.
A useful response would review the information flow, assess the risk, change access and retention arrangements where needed, and train the people involved. Management should then check whether similar exports occur elsewhere. This fictional example illustrates a boundary and operating-control issue. It is not a breach report, a prescribed technical configuration or evidence about a named company.
Implement the ISMS as a management process
Obtain the requirements standard, agree sponsorship and define scope. Review obligations and interested-party needs, assess risks, determine treatment and establish the necessary controls. Use existing service-management and engineering records where they provide reliable evidence. Assign responsibility for maintaining the risk assessment and Statement of Applicability as operations change.
Before seeking certification, operate the arrangements, evaluate performance, conduct internal audits and hold a management review. Audit across business and technical functions rather than interviewing only the security lead. Record findings and verify corrective actions. The NIST Cybersecurity Framework 2.0 can support wider security discussions, but its use should not be represented as ISO certification or as an interchangeable requirements standard.
Ask certification bodies about relevant expertise
Tell CB Name about your services, development activities, information sensitivity, locations and supplier dependencies. Ask how the audit will address the proposed boundary and whether the team understands comparable technology and operating arrangements. Confirm relevant accreditation and the exact certificate issuer. ISO/IEC 27006-1:2024 provides additional requirements for bodies auditing and certifying ISMS, as explained in ISO’s record.
The certification-body directory can help identify candidates, but each provider’s approval needs independent checking. Compare audit coverage and commercial terms on the same information. Clarify how sensitive evidence will be handled and whether remote assessment is appropriate for particular activities. Competent assessment requires meaningful access to evidence, with confidentiality arrangements that suit the risks.
Budget for the system you need to maintain
Costs can include internal time, security improvements, specialist advice, training, tools and external assessment. Existing technical maturity can make a large difference. A certificate fee alone cannot reveal the work needed to close gaps. Obtain quotations based on accurate scope information and ask what additional work or charges could arise.
After certification, review changes in products, hosting, suppliers, acquisitions and significant incidents. Keep public statements aligned with the certified boundary. For supplier checks, use the certificate verification guide. A current certificate is useful evidence about the system assessed, but it does not replace service-specific due diligence, privacy analysis or technical assurance appropriate to the purchase.
Give procurement a service-specific assurance brief
Before contacting providers, write a short brief describing the service, information involved and consequences of failure. Identify any customer or contractual security requirements separately from preferred controls. This helps a prospective certification body understand the business and helps buyers avoid collecting certificates unrelated to their actual dependency.
For an existing supplier, ask focused questions rather than demanding every internal security document. Which part of the service is certified? What assurance is available for important outsourced components? How are significant incidents and service changes communicated? Agree a proportionate confidentiality arrangement for sensitive evidence. The aim is useful assurance, not disclosure that creates unnecessary security risk.
Record the decision your organisation makes after reviewing the evidence. A valid certificate can coexist with a contractual gap, an unsupported recovery expectation or a configuration responsibility that belongs to you. Assign the remaining actions and an owner. Revisit them when the service changes or the contract renews. A procurement file containing a certificate but no explanation of how it relates to the purchase is difficult to defend. A concise assurance brief and decision record make the boundary, accepted limitations and continuing responsibilities much easier for future reviewers to understand.
References and information note
· ISO/IEC 27001: current requirements standard
· ISO/IEC 27002: information security control guidance
· ISO/IEC 27006-1: ISMS certification-body requirements
· NIST: cybersecurity supply chain risk management
· NIST: Cybersecurity Framework 2.0
This global guide does not replace the standard, a security assessment or legal advice. Examples and tables are practical illustrations. Certification does not guarantee freedom from incidents. Send factual corrections through the contact page.
