Our ISO 27001 Journey: Tooling, Maturity and What We’ve Learned

We made a deliberate choice early on: Volo Digital would pursue ISO 27001 certification, not just "alignment". Alignment is easy to claim and hard to verify. Certification means an independent auditor checks that our controls exist, operate and improve over time. For a digital solutions provider that holds the keys to our clients' environments, we think that's the standard clients deserve.

This is an honest look at how we've approached it: the risks that shaped our scope, the tooling we chose, and where we sit on the maturity curve today.

Starting with our real risks

Our environment made some decisions easy. We run no servers of our own. Everything is SaaS, built on Microsoft 365 and Azure, with tenant configuration managed as code and laptops that can be rebuilt from scratch automatically. That shrinks the attack surface and keeps the scope of our information security management system (ISMS) tight.

The harder risks sat elsewhere. A shared office means other parties have access to our building, so physical controls mattered more than you might expect for a cloud business. Our partners need access to deliver services, which forced careful least-privilege decisions. And we knew from day one that auditors want evidence, not intent, so we designed everything with the Stage 1 and Stage 2 audits in mind.

Our tooling approach

Our principle is simple: the platforms we already run are the source of truth, and a governance, risk and compliance (GRC) platform ties them together. After comparing the leading options, we chose one that let us start with policy and personnel management and expand from there. It gathers evidence continuously from our systems, rather than relying on screenshots collected the week before an audit.

Underneath sits a layered defence. Enterprise-grade endpoint protection, identity threat detection, device management and data loss prevention form the foundation. For our clients, we add managed detection and response, with a 24/7 security operations centre watching over that same foundation. Our service management platform runs our ITIL v4 practices, so change, incident, asset and configuration management create audit records as a by-product of normal work. Ongoing security awareness training and centrally managed credentials round out the picture. You'll notice we don't name the products. That's deliberate: publishing your security stack hands attackers a head start.

Where we sit on the maturity curve

We'd describe ourselves as documented and operating, and moving towards measured. The documentation layer is complete: an ISMS scope statement, an information security objectives register, and a Statement of Applicability covering all 93 Annex A controls of ISO 27001:2022. Behind those sit more than 40 policies, plus the operational plans, registers and runbooks that put them into practice, including our incident response plan and a library of communications templates.

We've also mapped our controls across ISO 27001, SOC 2, the ASD Essential Eight and ITIL v4. One well-designed control can then satisfy several frameworks, instead of being built four times.

The next stage is proving it over time: continuous evidence, internal audits, management reviews, and objectives tracked against real numbers. That's the gap between having good policies and running a mature ISMS, and it's where our effort is focused now.

What we've learned

Write policies for how you actually operate. Ours reference the real tools and workflows our team uses every day, so they describe reality rather than aspiration. Keep your positions consistent: a decision made in one policy has to carry through to incident playbooks, client contracts and the risk register. And let tooling carry the evidence burden, so compliance becomes a by-product of good operations rather than an annual scramble. AI helped us draft and cross-check more than 70 documents, but every one was reviewed and owned by our team.

For our clients, this matters directly. The controls, contracts and security posture statements we've built for ourselves are the same ones we bring to every engagement. When we talk about security, we're describing how we run our own business.

About the author

Pete

Chief Executive Officer

Peter leads Volo Digital’s commercial and strategic direction, with a focus on building a business that delivers well for clients and gives the team the support to do their best work.

Related services: Cyber security