Customer Drivers

Companies start this work for different reasons. Some choose it. Some are asked.

The business stays aimed at the customer. Revenue and livelihood are not a pile of money for an attacker to spend.

Who already holds a certificate

The ISO Survey counts 96,709 valid ISO/IEC 27001 certificates and 179,877 sites as of 31 December 2024. That count includes the 2013 and 2022 editions. It is fourth among the sixteen management system standards in that survey. It counts certificates reported by accredited certification bodies. It is not every company in the world, and it is not a growth rate.

Sources: ISO Survey and IAF CertSearch.

Why you start

Some choose it. Some are asked. Companies start this work for different reasons. Here are five of them.

Percentages are from the UK ISO Standards Survey, Summer 2024 (Statius). They come from UK businesses talking about ISO registration in general, not only ISO/IEC 27001. People could pick more than one reason, so the numbers do not add to 100. They are not a Trygg forecast. Open the source (PDF).

What that survey measured about winning business is on Return on Investment. This page does not repeat it.

  • You choose it. Leadership wants the company protected before anyone asks. 68.4% wanted to improve internal processes and practices.
  • You need a certificate. A customer, a board, or your leadership team wants an independent certification body to look at the program. An ISO/IEC 27001 certificate. The independent certification body decides.
  • A customer requests. A questionnaire, a contract, or a security review. 61.4% said existing clients demanded it. 56.1% wanted it to win new clients.
  • A trade body respects your position. A trade body or a similar rule sets the requirement. 40.4% needed it to meet a trade body requirement.
  • A vendor partners with you. The partnership rests on your security position, and it works both ways. You know the specifics to ask for, and they provide an in-kind, reciprocal certificate and data protection approach. The survey gives no vendor figure, so we do not show one.

Different reasons. Same point.

The business stays aimed at the customer. Revenue and livelihood are not a pile of money for an attacker to spend. With the mission surrounded, leadership works on customers, not on reacting to attackers all year.

  • You choose it.
  • You need a certificate.
  • A customer requests.
  • A trade body respects your position.
  • A vendor partners with you.

What they look for

Whoever is asking, they look for the same three things. Each request asks for proof in its own way. Underneath, every row comes out the same.

The question is not which request to answer. It is whether one program answers all five.

This is how we read the requests. It is not a survey result.

  • You choose it. A named owner. Evidence that is current. Reviewed on a schedule.
  • You need a certificate. A named owner. Evidence that is current. Reviewed on a schedule.
  • A customer requests. A named owner. Evidence that is current. Reviewed on a schedule.
  • A trade body respects your position. A named owner. Evidence that is current. Reviewed on a schedule.
  • A vendor partners with you. A named owner. Evidence that is current. Reviewed on a schedule.

The work runs every year

The certificate is three years. The work is every year. Getting certified is one event. Keeping the certificate is a program that runs every year.

A certificate is typically granted for three years. A surveillance audit comes at least once a year, and recertification comes before the three years end. ISO/IEC 27001 asks top management to review the system at planned intervals (Clause 9.3) and to keep improving it (Clause 10). This part is a requirement, not a survey result. Certification is where we describe how an independent certification body fits.

The human side, from the same UK survey: 62.5% said the hardest part of keeping a standard was the time to administer it, 55.4% said keeping documents current, and 50% said making the system match how the business works. Most said it takes more than a day a month. Open the source (PDF).

  • Year 1. Certification audit. An independent certification body decides.
  • Year 2. Surveillance audit. At least once a year.
  • Year 3. Surveillance audit. At least once a year.
  • Before year 3 ends. Recertification. Then the three year cycle starts again.
  • What a visit looks for. A program still running. Internal audit, management review (Clause 9.3), open findings, objectives, changes, and progress on improvement (Clause 10).

Map. Disrupt. Disable. Dismantle.

This is the leadership job Trygg is built to support. Everyone on the leadership team is in it, before the incident, not only after it.

Trygg keeps the record. It does not attack an intruder on the network.

  • Map. Name the threat, the weakness it would use, who owns the response, and where the evidence sits.
  • Disrupt. Break the easy path. A control with an owner, a date, and a result that is still current.
  • Disable. Close the weakness the threat depends on, and keep the closure visible.
  • Dismantle. Take apart the habit that would let it return. An old account. A shared mailbox nobody owns. A vendor still connected. A written rule the daily work no longer follows.

Where the work lives

These are the tests and meetings leadership runs. Trygg gives each one a home in the program.

A penetration test. A specialist performs the internal and external tests. In Trygg, that record lives with BC/DR Assessments. Penetration tests shine a light where gaps exist. The portal tracks the evidence.

A phishing campaign. The campaign tests for spam and impersonation. It gives employees a chance to self-identify attacks. In Trygg, that record lives with Security Insights. Trygg partners with KnowBe4, along with other programs, to track the results.

A change review board meets regularly to make sure changes are approved and prioritized. A project review board meets regularly so initiatives are prioritized and approved before they are implemented. A quarterly review is where leaders take part in the overall solution, based on their own areas of expertise and responsibility. In Trygg, those records live with Management Reviews.

Trygg gives every event a record, an owner, and a place in the program.

Trygg does not run the penetration test, send the phishing campaign, or decide certification. Trygg does not promise that an attack will fail, that a contract will close, or that you will be certified. The independent certification body decides.

Book a demo

Why you start, and why the work runs every year.

