Skip to content

02 — INFRASTRUCTURE SECURITY

External and internal infrastructure testing.

We map what can be reached, how far an attacker can get from different starting points, and which weaknesses open the way.

WHAT WE ASSESS

External testing shows how your organization looks from the internet: exposed services, administrative interfaces and vulnerable systems.

Internal testing starts from an assumed foothold — such as a compromised workstation or user account — and examines opportunities for lateral movement and privilege escalation.

TYPICAL RISK AREAS

01
Exposed services

Services and interfaces reachable without needing to be.

02
Identity and access

Weaknesses in directory services, delegations, service accounts and password policies.

03
Configuration and hardening

Default settings, legacy protocols and missing segmentation.

04
Patch level

Systems with known vulnerabilities that are exploitable in your environment.

Scoping

  • External IP ranges and domains in scope.
  • Starting position for internal testing and network segments covered.
  • Testing windows and any systems to exclude.
  • Contact routes during testing if something unexpected occurs.

What you receive

  • A summary of overall exposure.
  • Verified findings, including attack paths where identified.
  • Prioritized remediation and hardening recommendations.
  • Retesting when included in scope.

PROCESS

  1. 01

    Scope

    Establish objectives, asset boundaries, access, constraints and rules of engagement.

  2. 02

    Test

    Perform structured testing, combining suitable automation with hands-on investigation.

  3. 03

    Validate

    Verify findings, assess real-world implications and gather appropriate supporting evidence.

  4. 04

    Report & Retest

    Deliver prioritized findings, remediation guidance and follow-up validation where agreed.

FREQUENTLY ASKED

How is this different from a vulnerability scan?

A scan lists potential weaknesses. A penetration test verifies which are exploitable, how they combine and what that means in practice.

Do you need to be on site for internal testing?

Not necessarily. Internal testing can often be performed through a provided access point. This is agreed during scoping.

NEXT STEP

Let’s start with your security objectives.

Tell us what you want to test, build or improve. We will suggest a suitable approach and explain the next steps.