Skip to content

How we achieved ISO/IEC 27001

Three founders, all 21, and eight weeks of building. What it took to put an information security management system in place, pass a UKAS-accredited audit and keep it running.

Start reading
Case study · ISO/IEC 27001

At a glance

Certified
19 October 2026
Standard
ISO/IEC 27001:2022
Certification body
Tempo Audits, UKAS accredited
Certificate
TA-01-BAL-191026
Time from start to certificate
Eight weeks of building, from 25 August to 19 October 2026, after a month of research and choosing an auditor
Audit result
  • 0major findings
  • 1minor finding
  • 1suggestion
With a corrective action plan Tempo accepted
Led by
Deen Aslam (project lead), with co-founders Kristiyan Andreev (technical controls and operations) and Theo Coleman (development)
Scope
The design, custom development, integration, deployment, operation, maintenance and support of software applications, workflow automation and AI-enabled solutions, including cloud-hosted client systems
Check the certificate

Case study · November 2026

All certifications

Why we did it

We wanted every client we work with, now and in future, to see how seriously we take security: not only how we protect their information, but how the whole company works. The three of us who started BespokeWorks are all 21, and we know what people might assume about a team like ours. We wanted to show that we do things properly.

Nothing forced us to. In the tenders we were bidding for in July, Cyber Essentials, which we already held, was the pass-or-fail requirement, and ISO 27001 was usually scored rather than required. Few small firms go further: in the government’s Cyber Security Breaches Survey 2025/26, 5% of micro businesses said they follow ISO 27001. We did it because we wanted to.

Where we started

I started in July by trying to understand what we were getting ourselves into: what the standard asks for, how the audits work, and which certification bodies are accredited to do them. I asked several for quotes and chose Tempo Audits at the start of August. The building began on 25 August.

That day we had a Cyber Essentials certificate, three laptops, no office, a lot of cloud services and no management system. The first day went on walking through all 93 controls in Annex A of the standard, scanning our laptops, code repositories and cloud accounts, and writing down every risk we could see. There were 27 by the end of the day.

Two weeks later, an honest review counted where we really were. Every one of our 24 policy documents was still a draft. We had identified and ranked our risks, and work on them had only just begun. And we had a single dated record of anything actually happening.

That last number was the real gap. Writing a policy that says we review access every quarter takes an afternoon. An auditor wants to see the review: who did it, on what date, what they found and what they removed.

The other gaps were the ordinary ones for a small team that grew quickly. Our everyday accounts carried admin rights. The same person granted access and checked it. Three functional mailboxes we no longer needed were still live. Our backups ran, but nobody had proved we could restore from them.

Illustrative still life of a squared stack of plain printed pages beside a closed laptop, a fountain pen and a cup

“Security isn’t something we add at the end. It’s how we work every day, and we wanted every client to see that the processes keeping their information safe are real, and checked by someone independent every year.”

Deen Aslam, Founder and Chief Executive

What we put in place

Everything lives in one private Git repository: the manual, 13 policies, a device agreement, 5 procedures, our registers of assets, risks, suppliers and incidents, and the Statement of Applicability, which records which of the standard’s 93 controls apply to us and why. 89 do; the four we excluded are physical controls for premises we don’t have. By certificate day the repository held more than 700 commits.

Figure 1 · Statement of Applicability

Organisational 37People 8Physical 14Technological 34

89of 93 apply

Of the 93 controls in Annex A of the standard, 89 apply to us. The four we excluded are physical controls for premises we don’t have.

Organisational
37 controls
People
8 controls
Physical
14 controls, 4 excluded
Technological
34 controls

Each petal is one control, in the four themes of Annex A. Where a petal sits inside its arc carries no meaning.

ISO/IEC 27001:2022, Annex A, and the BespokeWorks Statement of Applicability.

Of the 93 controls in Annex A, 89 apply to BespokeWorks. All 37 organisational controls, all 8 people controls and all 34 technological controls apply. Of the 14 physical controls, 10 apply and 4 are excluded.

The change that mattered most to me is that nothing about the company, our code or our website changes without being checked. The bigger the change, the more checking it gets, and every week we sample what changed, including changes made under my own accounts, which Theo checks.

Admin rights now sit on separate accounts, nobody approves their own access, and access is reviewed every quarter. Theo and Kris built our monitoring, using AI coding tools to help: when a service or scheduled job fails, an alert email reaches all three of us with the first checks already written into it, and any fix is made by one of us through our normal change process. And we proved our backups work, with five database restores in September.

Figure 2 · Then and now

From our first review to certificate day

