Compliance

Phase 1, Phase 2, then keep it running

A fixed-price gap analysis, remediation through to your audit, and upkeep after it. All in a workspace you keep.

All compliance →
Security

Testing, review and leadership

Led by a published security researcher with five CVEs. A findings report, a letter of attestation for your buyers, and a retest of your fixes.

All security →
Who we help

Prove you are secure

To the people you sell to, raise from or answer to.

All industries →
Resources

Learn the space

Original research, free tools, and plain-language guides on security and compliance, from a published security researcher.

Read the blog →
Compliance

ISO 27001 Implementation Consultant: Contract Work Building an ISMS

An ISO 27001 implementation consultant on contract builds the client's information security management system so it can pass certification: defining scope, running the risk assessment and treatment, writing the Statement of Applicability against the 93 Annex A controls, setting up internal audit and management review, and preparing the client for Stage 1 and Stage 2 with an accredited certification body.

Implementation is not auditing

There are two kinds of ISO 27001 contract work, and they pull in opposite directions. An auditor examines a management system and reports on whether it conforms. An implementer builds one. Our post on becoming a freelance ISO 27001 auditor in Canada covers the audit side, including certification body work and internal audits. This post is about implementation, which is where most contract ISO work sits for consultants who work with small and mid-sized companies.

The difference matters for independence. If you implemented the ISMS, you should not perform the client's certification audit, and you should think carefully before acting as its internal auditor. Many implementers do internal audits for other clients and stay out of them for their own.

The management system comes first

New implementers often start from Annex A because it looks like a checklist. That is backwards. ISO/IEC 27001:2022 certifies a management system, and the requirements that the certification body tests first are in clauses 4 to 10:

  • Clause 4, context. Internal and external issues, interested parties and their requirements, and the scope of the ISMS. The 2024 amendment added that organizations determine whether climate change is a relevant issue, which most small clients can address in a sentence, but it does need addressing.
  • Clause 5, leadership. Top management commitment, an information security policy, and assigned roles and responsibilities.
  • Clause 6, planning. Risk assessment and treatment, information security objectives, and planning of changes.
  • Clause 7, support. Resources, competence, awareness, communication and documented information.
  • Clause 8, operation. Operating the processes, carrying out risk assessments at planned intervals and implementing the treatment plan.
  • Clause 9, performance evaluation. Monitoring and measurement, internal audit and management review.
  • Clause 10, improvement. Nonconformity, corrective action and continual improvement.

A client with excellent technical controls and no working management system will not be certified. A client with a modest control set and a management system that genuinely runs often will.

Scope is a business decision

Scope defines what the certificate covers, and it is the first thing a buyer reads on it. The implementer's job is to help the client choose a scope that is honest, useful to their customers and achievable. That means naming the products or services, the locations, the teams, the technology and the interfaces with things outside scope, such as a parent company or outsourced functions.

Two common traps: a scope so narrow it does not cover what customers care about, and a scope that includes every entity and site in year one when the client has no capacity to run the ISMS that widely. For multi-site clients, the post on ISO 27001 scope across multiple sites covers the options.

Risk assessment and treatment

Clause 6.1.2 asks the client to define and apply a risk assessment process with criteria for accepting risk and for performing assessments, so that repeated assessments produce consistent and comparable results. It does not prescribe a method. Asset-based and scenario-based approaches both work. Pick one the client can repeat without you in the room.

Practical advice from the implementer's chair:

  • Keep the risk criteria simple. A five-by-five matrix with clear definitions beats an elaborate model nobody can apply consistently.
  • Name risk owners who actually have authority over the risk. Clause 6.1.2 requires owners, and the certification body will ask them about it.
  • Write risks in business terms. "Customer data exposed through misconfigured storage" is a risk. "Cloud" is not.
  • Have risk owners approve the treatment plan and accept residual risk, as clause 6.1.3 requires. Keep the record.

ISO/IEC 27005 gives guidance on information security risk management if a client wants a reference, but it is guidance, not a requirement.

The Statement of Applicability

The Statement of Applicability (SoA) is the document that links risk treatment to Annex A. Under clause 6.1.3, the client determines the controls needed to treat its risks, compares them against Annex A to check nothing necessary has been missed, and produces an SoA listing the necessary controls, the justification for including them, whether they are implemented, and the justification for excluding any Annex A controls.

The 2022 edition has 93 Annex A controls in four themes: organizational, people, physical and technological. ISO/IEC 27002:2022 gives implementation guidance for each. A few points that save clients trouble:

  • Exclusions need real reasons tied to scope and risk. "Not applicable" with no justification draws questions.
  • Implementation status should be true on the day of the audit. Mark partly implemented controls honestly and track them in the treatment plan.
  • Keep the SoA consistent with the risk register. Auditors trace from one to the other.

Our post on the Statement of Applicability, explained with an example shows the structure a buyer and auditor expect.

Policies, procedures and making it run

ISO 27001 requires certain documented information, including the scope, the information security policy, the risk assessment and treatment processes and their results, the SoA, objectives, evidence of competence, and records of monitoring, internal audit, management review and corrective action. Beyond that, document what the client needs to operate consistently. Avoid producing a binder of procedures that describe a company the client is not.

