ISO Compliance: How to Build an ISO 27001 ISMS Step by Step
ISO compliance for mid-market firms comes down to an ISO 27001 ISMS with a defined scope, a risk register and one accountable owner. This is how to build it before the audit.
ISO 27001 compliance means running a documented information security management system (ISMS) within a defined scope. Certification means an independent body has audited it. The certificate is the output, not the program. Start with the data boundary and risk register, then build controls you can prove are operating.
If a customer questionnaire has put certification on your agenda, your first decision is who will own the ISMS, not which policy template to buy.
Why does procurement ask for ISO 27001 certification?
Procurement uses certification as a shortcut. An independent body has checked your security management system against a recognized standard. That gives the customer more to assess than your answers on a questionnaire.
Get the customer's requirement in writing before you commit resources. Some customers require a certificate covering the service they buy. Others want evidence of specific controls. Those are different deliverables, and building the wrong one can cost months.
What does an ISMS include before you can certify?
An ISMS ties each information risk to a control and to the records that show the control works. Before certification, you need these elements:
- A defined scope stating what the ISMS covers.
- A risk assessment and treatment process, supported by a risk register.
- A Statement of Applicability explaining which Annex A controls apply and justifying exclusions.
- Policies tied to identified risks and named owners.
- Records showing that controls operated.
- An internal audit and management review.
The certificate covers only its stated scope. It does not automatically cover every product or system you operate. Confirm the current edition of ISO/IEC 27001 on the ISO website, then ask your certifying body which edition it will audit against.
How do you choose the scope of certification?
Start with the customer data, not the product name. A scope drawn around the team procurement recognizes can miss the infrastructure supporting that team's work. A narrow certificate is not useful if it excludes the service your customer needs assessed.
Map where the data lives before drawing the boundary
Trace customer data from collection through deletion. Record where it is stored and who can access it, backups included. Use that map to define the boundary and identify dependencies outside it.
Include vendors with access to the data
Third-party software holding customer or employee records belongs in the risk assessment. Include your payroll provider and support platform where relevant. A vendor incident can expose your records even when your own systems remain untouched.
A supplier does not automatically become part of your certified organization. You still need to understand the dependency, assign responsibility for reviewing it and retain evidence of the checks you perform.
Why build the risk register before writing any policy?
The risk register gives each policy a reason to exist. Record the exposure, its potential consequences, the person accountable and the treatment decision. If you accept a risk rather than reduce it, document who approved that decision.
Policies written first tend to describe an organization that does not exist. An auditor can compare the procedure with actual records and spot the mismatch. Our cyber risk assessment services guide explains what a useful assessment should contain. Our enterprise security risk management programs connect information security risks to the wider business.
Which policies should you write first, and who owns them?
Write the policies your risks require and your people can follow. An access review policy, for example, needs a named reviewer and a dated record of each review. A document without an operating process is shelfware.
Name one accountable executive for the ISMS. That person does not need to perform every control, but must have authority to assign work and resolve missed commitments. A committee can support the owner; it cannot replace one.
Start with the highest-ranked risks. If former employees retain access to customer records, fix the access removal process and document it before polishing lower-priority policies. Where you lack internal cybersecurity leadership, our virtual CISO services provide compliance program ownership.
When should the internal gap audit run, and what does it test?
Run the internal audit after controls have produced records, with time left to correct findings. The week before the certification audit is too late to discover that nobody performed the access reviews.
A readiness gap assessment can identify missing requirements early. The formal internal audit needs to test whether the ISMS meets its requirements and operates effectively. Relevant evidence includes:
- Access reviews showing who performed the review and what changed as a result.
- Training records showing completion against your requirements.
- Incident records and tabletop notes, including assigned follow-up work.
- Supplier security reviews for relevant dependencies.
- Management review minutes showing decisions and assigned actions.
- Risk register updates and approved treatment decisions.
For Texas teams, account for winter disruption and holiday absences when scheduling reviews. Confirm that decision-makers and deputies can attend. Recovery planning also needs to address unavailable staff and suppliers, issues covered by business continuity.
What do Stage 1 and Stage 2 certification reviews check?
Stage 1 examines readiness and ISMS design. Stage 2 tests implementation and effectiveness. Finished documents alone do not establish that the system operates.
| Review | What it asks | What can go wrong |
|---|---|---|
| Stage 1 | Is the ISMS designed and documented? Is the organization ready for Stage 2? | The scope misses relevant dependencies, or control choices lack justification. |
| Stage 2 | Does the ISMS operate effectively, with records to support it? | Policies exist without evidence of implementation, or identified problems remain unresolved. |
What Stage 1 checks
The reviewer examines your scope, risk process, Statement of Applicability and supporting documentation. These must describe the same operation. If your risk assessment identifies a supplier dependency but your scope ignores it, expect questions.
Treat Stage 1 as a real review, not a rehearsal. Readiness concerns can affect the timing of Stage 2. Build time into your customer commitment to address what the reviewer finds.
What Stage 2 tests
The reviewer samples evidence and interviews people to establish whether the documented system works. A training policy is not a completion record. An incident response plan is not evidence that the team has tested it.
Before Stage 2, check that records match your stated procedures. If a policy requires a review every quarter, the auditor will expect evidence consistent with that commitment. Do not write a schedule your team cannot sustain.
How do you keep the ISMS running after certification?
Assign a review cadence based on risk and applicable requirements. Name an owner for each control and record completed reviews, exceptions and corrective actions. Reassess the scope when a new product, acquisition or supplier changes how you handle information.
Surveillance visits and recertification test the system after the initial project team has moved on. Certification is not proof that you cannot be breached. Our how we work page describes our approach to operating a security program rather than stopping at an assessment.
Which decision should you make this quarter?
Name the accountable executive and confirm the customer's requirement. Then map the data boundary. Without those decisions, you risk buying controls for the wrong scope or producing documents nobody owns.
We run security programs across 13 risk domains and report directly to the board. We are Texas DPS-licensed and CPP, CISSP, CISM credentialed. We have been operating since 2013.
Bring your questionnaire and deadline to a 30-minute risk discussion, or send an inquiry identifying the service your customer wants covered and who currently owns security.
Frequently asked questions
What is ISO certification?
ISO certification is independent confirmation that a management system meets the requirements of a particular ISO standard. ISO itself does not certify organizations; certification bodies do. For ISO/IEC 27001, the certificate applies to the stated scope of the information security management system.
What is the ISO standard for compliance?
No single ISO standard covers every compliance obligation. ISO/IEC 27001 addresses information security management and is commonly requested in customer security questionnaires. Ask the customer which standard, edition and scope it requires before starting a certification project.
What is the ISO risk management standard?
ISO 31000 provides risk management guidelines; it is not a certification standard. ISO/IEC 27001 requires information security risk assessment and treatment as part of the ISMS. Certification against ISO/IEC 27001 does not require separate ISO 31000 certification.
What is ISO 9001 in brief?
ISO 9001 specifies requirements for a quality management system. It addresses consistent delivery and improvement, rather than serving as an information security certification. An ISO 9001 certificate does not substitute for ISO/IEC 27001 when a customer requires the latter.
Total 360 Security provides virtual Chief Security Officer, vCISO, and Enterprise Security Risk Management programs for mid-market organizations. They design, run, and report security programs covering all 13 risk domains rather than just offering advisory decks or point solutions. The firm is Texas DPS-licensed with CPP, CISSP, and CISM credentials.
Serving Texas, California, Nevada, New Mexico.
More from the blog
10 min read
Identity Access Management Software: What to Govern First
A practical order for identity access management software: define privileged access, name an owner, inventory raw exports and review each quarter before buying a tool.
Read article7 min read
SOC 2 Audit: What Type II Requires and Who Owns Each Control
A SOC 2 audit is an independent CPA examination of your controls against the AICPA criteria. Here is what a Type II report requires, who owns each control and what evidence to keep.
Read article7 min read
Compliance Monitoring: What to Check Monthly and Quarterly
Compliance monitoring is the ongoing check that your operations follow the rules that apply to you. This guide sets a monthly evidence set, a quarterly sampling routine and clear ownership for every exception.
Read article