ESSENTIAL GUIDANCE · POST-TEST · 3 min read

Part of Validate insights →

Which penetration-test findings should you fix first?

How to order confirmed penetration-test findings using validated exploitability, credible attack paths and business consequence.

Technical review lead: James Hinton · Offensive security lead

A penetration-test report gives you confirmed findings, but it does not remove the need for a defensible action order. Security leaders and engineering owners should prioritise the attack paths that create the greatest practical consequence, then distinguish urgent containment from planned root-cause remediation.

Need an acronym translated?Open the cyber glossary →

Start with validated exploitability

Use the evidence produced during the penetration test rather than treating scanner severity as the queue. A reproduced weakness with clear preconditions and demonstrated impact should carry more decision weight than an unverified detection. Confirm what the tester achieved, which access was required and which limitations affected the result.

Look for findings that enable an attack chain

A medium-rated weakness can become urgent when it supplies credentials, access or information needed to exploit another condition. Review findings together and identify which one opens, shortens or strengthens a credible route to sensitive systems, privileged identities or important business processes.

Add asset importance and business consequence

Consider what the affected asset supports, the data or operations at risk and the consequence of loss of confidentiality, integrity or availability. The same technical weakness can justify a different response on an isolated test service than on an internet-facing identity system or revenue-critical application.

Account for exposure, privileges and controls

Priority increases when an attacker can reach the condition easily, exploit it without authentication or use it to gain valuable privileges. Effective segmentation, monitoring, access restrictions or other compensating controls may reduce immediate likelihood, but record their limits and do not treat them as proof that the root cause is resolved.

Fix dependencies and root causes in the right order

Identify findings that share a dependency or stem from the same design, configuration or development weakness. A root-cause fix may close several attack paths, while patching symptoms individually can leave equivalent routes open. Sequence work so prerequisite controls and shared causes are addressed before teams repeat the same change across multiple tickets.

Separate containment from planned remediation

Immediate containment may involve restricting access, disabling a feature, rotating credentials or increasing monitoring while a durable fix is designed and tested. Record the temporary control, its owner and review date. Containment changes urgency; it does not automatically close the confirmed finding.

Define the evidence needed for closure

For each material finding, name the accountable owner, target date, expected remediation evidence and retest criteria. Preserve the original steps and affected scope so the tester can verify the fix against the demonstrated condition and check that an alternative route has not been introduced.

Ready for the Pentesys point of view?

This guide covers the essentials. Continue into our technical analysis for a firmer position, practical implications and recommended action.

Read “Stop treating vulnerability severity as vulnerability priority” →
TALK TO PENTESYS

Apply this guidance to your environment.

Tell us what you need to understand, test or prove. We'll help you choose a proportionate next step—without forcing the conversation into a predefined package.

Discuss your penetration-test findings →Explore Validate

Keep reading

Pentesys trust and assurance

Recognised credentials. Responsible AI. Experienced people.

Clear evidence of our company standards, testing services and access to AI programmes.

Independent company assurance

CREST member company for Penetration Testing in EMEA

CREST member company

Penetration Testing in EMEA. Company standards independently assessed by CREST.

Valid until 1 November 2026View company certificate
CREST Security Testing accreditation for penetration testing

CREST-accredited human-led penetration testing

Independent assurance for Pentesys’s human-led penetration-testing service.

Human-led testingView CREST listing

AI-enabled testing assurance

CREST accreditation for AI-enabled penetration testing

CREST-accredited AI-enabled penetration testing

Pentesys is one of the first ten companies worldwide accredited by CREST for AI-enabled penetration testing. The accreditation assesses the responsible, secure and appropriate use of AI in penetration-testing services.

AI-enabled penetration testingView CREST announcement

Responsible-AI commitment

CREST AI Charter signatory

CREST AI Charter signatory

A separate commitment to responsible, transparent and accountable use of AI in cybersecurity.

Responsible-AI commitmentAbout the CREST AI Charter

Secure organisational baseline

Cyber Essentials certified

Cyber Essentials certified

Pentesys is certified across the whole organisation against the Cyber Essentials baseline controls.

Recertification due 12 August 2027View Cyber Essentials certificate

Controlled AI programme access

Pentesys participates in Anthropic’s Cyber Verification Program (CVP) for Claude and has approved access to OpenAI Daybreak Blue.

Anthropic CVP for Claude

Participation in Anthropic’s Cyber Verification Program.

Programme participationAbout Anthropic CVP

OpenAI Daybreak Blue

Approved access for defensive cybersecurity work.

Approved programme accessAbout Daybreak Blue

CREST accreditation applies to Pentesys’s service delivery, not to an AI model, the Portal or an appliance.

Meet the expertise behind our testing