Preparation

Penetration Testing (Pentest): Process, Types, Methods and Choosing a Provider

Ransomware Reverse Editorial TeamLast technical review: 28 min read

A penetration test (pentest) is an authorised, simulated cyberattack on networks, servers or web applications. Security specialists use tools and manual analysis to check whether vulnerabilities can actually be exploited, and deliver a report with prioritised recommendations. It rests on a clearly agreed scope, written authorisation and recognised methodologies such as the BSI implementation concept, OWASP or PTES.

Key takeaways

  • Define objectives, scope, test depth, emergency contacts and abort criteria in advance, and commission the test in writing with liability and confidentiality terms.
  • Combine regular vulnerability scans for breadth with a penetration test for depth, because only exploitation proves a vulnerability with certainty.
  • Do not prioritise findings by the CVSS base score alone, but also by the threat situation and the protection requirements of the affected systems.
  • Choose independent testers with proven qualifications who were not involved in designing, building or operating the infrastructure under test.
  • With ransomware in mind, specifically test remote access, the path from a compromised user account to domain admin and whether backups can be reached.

Short answer: what is a penetration test?

A penetration test – pentest for short – is an authorised, controlled attack on your own infrastructure. Security specialists take the attacker's perspective and check whether vulnerabilities in networks, servers and applications can actually be exploited, and how far an intruder would get. Germany's Federal Office for Information Security (BSI) describes the penetration test as a proven way to determine the attack potential against a network, a single system or a (web) application: it estimates the chances of success of a deliberate attack and checks how effective the security measures in place really are.[1]

The US National Institute of Standards and Technology (NIST) defines penetration testing in similar terms: assessors mimic real-world attacks to identify ways of circumventing the security features of an application, system or network – often using the same tools and techniques that attackers use.[3] Most penetration tests look for combinations of vulnerabilities that together provide more access than any single flaw.[3] This is why the discipline is also called ethical hacking: the methods resemble those of criminals, but the purpose and the permission are entirely different.

For information security, a pentest is therefore a proactive tool: it should uncover security gaps before cybercriminals exploit them and cause damage. It complements controls such as firewalls, monitoring and awareness training, and adds something audits and policies cannot provide – the attacker's view.

The outcome is not a seal of approval but a report: which vulnerabilities were found, how severe they are, how they can be reproduced and how to fix them.

Definition: pentest vs. vulnerability scan, audit and red teaming

The terms are often used interchangeably. When commissioning work, however, the difference matters, because effort, output and objectives vary considerably.

MethodKey questionApproachOutput
Vulnerability scanWhich known vulnerabilities exist?automated, mostly based on versions and configurationslist of potential findings, often with false positives
Vulnerability assessmentHow relevant are the findings?scan plus manual triageprioritised list of vulnerabilities
Penetration testCan the vulnerabilities be exploited?manual attacks within the agreed scope, supported by toolsproof of exploitability, attack paths, recommendations
Audit / IS auditHave the agreed controls been implemented?review of documentation, processes and samplesdeviations from requirements
Red teamingCan an attacker reach a specific objective unnoticed?covert attack simulation over a longer periodassessment of prevention, detection and response

Pentest vs. vulnerability scan

According to the BSI guide, a non-invasive vulnerability scan is a separate, lower test depth: scanners flag suspicious points, but they are not exploited. Because most vulnerability scanners infer weaknesses from version numbers, false positives are common – for example when an old version is deliberately used but has been patched.[1] Only in a penetration test are exploits used: software written specifically to take advantage of known vulnerabilities. This proves that a target system is genuinely vulnerable.[1]

There are also breach and attack simulation (BAS) platforms that replay known attack techniques automatically and continuously, as well as managed services in which a provider runs vulnerability scans on an ongoing basis. Such solutions provide regular insight into your security status but do not replace the creative analysis of a penetration test.

Automated scanners still have their place: they are worthwhile when a large number of servers and clients need to be checked in a short time.[1] A proven combination is regular scans for breadth and a penetration test for depth. A vulnerability analysis without exploitation only tells you what might be vulnerable; pentesting shows what an attacker can actually do with it.

Pentest vs. audit

An IS audit based on the BSI's IT-Grundschutz (the German baseline protection methodology) checks whether defined security measures have been implemented as agreed. The penetration test goes a step further and deliberately looks for ways to bypass those measures.[1] Whether backups could be restored after hardware failure is not what a pentest examines; it only checks whether an attacker could access that data.[2] Audits and pentests complement each other – one does not replace the other.

Pentest vs. red teaming

In a red team exercise, an attacking team takes on the defenders, the so-called blue team. It simulates a real adversary with a specific objective – such as access to a particular database – and combines attacks on networks and applications with social engineering and physical access. Unlike classic pentesting, the focus is less on a complete list of vulnerabilities and more on whether detection, escalation and incident response work. For such scenarios, the BSI study describes a covert approach: if secondary security systems such as an IDS or escalation procedures are to be tested, at least the initial phase uses methods that are not directly recognisable as an attack.[2] The aim is to uncover weaknesses in alerting and response. Such an exercise makes sense once basic gaps have been closed through security testing and security teams want to practise their response under realistic conditions.

