EN · DE Request an offer
Services

Penetration Testing

In-depth security tests of all system components from the perspective of an external or internal attacker.

Overview

Attacks on applications and infrastructure, external or internal

During a penetration test, our analysts take the perspective of an attacker. The goal is to find vulnerabilities in the systems in scope and to exploit them or use them for further attacks.

By exploiting multiple vulnerabilities, the analysts try to infiltrate as many components of the infrastructure in scope as possible. Before the test starts, we define together with you which components of the infrastructure are analysed and how far the analysts may penetrate these systems.

Focus areas

  • Web applications
  • APIs and web services
  • External infrastructure
  • Internal networks and Active Directory
  • Authentication and access control
  • Injection vulnerabilities
  • Privilege escalation and lateral movement
  • Exploitation and post-exploitation
Scope

What we test

Depending on your environment and the agreed scope, we examine in particular:

Web applications

15 areas

Authentication

Examination of login procedures, password policies, password reset functions, the protection against brute-force attacks and against the enumeration of valid user accounts, Single Sign-On (SSO, e.g. OAuth 2.0, OpenID Connect or SAML) and multi-factor authentication (MFA) for weaknesses that could allow unauthorised access.

Session Management

Evaluation of session handling, including session cookies and tokens (e.g. JWT), session expiration, logout and the protection against session fixation and session hijacking.

Access Control (Broken Access Control)

Review of whether users can only access the data and functions they are authorised to, both horizontally (e.g. data of other users or tenants via Insecure Direct Object References, IDOR) and vertically (e.g. administrative functions).

Injection Vulnerabilities

Investigation of whether an attacker can inject malicious code or commands, for example via SQL, NoSQL, OS command, LDAP or template injection (SSTI).

Cross-Site Scripting (XSS)

Analysis for reflected, stored and DOM-based XSS vulnerabilities that could allow an attacker to execute malicious JavaScript code in the browsers of other users.

Cross-Site Request Forgery (CSRF) and Clickjacking

Check for vulnerabilities that could allow an attacker to perform actions on behalf of an authenticated user.

Server-Side Vulnerabilities

Testing for vulnerabilities such as Server-Side Request Forgery (SSRF), XML External Entities (XXE), path traversal, file inclusion and insecure deserialisation.

File Uploads

Checking the upload functions for vulnerabilities that could allow an attacker to upload and execute malicious files or to access the files of other users.

Business Logic

Review of business processes and workflows for logic flaws, for example the manipulation of prices or quantities, the skipping of process steps or race conditions.

Security Misconfigurations

Review of the application and the web server for insecure settings, such as exposed HTTP methods, debug or administration interfaces, directory listings, backup files, missing security headers (e.g. Content Security Policy, HSTS) and insecure CORS configurations.

Information Disclosure

Review of whether error messages, comments, source code or responses disclose internal information such as stack traces, software versions or internal paths.

Protection of Sensitive Data

Review of whether sensitive data such as passwords, payment information or personal data is transmitted and stored securely, including the TLS configuration.

Third-Party Components

Identification of outdated libraries, frameworks and components with known vulnerabilities.

Client-Side Security

Analysis of the client-side code (e.g. JavaScript of single-page applications) for sensitive information, insecure data storage in the browser and weaknesses such as open redirects or insecure communication between windows (postMessage).

Denial-of-Service (DoS) Attacks

Evaluation of whether individual functions can be abused to exhaust resources. Tests that could impair the availability of the application are only carried out after explicit agreement with you confirmed in text form.

APIs and web services

13 areas

Authentication (Broken Authentication)

Review of the authentication mechanisms in use, such as API keys, OAuth 2.0 and OpenID Connect, of the handling of tokens (e.g. signature, validity and revocation of JWTs) and of the protection against brute-force attacks.

Authorisation at Object and Function Level (Broken Object Level Authorization, Broken Function Level Authorization)

Review of whether users can only access the objects, data and functions they are authorised to, for example by manipulating object IDs or by calling administrative endpoints.

Authorisation at Object Property Level (Broken Object Property Level Authorization)

Investigation of whether API endpoints return more information than necessary, including sensitive or internal data, or allow changes to properties that must not be modified (mass assignment).

