1. Home
  2. Services
  3. Penetration Testing

01 / Assess

Penetration testing for networks, applications and APIs

We test a defined scope the way a skilled attacker would: manually, creatively and with a focus on what can really be exploited. You get proof, impact and a fix for every finding.

shadowops@ops: ~/engagement

What we test

Four scopes, one rigorous method

Choose one scope or combine them. We test black box, grey box or white box depending on what gives you the most value for the time available.

Infrastructure / outside-in

External network penetration testing

Everything you expose to the internet, seen through the eyes of an attacker with no prior access.

Typical targets
Firewalls, VPN gateways, mail, remote access, exposed services
Goal
Find a way in before anyone else does

Attack surface discovery

OSINT, DNS and certificate analysis to find the hosts and services you might not know about.

Perimeter devices

VPN, firewall and remote access appliances tested for known and unknown weaknesses.

Authentication

Password spraying, MFA gaps and exposed login portals, within agreed safe limits.

Exploitation

Confirmed, controlled exploitation to show whether a weakness really leads inside.

Infrastructure / inside-out

Internal network & systems penetration testing

What happens once an attacker is inside: a compromised laptop, a malicious insider or a rogue device on the network.

Typical targets
Workstations, servers, Active Directory, network segments, OT boundaries
Goal
Measure how far one foothold can go

Assumed breach

We start from a standard employee device and account, just like a phished user.

Privilege escalation

Local and domain escalation paths, misconfigurations and credential exposure.

Lateral movement

How an attacker moves between hosts, segments and trust boundaries.

Segmentation testing

Validation that sensitive zones, servers and OT networks are really isolated.

Applications / browser

Web application penetration testing

In-depth testing of customer portals, SaaS platforms and internal business applications, well beyond what a scanner finds.

Methodology
OWASP WSTG, OWASP Top 10 and ASVS
Goal
Protect your data, users and business logic

Authentication & sessions

Login, MFA, password reset, SSO and session handling flows.

Access control

Horizontal and vertical privilege checks across roles and tenants.

Injection & input handling

SQL and command injection, XSS, SSRF, deserialisation and file upload abuse.

Business logic

Abusing workflows, prices, limits and approvals in ways developers did not foresee.

Applications / machine-to-machine

API penetration testing

REST, GraphQL and SOAP APIs behind your web and mobile apps, partner integrations and microservices.

Methodology
OWASP API Security Top 10
We work from
OpenAPI / Swagger specs, Postman collections or live traffic

Object-level authorisation

The most common API flaw: reading or changing objects that belong to someone else.

Tokens & authentication

JWT, OAuth 2.0 and API key handling, scopes and token lifetimes.

Mass assignment & data exposure

Hidden fields, over-sharing responses and parameters that should never be writable.

Rate limits & resource abuse

Brute force, enumeration and expensive queries, including GraphQL introspection and batching.

Every pentest includes

More than a list of vulnerabilities

The same standards apply to every scope, from a single API to a full network.

OWASP WSTGOWASP ASVSOWASP API Top 10PTESNIST SP 800-115CVSS v4.0
  • Kick-off and rules of engagement Agreed scope, test windows, contacts and safe-testing limits.
  • Manual testing by senior consultants Tools for coverage, people for the findings that matter.
  • Immediate escalation of critical issues You hear about serious risks the moment we confirm them.
  • Report with evidence and remediation Executive summary, CVSS-rated findings and reproduction steps.
  • Debrief and free retest We walk your team through the results and verify the fixes.

Questions

Penetration testing FAQ

Anything else? Ask us during a no-obligation scoping call.

How long does a penetration test take?

It depends on the scope. A single web application or API typically takes between three and ten testing days; a combined external and internal network test can take two to four weeks. We give you a fixed estimate after scoping.

Will testing disrupt our production systems?

We agree safe-testing limits and test windows up front, avoid denial-of-service techniques unless explicitly requested, and stay in contact throughout. Many clients test production; we can also test an acceptance environment.

Black box, grey box or white box?

Grey box, with test accounts and documentation, gives the most results per day. Black box is useful when you want an outsider's view; white box with source code access gives the deepest coverage.

Does a pentest help with compliance?

Yes. Our reports support requirements in ISO 27001, NIS2, DORA, SOC 2 and PCI DSS, and customer security questionnaires that ask for independent testing.

Go further

Related services

A pentest shows what is vulnerable. These show what an attacker could do with it.

Ready to scope your pentest?

Share what you want tested and we will come back with a scope, approach, timeline and fixed price.