Disclosure: Cyber Veda is an official Vanta partner and also works with Drata, Secureframe, Scrut and Sprinto.
The real question: who does the work?
Getting to an ISO 27001 certificate or a SOC 2 report involves two different kinds of work. One is repetitive and mechanical: collecting evidence, chasing policy sign-offs, checking settings across dozens of systems. The other is judgement: deciding what is in scope, which risks matter, which controls apply and whether the system is ready for an auditor. Software is very good at the first kind. The second still needs a person who has done it before, either on your team or brought in.
So the decision isn’t really “platform or consultant”. It’s who on your side makes the judgement calls, and how much of the mechanical work you want automated.
What a compliance platform does
- Connects to your systems. Cloud accounts, identity provider, code repositories, HR system and devices, then tests controls continuously.
- Collects evidence automatically. Screenshots and exports that used to take days are gathered on a schedule.
- Provides templates. Policies, training and a starting risk register.
- Tracks people tasks. Policy acceptance, security training and background checks.
- Gives the auditor access. Evidence is shared in one place, which shortens fieldwork.
- Publishes a trust centre. A page customers can use instead of sending questionnaires.
For what the main platforms offer and how to compare them, see choosing a compliance platform.
What a platform doesn’t do
- Decide your scope. What’s in, what’s out and how it matches what customers are buying.
- Judge your risks. A template risk register is a start, not an assessment of your business.
- Justify your Statement of Applicability. Auditors expect reasoned decisions for each control, especially exclusions.
- Fix the gaps. If you have no device management, no logging or untested backups, someone still has to set them up.
- Run your internal audit. ISO 27001 requires an objective, impartial auditor, which a dashboard isn’t.
- Certify you. Only an accredited certification body issues an ISO 27001 certificate, and only a CPA firm issues a SOC 2 report.
What a consultant does
A good consultant fills exactly those gaps: they scope the certification to your customers, run the risk assessment with you, write policies that match how you work, guide remediation, carry out or arrange an independent internal audit and prepare you for the certification body. A poor one hands over templates and invoices by the day. Ask what’s delivered, by whom and by when. Our guide to choosing an ISO 27001 consultant lists the questions to ask.
What a consultant shouldn’t do is own your ISMS. Top management must show leadership and commitment, risk owners accept their own residual risk, and the certification auditor will interview your people, not your advisor. The goal is a system your team understands and can run without them.
Who does what, stage by stage
This is how the work typically splits when you use both. With a platform only, your team takes on the consultant column; with a consultant only, the platform column becomes manual work.
| Stage | Platform | Consultant | Your team |
|---|---|---|---|
| Scope and context | Holds the record | Proposes the boundary and why | Agrees it with leadership |
| Gap assessment | Shows failing automated tests | Assesses processes, people and documents too | Answers questions, provides access |
| Risk assessment | Template register and workflow | Runs the method and the workshops | Owns and accepts the risks |
| Statement of Applicability | Lists controls | Justifies each inclusion and exclusion | Approves it |
| Policies | Templates and acceptance tracking | Fits them to how you work | Reviews, approves, follows them |
| Remediation | Flags misconfigurations | Prioritises and guides the fixes | Makes the changes |
| Evidence | Collects it continuously | Checks it before the auditor does | Uploads the manual items |
| Internal audit | Stores findings | Audits independently | Closes corrective actions |
| Management review | Supplies metrics | Prepares the inputs | Leadership holds it and decides |
| Stage 1 and Stage 2 | Gives the auditor access | Prepares you, supports findings | Attends interviews |
Notice that the right-hand column never empties. Whatever you buy, your team still has decisions to make and changes to carry out. A well-run project with outside help typically needs about two hours a week from the person leading it internally, plus engineering time for any fixes.
The ways to do it
| Platform only | Consultant only | Both | |
|---|---|---|---|
| Works best for | Teams with ISO 27001 or SOC 2 experience in-house and a simple cloud setup | Small, simple scopes; teams that prefer documents to dashboards | First-time certification, tight deadlines, SOC 2 Type 2 |
| Your team’s effort | Highest: you make every decision and write what the templates don’t cover | Moderate: evidence is gathered by hand | Lowest: judgement from the consultant, automation from the platform |
| Main risk | Stalling on scope, risk and the SoA; a weak internal audit | Manual evidence gets harder to sustain each year | Paying for two things if either is poorly matched to you |
| Ongoing years | You run it, with an independent internal audit each year | Retainer or in-house upkeep | Platform keeps evidence flowing; consultant runs the internal audit |
Two hybrids sit between these and are often the best fit:
- Platform plus targeted help. Your team runs the program in the platform and buys in only the scope and risk workshops, a readiness review and the internal audit. This suits teams with a capable security lead who hasn’t been through a certification audit before.
- Managed compliance. After certification, an outside partner runs the ISMS calendar for you: alert triage in the platform, access reviews, supplier reviews, the internal audit and surveillance audit preparation. This suits teams who want the certificate kept current without a dedicated compliance hire.
Three typical situations
A 30-person SaaS company, first certificate, enterprise deal waiting
Everything runs in AWS, Google Workspace and GitHub, and nobody has done ISO 27001 before. Both is usually right: the platform makes the cloud evidence almost free, and the consultant gets scope, risk and the SoA decided in the first fortnight so the deadline holds. See ISO 27001 for SaaS companies.
A 12-person professional services firm answering a government tender
Microsoft 365, a line-of-business app and an MSP looking after the laptops. Few integrations, one framework, a fixed tender date. A consultant alone is often enough, with evidence kept in a well-organised SharePoint site. See ISO 27001 for government tenders.
A 100-person fintech with an experienced security engineer
The team has done SOC 2 before and now needs ISO 27001 for Australian banks. A platform with targeted help usually fits: the engineer runs the platform, and outside help covers the ISO-specific clauses, the risk method and an independent internal audit.
How to decide
Answer these honestly:
- Has anyone on the team done this before? If not, the judgement work is where you’ll need help.
- How many systems and devices are in scope? The more there are, the more a platform saves.
- Is it SOC 2 Type 2? Months of continuous evidence strongly favours a platform.
- How fixed is the deadline? A tender date favours more done for you.
- Who will run it next year? Surveillance audits and the annual internal audit don’t go away.
Weigh costs over the full three-year certificate cycle, not just the first audit: a platform is a yearly subscription, consulting is mostly up front, and your team’s time is the cost most often left out. Our guide to what drives the cost of ISO 27001 lists every part.
Mistakes when combining them
- Two sets of documents. The consultant writes policies in Word while the platform holds its own templates. Pick one home for every document and keep it there.
- A consultant who doesn’t know your platform. They end up asking for screenshots the platform already has. Ask which platforms they have taken through an audit.
- The implementer audits their own work. If your consultant built the ISMS, a different person must do the internal audit.
- Handing over ownership. If only the consultant understands the risk register, the Stage 2 interviews will show it.
- Buying the platform first, then scoping. Decide scope before you connect everything, or you’ll spend weeks clearing alerts for systems outside the ISMS.
How we work with platforms
We can set up and run your program in Vanta, work inside Drata, Secureframe, Scrut or Sprinto if you already have one, or run it with no platform when that makes more sense. A typical SME is audit-ready in about eight weeks, and our internal audit is independent of the implementation either way. After certification, our managed compliance service keeps it running.
See our ISO 27001 and SOC 2 services, or book a free 30-minute consultation to work out which combination fits your team.