Input Validation and Injection

Testing the processing of parameters and requests (e.g. JSON or XML) for vulnerabilities such as SQL, NoSQL or OS command injection and for insufficient schema validation.

Resource Consumption (Unrestricted Resource Consumption)

Verification of whether rate limits, size limits and pagination are sufficient to prevent abuse and the exhaustion of resources. Tests that could impair the availability of the API are only carried out after explicit agreement with you confirmed in text form.

Business Flows (Unrestricted Access to Sensitive Business Flows)

Assessment of whether legitimate functions and business flows can be misused for unauthorised or harmful purposes, for example through automation.

Server-Side Request Forgery (SSRF)

Testing whether the API fetches supplied URLs without sufficient checks and thereby allows requests to internal systems.

Security Misconfiguration

Identification of weaknesses in the configuration, for example in CORS, HTTP methods, TLS and security headers, and of error handling that discloses internal information.

API Inventory (Improper Inventory Management)

Identification of undocumented, outdated or no longer maintained API versions, endpoints and environments (e.g. test or staging systems).

Consumption of Third-Party APIs (Unsafe Consumption of APIs)

Testing whether data from connected third-party APIs is processed without sufficient validation.

GraphQL-Specific Weaknesses

For GraphQL APIs, review of introspection, limits on query depth and complexity, batching and authorisation at field level.

File Uploads

Testing whether the API allows the upload and execution of malicious files that could compromise the system.

Third-Party Components

Identification of outdated libraries and components with known vulnerabilities used by the API.

External infrastructure

10 areas

Information Gathering (OSINT)

Collection of publicly available information about your company, such as IP ranges, domain names and subdomains, DNS records, certificate transparency logs, technologies in use and indications of compromised credentials in public sources.

Port and Service Scanning

Identification of reachable systems and open TCP and UDP ports, and determination of the services and software versions running on them.

Remote Access and VPN

Review of VPN gateways and of remote desktop, Citrix and SSH access for vulnerabilities, insecure configurations and missing multi-factor authentication (MFA).

Known Vulnerabilities and Patch Level

Identification of outdated software and known vulnerabilities (CVEs), in particular in perimeter devices such as firewalls, VPN gateways and load balancers.

Administration Interfaces

Searching for administration and management interfaces that can be reached from the internet, for example of network devices, servers (e.g. IPMI) or applications, and testing them for default credentials and weak passwords. Password attacks take the account lockout policy into account.

Mail Servers and Email Security

Review of the mail servers for open relays and insecure configurations, and of the protection against spoofed sender addresses (SPF, DKIM and DMARC).

DNS

Review of the DNS configuration, for example for zone transfers, open resolvers and subdomains that can be taken over (subdomain takeover).

Encryption (TLS)

Review of the encryption of the services in use for outdated protocols, weak cipher suites and invalid certificates.

Web Servers and Web Applications

Basic review of the web servers and web applications that can be reached from the internet for misconfigurations, information disclosure and known vulnerabilities. An in-depth analysis of individual web applications is part of the web application security analysis module.

Exploitation and Post-Exploitation

Exploitation of identified vulnerabilities in order to demonstrate their actual risk. After successful access, Nullsecurity Labs examines, in agreement with you, whether further systems or the internal network can be reached from there.

Internal networks and Active Directory

10 areas

Network Discovery

Identification of active systems, open ports and services in the internal network and of the network structure.

Network Access Control

Review of whether unauthorised devices can connect to the network and whether mechanisms such as 802.1X can be bypassed.

Network Segmentation

Verification of whether the separation between network zones (e.g. client, server, production and management networks) is effective and whether firewall rules only allow the required connections.

Network-Based Attacks

Testing for weaknesses in network protocols, for example manipulation of name resolution (LLMNR, NBT-NS, mDNS), IPv6 attacks, ARP spoofing, VLAN hopping and relay attacks against NTLM authentication. Attacks that can disrupt network operations (e.g. ARP spoofing) are only carried out after explicit agreement with you confirmed in text form.

Active Directory