How we think about the program, in six short steps. It plays on its own, or you can step through at your own pace.

Step 1 of 6 · Why you start

Some choose it. Some are asked.

Companies start this work for different reasons. Here are five of them.

  • 01

    You choose it.

    Leadership wants the company protected before anyone asks.

    68.4%wanted to improve internal processes and practices
  • 02

    You need a certificate.

    A customer, a board, or your leadership team wants an independent certification body to look at the program.

    An ISO/IEC 27001 certificate. The independent certification body decides.
  • 03

    A customer requests.

    A questionnaire, a contract, or a security review.

    61.4%said existing clients demanded it
    56.1%wanted it to win new clients
  • 04

    A trade body respects your position.

    A trade body or a similar rule sets the requirement.

    40.4%needed it to meet a trade body requirement
  • 05

    A vendor partners with you.

    The partnership rests on your security position, and it works both ways. You know the specifics to ask for, and they provide an in-kind, reciprocal certificate and data protection approach.

    The survey gives no vendor figure, so we do not show one.

Percentages are from the UK ISO Standards Survey, Summer 2024 (Statius). They come from UK businesses talking about ISO registration in general, not only ISO/IEC 27001. People could pick more than one reason, so the numbers do not add to 100. They are not a Trygg forecast. Open the source (PDF)

Step 2 of 6 · Same point

Different reasons. Same point.

The business stays aimed at the customer. Revenue and livelihood are not a pile of money for an attacker to spend. With the mission surrounded, leadership works on customers, not on reacting to attackers all year.

  • You choose it
  • You need a certificate
  • A customer requests
  • A trade body respects your position
  • A vendor partners with you
Your customersRevenue and livelihood
Your program
Step 3 of 6 · What they look for

Whoever is asking, they look for the same three things.

Each request asks for proof in its own way. Underneath, every row comes out the same.

Each reason for starting, and the three things it looks for
The driverA named ownerOwner, namedEvidence that is currentEvidence that is currentReviewed on a scheduleReviewed on a schedule
You choose it Yes Yes Yes
You need a certificate Yes Yes Yes
A customer requests Yes Yes Yes
A trade body respects your position Yes Yes Yes
A vendor partners with you Yes Yes Yes
The question is not which request to answer. It is whether one program answers all five.

This is how we read the requests. It is not a survey result.

Step 4 of 6 · Every year

The certificate is three years. The work is every year.

Getting certified is one event. Keeping the certificate is a program that runs every year.

  1. 1
    Year 1Certification auditAn independent certification body decides.
  2. 2
    Year 2Surveillance auditAt least once a year.
  3. 3
    Year 3Surveillance auditAt least once a year.
  4. Before year 3 endsRecertificationThen the three year cycle starts again.
What a visit should not find Frozen at the year it was certified Same risks. Same objectives. Same documents.
What a visit looks for A program still running Internal audit, management review (Clause 9.3), open findings, objectives, changes, and progress on improvement (Clause 10).

A certificate is typically granted for three years. A surveillance audit comes at least once a year, and recertification comes before the three years end. ISO/IEC 27001 asks top management to review the system at planned intervals and to keep improving it. This part is a requirement, not a survey result.

The human side, from the same UK survey: 62.5% said the hardest part of keeping a standard was the time to administer it, 55.4% said keeping documents current, and 50% said making the system match how the business works. Most said it takes more than a day a month. Open the source (PDF)

Step 5 of 6 · Leadership’s job

Map. Disrupt. Disable. Dismantle.

This is the leadership job Trygg is built to support. Everyone on the leadership team is in it, before the incident, not only after it.

Threat What could reach you NamedResponse owner
Weakness The gap it would use NamedEvidence location Closed, kept visible
Your customersThe mission
Habits that would let it come back
  • An old account
  • A shared mailbox nobody owns
  • A vendor still connected
  • A written rule the daily work no longer follows
  1. 01MapName the threat, the weakness it would use, who owns the response, and where the evidence sits.
  2. 02DisruptBreak the easy path. A control with an owner, a date, and a result that is still current.
  3. 03DisableClose the weakness the threat depends on, and keep the closure visible.
  4. 04DismantleTake apart the habit that would let it return.

Trygg keeps the record. It does not attack an intruder on the network.

Step 6 of 6 · Where it lives

Where it lives in Trygg.

These are the tests and meetings leadership runs. Trygg gives each one a home in the program.

The test or meeting Where it lives in Trygg
A penetration testA specialist performs the internal and external tests.
In TryggBC/DR AssessmentsPenetration tests shine a light where gaps exist. The portal tracks the evidence.
A phishing campaignThe campaign tests for spam and impersonation. It gives employees a chance to self-identify attacks.
In TryggSecurity InsightsTrygg partners with KnowBe4, along with other programs, to track the results.
A change review boardMeets regularly to make sure changes are approved and prioritized.
A project review boardMeets regularly so initiatives are prioritized and approved before they are implemented.
A quarterly reviewLeaders take part in the overall solution, based on their own areas of expertise and responsibility.
In TryggManagement ReviewsChange review, project review, and the quarterly review. Each meeting gets a record, an owner, and a place in the program.
Trygg Trygg gives every event a record, an owner, and a place in the program. Book a demo

Trygg does not run the penetration test, send the phishing campaign, or decide certification. Trygg does not promise that an attack will fail, that a contract will close, or that you will be certified. The independent certification body decides.

Step 1 of 6