Service 1.4

Internal network penetration testing.

We start from one foothold inside your network, as if an attacker had a staff laptop or password, and find out how far that reaches.

1 What we test

Active Directory: the accounts, groups, rights and settings that could let an ordinary user become a domain administrator.
Privileges on the machines we reach: whether a standard user can become a local administrator.
Reach: how far one account or one machine can go across the network.
Segmentation: whether zones that should be apart, such as offices, servers and payment systems, really are.
Passwords and secrets left in file shares, scripts and settings.

Method: PTES, NIST SP 800-115.

Actions that could break production, physical intrusion.

A way in: a VPN account, or a machine on your network we can connect to remotely.
A standard user account, like the one a new member of staff gets.
The network ranges in scope, and any systems we must not touch.
A contact who can act fast during the test windows if something has to stop.

Scope call: we agree the ranges, the systems to avoid, the test windows and who to call. You get a written offer with dates and price.
You sign the authorization. Nothing reaches your network before that.
We test from the foothold you give us, with the standard account.
Any action that could affect a production system is agreed with your contact first.
A critical finding goes to your contact as soon as it is proven. It does not wait for the report.
Any account, file or tool we add is listed in the report and removed at the end.
Report and readout, then a retest once you have fixed.

Document	What it holds	For
Technical report	Each finding with its exploit path, proof, CVSS 4.0 score, CWE and fix.	Developers, IT
Executive report	Five to eight pages on business risk, in plain words.	Management, board
Remediation plan	Findings ranked by what to fix first.	IT, project leads
Readout	A remote session to walk through the findings and answer questions.	Both
Retest attestation	Proof that the findings were fixed.	Auditors, clients

How long does it take?: It depends on the size of the network and the number of sites. The written offer gives the number of testing days and the dates before you sign.
Could it break production?: We avoid anything that could: no denial of service, no changes to your data, and anything risky is agreed with your contact before we do it.
Do you need to be on site?: No. Tests run remotely, through the access you give us.
Should we warn our IT team?: Your choice. Telling a few people means a real alert during the test is not ignored. Not telling them also shows whether they notice.

Tell us what needs testing. A tester replies with a written offer: scope, dates and price.