For AI applications such as chatbots or assistants based on large language models, the term AI red teaming has become established. It refers to the targeted search for ways to misuse such systems and complements testing of the underlying web application and its interfaces.

Objectives of a penetration test

The BSI study "Implementation Concept for Penetration Tests" groups a client's objectives into four categories:[2]

  1. Improving the security of technical systems – for example firewalls, routers or web servers.
  2. Identifying vulnerabilities – for example before two networks are connected after a merger.
  3. Confirmation of IT security by an independent third party – as evidence for business partners, regulators or compliance purposes.
  4. Improving the security of organisational and personnel infrastructure – for example by testing escalation processes or social engineering scenarios.

According to NIST, a penetration test also shows how well a system tolerates real-world attack patterns, what level of sophistication an attacker would need to compromise it, which additional countermeasures could mitigate threats, and whether defenders can detect attacks and respond appropriately.[3]

A clear objective before the start is essential. If goals cannot be achieved efficiently, the testers should say so and suggest alternatives such as an audit or security consulting.[2] The result should not just list vulnerabilities but also propose concrete solutions for fixing them.[2] For management, a pentest thus provides reliable insight into the actual security posture – a sound basis for allocating budget and resources and for sharpening the security strategy.

Benefits at a glance:

  • a realistic view of attack vectors and security risks instead of theoretical lists
  • demonstrated exploitability and therefore robust prioritisation
  • verification that security measures, policies and processes work in practice
  • independent confirmation for auditors, partners and regulators
  • greater resilience against cyberattacks before an emergency occurs

When does a pentest make sense?

Typical triggers are the commissioning of a new system, significant changes to infrastructure or applications, and the period after a security incident. In such cases the test object can usually be narrowed down easily.[1] For purely preventive testing, a sensible strategy is to identify the interfaces where an attack is most likely first and to cover further areas in follow-up projects.[1] For repeat tests, the BSI guide recommends an interval of two to three years because new vulnerabilities and attack methods keep emerging.[1] The higher the protection requirements, the more often testing should take place.[2] A changed threat landscape – such as new campaigns targeting products you use – or requirements such as NIS 2 and DORA can also be a reason. Test depth can be adapted to the client's wishes and protection requirements.[1]

The purpose is not a certificate for the wall but the identification of real security risks. The assets that need the most protection – data, processes, technologies – determine the focus. Results support risk management within the ISMS, help improve security processes and raise security maturity over time. It is also important to understand the limits: a penetration test cannot find every flaw. Results apply only to the time of testing, and because resources are limited there is no guarantee that all existing vulnerabilities will be found.[1]

Types of penetration tests

Pentests differ by target, starting point and technique. The BSI study classifies them according to six criteria: information basis, aggressiveness, scope, approach, technique and starting point.[2] The following types have become established; they cover different attack scenarios, and the right test methods depend on the objective. Specialised providers such as pentest24.de (external link) offer external and internal penetration tests as well as tests for web applications, mobile apps and IoT.

External and internal pentest

In an external pentest, the specialists attack via the internet – targeting firewalls, VPN gateways, mail servers, web servers and other publicly reachable components. The focus is on external interfaces through which potential attackers could gain entry; typical findings are configuration errors and unpatched vulnerabilities.[1] The guiding question: can someone gain unauthorised access to internal resources from outside?

An internal pentest starts inside the corporate network, for example from a prepared endpoint or with a standard user account. It answers the question: what happens if an attacker already has a foot in the door, for instance after a phishing email or with stolen credentials? This perspective is crucial for defending against modern cyberattacks, because attackers usually move laterally through the network after initial access.

Web applications, APIs and apps

Web applications, online shops, customer portals and APIs are often directly reachable from the internet and process sensitive data. Web application penetration testing covers functions such as login and password reset as well as authentication, session management, access rights and input validation. Typical findings are broken access controls, injection flaws such as SQL injection, cross-site scripting (XSS) or misconfigurations. The OWASP Top 10:2025 lists "Broken Access Control" in first place, "Security Misconfiguration" in second and "Injection" in fifth.[5] Similar principles apply to mobile apps, supplemented by device-specific aspects. A code review – the systematic examination of source code for vulnerabilities and errors – is part of quality assurance, should therefore be an integral part of software development and can complement the security analysis.[1] For APIs, testers also check whether each API function correctly enforces authentication and user permissions – a typical entry point for data leaks.

Cloud pentest

In cloud environments such as AWS or Azure, the focus is on identities, roles, permissions, publicly accessible storage and misconfigurations. The rules of the respective cloud provider must be observed before testing begins. The shared responsibility model applies: the provider is responsible for the security of the platform, the customer for configurations, identities and data. If services are outsourced to a hosting provider, the provider must be included in the engagement;[1] cloud platforms and other third parties also have their own rules for security testing.

Active Directory

