{
  "slug": "penetration-testing",
  "topic": "Penetration testing",
  "status": "published",
  "order": 34,
  "capability": "exposure/pentest",
  "title": "Penetration testing: are you testing what attackers target, and fixing what testers find?",
  "short": "Scope tests around identity, internet-facing systems and critical apps, and fix and retest critical and high findings within 30 days, or 14 if internet-facing.",
  "answer": "Before the next test, write down the question it must answer and scope it around identity, internet-facing systems and critical apps, not an IP list. Judge each test by how many findings were fixed and retested on time.",
  "audience": "IT, security and engineering leads in EU organizations, many in Germany, who commission penetration tests or red team exercises, or must under DORA or PCI DSS",
  "version": "1.0",
  "lastReviewed": "2026-11-05",
  "reviewEveryDays": 30,
  "blocks": [
    {
      "type": "ranked",
      "id": "first",
      "title": "If you only do five things",
      "navTitle": "Five things",
      "items": [
        {
          "title": "Start from a question, not a product.",
          "text": "The NCSC treats a penetration test as an audit of your vulnerability management: you should already know most of what it finds[^ncscpt]. Write down the question the test must answer."
        },
        {
          "title": "Scope by attacker targets.",
          "text": "Exploits opened 32% of Mandiant's 2025 intrusions and voice phishing 11%, with groups calling help desks to get past MFA[^mtrends]. Scope identity, the help desk, the edge and critical apps first."
        },
        {
          "title": "Give testers the inside view.",
          "text": "The BSI recommends white-box tests, since black-box tests miss more and risk more damage[^bsipt]. Hand over network plans, test accounts, source code and your latest vulnerability assessment[^bsipt][^ncscpt]."
        },
        {
          "title": "Get written authorization from every owner.",
          "text": "The BSI says never to test without a written contract, and to include any hoster[^bsipt]. Microsoft won't authorize testers for you[^azpt]."
        },
        {
          "title": "Retest and track every finding to closure.",
          "text": "PCI DSS requires a retest to verify fixes[^pci] and DORA a check that every weakness is addressed[^dora]. Give each finding an owner and a deadline, and book the retest with the test."
        }
      ]
    },
    {
      "type": "steps",
      "id": "commission",
      "title": "Commission a test in this order",
      "navTitle": "Commissioning",
      "items": [
        {
          "title": "Agree the scope with the risk owner.",
          "text": "Involve risk owners, technical staff and the testers, and agree boundaries, test types, effort in days and reporting[^ncscpt]."
        },
        {
          "title": "Get everyone on board.",
          "text": "The system owner, any hoster or SaaS provider and, if staff or personal data are affected, the data protection officer and works council[^bsipt]."
        },
        {
          "title": "Set the rules of engagement.",
          "text": "Agree the window, exclusions, depth and a stop rule[^bsipt], and a contact on call[^ncscpt]. Freeze changes; if a flaw can't wait, pause the test[^bsipt]."
        },
        {
          "title": "Read the report critically.",
          "text": "The risk decision is yours[^ncscpt]. Group repeated findings[^bsipt] and ask why you didn't already know about each one[^ncscpt]."
        },
        {
          "title": "Close the loop.",
          "text": "Fix by deadline, retest and add each finding to your own regular checks[^bsipt]. Removing the software or adding monitoring may suffice instead of the suggested patch[^ncscpt]."
        }
      ]
    },
    {
      "type": "list",
      "id": "types",
      "title": "Pick the test that answers your question",
      "navTitle": "Test types",
      "span": "full",
      "items": [
        "**Vulnerability scan: which known flaws are open?** Automated and frequent; see the attack surface sheet. A penetration test adds a competent manual attacker[^pci].",
        "**Penetration test: does this system hold up against a skilled tester?** Days of manual work on one system with full information, after go-live and significant changes[^bsipt].",
        "**Assumed breach: how far does one compromised laptop or account get?** The tester starts inside, as in the NCSC's lost laptop scenario[^ncscpt].",
        "**Red team: would you detect and stop a real attacker?** A covert, threat-led attack on live systems; under DORA the active phase lasts at least 12 weeks[^rts]. Wait until logging and alert handling work.",
        "**Purple teaming: which attacker techniques do you detect?** Testers and defenders work together and tune detections as they go. DORA requires it after every threat-led test[^rts].",
        "**Bug bounty: what do outsiders find over time?** See the secure development sheet."
      ]
    },
    {
      "type": "list",
      "id": "scope",
      "title": "Scope by risk, not by IP list",
      "navTitle": "Scope",
      "items": [
        "**Identity.** Paths from a normal user to domain admin or Global Administrator, including AD CS; the privileged access sheet lists fixes.",
        "**The help desk.** A call asking for an MFA reset, under rules agreed with the works council and run by specialists[^bsipt].",
        "**The internet edge and critical apps.** Everything in the attack surface sheet's inventory, and apps tested as the API security sheet describes.",
        "**Backups, hypervisors and tenants.** Ransomware groups target backups and virtualization management[^mtrends]; Microsoft encourages tenant tests[^azpt].",
        "**How often.** Test high-risk areas yearly and after major changes, as PCI DSS requires for card data[^pci]. For the rest, the BSI suggests every two to three years[^bsipt]."
      ]
    },
    {
      "type": "list",
      "id": "provider",
      "title": "Choose a provider",
      "navTitle": "Provider",
      "items": [
        "**Treat certificates as signals.** PCI DSS calls them an indication of skill and asks about past engagements too[^pci]. BSI personnel certification and CREST include practical exams[^bsipt].",
        "**In Germany, check the BSI list.** It names 22 providers certified for IS penetration tests[^bsilist].",
        "**In UK government and CNI, use CHECK.** Its team leaders hold the UK Cyber Security Council's Principal title and SC clearance[^check].",
        "**Buy the people, not the logo.** Get CVs of the named testers, at least two, check they do the work and rotate them over the years[^bsipt]."
      ]
    },
    {
      "type": "list",
      "id": "rules",
      "title": "Stay legal and safe",
      "navTitle": "Legal and safe",
      "items": [
        "**Authorization.** In Germany, getting past access protection without permission carries up to three years in prison or a fine[^stgb].",
        "**Cloud.** Azure and Google Cloud need no notice to test your own resources, AWS none for its listed services[^azpt][^gcp][^aws]. Azure and AWS ban DoS; AWS must approve covert red teaming and phishing, asked two weeks ahead[^aws].",
        "**Production and OT.** No test rules out side effects[^ncscpt]: keep a stop rule. In OT, use testers with OT experience[^ncsccni] and test in outages or on a replica."
      ]
    },
    {
      "type": "list",
      "id": "changed",
      "title": "What changed in 2026",
      "navTitle": "What changed",
      "items": [
        "**AI-assisted testing needs ground rules.** The NCSC's 10 questions from May 2026 cover who fixes the findings, sandboxing, data terms and legality[^ncscai]. Ask testers who use AI the same.",
        "**CREST accredits AI security testing.** It named the first four companies in November 2026[^crestai]. Ask for it, or comparable evidence, before testing a GenAI or LLM system."
      ]
    },
    {
      "type": "timelines",
      "id": "regulated",
      "title": "Tests a regulation or contract requires",
      "navTitle": "Required tests",
      "span": "full",
      "intro": "NIS2 requires essential and important entities to assess whether their measures work[^nis2], and cloud, managed service and other digital providers to set a risk-based testing policy[^nis2ir]. DORA requires yearly tests of systems behind critical or important functions, except at microenterprises[^dora].",
      "items": [
        {
          "name": "DORA threat-led penetration test (TLPT)",
          "scope": "Entities their authority selects, at least every 3 years, on live systems[^dora]. In Germany the Bundesbank's TIBER team manages tests BaFin or the ECB orders[^tiberde]. Clocks start at the notice, then at the end of red teaming[^rts].",
          "steps": [
            {
              "at": "3 months",
              "what": "Initiation papers"
            },
            {
              "at": "6 months",
              "what": "Scope document"
            },
            {
              "at": "12+ weeks",
              "what": "Active red teaming"
            },
            {
              "at": "4 weeks",
              "what": "Red team report"
            },
            {
              "at": "10 weeks",
              "what": "Replay, purple teaming"
            }
          ]
        },
        {
          "name": "PCI DSS v4.0.1, requirement 11.4",
          "scope": "The card data environment, by a qualified, organizationally independent tester who needn't be a QSA[^pci]. For segmentation tests, see the network segmentation sheet.",
          "steps": [
            {
              "at": "12 months",
              "what": "Internal and external tests"
            },
            {
              "at": "After changes",
              "what": "Significant upgrades"
            },
            {
              "at": "After fixes",
              "what": "Retest exploitable findings"
            }
          ]
        }
      ]
    },
    {
      "type": "list",
      "id": "skip",
      "title": "What you can skip",
      "items": [
        "**Black-box tests for realism.** Testers then spend paid days finding out what you could tell them. The BSI recommends white-box tests[^bsipt].",
        "**A red team before the basics.** If scans still find unpatched edge systems and nobody handles alerts, a red team only confirms it, at a high price.",
        "**Paying testers to recheck every finding.** The BSI wants your own staff to check fixes with repeatable tests[^bsipt]. Book external retests for critical and high findings only."
      ]
    },
    {
      "type": "list",
      "id": "mistakes",
      "title": "Mistakes that cost the most",
      "navTitle": "Mistakes",
      "items": [
        "**Taking a clean report as proof.** PCI DSS says a test that finds nothing usually reflects the tester's shortcomings[^pci]; see the edge devices sheet.",
        "**Letting the WAF test itself.** If it blocks the testers, you test the filter. Lift the blocks for them and test the gateway separately[^bsipt].",
        "**Leaving the testers' tools behind.** DORA makes testers remove backdoors and delete captured credentials[^rts]; demand the same.",
        "**Findings without an owner.** Risk decisions stay with you, not the testers[^ncscpt]."
      ]
    },
    {
      "type": "columns",
      "id": "by-size",
      "title": "What this looks like at your size",
      "navTitle": "By team size",
      "span": "full",
      "columns": [
        {
          "title": "Small team, no security staff",
          "items": [
            "Test your cloud tenant and internet edge yearly.",
            "Fix critical and high flaws in 30 days, 14 if exposed.",
            "Shortlist from the BSI list or CREST."
          ]
        },
        {
          "title": "Growing, with IT or security staff",
          "items": [
            "Test AD and Entra ID yearly from a user's laptop.",
            "Test critical app releases with source code.",
            "Report open findings by age every month."
          ]
        },
        {
          "title": "Enterprise or regulated",
          "items": [
            "Plan tests by risk for several years ahead.",
            "Map the plan to DORA[^dora] and PCI DSS 11.4[^pci].",
            "Report time to close to the board."
          ]
        }
      ]
    }
  ],
  "changes": [
    {
      "date": "2026-11-05",
      "version": "1.0",
      "text": "Published after a copy edit and a source-by-source fact check, which aligned fix deadlines with the patching sheet and narrowed 12 statements to what the sources say."
    },
    {
      "date": "2026-11-05",
      "version": "0.1",
      "text": "First draft, based on NCSC and BSI guidance, DORA and its TLPT standard, PCI DSS v4.0.1, M-Trends 2026 and the cloud providers' testing rules."
    }
  ],
  "sources": [
    {
      "id": "ncscpt",
      "title": "Penetration testing",
      "publisher": "NCSC (UK)",
      "date": "reviewed 10 Jan 2022",
      "url": "https://www.ncsc.gov.uk/guidance/penetration-testing"
    },
    {
      "id": "mtrends",
      "title": "M-Trends 2026",
      "publisher": "Google Cloud (Mandiant)",
      "date": "23 Mar 2026",
      "url": "https://cloud.google.com/blog/topics/threat-intelligence/m-trends-2026"
    },
    {
      "id": "bsipt",
      "title": "Praxis-Leitfaden für IS-Penetrationstests, version 1.2",
      "publisher": "BSI",
      "date": "Nov 2016",
      "url": "https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Sicherheitsberatung/Pentest_Webcheck/Leitfaden_Penetrationstest.pdf?__blob=publicationFile&v=3"
    },
    {
      "id": "azpt",
      "title": "Azure penetration testing",
      "publisher": "Microsoft Learn",
      "date": "15 May 2026",
      "url": "https://learn.microsoft.com/en-us/azure/security/fundamentals/pen-testing"
    },
    {
      "id": "pci",
      "title": "PCI DSS v4.0.1, req. 11.4",
      "publisher": "PCI SSC",
      "date": "Jun 2024",
      "url": "https://www.pcisecuritystandards.org/document_library/"
    },
    {
      "id": "dora",
      "title": "Regulation (EU) 2022/2554 (DORA), Art. 24 to 27",
      "publisher": "EUR-Lex",
      "date": "2022",
      "url": "https://eur-lex.europa.eu/eli/reg/2022/2554/oj"
    },
    {
      "id": "rts",
      "title": "Delegated Regulation (EU) 2025/1190 (DORA TLPT)",
      "publisher": "EUR-Lex",
      "date": "18 Jun 2025",
      "url": "https://eur-lex.europa.eu/eli/reg_del/2025/1190/oj"
    },
    {
      "id": "ncsccni",
      "title": "Building more resilient CNI: what industry pen testers told us",
      "publisher": "NCSC (UK)",
      "date": "1 Jul 2026",
      "url": "https://www.ncsc.gov.uk/blogs/building-more-resilient-cni-what-industry-pen-testers-told-us"
    },
    {
      "id": "bsilist",
      "title": "Liste IS-Penetrationstests",
      "publisher": "BSI",
      "date": "checked 5 Nov 2026",
      "url": "https://www.bsi.bund.de/DE/Themen/Unternehmen-und-Organisationen/Standards-und-Zertifizierung/Zertifizierung-und-Anerkennung/Listen/Liste-IT-Sicherheitsdienstleister-Pentester/liste-it-sicherheitsdienstleister-pentester_node.html"
    },
    {
      "id": "check",
      "title": "Information for CHECK buyers",
      "publisher": "NCSC (UK)",
      "date": "checked 5 Nov 2026",
      "url": "https://www.ncsc.gov.uk/schemes/check/information-for-buyers"
    },
    {
      "id": "stgb",
      "title": "StGB § 202a",
      "publisher": "BMJV",
      "date": "checked 5 Nov 2026",
      "url": "https://www.gesetze-im-internet.de/stgb/__202a.html"
    },
    {
      "id": "aws",
      "title": "Penetration Testing",
      "publisher": "AWS",
      "date": "checked 5 Nov 2026",
      "url": "https://aws.amazon.com/security/penetration-testing/"
    },
    {
      "id": "gcp",
      "title": "Cloud Security FAQ",
      "publisher": "Google Cloud",
      "date": "checked 5 Nov 2026",
      "url": "https://support.google.com/cloud/answer/6262505?hl=en"
    },
    {
      "id": "nis2",
      "title": "Directive (EU) 2022/2555 (NIS2), Art. 21",
      "publisher": "EUR-Lex",
      "date": "2022",
      "url": "https://eur-lex.europa.eu/eli/dir/2022/2555/oj"
    },
    {
      "id": "nis2ir",
      "title": "Implementing Regulation (EU) 2024/2690, Annex 6.5",
      "publisher": "EUR-Lex",
      "date": "Oct 2024",
      "url": "https://eur-lex.europa.eu/eli/reg_impl/2024/2690/oj"
    },
    {
      "id": "tiberde",
      "title": "Implementation of TIBER-DE, version 4.0",
      "publisher": "Bundesbank",
      "date": "Jul 2025",
      "url": "https://www.bundesbank.de/resource/blob/848920/d54c662179f26da23b9b0bc3daf9bafb/472B63F073F071307366337C94F8C870/tiber-implementierung-data.pdf"
    },
    {
      "id": "ncscai",
      "title": "10 questions to ask when using AI models to find vulnerabilities",
      "publisher": "NCSC (UK)",
      "date": "11 May 2026",
      "url": "https://www.ncsc.gov.uk/blogs/10-questions-ask-using-ai-models-find-vulnerabilities"
    },
    {
      "id": "crestai",
      "title": "First companies accredited to test the security of AI systems",
      "publisher": "CREST",
      "date": "2 Nov 2026",
      "url": "https://www.crest-approved.org/crest-announces-first-four-companies-accredited-to-test-the-security-of-ai-systems/"
    }
  ]
}