First review7 SeptemberTwo weeks in
42 days
Certificate day19 OctoberSix weeks later
Policy documents7 September24 written in draft
19 OctoberBrought together into 13 policies, a device agreement and 5 procedures
Risks7 SeptemberIdentified and ranked by severity
19 OctoberEach with a named owner and a treatment plan
Evidence7 SeptemberOur first dated record
19 OctoberDated records the auditor tested, from access reviews and restore tests to a management review
Admin rights7 SeptemberHeld on everyday accounts
19 OctoberMoved to separate admin accounts
Access7 SeptemberGranted and checked by one person
19 OctoberNobody approves their own access
Backups7 SeptemberRunning, with restores still to be tested
19 OctoberFive database restores tested in September

In the first row each line is one document: 24 drafts come together into 13 policies, a device agreement and 5 procedures. Every other row is a single line. A dashed line is a draft or something not yet proven; a solid line is in place. Where a line turns solid on the way across is drawn, not dated.

BespokeWorks baseline review of 7 September 2026, and the management system as certified on 19 October 2026.

Six things compared between the first review on 7 September 2026 and certificate day, 19 October 2026, 42 days later. Policy documents: 24 written in draft, then brought together into 13 policies, a device agreement and 5 procedures. Risks: identified and ranked by severity, then each with a named owner and a treatment plan. Evidence: our first dated record, then dated records the auditor tested, from access reviews and restore tests to a management review. Admin rights: held on everyday accounts, then moved to separate admin accounts. Access: granted and checked by one person, then nobody approves their own access. Backups: running, with restores still to be tested, then five database restores tested in September.

The audit

Before an external auditor saw anything, we engaged ProtectifyAI, an independent security and compliance assurance provider, to conduct our internal audit. We went through everything together, and the report gave us a clear, detailed list of what still needed work, in time to act on it. By Stage 2 every finding had been closed, and Tempo’s auditor checked that.

From our internal auditor

BespokeWorks has built a thorough and unusually honest ISMS in a short time. The document set is complete, the risk register is specific to the business, and the company raised its own nonconformities.

ProtectifyAIIndependent Internal Audit & Assurance Service ProviderISO/IEC 27001:2022 · 23–24 September 2026protectifyai.com

Tempo Audits, a UKAS-accredited certification body, then audited us in two stages. Stage 1, on 1 October, checked the system on paper. Stage 2, on 7 and 8 October, checked it in practice, and most of the time went on records: policy acknowledgements, a restore test, an access review, an incident record, our management review and a supplier review.

The result was no major findings, one minor finding and one suggestion. The minor one is my favourite: our own Statement of Applicability still marked some controls as partial or gaps after the auditor had seen them working. Our record was stricter than the audit, but it was rightly still a finding, because the document has to match reality. The suggestion was to set out our management review minutes against the inputs the standard lists.

Tempo accepted our corrective action plan, and the certificate was issued on 19 October 2026. When the email came through, the three of us were very happy. It runs to October 2029, with a one-day surveillance audit in each of the next two years, the first on 30 September 2027.

From our certification body

We are delighted to award BespokeWorks their UKAS-accredited ISO/IEC 27001 certification.

From meeting Deen when they were starting out the process, they clearly worked very hard to implement a robust information security management system. In a short period, the team put in place a structured, evidence-led system covering the development and delivery of its software, workflow automation and AI-enabled services. Achieving ISO/IEC 27001 certification is a strong reflection of the founders’ commitment to security from an early stage.

Rob HallFounder & CEO, Tempo AuditsCertificate TA-01-BAL-191026tempoaudits.com

For context, Amtivo, one of the UK’s certification bodies, says its clients take three to six months on average to get ISO certified. We took eight weeks of building, after a month of research. It isn’t a race, though, and it was harder than I expected.

Figure 3 · The route

From the first walk‑through to the certificate

8 weeks

of building, from 25 August to 19 October 2026, after a month of research and choosing an accredited certification body.

123456725 AugustBuilding begins. 27 risks by the end of the day7 SeptemberAn honest review of where we were23 and 24 SeptemberInternal audit by ProtectifyAI1 OctoberStage 1 audit7 and 8 OctoberStage 2 audit14 OctoberCorrective action plan to Tempo19 OctoberCertificate issued
  1. 25 AugustBuilding begins. 27 risks by the end of the day
  2. 7 SeptemberAn honest review of where we were
  3. 23 and 24 SeptemberInternal audit by ProtectifyAI
  4. 1 OctoberStage 1 audit
  5. 7 and 8 OctoberStage 2 audit
  6. 14 OctoberCorrective action plan to Tempo
  7. 19 OctoberCertificate issued