Active Directory is at the heart of many Windows networks; organisations use it to manage users, groups and permissions. An AD pentest looks for ways to get from a normal account to domain admin rights. Typical attack vectors: weak passwords, incorrectly delegated rights, outdated protocols and unprotected service accounts. Why this matters so much for defence is explained in our article on Active Directory as an attack target.

IoT and OT

For IoT devices and OT systems such as production and building controls, availability is the top priority. Many controllers run on outdated operating systems and cannot easily be patched. The BSI guide explicitly lists infrastructure facilities such as access control and building management as possible test objects.[1] Testing is particularly cautious here, often passive at first or in a replicated test environment. Results from such a simulation can, however, only be transferred to the original system to a limited extent.[1]

Social engineering and phishing simulation

Many real attacks start with people. A social engineering assessment checks, for example, whether employees respond to a phishing email or disclose passwords over the phone. Such simulations should only take place under precisely defined conditions, with the involvement of employee representatives and by specialists trained for the task, because otherwise staff may feel exposed.[1] The goal is not to single out individuals but to uncover organisational weaknesses and make awareness programmes and training more effective.

Physical pentest

This type of test checks whether an unauthorised person can get into buildings, server rooms or unlocked workstations. Security staff should know in advance how to verify that testers are legitimate, for example via a point of contact or an authorisation letter.[3]

Approaches: white box, grey box and black box

The choice of approach shapes the entire engagement: how much prior knowledge do the testers receive? The information basis is one of the central planning criteria.[2]

ApproachPrior knowledgeSimulatesStrengthsLimitations
White boxextensive: network diagrams, IP addresses, configurations, possibly source codeinformed insider or service providergreatest test depth, efficientless realism for initial access
Grey boxpartial: e.g. a user account, architecture overviewattacker with initial accessgood balance of depth and realismboundaries must be clearly agreed
Black boxtarget addresses onlyexternal hacker without insider knowledgerealistic outside viewmore time required, gaps more likely to be missed

In a black box approach, testers only receive the address information of the target, simulating a typical outside attacker; in a white box approach, they have extensive knowledge of the target systems.[1] The BSI generally recommends white box testing: otherwise vulnerabilities may be overlooked, scenarios such as an informed insider are not considered, the risk of unintended damage increases and the effort is considerably higher.[1] In practice, a grey box approach is often the pragmatic middle ground: the test team starts with a normal account, for example, and can thus simulate a compromised user.

Standards, methodologies and frameworks

Reputable teams follow a transparent, structured methodology. The following standards are widely used in Germany and internationally:

  • BSI implementation concept for penetration tests: The study by Germany's Federal Office for Information Security divides a penetration test into five phases and provides a classification scheme with six criteria.[2] The BSI's practical guide for IS penetration tests additionally describes framework conditions, test depth and report structure.[1] A special case is the IS web check, which assesses the security of a website largely through automated methods over the internet.[1]
  • OWASP Web Security Testing Guide (WSTG): The OWASP project's guide is a comprehensive basis for testing web applications. Version 4.2 is currently published; version 5.0 is in development.[4] The OWASP Top 10 names the most important risk categories for web applications and was released in a new edition in 2025.[5]
  • PTES (Penetration Testing Execution Standard): The standard defines seven main sections: pre-engagement interactions, intelligence gathering, threat modeling, vulnerability analysis, exploitation, post exploitation and reporting.[6] Separate technical guidelines support practical implementation.[6]
  • OSSTMM (Open Source Security Testing Methodology Manual): The ISECOM manual looks at security testing beyond data networks, including human and physical aspects.
  • NIST SP 800-115: The "Technical Guide to Information Security Testing and Assessment" is intended to help organisations plan and conduct technical security tests, analyse findings and develop mitigation strategies.[3] Its appendix contains a rules of engagement template.[3]
  • IT-Grundschutz and ISO/IEC 27001: Both standards describe how to build an ISMS, i.e. structured management of information security. Pentests provide insight into how well systems are actually protected; within IT-Grundschutz, the IS audit checks whether measures have been implemented.[1]
  • CVSS (Common Vulnerability Scoring System): The FIRST scoring system, currently at version 4.0, rates vulnerabilities on a scale from 0.0 to 10.0.[7]

No standard replaces experience and creativity. Attackers do not work from checklists either; they target the environment they find – which is why a good penetration test adapts flexibly to each situation.[1]

Process: the phases of a pentest

The BSI implementation concept describes five consecutive phases: preparation, information gathering and evaluation, assessment of information and risk analysis, active intrusion attempts, and final analysis.[2] NIST uses a similar structure: planning, discovery, attack and reporting.[3] Remediation and retesting follow.

