Everything we do,
and how it is scoped.

1.1

Vulnerability assessment

Identifies and reports known technical vulnerabilities on a server or service, improving its resilience.

Automated vulnerability analysis across the target, with manual validation of the results to remove false positives.

This is scanning with validation, not a penetration test. We keep the distinction visible in the proposal so nobody is surprised later by what it did not cover.

1.2

External infrastructure penetration test

Simulates an attacker with no prior access, from the internet, against your exposed infrastructure.

Controlled exploitation and manual validation of every vulnerability found. The assessment can cover specific assets or the whole public surface the company owns.

1.3

Web application penetration test

Assesses the application from the perspective of an attacker on the internet, with and without valid credentials.

Testing across authentication, authorisation, session management, user input and business logic, with a focus on the OWASP Top 10 categories. Business logic and authorisation flaws are where scanners stop and manual testing earns its money.

1.4

Internal network penetration test

Simulates an attacker already inside the network, whether a malicious insider or a compromised workstation.

An in-depth test of internal infrastructure to identify and exploit weaknesses that could compromise the confidentiality, integrity or availability of your systems, including Active Directory paths to privilege.

1.5

Mobile application penetration test

Covers the application, local storage on the device, and the APIs behind it.

Analysis of the mobile application and its backend, including data stored on the device, communication with the server and authentication controls, following OWASP MASVS.

1.6

Wireless network penetration test

The wireless network is often where the external perimeter and the internal network touch.

Assessment of authentication mechanisms, segregation between guest and corporate networks, and whether an attacker in the vicinity can reach the internal network.

1.7

Cloud and hybrid environment testing

In cloud environments most failures are not in the software. They are in the configuration.

Review and testing of identity configuration, permissions, service exposure and environment segregation across cloud and hybrid infrastructure.

1.8

OT and ICS environment testing

Industrial environments where availability is the dominant requirement and a conventional test is unacceptable.

Security assessment of operational technology with methodology adapted to how critical the systems are, and without actions that would compromise the availability of the operation. Few providers have validated competence in this area.

1.9

Red teaming

An objective-led exercise, with no scope announced to the defensive teams, to measure detection and response rather than the mere existence of vulnerabilities.

Simulation of a real attacker over several weeks, combining technical, physical and social engineering vectors, against objectives agreed in advance with management.

1.10

Phishing and social engineering

A large share of attacks do not begin with a vulnerable component. They begin with a person.

Simulated phishing sent to staff to measure susceptibility and the response to this kind of threat. We agree in advance what happens to people who fail: the campaign measures the process, not the individuals.

1.11

Physical intrusion test

An attacker who walks into the building does not need to get past the firewall.

Assessment of physical access controls, including attempts at unauthorised entry and connection to internal network points. Requires a signed authorisation letter and a reachable contact for the whole execution window.

1.12

Vulnerability management

A penetration test once in a company's life does not solve the problem. Continuous testing does.

New tests run every month against your assets, with real-time visibility of anything newly found. Instead of a report that ages, you get a live record: we find a vulnerability and it appears immediately for verification and assignment; you fix one and update its status, and it is re-checked as soon as possible.

3.1

Awareness and good practice

Designed for the whole organisation, including people who do not work in technical roles.

How to recognise the most common threats and scams, and the tools each person can use to improve their own security day to day. Where a phishing campaign ran first, its results become the material for the session.

3.2

Secure web application development

Designed for development teams.

Guided by the OWASP Top 10 and our internal security framework, this explains how the most frequent vulnerabilities work inside the code, in the language the company actually uses. Entirely hands-on: we provide vulnerable laboratories, demonstrate how each vulnerability is exploited and corrected, and give the team the chance to apply the techniques themselves.

3.3

Network security

Designed for IT and systems teams.

How the most frequent weaknesses in corporate infrastructure work, with laboratories where we demonstrate how they are exploited and corrected, and the team applies that knowledge directly.