Each step is a dated milestone and each bead is a day, 56 in all. A two-day audit is a step two days wide. The height of a step carries no number. Next come one-day surveillance audits, the first on 30 September 2027, and recertification by October 2029.

BespokeWorks ISMS records and the certificate issued by Tempo Audits.

Eight weeks of building, from 25 August to 19 October 2026. 25 August: building begins, 27 risks by the end of the day. 7 September: an honest review of where we were. 23 and 24 September: internal audit by ProtectifyAI. 1 October: Stage 1 audit. 7 and 8 October: Stage 2 audit. 14 October: corrective action plan to Tempo. 19 October: certificate issued. Next come one-day surveillance audits, the first on 30 September 2027, and recertification by October 2029.

What it means for clients

The certificate covers “the design, custom development, integration, deployment, operation, maintenance and support of software applications, workflow automation and AI-enabled solutions, including cloud-hosted client systems”. In practice that means a few things you can hold us to.

What you can hold us to

Same day

When someone leaves, their access goes that day, and the removal is checked within one working day.

24 hours

Our standard is to tell you within 24 hours of becoming aware of a breach of your data, or sooner if your agreement says so.

Every quarter

Someone other than the person who prepared it checks who can see what.

Every year

An accredited auditor comes back. The first surveillance audit is on 30 September 2027.

BespokeWorks access control policy and incident response procedure, inside the scope of our ISO/IEC 27001 certificate.

Four things clients can hold BespokeWorks to. Same day: when someone leaves, their access goes that day, and the removal is checked within one working day. 24 hours: our standard is to tell you within 24 hours of becoming aware of a breach of your data, or sooner if your agreement says so. Every quarter: someone other than the person who prepared it checks who can see what. Every year: an accredited auditor comes back. The first surveillance audit is on 30 September 2027.

Access to your information is given to a named person, for a reason, and taken away when the reason ends. When someone leaves, their access goes on the day they leave and the removal is checked within one working day. Every quarter, someone other than the person who prepared it checks who can see what.

If something goes wrong with your data, our standard is to tell you within 24 hours of becoming aware of it, or sooner if your agreement says so. A decision not to tell a client is written into the incident record the same day, with the name of the person who made it and why.

Hosting and sub-processors are set out in writing for every client; UK-region hosting is available. When your security team sends a supplier questionnaire, we answer it from the same system the auditor checked, with dated evidence, and you can check the certificate yourself on Tempo’s website.

It’s worth being clear about what the certificate doesn’t say. It doesn’t say our software can’t be breached, and it isn’t a penetration test. It says we run a system that finds our risks, treats them and checks the treatment works, and that an accredited body has audited it and will keep auditing it every year.

What we learned

We learned far more than we expected to. In the week or two before the audit, the three of us were reading about things we had never had to think about: the different types of encryption, the settings in each laptop’s BIOS and why they have to be set up in a particular way, and security protocols we hadn’t known existed. I found it genuinely interesting.

Security also reaches further than software. At Stage 2 the auditor looked at photos of where each of us works at home, because who can see your screen and where your laptop sits are part of keeping information safe. I doubt many people would expect a desk to be a security control.

If someone asked me whether they should do ISO 27001, I’d say yes, do it, but don’t rush it. Take your time and understand what you’re getting yourself into. I spent a long time beforehand learning the standard and the processes, and it was still a lot harder than I thought, and a lot more stressful. I’m glad it’s done.

Get your documentation ready for anything: for anyone starting, anyone leaving and anything that goes wrong. When something happens, the document should already say who does what.

Decide how changes happen before you make them. Knowing what people do before any code, any system or any page of the website changes was the other thing that mattered most.

Start the records on day one. Policies are quick to write. We drafted ours with AI help in a few days, and they were never the hard part. What gets tested is evidence that something happened: dated, named, with an outcome. If a control has evidence behind it and has been done at least once, it’s real. If not, it’s a plan.

And bring in an independent internal auditor early. Ours gave us a clear list of what to fix while there was still time to fix it.

Sources

  1. Department for Science, Innovation and Technology, Cyber Security Breaches Survey 2025/26 (data tables, Table 10)
  2. Amtivo, Frequently asked questions: How long will it take to become certified?
  3. Tempo Audits, BespokeWorks ISO 27001 certificate

About the author

Deen Aslam

Founder and Chief Executive of BespokeWorks. Deen led the company’s ISO/IEC 27001 programme as project lead, with co-founders Kristiyan Andreev and Theo Coleman.

Meet BespokeWorks

Working on your own information security?

We review the gaps, rank them by risk and help you close them.

See how we help with cyber security