Pentest subscription for web applications and APIs - Recurring pentests quarterly or monthly, with proof per confirmed finding, from €2,500 excl. VAT per year (quarterly, small application). Book an intro call · One-off pentest
How often a pentest is needed is answered with varying precision by standards. PCI DSS and, for financial entities designated by the authority, DORA Article 26 (threat-led tests at least every three years) name fixed deadlines for pentests. DORA Article 24 additionally requires yearly appropriate tests without prescribing a pentest. NIS2 requires procedures to assess the effectiveness of measures, the GDPR regular testing and evaluation, the IT-Grundschutz module APP.3.1 regular checks of web applications and TISAX, depending on protection needs, audits and tests. None of these further texts names a fixed pentest deadline. This article rereads the texts and reports what they say on frequency. It shows which events, according to the sources, are a reason for a test regardless of the calendar, compares an annual pentest with a subscription in cost and benefit, and marks what is source and what is our assessment. No line says that a specific test or provider satisfies a standard; that depends on the respective framework and the body that assesses it. The difference between a pentest and a scan is explained in Pentest vs Vulnerability Scan.
Table of contents
- How often to run a penetration test: the short answer
- What standards and frameworks require: pentest frequency by standard
- Triggers outside the calendar
- Annual, quarterly, monthly: a decision grid
- Cost: annual pentest vs subscription
- Our approach at WZ-IT
- Common misconceptions
- Status and methodology
- Further guides
How often to run a penetration test: the short answer
There is no single interval. Among the sources we checked, fixed deadlines for pentests are named by PCI DSS (at least every 12 months and after significant changes) and by DORA Article 26 for financial entities designated by the authority (threat-led tests at least every three years). DORA Article 24 additionally requires at least yearly "appropriate tests" for systems supporting critical or important functions, without prescribing a pentest. The BSI recommends repeat tests every two to three years. Significant changes are named as a reason for a test regardless of the calendar by PCI DSS (mandatory) and by the BSI and ENISA (as a recommendation). With frequent releases a quarterly or monthly rhythm is an option; that is our assessment.
| Question | Short answer |
|---|---|
| Where is there a fixed deadline? | PCI DSS 11.4: at least every 12 months (PCI SSC); DORA Art. 26(1): threat-led tests (TLPT) at least every three years, for financial entities designated by the competent authority; also Art. 24(6): at least yearly "appropriate tests", without prescribing a pentest (EUR-Lex) |
| Where is there no fixed deadline? | NIS2 Art. 21, GDPR Art. 32, IT-Grundschutz APP.3.1.A22, TISAX ISA 5.2.6 and 5.3.1; for ISO/IEC 27001 the standard text could not be checked |
| What does the BSI recommend? | Repeat test every two to three years (BSI guide, in German) |
| What counts outside the calendar? | Commissioning, significant changes, security incidents (BSI, PCI SSC) |
| Is an annual date enough? | For some requirements yes. With frequent releases, changes are not covered by the pentest until the next date (our assessment) |
What standards and frameworks require: pentest frequency by standard
The table reports what each text says on frequency, with a link to the source. Where no fixed deadline exists, the column "Fixed deadline?" says so.
| Framework | What the text says on frequency | Fixed deadline? |
|---|---|---|
| ISO/IEC 27001:2022, Annex A 8.8 and 8.29 (ISO) | The standard text is paid and was not checked, so we name no deadline. In its mapping table ENISA maps control A.8.29 to requirement 6.5 "Security testing" and control A.8.8 to requirement 6.10 "Vulnerability handling and disclosure" of Implementing Regulation (EU) 2024/2690. | Not checked |
| PCI DSS (wording of 4.0, current 4.0.1), requirements 11.3 and 11.4 (PCI SSC, SAQ D) | Internal (11.4.2) and external (11.4.3) penetration tests per the entity's defined methodology, at least once every 12 months and after any significant infrastructure or application upgrade or change, by a qualified internal resource or qualified external third party with organizational independence. Where segmentation is used, segmentation tests every 12 months (11.4.5), for service providers every 6 months (11.4.6). Vulnerability scans (11.3.1, 11.3.2) at least every three months. Intended for all entities that store, process or transmit cardholder data or could impact the security of the cardholder data environment. | Yes: 12 months |
| DORA, Articles 24 to 27 (Regulation (EU) 2022/2554, applicable since 17 January 2025) | Art. 24(6): financial entities other than microenterprises ensure, at least yearly, that appropriate tests are conducted on all ICT systems and applications supporting critical or important functions. Art. 25(1) lists possible tests, including vulnerability assessments and scans, source code reviews where feasible and penetration testing; Art. 24(6) does not prescribe the type of the yearly test. Art. 24(4): tests by independent parties, internal or external. Art. 26(1): threat-led penetration testing (TLPT) at least every three years, only for entities the authority identifies; microenterprises and entities under Art. 16(1) first subparagraph (simplified ICT risk management framework) are excluded; the authority may increase or reduce the frequency. Art. 27: requirements for TLPT testers. | Yes: yearly "appropriate tests", TLPT every 3 years |
| NIS2, Article 21 (Directive (EU) 2022/2555; in Germany section 30 BSIG, in German) | Art. 21(2)(e) requires security in acquisition, development and maintenance including vulnerability handling, point (f) policies and procedures to assess the effectiveness of the measures. The article names neither penetration tests nor a deadline. In Germany section 30(2) nos. 5 and 6 BSIG name corresponding measures for essential and important entities. For certain providers, including cloud computing, data centre and managed service providers, Implementing Regulation (EU) 2024/2690 provides: the need, scope, frequency and type of security tests derive from the risk assessment (Annex 6.5.2), vulnerability scans run, where appropriate, at planned intervals (6.10.2). | No |
| GDPR, Article 32(1)(d) (Regulation (EU) 2016/679) | A process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures. The article names neither pentests nor a deadline. | No |
| BSI IT-Grundschutz, Compendium Edition 2023, APP.3.1.A22 "Penetrationstest und Revision" (in German) | Standard requirement: web applications and web services "SOLLTEN regelmäßig auf Sicherheitsprobleme hin überprüft werden" (should be checked regularly for security problems), regular revisions, results documented and presented to the ISB. The requirement names no deadline. Outside the Compendium the BSI recommends repeat tests every two to three years (pentest guide) and at the latest after three years for the IS web check (web check guide). | No, recommendation 2 to 3 years |
| TISAX, VDA ISA 6 (ENX); ISA2027 applies to assessments ordered from 1 January 2027 (ENX) | 5.2.6: regular system or service audits; for high protection needs additional requirements for critical systems, with examples "service specific tests and tools and/or human penetration tests, risk-based time intervals"; for very high protection needs regular scans for vulnerabilities. 5.3.1, very high protection needs: the security of purpose-built or significantly customized software is tested (e.g. penetration testing) during commissioning, in case of significant changes or at regular intervals. | No |
For context: the PCI SSC describes the pentest in its 2017 supplement (on PCI DSS 3.2) as a manual process that may include tools. On "significant", PCI DSS 4.0 names categories of changes, including new hardware or software and replacements or major upgrades in the cardholder data environment, changes to the flow or storage of account data, to the scope, to the supporting infrastructure and to third-party providers. Each of these changes must be considered and evaluated as to whether it is significant for the entity (PCI SSC FAQ 1317). The 2017 supplement adds that a change may be considered significant if it could impact the security of the network or allow access to cardholder data (section 2.6). According to the PCI SSC, a merchant clarifies whether and which attestation is required with the compliance-accepting entity, typically an acquirer or a payment brand (PCI SSC FAQ 1215). In DORA, Article 24(6) names "appropriate tests", not expressly the pentest. The ENISA guidance on Implementing Regulation 2024/2690 is non-binding; it says tests should take place at set-up, after significant upgrades or modifications and following maintenance, and entity-wide tests at planned intervals or when significant incidents or changes occur (ENISA, section 6.5).
Triggers outside the calendar
A fixed interval only covers the time between two dates. Sources and practice name events that are a reason for a test regardless of the calendar.
| Trigger | Why | Source |
|---|---|---|
| First commissioning, go-live | According to the BSI a pentest is usually sought after first commissioning; TISAX names commissioning for purpose-built or significantly customized software at very high protection needs | BSI, ENX |
| Release with a significant change | PCI DSS requires tests after any significant upgrade or change to infrastructure or application; PCI DSS 4.0 names categories of significant changes, and the organization assesses them for its own environment | PCI SSC FAQ 1317 |
| New roles or tenants | A pentest with test accounts per role checks permissions and tenant separation; OWASP calls application security assessment software ineffective at in-depth assessment and test coverage | Our assessment, supported by OWASP |
| New interface, API or integration | A new interface can widen the attack surface; ENISA recommends thoroughly testing the endpoints of external integrations | Our assessment, ENISA |
| Security incident | The BSI names an attack as an occasion but cautions that any necessary evidence collection must be completed first; ENISA names significant incidents for entity-wide tests | BSI, ENISA |
| Takeover of an application or a company | The state of code and operations is not known from your own review | Our assessment |
Two notes on timing. In its 2008 guide NIST describes that tests may be postponed if a major upgrade is imminent, or brought forward if weaknesses are suspected: the timing follows the test objective (NIST SP 800-115, section 6.2). The BSI also states: because testers cannot take over quality assurance and operational blindness must be avoided, the same test objects should not be examined repeatedly by the same testers (section 3.1.1). After every change, reproducible tests of the internal quality assurance should check again (section 1.4.2) (BSI).
Annual, quarterly, monthly: a decision grid
In our assessment, two variables mainly determine the pentest interval: how often the code changes and how high the protection need is. Further factors are the size of the application, its attack surface, customer requirements and the legal scope. The grid is our assessment. The sources name minimum deadlines and recommendations but no upper bounds.
| Rhythm | Fits when | Background | WZ-IT offer |
|---|---|---|---|
| Every two to three years | Rarely changed systems with low protection needs | BSI recommendation for repeat tests | One-off pentest |
| Annual, plus after a significant change | Few releases a year or a requirement with a 12-month deadline | PCI DSS 11.4; DORA Art. 24(6); NIST (2008, networks and systems): an annual test can be sufficient given cost and impact | One-off pentest |
| Quarterly | Quarterly release rhythm, ongoing development, higher protection needs | Our assessment; ISA names risk-based time intervals for high protection needs | Subscription |
| Monthly | Frequent releases, new features at short intervals, very high protection needs | Our assessment | Subscription |
| Additionally by event | Any time an occasion from the previous section occurs | PCI DSS, BSI, ENISA | One-off pentest |
Two further rhythms exist alongside the pentest. Vulnerability scans run more often: PCI DSS requires them as a separate requirement at least every three months (PCI SSC), and NIST names a programme of regularly scheduled scans supplemented by periodic pentests (NIST SP 800-115, section 5.2). Between pentests an ongoing code review can technically assess risk-relevant changes to the code; we offer this as AI Code Review. The BSI recommends that the internal quality assurance tests reproducibly after every change.
Cost: annual pentest vs subscription
The WZ-IT one-off pentest costs €1,000 to €2,000 excl. VAT, depending on the size of the application. The subscription with quarterly or monthly tests costs from €2,500 excl. VAT per year (quarterly, small application).
| Model | Price excl. VAT |
|---|---|
| One-off pentest | €1,000 (small), €1,500 (medium), €2,000 (large), fixed price by size of the application |
| Quarterly subscription, 4 runs a year | €2,500 (small), €3,750 (medium), €5,000 (large) per year |
| Monthly subscription, 12 runs a year | €4,000 (small), €6,000 (medium), €8,000 (large) per year |
The following table names anonymized ranges of published offers from other providers (as of 19 November 2026). They come from our own survey of publicly visible price information of several providers, who are deliberately not named. The services differ in method, application size and depth of reporting and are not equivalent.
| Model | Published price range |
|---|---|
| Once a year, manual | Billed by effort: one provider states hourly rates of around €100 to €210 net depending on the role, another around €1,600 per person-day; several providers state a retest at no extra charge |
| Single test, automated | Around €1,250 to €3,500 or around US$3,000 to US$5,100 per test; euros and dollars not converted |
| Continuous | Scanner platforms with an annual fee from €0 in an entry plan up to four to five digits in euros; automated continuous pentests are billed as an annual package or by usage |
Our approach at WZ-IT
We offer the pentest subscription quarterly or monthly; the subscription costs from €2,500 excl. VAT per year (quarterly, small application). If you only need one date before a release, you book the one-off pentest, which costs €1,000 to €2,000 excl. VAT, depending on the size of the application. Whether your framework fits is clarified before the offer. This is how a test runs:
- Handover: you hand over the source code, a test instance and test accounts per role and tenant.
- Ownership check: we verify ownership of the target.
- Inventory: we record all routes of the application completely.
- Attack: the attacks run against the test instance, never against the production system.
- Proof: confirmed findings come with proof. Every finding carries one of four states: confirmed, refuted, suspicion without confirmation, or not tested.
- Manual review: the team reviews severe confirmed findings by hand.
- Report: the report contains a coverage table that shows what was tested and what was not.
Between pentests, the ongoing AI Code Review can technically assess risk-relevant changes to the code at the agreed rhythm, from €990 excl. VAT a month. On request we fix the findings and take over hosting and operations. We clarify in advance which requirements your customers or auditors set. Whether a test satisfies a requirement depends on the respective framework and the body that assesses it.
Common misconceptions
| Misconception | Correct | Source |
|---|---|---|
| ISO 27001 requires a pentest every year. | We could not verify this: the standard text is paid and was not checked. Clarify the expected type of test and interval with the certification auditor. | ISO |
| NIS2 prescribes an annual pentest. | Article 21 names neither penetration tests nor a deadline. | NIS2 Directive |
| DORA requires a pentest every year. | Article 24(6) requires yearly "appropriate tests" for systems supporting critical or important functions. TLPT every three years applies only to entities identified by the authority. | DORA |
| Under PCI DSS the quarterly scan is enough. | Scans (11.3, every three months) and pentests (11.4, every 12 months and after significant changes) are separate requirements. | PCI SSC |
| Every release needs a full pentest. | Under PCI DSS the significant change is the trigger (11.4.2, 11.4.3); PCI DSS 4.0 names categories of significant changes, and the organization assesses them for its own environment. | PCI SSC FAQ 1317 |
| The more often you test, the better. | In a 2008 guide, NIST considers an annual pentest of network and systems potentially sufficient given cost and potential impact and recommends additional, less labour-intensive regular tests. | NIST |
| A passed pentest satisfies the standard. | None of the sources says that a specific test or provider satisfies a requirement. That depends on the framework and the body that assesses it. | see table |
| The pentest replaces ongoing quality assurance. | The BSI recommends stating in the contract that the results are valid only at the time of the test, and recommends reproducible quality-assurance tests after every change. | BSI |
Status and methodology
Research status: 19 November 2026. This article is not legal advice. For legal and standard texts the quoted passages were checked against their wording: DORA, the NIS2 Directive, the GDPR and Implementing Regulation (EU) 2024/2690 from the Official Journal via the EU Publications Office (EUR-Lex returned no content on automated retrieval; the links lead to the version on EUR-Lex), section 30 BSIG from gesetze-im-internet.de, the BSI guides and the IT-Grundschutz module APP.3.1 (Edition 2023, listed as the latest edition on the BSI page on the reference date) as PDF, the VDA ISA catalogue (ISA 6 and ISA2027) and the ENISA mapping table as Excel files.
Limits of the check: we did not check the text of ISO/IEC 27001:2022, which is paid; the assignment of controls A.8.8 and A.8.29 comes from the ENISA mapping table. The wording of PCI DSS 11.3 and 11.4 comes from the PCI SSC's SAQ D for PCI DSS 4.0 (April 2022). The PCI SSC has announced that PCI DSS 4.0 will be retired on 31 December 2024, after which version 4.0.1 of June 2024 is the only supported version. It contains no new or deleted requirements but clarifies some of them (PCI SSC blog). The SAQ D for 4.0.1 and the main document of the standard were not reachable for automated retrieval (HTTP 403); we did not check whether the quoted deadlines and wording are word-for-word unchanged in 4.0.1. According to ENX, the English version of the TISAX catalogue is authoritative where translations differ (announcement on ISA2027); we quote it from VDA ISA 6. We compared the English version of ISA2027 with ISA 6 under 5.2.6 and 5.3.1: on the points named here (audits, scans, penetration tests, intervals) they make the same statements in substance; individual wordings are adjusted. The ENISA guidance is non-binding. The BSI pentest document dates from 2016 and the IS web check guide from 2020, both in German; quotes from them are our translations.
The ranges of other providers come from our own survey of publicly visible price information of several providers as of 19 November 2026; the providers are deliberately not named. Individual values rest on a single provider and are not a market average. Prices can change. The decision grid and all statements marked "our assessment" are our classification, not a requirement of any standard.
Further guides
- Pentest subscription: quarterly or monthly
- Automated white-box pentest for web applications and APIs
- AI Code Review: ongoing review of changes
- Pentest vs Vulnerability Scan: differences, proof and when to use which
- Vulnerability scanning in operations
Settle the rhythm for your application: We assess release cadence, protection needs and requirements and tell you how often a pentest makes sense. Book an intro call · Request a pentest subscription
Sources
- PCI SSC: SAQ D for service providers, PCI DSS 4.0, April 2022
- PCI SSC: Information Supplement Penetration Testing Guidance, version 1.1, September 2017
- PCI SSC: FAQ 1317, What is meant by "significant change" in PCI DSS?, April 2023
- PCI SSC: FAQ 1215, What is a PCI DSS Self-Assessment Questionnaire?, April 2024
- PCI SSC blog: Just Published, PCI DSS v4.0.1
- Regulation (EU) 2022/2554 (DORA)
- Directive (EU) 2022/2555 (NIS 2)
- Implementing Regulation (EU) 2024/2690
- Regulation (EU) 2016/679 (GDPR)
- BSIG section 30: risk management measures, in German
- ENISA: Technical Implementation Guidance on cybersecurity risk-management measures, version 1.0, June 2025
- ENISA: mapping table to the Technical Implementation Guidance, version 1.2
- BSI: Practical guide to IS penetration tests (Praxis-Leitfaden für IS-Penetrationstests), version 1.2, November 2016, in German
- BSI: Practical guide to the IS web check (Praxis-Leitfaden für den IS-Webcheck), version 1.6, January 2020, in German
- BSI: IT-Grundschutz Compendium Edition 2023, APP.3.1 Web applications and web services, in German
- ENX: VDA ISA 6, information security assessment catalogue
- ENX: 10 Years of TISAX, VDA ISA2027 Released
- ENX: VDA ISA2027, English version (Excel)
- ISO: ISO/IEC 27001:2022
- NIST SP 800-115: Technical Guide to Information Security Testing and Assessment, September 2008
- OWASP Web Security Testing Guide, version 4.2











