Frequently asked questions.
Straight answers about penetration testing, what it costs, how it works, and what you walk away with. Don’t see your question? Ask us directly.
How much does a penetration test cost?
Pricing is based on scope: the size and complexity of what you want tested. A focused application or external network test can start in the low thousands, and larger, multi-target engagements scale from there. Because we scope each engagement to what you actually need instead of selling a fixed package, many clients are surprised it costs less than they expected, and far less than a breach. Tell us what you’d like tested and we’ll give you a clear, scoped quote.
What is the difference between a penetration test and a vulnerability scan?
A vulnerability scan is automated: a tool checks your systems against a database of known issues and produces a list, often padded with false positives. A penetration test is human-led: a senior engineer actually exploits weaknesses, chains them into real attack paths, and proves what an attacker could do. A scan tells you what might be vulnerable; a penetration test tells you what is genuinely exploitable, and how much it matters.
Do you test manually or with automated tools?
Both, in the right balance. Our senior engineers lead every engagement and do the deep, creative exploitation that tools cannot. We use automation and our own AI tooling to expand coverage and move faster, never to replace human judgment. You get the reach of automation with the depth of a senior human, and findings that are validated rather than scanner noise.
How long does a penetration test take?
Most engagements involve a few days to a couple of weeks of active testing, depending on scope, followed by reporting. We give you a clear timeline when we scope the work and plan testing windows around your operations.
Will testing disrupt our production systems?
We design engagements to be safe. We agree on scope and rules of engagement up front, avoid destructive techniques unless you specifically authorize them, and coordinate sensitive testing with your team. The goal is to find what an attacker would, without causing an outage.
What is the difference between a penetration test and a red team engagement?
A penetration test answers “what is exploitable?” across a defined scope. A red team engagement answers “can an attacker reach a specific objective?”, such as your most sensitive data, while also testing whether your team detects and responds. Red teaming is broader, goal-driven, and blends digital, physical, and social-engineering vectors.
What do we get at the end of an engagement?
A clear, prioritized report written for both executives and engineers: every finding with its risk rating, proof-of-concept evidence, business impact, and specific remediation guidance. We walk your team through the results, and we retest your fixes to confirm the risk is closed, included, not billed as an extra.
How often should we get tested?
At least annually, and after any significant change: a major release, a new environment, a merger, or a move to the cloud. Many clients run a regular program, such as semi-annual or quarterly testing, to keep pace with how quickly their systems and the threat landscape change.
Can you help us meet compliance requirements like SOC 2, PCI DSS, HIPAA, or ISO 27001?
Yes. Our testing maps cleanly to the frameworks your business answers to, so a single rigorous engagement supports your audit and genuinely reduces risk. You get the evidence and reporting your auditors expect, while we find the issues a checkbox approach would miss.
How do we get started?
Tell us what you’d like tested and a bit about your environment. We’ll scope the engagement, give you a clear quote and timeline, and put a senior engineer on it. No junior analysts, no scripted sales calls. Reach us through the contact page or call 888-275-1001.
Still have questions?
Talk to a senior engineer who actually does the work, not a sales rep working from a script.