How a penetration test works – steps and phase models1. Preparation and scope: Define objectives, target systems, test type, time frame and emergency contacts; written authorisation (BSI 1 Preparation, NIST Planning). 2. Information gathering (OSINT): Evaluate public sources: domains, IP ranges, email addresses (BSI 2 Information gathering, NIST Discovery). 3. Scanning and risk analysis: Identify ports and services, map vulnerabilities, select targets (BSI 2–3 Evaluation, risk analysis, NIST Discovery). 4. Exploitation: Active intrusion attempts show whether vulnerabilities can be exploited (BSI 4 Active intrusion attempts, NIST Attack). 5. Post-exploitation: Privilege escalation, access to further systems, data and backups (BSI 4 Active intrusion attempts, NIST Attack). 6. Reporting and debrief: Traceable report with risk assessment and recommendations (BSI 5 Final analysis, NIST Reporting). 7. Remediation and retest: Prioritise findings, implement measures, verify their effect (after the test). StepWhat happensBSI phaseNIST SP 800-115Preparation and scopeDefine objectives, target systems, test type,time frame and emergency contacts; writtenauthorisation1 PreparationPlanningInformation gathering(OSINT)Evaluate public sources: domains, IP ranges,email addresses2 InformationgatheringDiscoveryScanning and riskanalysisIdentify ports and services, mapvulnerabilities, select targets2–3 Evaluation, riskanalysisDiscoveryExploitationActive intrusion attempts show whethervulnerabilities can be exploited (highest risk)4 Active intrusionattemptsAttackPost-exploitationPrivilege escalation, access to furthersystems, data and backups4 Active intrusionattemptsAttackReporting and debriefTraceable report with risk assessment andrecommendations5 Final analysisReportingRemediation andretestPrioritise findings, implement measures,verify their effectafter the testafter thetest1234567 © 2026 ransomware-reverse.de
How a penetration test works – steps and phase models1. Preparation and scope: Define objectives, target systems, test type, time frame and emergency contacts; written authorisation (BSI 1 Preparation, NIST Planning). 2. Information gathering (OSINT): Evaluate public sources: domains, IP ranges, email addresses (BSI 2 Information gathering, NIST Discovery). 3. Scanning and risk analysis: Identify ports and services, map vulnerabilities, select targets (BSI 2–3 Evaluation, risk analysis, NIST Discovery). 4. Exploitation: Active intrusion attempts show whether vulnerabilities can be exploited (BSI 4 Active intrusion attempts, NIST Attack). 5. Post-exploitation: Privilege escalation, access to further systems, data and backups (BSI 4 Active intrusion attempts, NIST Attack). 6. Reporting and debrief: Traceable report with risk assessment and recommendations (BSI 5 Final analysis, NIST Reporting). 7. Remediation and retest: Prioritise findings, implement measures, verify their effect (after the test). Preparation and scopeDefine objectives, target systems, test type,time frame and emergency contacts; writtenauthorisationBSI 1 Preparation · NIST PlanningInformation gathering (OSINT)Evaluate public sources: domains, IP ranges, emailaddressesBSI 2 Information gathering · NIST DiscoveryScanning and risk analysisIdentify ports and services, map vulnerabilities,select targetsBSI 2–3 Evaluation, risk analysis · NIST DiscoveryExploitationActive intrusion attempts show whethervulnerabilities can be exploited (highest risk)BSI 4 Active intrusion attempts · NIST AttackPost-exploitationPrivilege escalation, access to further systems,data and backupsBSI 4 Active intrusion attempts · NIST AttackReporting and debriefTraceable report with risk assessment andrecommendationsBSI 5 Final analysis · NIST ReportingRemediation and retestPrioritise findings, implement measures, verifytheir effectafter the test1234567 © 2026 ransomware-reverse.de
How a penetration test works – steps and phase models. The BSI implementation concept (five phases) and NIST SP 800-115 (four phases) describe the same process. Remediation and retest follow the actual test.

1. Preparation, scope and authorisation

Without thorough preparation, it is hard to meet the client's expectations.[2] This phase defines test objectives, target systems, attack scenarios, test type, time frame, contacts and emergency procedures. No testing takes place during planning: rules are identified, management approval is documented and goals are set.[3] Both sides should also agree how communication works in an emergency and who may stop a test.

Written authorisation is central. Testers should never test without a written mandate; the contract should define the test period, test object and test depth and cover liability and confidentiality.[1] A penetration test that ignores legal requirements can have criminal or civil consequences, and the failure of a production system caused by techniques that were not agreed can trigger claims for damages.[2] If personal data is affected, the data protection officer and, where applicable, employee representatives should be involved in advance – the GDPR applies to testing too.[1] Advance information such as network diagrams, system lists and descriptions of hardening measures helps testers identify relevant interfaces quickly.[1]

2. Information gathering and OSINT

Next, the team gathers information about the target. The BSI study also calls this step a passive penetration test; the goal is as complete an overview as possible of installed systems, potential points of attack and known security weaknesses.[2] This includes open source intelligence (OSINT) from publicly available sources: domains, subdomains, IP ranges, email addresses and employee names. NIST notes that such contact details can be found, for example, on the organisation's web servers or directory servers.[3]

3. Scanning and risk analysis

Scanning identifies open ports and services and thus potential attack vectors; version information can be recorded through banner grabbing, for example.[3] Tools such as Nmap identify reachable ports and protocols; vulnerability scanners such as OpenVAS map discovered versions to known CVEs. This is followed by vulnerability and risk analysis: the agreed objectives, potential exposure and estimated effort all feed into the evaluation. The targets for the next phase are selected on this basis; any restrictions must be documented and clearly communicated.[2]

