PENTESYS POINT OF VIEW · ENGINEERING · 3 min read

Part of Validate insights →

OWASP Top 10 2025 for development teams

Translate the current awareness list into engineering priorities and a testable application-specific plan.

Technical review lead: James Hinton · Offensive security lead

OUR POSITIONUse the current OWASP Top 10 as a starting point for risk discussion, then define controls and verification for the application’s real boundaries.

Use the current OWASP Top 10 as a starting point for risk discussion, then define controls and verification for the application’s real boundaries.

01

Use the current edition and its purpose

OWASP's current web-application awareness list is the Top 10 2025 edition. It is a way to discuss important categories of application risk, not a complete test specification or a certification scheme. Record the edition when mapping work so old identifiers and new categories are not mixed. Build the assessment around the application rather than assuming ten headings create complete coverage.

02

Recognise the 2025 categories

The list covers Broken Access Control, Security Misconfiguration, Software Supply Chain Failures, Cryptographic Failures and Injection, followed by Insecure Design, Authentication Failures, Software or Data Integrity Failures, Security Logging and Alerting Failures, and Mishandling of Exceptional Conditions. Keep the category name and version with any mapping, then identify the specific application behaviour or engineering control that needs attention.

03

Connect categories to the design

For each important workflow, identify identities, assets, inputs, dependencies and trust boundaries. Ask what the server must enforce and what should happen when a dependency or action fails. A category can prompt that discussion without answering it automatically. For example, knowing that access control matters does not establish which tenant should own a particular record or which support action is legitimately privileged.

04

Choose evidence that tests the control

Use suitable design review, code review, configuration checks and authorised runtime testing for the question. Include business-specific abuse and failure paths rather than relying only on generic scanner coverage. Define access, test data and expected outcomes before active work begins. A tool's claim to cover the Top 10 does not establish which parts of the application were meaningfully assessed.

05

Make remediation specific and durable

Assign corrections to the affected design or implementation boundary, then verify both permitted and prohibited behaviour where relevant. Keep the observed issue, the change and follow-up evidence connected. Add useful regression checks and review recurring patterns across teams. Report the mapping as context alongside concrete evidence, not as a pass badge that implies every vulnerability or risk has been eliminated.

Sources and further guidance

Start with the complete guide

Use the essential guide for the wider scope, process and buying context behind this analysis.

Read “Penetration testing: scope, process, costs and what happens after the report” →
Editorial note

This current engineering guide replaces the retired legacy topic. Apply the recommendations to the actual application and verify changes within an authorised scope.

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.

Apply this to my environment →Explore Validate

More Pentesys analysis

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