Cybersecurity Advisory / Field guide
Security assessment, vulnerability scan, or penetration test: which do you need?
These services are often grouped together even though they answer different questions. The right choice depends on whether you need a broad view of controls, repeatable coverage of technical weaknesses, or controlled proof that an authorized weakness can become a realistic attack path.
1. Start with the decision—not the service label
A request for a “security test” may actually be asking one of several questions: Are important controls designed and operated effectively? Are known technical weaknesses present across the authorized asset population? Can a weakness be used to reach meaningful impact? Each question requires a different evidence model.
Before selecting a service, identify the decision the result must support, the systems and locations that matter, the audience for the output, the level of operational risk that is acceptable, and what the organization expects to do next.
2. Security assessment: understand posture and priorities
A security and risk assessment reviews agreed controls, configurations, architecture, evidence, and operating practices. It is useful when leadership or technical owners need an independent view of current posture, material gaps, and the sequence of improvement.
An assessment may include focused technical validation, but active exploitation is not implied. The output typically connects observations to affected scope, risk context, ownership, and a prioritized roadmap. It is not automatically a compliance attestation, certification, or legal opinion.
- Best question: Which gaps materially change risk, resilience, or assurance?
- Typical evidence: architecture, configurations, control records, procedures, and stakeholder context
- Typical output: executive risk brief, findings register, and prioritized improvement roadmap
3. Vulnerability assessment and management: establish coverage and accountable action
Vulnerability scanning uses automated tools to identify potential weaknesses across authorized assets. A professional vulnerability assessment adds coverage review, credential-quality analysis, technical validation, asset and exposure context, exception handling, and prioritization.
The work can be point in time or recurring. A recurring program also defines authoritative asset sources, cadence, ownership, remediation workflow, aging, exceptions, trend reporting, and validation. Scanning alone does not establish that every detection is exploitable or that every in-scope control is effective.
- Best question: Are the right assets covered, and which credible findings should be owned first?
- Typical evidence: asset inventory, scan coverage, credentials, validated detections, exposure, and remediation status
- Typical output: validated register, coverage summary, accountable priority queue, and recurring trend record
4. Penetration testing: validate realistic attack paths
Penetration testing uses controlled manual techniques to determine whether authorized weaknesses form realistic attack paths and what impact those paths could support. It goes beyond broad detection by testing assumptions, chaining conditions where permitted, and preserving reproducible evidence.
Because the activity can affect systems and data, written authorization, approved targets, exclusions, timing, communications, safety limits, evidence handling, stop conditions, and escalation contacts must be established before testing. Denial-of-service, social engineering, physical access, persistence, and third-party targets are not implied.
- Best question: Can an authorized weakness become a credible path to material impact?
- Typical evidence: reproducible findings, attack-path sequence, affected scope, and impact context
- Typical output: validated findings, attack-path narrative, remediation guidance, and optional retest record
5. When the services should work together
The services can form a useful sequence when the phases remain explicit. An assessment may identify control or architecture concerns. Vulnerability work may establish asset coverage and a credible technical backlog. A penetration test may then validate selected attack paths within an authorized boundary.
Combining the labels into an undefined “full security review” usually weakens the work. Each phase should identify its objective, targets, methods, limitations, evidence, decision owner, and handoff. Findings should not be presented as interchangeable simply because they share a severity label.
6. Questions to ask before approving a proposal
A credible proposal should make the service boundary understandable before work begins. It should also explain how material observations will be communicated, how evidence will be protected, and how the final output will support remediation or another decision.
- What exact question will this engagement answer?
- Which systems, identities, locations, third parties, and time periods are in and out of scope?
- Which techniques are permitted, and what requires separate written authorization?
- How are coverage, evidence quality, limitations, and confidence communicated?
- What artifacts will leadership and technical owners receive?
- Is remediation support, retesting, or recurring program design included or separate?
This guide provides general information for planning and evaluation. Exact technical, security, legal, and commercial requirements depend on the environment and agreed scope.