4. Exploitation: active intrusion attempts

In this phase, the selected target systems are actively attacked. According to the BSI study, it carries the greatest risk and shows whether suspected vulnerabilities represent real risks.[2] A vulnerability is only proven once it has been exploited.[1] NIST warns that systems may be damaged or rendered inoperable during penetration testing; experienced testers can reduce this risk but never eliminate it entirely, and the work is labour-intensive and requires great expertise.[3] The BSI therefore recommends a moderate attack intensity and only exploits whose behaviour has been examined beforehand.[1] Frameworks such as Metasploit provide maintained exploit modules, but every module has to fit the environment.

5. Post-exploitation

Once initial access succeeds, testers try to go further: privilege escalation, lateral movement to other servers, access to confidential data or backups. The aim is to show access to sensitive databases without altering them. PTES treats post exploitation as a separate section.[6] This is where it becomes clear whether segmentation, hardening and access controls hold up in an emergency.

6. Reporting and debrief

The final report must make the test steps and the vulnerabilities found traceable and include an assessment of the risks and detailed recommendations.[2] Severe vulnerabilities should already be evaluated sufficiently on site for the closing meeting so that those responsible can fix them immediately; this direct communication does not replace the report, which contains the binding account of all findings.[1] Findings and risks are discussed in detail with the client in a closing meeting once testing has ended.[2]

7. Remediation and retest

After reporting, the real work begins: prioritise findings, implement security measures, verify their effect. The BSI guide advises having the remediation of identified gaps checked by internal quality assurance or in-house IT staff so that the independence of the external testers is preserved.[1] Many organisations nevertheless have the provider confirm the fix of critical findings in a short retest – a trade-off that should be made consciously. Insights feed into continuous improvement.

Pentest tools

Automation speeds up the work but does not replace manual analysis. Tools must be selected carefully and understood thoroughly, because incorrect use can impair systems.[1] Commonly used tools include (in no particular order):

ToolPurpose
Nmapnetwork and port scanning, service and version detection
OpenVAS, Nessusautomated vulnerability scanners
Metasploitframework with an extensive library of exploit modules
Burp Suiteproxy and platform for testing web applications
ZAPopen-source proxy for web applications (Zed Attack Proxy, formerly OWASP ZAP)
Wiresharkcapturing and analysing network traffic
John the Rippertesting the strength of password hashes

There are also tools for fuzzing, which can uncover unknown flaws, for analysing permissions in Active Directory or for cloud configurations, usually running on specialised Linux distributions. Wireshark can show, for example, whether credentials are transmitted without encryption; ZAP is also suitable for automated scans during development. Both open-source and commercial products exist; according to the BSI, the advantage of commercial tools is that they are often better documented.[1] What matters most is the knowledge and skill of the testers, not the number of tools. AI-assisted software can help evaluate large amounts of data, but deciding whether a finding is exploitable and critical in context remains a job for experienced people.

The report and prioritisation with CVSS

The report is the most important deliverable. The BSI recommends this structure: a description of the test object and test conditions, followed by a management summary with the key messages, then the vulnerabilities with precise descriptions and recommendations for technical staff.[1] Because of its sensitive, confidential content, the report should only be made available to a selected group of people.[1]

A good pentest report contains:

  • scope, time frame, approach and methodology
  • a management summary in plain language
  • for each identified vulnerability: description, affected components, evidence, impact, severity and recommendation
  • areas not tested, with reasons
  • notes on identical systems, so that the same finding is not repeated a hundred times[1]

Rating severity

For rating, the BSI guide refers to established industry standards such as CVSS (still version 2 in the guide) or DREAD; the rating helps administrators and security teams decide on the order of remediation.[1] For its own IS penetration tests, the BSI distinguishes four levels of damage potential with a corresponding response: high (immediately), medium (short term), low (medium term) and "for information" (long term).[1]

CVSS v4.0 maps scores to qualitative ratings: None (0.0), Low (0.1–3.9), Medium (4.0–6.9), High (7.0–8.9) and Critical (9.0–10.0).[7] The base score alone does not describe the risk to your organisation, however. FIRST provides for supplementing base metrics with threat and environmental metrics to produce a more comprehensive input for organisation-specific risk assessment.[7] This is consistent with the BSI's practice of rating the same vulnerability differently depending on the protection requirements of the data processed.[1] A medium vulnerability on a domain controller may therefore be more urgent than a high one on an isolated test server.

Compliance and regulation

