Quick Answer: What questions should I ask a security auditing company before hiring?
You should ask a security auditing company what exactly it is selling, which standard it measures against, who will perform the work, and what written authorization and reporting you will receive. In plain terms, the goal is to separate a real technical assessment from a sales pitch with a logo on it. You can act on this by requesting a redacted sample report, naming your own scope, and confirming insurance and data-handling terms before any contract is signed.
The word “audit” covers several different services, including penetration tests, compliance gap assessments, and architecture reviews, and each one produces different deliverables. Some firms sell remediation work alongside testing, which raises independence questions worth resolving early.
Before committing, compare scope definition, framework and version, tester certifications, rules of engagement, evidence handling, report quality, retest terms, insurance limits, and independence from vendors.
Why the Label on the Proposal Matters More Than the Price

Picture this. A vendor sends a glossy proposal promising “a full security audit” for a fixed fee. It sounds thorough. Then the report arrives, and it is twelve pages of generic findings with no reproduction steps and no severity ratings. The buyer paid for reassurance and got a document nobody can act on.
That gap is common, and it is almost always traceable to questions that were never asked during procurement. A penetration test is a point-in-time, goal-directed attack simulation. A security audit or assessment is usually a broader review against a standard. Those are different products with different effort levels, and confusing them is the single most expensive mistake buyers make.
The good news is that a short, sharp question list closes most of the gap. What follows is the practical version, the one that experienced buyers actually use.
Scope and Methodology: What Are You Actually Buying?
The first question is deceptively simple: what is in scope, and what is explicitly out of scope? A credible firm will answer with a list of hosts, applications, network ranges, and user roles, plus a clear statement of exclusions.
Watch for vagueness here. “We’ll test your web applications” is not a scope. “We will test the three customer-facing applications at these URLs, using authenticated and unauthenticated testing, excluding the third-party payment iframe” is a scope.
Then ask which methodology governs the work. Common answers include NIST SP 800-115, the Technical Guide to Information Security Testing and Assessment published in September 2008, and the OWASP testing guides for web applications. A firm that cannot name a standard and a version is improvising.
Practical tip: ask how many tester-days the engagement includes. A quote that is half the price of competitors usually reflects half the effort, and depth of testing is directly tied to hours on task.
Standards, Frameworks, and What “Compliant” Really Means
If your motivation is compliance, say so up front and ask which framework the assessment maps to. ISO/IEC 27001 is the international standard for information security management systems, and it was revised in 2022, so confirm the firm is working from the current version rather than a stale checklist.
Be careful with the word “certification.” An auditor can assess you against a standard, but certification is issued by an accredited certification body, not by the testing firm itself. If a vendor implies it can hand you a certificate after a week of testing, that is a red flag worth walking away from.
A useful comparison of how these engagements differ:
| Question | Penetration test | Compliance audit | Gap assessment |
|---|---|---|---|
| Primary goal | Find exploitable weaknesses | Verify controls against a standard | Identify distance to a target state |
| Typical output | Findings with severity and evidence | Conformity statement and exceptions | Roadmap with priorities |
| Depth | Technical, hands-on | Documentary and control-based | Mixed, often interview-led |
| Best for | Validating defenses | Certification readiness | Budget planning |
Ask which column your proposal sits in. If the firm cannot place its own offer in that table, the scope is probably fuzzy.
Who Is Doing the Work, and What Are Their Credentials?
Sales teams sell audits. Testers perform them. Ask directly who will be on the keyboard and whether those named people hold current credentials.
Widely recognized qualifications include OSCP (Offensive Security Certified Professional), CREST accreditation, and CISSP for broader security governance. Ask how many staff hold each, and then ask the sharper follow-up: will the person who scoped the work also deliver it?
Common mistake: buyers accept a “senior team” claim in the pitch deck without checking that the named lead is contractually assigned. Add a clause naming key personnel, or at minimum request the CVs of the lead tester and reviewer.
Also ask about quality control. A second tester reviewing findings before the report ships catches false positives, and a report full of false positives destroys trust in the entire engagement.
Rules of Engagement and Written Authorization
This is the question that protects you legally as much as technically. Testing without explicit written authorization can be an offence under computer-misuse laws, including the U.S. Computer Fraud and Abuse Act of 1986 and the UK Computer Misuse Act 1990.
A professional firm will insist on a signed scope and authorization document before touching anything. That document should define the testing window, the source IP addresses testers will use, emergency stop contacts, and what happens if a tester accidentally disrupts a production system.
Practical tip: give your hosting provider and any third-party SaaS vendors notice before testing begins. Testers hitting a cloud provider’s infrastructure without approval can trigger abuse detection and get your account suspended mid-engagement. It happens more often than anyone admits.
If customer data or credentials will be accessed, ask how findings, evidence, and captured data are stored, encrypted, retained, and destroyed, and whether the firm will sign a nondisclosure agreement. Get the retention period in writing. “We delete it when the project ends” is not a policy.
Reporting, Retesting, and Remediation Support
A useful deliverable includes severity ratings, reproducible steps, evidence, business impact, and remediation guidance. Not a pass or fail summary. Ask to see a redacted sample report before signing, and read it the way you would read a contract.
Three questions sharpen this fast. First, who writes the report, and how long after testing ends does it arrive? Second, is a retest included, and at what cost? Third, will the firm answer follow-up questions from your engineers during remediation?
There is a real tension around remediation. If the firm also sells fix-it services, ask how it manages independence and whether the same people who found the flaws will be paid to close them. Some standards require separation between assessment and remediation advice. If you already have a managed detection provider, check how the audit findings will feed into that relationship, and review this managed detection response checklist of 12 questions to ask before signing anything new.
Insurance, Liability, and Commercial Terms
Testing can break things. Ask for proof of professional indemnity and cyber liability insurance, and ask what the limits are. Then ask the awkward question: if a tester takes down a production system, what does the contract actually say about liability?
Many standard terms cap liability at the fee paid, which may be trivial compared to an outage. That is negotiable, and it is worth negotiating before the engagement, not after an incident.
While you are in the contract, check payment milestones, notice periods, and whether findings can be shared with your board, insurers, or regulators without approval.
Independence, References, and Conflicts of Interest
Ask for two or three references from clients of similar size and sector, and actually call them. Ask what surprised them, what the report quality was like, and whether they would hire the firm again.
Then ask about conflicts. Does the firm resell products it might recommend? Does it have a reseller relationship with a vendor whose platform you use? Independence is not a luxury; it is the difference between advice and a sales channel.
Due diligence habits carry across categories. Buyers who scrutinize a Rillabox review before ordering apply the same instinct here: read the fine print, check who benefits, and confirm what happens after the money moves.
Questions Specific to Cloud, AI, and Modern Environments
If your stack includes AI systems, the question list grows. Ask whether the firm tests prompt injection, model access controls, and data leakage paths, or whether it only covers the surrounding infrastructure.
Buyers evaluating conversational tools should also work through these AI chatbot security questions to ask before buying, because an audit that ignores the chatbot layer leaves a wide gap. Similarly, a DNS security checklist for hardening your resolver is worth reviewing so you can tell whether the proposed scope covers DNS abuse, spoofing, and resolver configuration at all.
Practical tip: hand the firm your architecture diagram and ask it to mark what it would not test. The omissions tell you more about capability than the promises do.
How to Compare Proposals Without Getting Fooled by Price
Line up two or three proposals and normalize them before comparing cost. Convert each quote into tester-days, then divide. The cheapest per-day rate often belongs to the least experienced team, and the most expensive is not automatically the best.
A simple scoring approach works well:
- Score scope clarity out of five.
- Score named methodology and framework version out of five.
- Score credentials of the assigned lead out of five.
- Score sample report quality out of five.
- Score retest and remediation support out of five.
- Score insurance and liability terms out of five.
Add the scores, then look at price. In practice, the firm with the clearest scope usually wins even when it is not the cheapest, because vague scopes generate change orders later.
Conclusion
Hiring a security auditing company is a procurement decision before it is a technical one. The firms worth your budget will welcome hard questions about scope, standards, credentials, authorization, evidence handling, and liability, and they will answer them in writing. The ones that deflect are telling you something useful.
Start with the questions above, request a redacted sample report, name your key personnel in the contract, and confirm insurance limits before anyone touches a keyboard. Do that, and the report you receive at the end will be something your team can actually use.
Frequently Asked Questions
How long should a security audit take?
It depends on scope. A single web application penetration test often runs three to ten tester-days, while a broader assessment covering multiple systems and a compliance framework can span several weeks. Ask for the effort estimate in tester-days and compare it against the deliverable you expect.
Is a penetration test the same as a security audit?
No. A penetration test is a goal-directed attack simulation at a point in time. A security audit or assessment is typically a broader review against a standard, often involving documents, interviews, and control checks. Many organizations need both, but they should be scoped and priced separately.
What certifications should testers hold?
Look for credentials such as OSCP for hands-on offensive testing, CREST accreditation for the firm itself, and CISSP for broader security governance. Certifications are a starting signal, not proof of quality, so pair them with a sample report and client references.
Who is legally responsible if testing causes an outage?
Responsibility is defined by the contract, which is why liability caps and insurance matter. Ask for proof of professional indemnity and cyber liability coverage, confirm the limits, and negotiate liability terms before the engagement begins rather than after an incident.
Should I hire the same company to fix what it finds?
Sometimes, but manage the conflict. If the firm also sells remediation, ask how it separates assessment from fix work and whether the same staff do both. Independent remediation advice, or a separate implementation partner, usually produces a cleaner outcome.
How do I verify a firm’s claims before signing?
Request a redacted sample report, ask for two or three references in your sector, confirm named personnel in the contract, and check insurance certificates directly. A short call with a past client reveals more about report quality and communication than any pitch deck.

