Quick Answer: How do I choose a security auditing company?
Start by defining what you actually need audited, because “security auditing company” covers at least four different services: ISO 27001 certification, penetration testing, SOC 2 reporting, and internal gap assessments. Each one has its own credential system, and a firm that excels at one may be unqualified for another.
Only an accredited certification body can issue an accredited ISO/IEC 27001 certificate, while SOC 2 reports must come from a CPA firm working under AICPA standards, and pentests are best matched to recognised schemes like CREST or CHECK. A consultancy can do a gap assessment or internal audit but cannot certify you.
Before signing anything, compare accreditation status, scope of the proposed work, named methodology, auditor independence, sample deliverables, and total cost including retesting.
Why the Word “Audit” Is the First Trap

Ask ten vendors what a security audit is and you will get ten answers. Some mean a technical penetration test. Some mean a paperwork review against ISO 27001. Some mean a SOC 2 examination for investors. Others mean an internal audit that never produces a certificate at all.
That ambiguity is not a marketing quirk. It changes who is legally allowed to do the work. A penetration testing firm cannot issue an accredited ISO 27001 certificate, and a certification body generally should not turn around and sell you the consulting to fix what it just found, because independence rules exist to prevent exactly that conflict. Buyers who skip this distinction end up paying twice: once for a “pre-certification audit” from a consultancy, then again for the real certification body.
So the honest first step is to write one sentence describing the outcome you need. “A certificate our enterprise client will accept” is a different sentence from “evidence our pentest found no critical vulnerabilities” or “a report our investor will read.” Once that sentence exists, the shortlist almost writes itself.
Match the Credential to the Service
Different audit types run on different credential rails. Here is how the main ones compare.
| Service | Who can legitimately deliver it | Credential to verify | Typical output |
|---|---|---|---|
| ISO/IEC 27001 certification | Accredited certification body | Accreditation by a national body that is an IAF MLA signatory | Accredited certificate, valid three years with surveillance audits |
| SOC 2 report | CPA firm | AICPA standards (SSAE 18 / AT-C 205), peer review | SOC 2 Type I or Type II report |
| PCI DSS assessment | Qualified Security Assessor (QSA) company | Listing with the PCI Security Standards Council | Report on Compliance |
| Penetration test | Specialist testing firm | CREST accreditation, CHECK (UK), individual certifications | Technical report with findings and retest |
| Gap assessment or internal audit | Consultancy or internal team | Relevant auditor experience, no accreditation needed | Findings report, remediation roadmap |
The ISO row deserves emphasis. ISO itself does not certify anyone; third-party certification bodies do. The certificate’s value depends on the body being accredited by a national accreditation body that is a signatory to the IAF Multilateral Recognition Arrangement, which is the framework under which accredited certificates are recognised across borders. If a firm cannot tell you which accreditation body oversees it, that is your answer.
For ISO work, ISO/IEC 27006 is the standard that sets requirements for bodies auditing and certifying information security management systems, so it doubles as an interview checklist. Independence requirements live in ISO/IEC 17021-1, which covers impartiality and conflict of interest for management system certification bodies.
Check Accreditation Before You Check Anything Else
Accreditation is the single fastest filter, and it is also where marketing gets slippery. Plenty of firms say “ISO 27001 certified” when they mean their own internal management system passed an audit. That says something about their housekeeping. It says nothing about their right to certify yours.
The practical test is blunt: ask for the accreditation certificate of the body that will sign your certificate, and ask which accreditation body issued it. Then verify the scope covers your industry and your standard version. A body accredited for quality management is not automatically accredited for information security management.
The same logic applies elsewhere. For PCI DSS work, check the QSA company against the PCI Security Standards Council’s own listing rather than a logo on a slide. For UK government-related penetration testing, CHECK scheme membership signals recognised capability. For CREST, membership covers both companies and individual testers, and the individual matters as much as the firm, because your test is only as good as the person at the keyboard.
One more subtlety: accreditation scope changes and lapses. A firm that was accredited two years ago may not be today. Verify at the time of engagement, not from a case study PDF.
Read the Methodology, Not the Brochure
Every credible firm will name a methodology. The interesting part is whether the name means anything to the person doing the work.
For penetration testing, common references include the Penetration Testing Execution Standard, the OWASP Testing Guide for web applications, MITRE ATT&CK for adversary emulation, and NIST SP 800-115 for technical security testing and assessment. For ISO 27001 work, the methodology is essentially fixed by the standard, so the differentiator becomes the auditor’s sector experience and the quality of the sampling approach.
Ask three questions that brochures cannot answer. First, who exactly will be on site, and what are their certifications? Second, how do you decide what to sample? Third, what does the report look like? Request a redacted sample report. A good report states scope, method, evidence, findings rated by severity, and clear remediation guidance. A bad one is a screenshot dump with a cover page.
This is the same discipline that applies when you choose API security testing that fits your stack: the tooling and framework names matter less than whether the testing approach matches the architecture you actually run.
Independence and Conflict of Interest
A clean audit is worth more when the auditor has nothing to gain from the result. That is why impartiality rules exist, and why a certification body should not certify a management system it consulted on.
In practice, this creates a fork in the road. You can hire a consultancy for gap assessment and remediation support, then hire an accredited certification body for the certification audit. Or you can hire one firm for both, accepting that many certification bodies will refuse, and that regulators and customers may question the result if they do not.
Watch for softer conflicts too. Does the firm resell the security products it recommends in its findings? Does it have a managed service arm that benefits when your gaps look scary? Neither is automatically disqualifying, but both deserve a straight question and a straight answer.
The same thinking applies across the stack. If you are weighing monitoring and detection tooling alongside the audit, the logic in choosing cloud security posture management without wasting resources is similar: vendor incentives shape recommendations, so separate advice from supply.
Scope, Sampling, and the Cost of a Cheap Quote
Audit pricing varies enormously, and the cheapest quote is often the most expensive engagement. A low bid usually means a narrow scope, remote-only evidence review, or a junior team learning on your time.
Define scope in writing before you compare prices. Which locations, business units, cloud environments, and third parties are in scope? How many days of fieldwork? How many auditor days are included in the report phase? What happens if findings require a follow-up visit?
For ISO 27001, remember the certification cycle: an initial certification audit, then surveillance audits in following years, then recertification. Ask for the three-year total, not the year-one number. For SOC 2, ask whether you are buying a Type I (point in time) or Type II (period of time) report, because the price gap is large and the usefulness gap is larger.
For penetration testing, insist on a retest clause. Finding a critical vulnerability is only half the job; proving it is fixed is the other half, and it should be priced up front rather than negotiated in a panic.
There is a related trap in cloud environments. Auditors who do not understand shared responsibility models will mark controls as missing when the provider handles them, or accept provider assurances without evidence. If your estate is mostly cloud, the guidance on cloud compliance challenges where security audit rules intersect is worth reading before scoping meetings, because it frames the questions that separate cloud-fluent auditors from the rest.
Questions That Reveal Competence in Ten Minutes
A short, sharp interview beats a long proposal. These questions tend to sort firms quickly.
- Which accreditation body oversees your certification work, and can you send the certificate?
- Who will lead fieldwork, and what are their qualifications and sector experience?
- Which methodology will you follow, and can I see a redacted report?
- How do you handle a finding we disagree with?
- What is explicitly out of scope in this proposal?
- What does the three-year cost look like, including surveillance and retests?
- Do you sell any products or remediation services related to your findings?
Vague answers to questions two, four, and seven are the warning signs. A confident auditor will happily explain how disputes are escalated, because good firms have a process and bad firms have a shrug.
If your programme spans multiple teams and tooling, the same selection discipline you would apply when you choose security orchestration that fits your team applies here: fit to how your organisation actually works beats a feature list every time.
Common Mistakes Buyers Make
The most frequent error is buying a certificate instead of an audit. Firms that promise a guaranteed pass are selling you paperwork, and the certificate will not survive scrutiny from a serious customer.
The second is skipping the scoping call. Audits that begin without a written scope, asset list, and evidence plan burn days on discovery that you already paid for.
The third is treating the report as the deliverable. The deliverable is a changed security posture. Budget for remediation before you budget for the audit, or you will have an expensive document and the same vulnerabilities.
The fourth is forgetting the human side. Auditors will interview your staff, and a team that has never heard of the audit will give confused answers that look like control failures. Brief people early, and consider pairing the programme with security awareness training that actually changes behaviour so interviews reflect reality rather than panic.
Finally, do not neglect the technical estate that feeds the audit. Continuous evidence, such as retained footage from physical controls or logs from monitoring, is what auditors sample. If your recording infrastructure is flaky, fix it first, using guidance like choosing continuous security recording that lasts where relevant, so the audit does not fail on an avoidable technicality.
Conclusion
Choosing a security auditing company is really a matching exercise. Decide which outcome you need, then verify the credential that legally or professionally covers it: accreditation for ISO 27001 certification, AICPA standards for SOC 2, QSA status for PCI DSS, and recognised schemes for penetration testing. Interview the people who will do the work, read a sample report, confirm independence, and price the full cycle rather than the first invoice.
Do that, and the audit becomes a genuinely useful mirror held up to your security programme. Skip it, and you buy a PDF that impresses nobody who matters.
FAQ
How long does an ISO 27001 certification audit take?
Most organisations spend three to six months on readiness before the stage one and stage two audits, which themselves typically span several days depending on size and complexity. The certificate then runs on a three-year cycle with surveillance audits, so plan resourcing across the whole period rather than the first audit alone.
Can the same company do my gap assessment and my certification?
Usually not for the certification itself. Impartiality rules mean a certification body should not certify a management system it consulted on, so most will decline or refer you elsewhere. The common pattern is a consultancy for gap assessment and remediation, followed by an accredited certification body for the formal audit.
Is a penetration test the same as a security audit?
No. A penetration test is a technical attempt to exploit vulnerabilities within an agreed scope. A security audit examines controls, processes, and evidence against a standard or framework. Many programmes need both, and they answer different questions for different audiences.
How do I verify a firm’s accreditation?
Ask for the accreditation certificate and identify which accreditation body issued it, then check that body’s public directory. For ISO work, confirm the accreditation covers information security management and your standard version. For PCI DSS, check the PCI Security Standards Council listing, and for UK government work, check CHECK scheme membership.
What should a penetration test report contain?
At minimum: scope and testing window, methodology referenced, findings rated by severity with evidence, affected assets, business impact, and remediation guidance. A retest section confirming fixes is a strong signal of quality. Ask for a redacted sample before you buy.
How much should a security audit cost?
There is no single figure, because scope drives price far more than firm size. Compare three-year totals for certification work, Type I versus Type II for SOC 2, and always include retest and surveillance costs. A quote that is dramatically cheaper than the others usually reflects narrower scope or less experienced staff.