Whether you are a critical infrastructure operator, a financial institution or a supplier: in many sectors, penetration testing is not an end in itself but part of regulatory requirements and compliance. It is important to assume only what the regulations actually require.

  • DORA (financial sector): The EU Digital Operational Resilience Act requires financial entities other than microenterprises to maintain a digital operational resilience testing programme as an integral part of their ICT risk management framework.[8] This includes appropriate tests such as vulnerability assessments and scans, source code reviews where feasible, and penetration tests.[8] Financial entities identified by the authorities must carry out advanced testing by means of TLPT (threat-led penetration testing) on live production systems at least every three years.[8] DORA also sets requirements for TLPT testers, such as demonstrated expertise in threat intelligence, penetration testing and red team testing, and professional indemnity insurance.[8]
  • NIS 2: The NIS 2 Directive requires essential and important entities to take cybersecurity risk-management measures, including vulnerability handling and disclosure as well as policies and procedures to assess the effectiveness of those measures.[9] Authorities may subject essential entities to regular and targeted security audits and to security scans; the audits are carried out by an independent body or the authority itself.[9] A pentest is not explicitly required, but it is an obvious way to demonstrate the effectiveness of cybersecurity measures. The detailed obligations depend on national transposition; critical infrastructure operators may face additional requirements.
  • GDPR: The General Data Protection Regulation requires appropriate technical and organisational measures to protect personal data. A pentest can help demonstrate the effectiveness of these measures and thus support GDPR compliance.
  • Cyber Resilience Act: For manufacturers of products with digital elements, the EU Cyber Resilience Act introduces its own security requirements, which make security testing during software development an obvious step.
  • ISO/IEC 27001, PCI DSS and TISAX: In an ISMS under ISO/IEC 27001, under the card payment standard PCI DSS or in TISAX assessments in the automotive industry, security tests often serve as evidence. Which type of test is required and how often follows from the current version of the respective framework and should be agreed with the auditor or assessor.

Which obligations apply depends on your sector, size and role. For a definitive assessment, consult your legal department, data protection officer or a specialist lawyer; a pentest is no substitute for legal advice.

How much does a pentest cost? Cost drivers

There are no meaningful flat prices because no two projects are alike. According to the BSI study, effort usually depends directly on the scope of the systems to be examined.[2] The main factors:

  • Scope and size: number of IP addresses, sites, web applications, APIs or cloud accounts
  • Complexity: custom software, many user roles, a grown architecture
  • Test depth and approach: white box or black box, scanning only or real exploitation, additional social engineering or physical testing
  • Test type: a single web check, an internal infrastructure pentest, a covert attack simulation or TLPT
  • Conditions: on-site work, testing outside business hours, special security clearances for the test team
  • Reporting: presentations to management, translations, retests

The BSI guide recommends specifying in the contract which costs will be incurred and what is expected besides the test itself, such as a presentation to management or a particularly detailed report.[1] Every extensive penetration test also means considerable effort – for the testers and for your own staff who look after the systems concerned.[1] A small, clearly defined scope with high test depth can deliver more than a broad, superficial test.

Many providers only quote on request once scope details are clear. It helps to include target systems, the preferred approach and the time frame in your request. When comparing offers, check which services are included: retest, presentation, support with remediation? Additional services at the customer's request should be listed separately.

Choosing a provider: what to look for

A pentester gains access to sensitive information about your infrastructure and its weaknesses. Choosing a provider is therefore a matter of trust.[1] Trust comes from transparency: a professional partner explains methodology, limits and risks openly. Quality shows above all in the final report and in the collaboration during the project.

Certified test labs: Ideally, the provider is certified as a testing body and demonstrably complies with data protection, secure data handling and information security.[1] Professional firms also have quality management for their deliverables, such as a review by a second expert.

Independence: The BSI generally recommends external testers who were not involved in the design, set-up or operation of the systems under test.[1] This avoids operational blindness and conflicts of interest.

Qualifications and certifications: The BSI cites certificates for testing bodies or individuals as evidence, such as its own personnel certification or CREST, both of which include practical exams, and the Certified Ethical Hacker, which is based on a theoretical exam.[1] Practical certifications such as OSCP are also widespread. Without a certificate, the BSI suggests that the lead tester should have at least five years of full-time IT experience within the last eight years, at least two of them in information security, and should have taken part in at least six penetration tests in the last three years.[1] Specialisation matters too: someone who is good at testing web applications is not necessarily the right person for firewalls or OT.[1] Look for proven expertise in the relevant technology – cloud, AD, IoT or application security. Certifications alone do not guarantee quality. For smaller organisations, it also matters that the results can be implemented without an in-house security team.

References: References provide useful pointers. Because many clients do not agree to be named, a provider can instead confirm the sectors and company sizes it has worked for.[1]

Test team: The BSI recommends at least two people so that the four-eyes principle is maintained.[1]

Contract, NDA and data handling: Agree in writing on target systems, time frame, test depth, liability, confidentiality, data retention and deletion, and the client's obligations to cooperate.[1]

Initial consultation and quote: A non-binding initial consultation clarifies objectives and scope. A good quote describes the test methods, scope, people involved and report format specifically. Make sure that the people named in the quote actually carry out the work.[1]

Pentesting as ransomware prevention

Ransomware groups rarely use exotic techniques. Typical entry points are poorly secured remote access such as VPN and Remote Desktop Protocol (RDP), unpatched systems with publicly known vulnerabilities (CVEs), stolen credentials and weak Active Directory configurations. In such cyberattacks, criminals often copy data out of the corporate network before encryption and then threaten to leak it.