The harder part is operation. The ISMS has to run before the Stage 2 audit: training delivered and recorded, access reviews done, suppliers assessed, incidents logged and handled, metrics reported, objectives tracked. Build a calendar of recurring activities and make sure each has an owner and leaves a record.

Internal audit and management review

Clause 9.2 requires an internal audit program covering the ISMS at planned intervals, with auditors who are objective and impartial. Clause 9.3 requires top management to review the ISMS, with defined inputs such as audit results, changes, nonconformities, monitoring results and opportunities for improvement. Both must happen before the certification audit, and the certification body will look at the records.

For a small client, the internal audit often comes from an outside party because nobody inside is independent of the ISMS. That can be another consultant or a separate firm, not usually the person who built it. Management review is the client's own meeting, but you can prepare the agenda and inputs. Keep the minutes specific: decisions, actions and owners. The post on clause 9.2 internal audit covers the audit program in more detail.

Stage 1, Stage 2 and after

Certification is done by an accredited certification body. In Canada, accreditation for ISO 27001 certification bodies comes through the Standards Council of Canada or another accreditation body that is a member of the international accreditation arrangements. Help the client confirm accreditation before they sign, since an unaccredited certificate is often rejected by buyers.

Stage 1 reviews documentation and readiness: scope, risk methodology, SoA, policies, internal audit and management review records. The auditor decides whether the client is ready for Stage 2 and raises concerns to fix. Stage 2 tests whether the ISMS is implemented and effective, with interviews, sampling and observation across the scope. Nonconformities need corrective action before the certification decision.

The certificate is valid for three years, with surveillance audits in the intervening years and a recertification audit at the end of the cycle. Many implementers stay on lightly through the first surveillance cycle to help the client keep the ISMS running without them.

What makes a good implementer

  • Knowing the clauses cold and being able to explain them without jargon.
  • Restraint. The smallest ISMS that genuinely meets the standard and suits the business is usually the right one.
  • Technical literacy across cloud, identity, endpoints and development practices, so the controls are realistic.
  • Facilitation. Risk workshops and management reviews go better with someone who can run a room.
  • Knowing when to step back so the client owns the system after you leave.

ISO 27001 Lead Implementer training is a common starting point, and Lead Auditor training helps implementers understand what will be tested. Neither replaces having built or run an ISMS.

Where the TrazTech Associate Network fits

We run the TrazTech Associate Network, so weigh this accordingly. The Associate Network is how TrazTech brings independent practitioners into client work. ISO 27001 implementation sits in the compliance readiness practice, and ISO 27001 internal audits sit in audit and assurance.

Associates are independent contractors, not employees, remote in Canada or the US, part-time or full-time, with no exclusivity. You need at least five hours a week, and if you are employed, your employer must allow side work. There is no experience minimum; newer associates are paired with a paid senior mentor.

Applying takes about five minutes. A verified credential such as ISO 27001 Lead Auditor, CISA or CISSP puts you in the fast lane and skips the simulated assessment. Otherwise you complete a simulated client engagement of about three hours of work, with 72 hours to submit, followed by a selection call and portal setup with the agreement signed online.

Work comes as fixed-scope work orders. You see the scope and the fee before you accept and can decline. The fee is fixed per milestone and agreed before work starts, and payment goes out every Friday by Interac e-Transfer or against your own invoice in CAD or USD. Larger engagements run as teams with a Lead, coverage checklists keep work consistent, and a TrazTech Principal reviews and signs off every deliverable before the client sees it. You also get a TrazTech email address, a verified credential, paid Lead reviews, paid mentoring, referral bonuses and a path from Associate to Senior, Lead and the core team. Work follows client demand in your practice, so approval does not guarantee volume. All open roles are on the careers page.

Common questions about ISO 27001 implementation contract work

Can an ISO 27001 implementation consultant also do the certification audit?

No. Certification audits are performed by an accredited certification body, which must be independent of anyone who implemented the ISMS. An implementer can support the client during the audit but cannot be the auditor.

Do I need Lead Implementer certification for ISO 27001 contract work?

It is not a legal requirement. Lead Implementer or Lead Auditor training is widely recognized and helps a CV get read, but firms and clients weigh hands-on ISMS experience more heavily.

How many Annex A controls are in ISO 27001:2022?

There are 93 controls in four themes: organizational, people, physical and technological. The Statement of Applicability records which are needed, why, whether they are implemented, and why any are excluded.

What is the difference between Stage 1 and Stage 2?

Stage 1 reviews documentation and readiness, including scope, risk methodology and the Statement of Applicability. Stage 2 tests whether the ISMS is implemented and operating effectively across the scope, through interviews, sampling and observation.

Should the implementer run the client's internal audit?

Usually not. Clause 9.2 requires internal auditors to be objective and impartial, and auditing a system you built is hard to defend. A separate consultant or firm is the cleaner choice.

Build ISMSs as an independent associate. The TrazTech Associate Network offers fixed-scope ISO 27001 work orders, with the scope and fee shown before you accept. Applying takes about five minutes.

Apply to the networkSee the role

Do this work with TrazTech

The TrazTech Associate Network is for independent security and compliance practitioners: scoped client work, no exclusivity, feedback after every job and a published path to the core team.

Apply to the network Open roles How it works