Before hiring a security assessment provider, ask how it scopes the work, verifies findings, and checks fixes. A sample report and written answers will tell you more than a sales presentation. Use these ten questions to compare the proposed engagements.
1. Is this a vulnerability assessment, a penetration test, or both?
Ask which activities are included. A vulnerability assessment identifies and validates weaknesses; a penetration test may also attempt exploitation and combine findings into an attack path. Providers use these terms differently, so get the planned techniques, access levels, and deliverables in writing.
2. What's included in the scope, and what costs extra?
List the applications, APIs, public assets, cloud accounts, and user roles to be tested. Ask whether internal testing and additional roles cost extra. Agree how discoveries outside the initial asset list will be handled before work starts.
3. How are findings verified before they land in the report?
Ask how a suspected issue becomes a confirmed finding. Request an example showing the tested request, relevant configuration, observed result, and business consequence. Automated results need review before your engineers spend time on them.
4. What powers the testing?
Ask how the provider combines automated tools, AI-assisted analysis, and specialist review. Find out who checks business logic and authenticated access, how suspected exploitation is validated, and what the methods cannot cover. The tool names matter less than the evidence the process produces.
5. How is severity determined?
Ask for the severity method and an example of its use. The rationale should include the affected asset, reachability, privileges, and business consequence alongside any CVSS score.
6. What does the pricing model charge for?
Compare hourly, fixed-fee, and outcome-based terms. For a no-findings, no-fee engagement, define what counts as a verified actionable finding and what you receive if nothing qualifies. Ceron’s core assessment is listed at $1,500 with no fee if no verified finding turns up. Confirm the scope and applicable terms before booking.
7. What does the deliverable include?
Request a sample report. Look for the tested asset list, verified findings, reproduction evidence, severity rationale, practical remediation guidance, and a concise explanation for leadership. Check whether an engineer could act on it without another sales call.
8. Is retesting after remediation included?
Ask whether the fee includes retesting and which cases it covers. Agree how fixes are submitted for verification and whether significant application changes require additional work.
9. How often should this run, and can they support that cadence?
Choose a cadence based on infrastructure changes, customer obligations, and applicable assessment requirements. Ask whether the provider can support both scheduled reviews and testing after a significant release. Compare the cost of that schedule with a single annual engagement.
10. Can they scale with you as your needs grow?
Ask how the engagement can expand when you add applications, cloud accounts, or authenticated roles. Check whether earlier scope and findings carry into later work and whether a deeper test requires a separate contract.
Before signing
Keep the answers with the proposal. Before signing, resolve unclear scope, finding criteria, deliverables, and retest terms. Those details determine what your team can expect when the report arrives.