How a ransomware attack unfolds – and where you can stop it1. Initial access: Phishing, stolen credentials, unpatched VPN or firewall appliances, remote access without MFA. Countermeasure: MFA on all remote access, timely patching, monitoring of unusual sign-ins. 2. Persistence: Remote management tools, new accounts, scheduled tasks or web shells keep access open. Countermeasure: Alerts on new admin accounts and unknown remote management software. 3. Privilege escalation: Harvesting passwords and tickets up to taking over domain admin rights. Countermeasure: Act on EDR alerts, separate and protect privileged accounts. 4. Lateral movement: Moving via RDP, SMB and admin tools to servers, hypervisors and backup systems. Countermeasure: Network segmentation, monitoring of internal traffic. 5. Data theft: Copying sensitive data to cloud storage or attacker servers. Countermeasure: Monitoring outbound data volumes, alerts on large uploads. 6. Sabotaging recovery: Deleting shadow copies and snapshots, attacking backups, disabling security tools. Countermeasure: Immutable or offline backups, alerts on deletion and tamper commands. 7. Encryption and extortion: Encrypting servers, clients and VMs, ransom note, threat to publish data. Countermeasure: Isolate, engage incident response, assess recoverability. PhaseWhat attackers typically doYour chance to detect and respondInitial accessPhishing, stolen credentials, unpatchedVPN or firewall appliances, remote accesswithout MFAMFA on all remote access, timely patching,monitoring of unusual sign-insPersistenceRemote management tools, new accounts,scheduled tasks or web shells keep accessopenAlerts on new admin accounts and unknownremote management softwarePrivilege escalationHarvesting passwords and tickets up totaking over domain admin rightsAct on EDR alerts, separate and protectprivileged accountsLateral movementMoving via RDP, SMB and admin tools toservers, hypervisors and backup systemsNetwork segmentation, monitoring ofinternal trafficData theftCopying sensitive data to cloud storage orattacker serversMonitoring outbound data volumes, alertson large uploadsSabotaging recoveryDeleting shadow copies and snapshots,attacking backups, disabling security toolsImmutable or offline backups, alerts ondeletion and tamper commandsEncryption andextortionEncrypting servers, clients and VMs,ransom note, threat to publish dataIsolate, engage incident response, assessrecoverability1234567Preparation – often unnoticed (1–6)Visible at the latest here (7) © 2026 ransomware-reverse.de
How a ransomware attack unfolds – and where you can stop it1. Initial access: Phishing, stolen credentials, unpatched VPN or firewall appliances, remote access without MFA. Countermeasure: MFA on all remote access, timely patching, monitoring of unusual sign-ins. 2. Persistence: Remote management tools, new accounts, scheduled tasks or web shells keep access open. Countermeasure: Alerts on new admin accounts and unknown remote management software. 3. Privilege escalation: Harvesting passwords and tickets up to taking over domain admin rights. Countermeasure: Act on EDR alerts, separate and protect privileged accounts. 4. Lateral movement: Moving via RDP, SMB and admin tools to servers, hypervisors and backup systems. Countermeasure: Network segmentation, monitoring of internal traffic. 5. Data theft: Copying sensitive data to cloud storage or attacker servers. Countermeasure: Monitoring outbound data volumes, alerts on large uploads. 6. Sabotaging recovery: Deleting shadow copies and snapshots, attacking backups, disabling security tools. Countermeasure: Immutable or offline backups, alerts on deletion and tamper commands. 7. Encryption and extortion: Encrypting servers, clients and VMs, ransom note, threat to publish data. Countermeasure: Isolate, engage incident response, assess recoverability. Initial accessPhishing, stolen credentials, unpatched VPN orfirewall appliances, remote access without MFAMFA on all remote access, timely patching,monitoring of unusual sign-insPersistenceRemote management tools, new accounts,scheduled tasks or web shells keep access openAlerts on new admin accounts and unknownremote management softwarePrivilege escalationHarvesting passwords and tickets up to takingover domain admin rightsAct on EDR alerts, separate and protectprivileged accountsLateral movementMoving via RDP, SMB and admin tools to servers,hypervisors and backup systemsNetwork segmentation, monitoring of internaltrafficData theftCopying sensitive data to cloud storage orattacker serversMonitoring outbound data volumes, alerts onlarge uploadsSabotaging recoveryDeleting shadow copies and snapshots, attackingbackups, disabling security toolsImmutable or offline backups, alerts on deletionand tamper commandsEncryption and extortionEncrypting servers, clients and VMs, ransomnote, threat to publish dataIsolate, engage incident response, assessrecoverability1234567AttackerYour chance © 2026 ransomware-reverse.de
How a ransomware attack unfolds – and where you can stop it. Encryption is the last step. The phases before it are where detection really happens.