Analysis of the Active Directory for misconfigurations and attack paths, for example insecure permissions (ACLs), Kerberos-based attacks (Kerberoasting, AS-REP roasting), insecure delegations, vulnerable certificate templates in Active Directory Certificate Services (AD CS) and trust relationships.

Passwords and Credentials

Review of password policies, default and weak passwords, reused local administrator passwords and credentials stored in plain text in file shares, scripts or configuration files. Password attacks take the account lockout policy into account.

Known Vulnerabilities and Patch Level

Identification of outdated operating systems and software and of known vulnerabilities (CVEs) in servers, clients and network devices.

Insecure Services and Protocols

Review of services such as SMB (e.g. missing signing), RDP, SSH, SNMP and databases, and of unencrypted protocols through which credentials or data are transmitted in plain text.

Infrastructure Components

Review of virtualisation platforms (e.g. VMware vCenter and ESXi), backup systems, monitoring systems, printers and management interfaces (e.g. IPMI, iLO, iDRAC) for vulnerabilities and insecure configurations.

Privilege Escalation and Lateral Movement

Exploitation of identified vulnerabilities in order to escalate privileges on individual systems and to spread to further systems, up to the takeover of privileged accounts or of the domain.

Approach

How it works

  1. 1
    Scoping

    Objectives, rules of engagement and time frame, agreed in writing.

  2. 2
    Testing

    Hands-on testing by experienced analysts, supported by tools.

  3. 3
    Reporting

    Management summary, reproducible findings and remediation advice.

  4. 4
    Retest

    On request, we verify your fixes and update the report.

Results

What you receive

  • Management summary, understandable without prior technical knowledge
  • Overview of all findings with their risk rating
  • Technical details for each vulnerability: affected systems, evidence and specific remediation advice
  • Description of the procedure, the tools used and the rating scheme
  • Report in English or German
  • On request a retest of your fixes and an updated report
From the field

Attack paths from our projects

Anonymised attack paths from our projects, step by step, and what helped against them.

Internal penetration test

From the office network to domain admin

Starting point: a test machine in the office network, without any credentials.

  1. Captured credentials

    Legacy name resolution (LLMNR) made machines send login hashes to the test machine.

  2. Weak password

    The hash of a service account could be cracked offline.

  3. Admin on many servers

    The service account was local administrator on numerous servers; one of them held the credentials of a domain admin in memory.

  4. Domain admin

    Full control over every system in the domain.

What helped: LLMNR and NBT-NS disabled, long random passwords for service accounts, admin tiering and LAPS for the local administrator passwords.

Web application penetration test

From one customer account to all customer data

Starting point: a regular test account in a customer portal.

  1. Predictable IDs

    Invoices were loaded by sequential numbers.

  2. Missing access control

    The server did not check whom an invoice belonged to: other numbers returned the invoices of other customers (IDOR).

  3. Admin function

    An administrative API function only checked that a user was logged in, not their role.

  4. All customer data

    Read and write access to the data of every customer.

What helped: authorisation checks for every object and every function on the server; the retest confirmed the fixes.

Cloud security test

From a public bucket to the cloud account

Starting point: only the company name, no access.

  1. Public bucket

    A storage bucket with build artefacts could be read without authentication.

  2. Key in the artefact

    A deployment package contained a valid access key.

  3. Permissions too broad

    The key was allowed to change IAM policies, including its own.

  4. Account administrator

    Full control over the cloud account.

What helped: bucket made private, key rotated and replaced by roles, least-privilege permissions and secret scanning in the build pipeline.

FAQ

Frequently asked questions

Questions we often hear about this service.

All questions
What is the difference between a penetration test and a vulnerability assessment?

A vulnerability assessment identifies vulnerabilities, if possible without exploiting them, and gives a broad overview. In a penetration test, our analysts also exploit the vulnerabilities found and use them for further attacks, as far as the agreed scope allows.

Which systems can be tested?

Web applications, APIs and web services, systems reachable from the internet as well as internal networks including Active Directory. Before the test, we define together which components are in scope.

Not sure where to start?

Tell us about your environment, and we will propose a scope that fits.

Talk to us
@nullseclabs

Follow us on X for more information and current topics.