Summary
Penetration testing has become one of the most active sub-categories in EU public procurement cybersecurity, driven by NIS2 compliance requirements, mandatory security testing for critical national infrastructure, and growing regulatory pressure on public health, transport, and digital services. Government pen test contracts typically range from €50,000 for a focused web application test to over €500,000 for comprehensive red team exercises or multi-year retainer frameworks. This guide covers the types of tests being procured, the specific CPV codes to monitor, qualification requirements including CREST and OSCP, and the strategies that win these contracts.
The Government Pen Test Market in 2026
Public sector penetration testing procurement has grown substantially as EU governments transition from reactive to proactive cybersecurity postures. The NIS2 Directive's explicit requirement for "regular security testing" has converted pen testing from an optional best practice to a compliance necessity for thousands of public bodies. National cybersecurity agencies in France (ANSSI), Germany (BSI), the Netherlands (NCSC), and others actively encourage or mandate regular penetration testing for critical infrastructure operators.
The procurement pipeline spans all government tiers:
- Central government ministries — IT systems handling tax, benefits, identity, and national security
- National health services — Patient record systems, connected medical devices, telemedicine platforms
- Transport authorities — Rail, aviation, port, and road management systems
- Energy utilities — Industrial control systems (ICS/SCADA), smart meter infrastructure
- Local governments — Citizen-facing portals, payment systems, planning applications
- EU institutions — European Commission, Parliament, and agencies via DIGIT and CERT-EU
Types of Pen Tests Procured by Government
Government tenders for penetration testing cover a wide range of test types, often bundled into a single contract or framework:
- Web application penetration testing: The most common type. Testing of citizen portals, internal web applications, APIs, and cloud-hosted systems for OWASP Top 10 vulnerabilities and beyond. Typical value: €15,000–€80,000 per engagement.
- Network infrastructure testing: External and internal network testing covering firewalls, routers, VPNs, and segmentation. Often procured alongside web app testing. Typical value: €20,000–€120,000.
- Red team exercises: Adversary simulation engagements testing the full kill chain — from initial access through lateral movement to data exfiltration. Typically reserved for higher-security environments. Value: €80,000–€500,000+.
- Social engineering assessments: Phishing simulations, vishing, and physical security testing. Increasingly bundled with awareness training programmes.
- OT/ICS/SCADA security testing: Specialist testing of operational technology environments in energy, water, and transport. High barriers to entry but premium contract values.
- Cloud penetration testing: Testing of cloud-hosted workloads, container environments, and cloud configuration against CIS Benchmarks.
- Mobile application testing: Government apps for citizen services, healthcare, and transport.
CPV Codes to Monitor
Penetration testing lacks a dedicated CPV code — contracting authorities use a range of codes:
- 72220000 — Systems and technical consultancy services (most commonly used for pen testing)
- 72212730 — Security software development services (sometimes used for automated scanning tools)
- 72222300 — Information technology services
- 79212000 — Auditing services (used when pen testing is framed as a security audit)
- 72212517 — IT software development services
Because no single code reliably captures all pen testing tenders, set up broad keyword alerts ("penetration test", "pen test", "ethical hacking", "vulnerability assessment", "red team") alongside CPV monitoring on TED and national portals.
Qualification Requirements
Government pen test contracts carry specific professional qualification requirements that vary by country and contract type. Commonly required:
- CREST certification: The CREST Registered Tester (CRT) and CREST Certified Tester (CCT) qualifications are widely specified in UK and Irish government tenders, and increasingly referenced in mainland European contracts.
- CHECK scheme membership: NCSC CHECK status is required for testing UK government systems (relevant for suppliers bidding into UK-adjacent contracts).
- OSCP / OSEP / OSED: Offensive Security certifications are commonly listed as "desirable" or "required" for individual testers on the project team.
- CEH (Certified Ethical Hacker): Widely recognised in Southern and Eastern European government tenders.
- ISO 27001 company certification: Required for corporate qualification, not just individual testers.
- Security clearances: Personnel clearances required for testing classified or law enforcement systems — plan 6–18 months ahead.
Framework Agreements for Pen Testing
Several national frameworks cover penetration testing services, allowing public bodies to call off contracts without running full open procedures:
- Germany: BSI-certified information security service providers (CISS) list — companies must apply for BSI certification to be eligible for federal security contracts.
- France: ANSSI PRIS (Prestataires de réponse aux incidents de sécurité) and PDIS (Prestataires de détection des incidents de sécurité) qualification schemes.
- Netherlands: Central government IT security framework via NCSC-NL affiliated procurement.
- EU institutions: DIGIT cybersecurity frameworks and CERT-EU approved supplier lists.
Winning Strategy for Government Pen Test Tenders
Government evaluators for pen testing contracts are typically technical but not always senior practitioners — they are often IT security managers or procurement officers guided by technical advisors. Your bid must be credible at both levels: technically rigorous for the security experts reviewing methodology, and clearly structured for the procurement team evaluating compliance.
Differentiate your bids by including: a clear testing methodology aligned to recognised frameworks (OWASP, OSSTMM, PTES, TIBER-EU); named testers with specific certifications; a sample deliverable showing the quality and clarity of your reporting; a remediation support offer (fixing identified vulnerabilities or advising on fixes); and references from comparable public sector engagements. Pricing transparency — showing day rates and estimated effort by phase — also builds evaluator confidence in contracts where the scope is fixed.