A pentest can check exactly these entry points before cybercriminals find them:

  • From the outside: Are VPN gateways, remote desktop access and web applications hardened and up to date?
  • From the inside (assumed breach scenario): How far can an attacker get with a single compromised user account? How short is the path to domain admin?
  • Backup access: Can backup servers and storage be reached with captured credentials?
  • Detection: Does monitoring pick up the test team's activities? Our guide to detecting an attack early explains what warning signs look like.

A penetration test answers the question "Where can an attacker get in, and how far?". Whether the organisation as a whole is prepared – with an incident response plan, backups and recovery – is what a readiness assessment clarifies. Both belong in a security strategy for greater cyber resilience. No security test can rule out an incident, but it reduces the attack surface and buys time for incident response.

Vulnerabilities often come to light after data loss or a ransomware incident. Our data recovery partner DATA REVERSE therefore also offers an IT security analysis with penetration testing (external link) (in German).

Checklist: preparing for and following up a pentest

  • Test objectives defined: which questions should the security analysis answer?
  • Scope defined: servers, applications, IP ranges, sites – and what is explicitly excluded
  • Approach chosen: white box, grey box or black box; external, internal or both
  • Written authorisation and contract covering liability, NDA and data deletion in place
  • Hosting providers, cloud providers and other third parties informed or involved
  • Data protection officer and, where applicable, employee representatives involved
  • Contacts, emergency contacts and abort criteria agreed
  • Documentation provided: network diagrams, system lists, configurations
  • No maintenance work or changes to target systems during the test period[1]
  • Report with management summary and prioritised findings received
  • Remediation plan created: owners and deadlines set
  • Retest carried out and next test cycle scheduled

Conclusion

A penetration test shows what attackers could actually achieve today – not in theory, but with evidence. Its strength lies in combining tools, methodology and human experience. To be effective, it needs clear objectives, a clean scope, written authorisation and a provider with demonstrable qualifications. What happens afterwards is decisive: prioritise findings, fix them, test again and repeat the exercise regularly. That turns a snapshot into a continuous process that raises the security level, strengthens the protection of critical applications and steadily shrinks the attack surface.

Frequently asked questions

What is a penetration test in simple terms?

Hired security specialists attack an organisation's IT in a controlled way and with written permission. They look for vulnerabilities, try to exploit them and document how far a real attacker could get. The result is a report with rated findings and recommendations for remediation.

What is the difference between a pentest and a vulnerability scan?

A vulnerability scan is largely automated and reports known weaknesses, mostly based on software versions. A penetration test goes further: testers check manually whether findings can really be exploited and chained into an attack path. Scans suit regular checks; the pentest provides depth.

How often should a pentest be carried out?

There is no universal interval. Germany's Federal Office for Information Security (BSI) recommends repeat tests every two to three years; according to the BSI, typical triggers for additional tests are the initial commissioning of new systems, significant changes or an attack that has already taken place. The higher the protection requirements, the more often you should test; frameworks such as DORA set their own intervals.

Is penetration testing legal?

Yes, provided the client is entitled to commission it and there is a written engagement with a clearly defined scope. Without that authorisation, attacking third-party systems can have criminal and civil consequences. If hosting or cloud providers are involved, their terms also apply; when in doubt, seek legal advice.

How much does a pentest cost?

Cost depends mainly on factors such as scope, the number and complexity of target systems, test depth, the chosen approach and reporting requirements. Flat prices are therefore of little use. A serious quote is only possible on request after a scoping conversation that clarifies objectives and boundaries.

What is the difference between a pentest and red teaming?

A penetration test looks for as many vulnerabilities as possible within a defined scope and rates them. A covert attack simulation pursues a specific objective over a longer period, stays undetected for as long as possible and also tests whether defenders notice the attack and respond correctly.

Can a penetration test damage systems?

There is a residual risk, for instance if an exploit crashes a service. That is why test depth, time windows, emergency contacts and abort criteria are agreed in advance. The BSI recommends a moderate attack intensity and only exploits whose effects have been tested beforehand.

What happens after the penetration test?

The organisation receives a final report with a management summary, technical findings and recommendations. Findings are prioritised by severity and remediated. A retest then shows whether the fixes work.

Related ransomware profiles

Read next

Sources and further reading

  1. [1]BSI – A Practical Guide for IS Penetration Tests (Ein Praxis-Leitfaden für IS-Penetrationstests, version 1.2, German) bsi.bund.de
  2. [2]BSI – Study: Implementation Concept for Penetration Tests (Durchführungskonzept für Penetrationstests, German) bsi.bund.de
  3. [3]NIST – SP 800-115: Technical Guide to Information Security Testing and Assessment csrc.nist.gov
  4. [4]OWASP – Web Security Testing Guide (WSTG) owasp.org
  5. [5]OWASP – Top 10:2025 owasp.org
  6. [6]PTES – Penetration Testing Execution Standard pentest-standard.org
  7. [7]FIRST – CVSS v4.0 Specification Document first.org
  8. [8]Regulation (EU) 2022/2554 (DORA) – Articles 24 to 27 eur-lex.europa.eu
  9. [9]Directive (EU) 2022/2555 (NIS 2) – Articles 21 and 32 eur-lex.europa.eu