Services · Compromised Machine Simulation

Compromised Machine Simulation: what if an attacker is already inside?

Compromised Machine Simulation is an Assumed Breach test that starts with ordinary employee access. We assess what an attacker could reach in your network from one compromised account and what your defences would detect.

What it is

What is Compromised Machine Simulation?

An attacker can enter an organisation in many ways: successful phishing, a leaked password or a compromised laptop. This test does not examine how they got in. It starts once they are inside.

You provide ordinary user access without elevated privileges. From that position, we follow one attack path: which data and servers are accessible, whether permissions can be increased, and how close an attacker could get to Active Directory administration or the systems that matter most to you.

We always assess detection. You see what we reached, which actions your defences recorded and which they missed.

The principle of assuming an attacker is already inside forms part of Zero Trust. NIST describes it in its Zero Trust Architecture (SP 800-207), and Microsoft includes it among its Zero Trust principles. Compromised Machine Simulation is our name for a specific test built on that principle.

Who it is for

When Compromised Machine Simulation makes sense

The test suits organisations with basic security measures in place that want to know what would happen if the first line of defence failed. Consider it if:

01

your perimeter has been tested

and the next question is what happens if an attacker gets through;

02

you have invested in detection

, such as EDR, SIEM or a SOC, and want to know whether it can distinguish an attacker using a valid account from normal activity;

03

your environment has changed significantly

, through a migration, network merger or new suppliers;

04

many people and suppliers have network access

and it is becoming difficult to keep track of their permissions;

05

management wants a specific answer

rather than a general list of risks;

06

you are preparing for a Red Team

and want to get more value from it.

When it is too early for this test

Sometimes a test mainly tells you what you already know. That can happen when you lack an inventory of systems and accounts, basic issues remain unresolved, such as shared administrator passwords or missing MFA, or nobody monitors security alerts. A security audit or internal penetration test may be a better first step. To assess the whole organisation, including people and physical access, choose Red Teaming.

What you receive

What you receive at the end

01

Executive summary

a clear account of what the attacker reached from one ordinary account and what it means for your business.

02

The attack path, step by step

from the starting account to the agreed objectives, with evidence for your IT team.

03

Detection assessment

which actions your defences detected, which they missed and when.

04

Prioritised recommendations

what to fix now and what can wait, for example in permissions, network segmentation or account management.

05

Presentation of findings

for your technical team and management.

The retest is priced separately, from 1 person-day for all findings.

How it works

How Compromised Machine Simulation works

01

Initial consultation

You identify one or two assets whose protection matters most, such as a specific system or dataset.

02

Rules and NDA

We sign an NDA before every project, together with a contract, and document the Rules of Engagement: scope, testing window and a contact for urgent findings.

03

Who knows about the test

You decide who in your team will be informed. This matters because detection is always assessed.

04

Testing

Starting with an ordinary user account, we act as an attacker who has already gained entry.

05

Report and debrief

We deliver the findings and review them with your team.

How it compares

Compromised Machine Simulation, internal pentest or Red Team?

Internal penetration test

Which vulnerabilities exist in the internal network?

Starting point
The internal network
Breadth
Broad coverage of internal vulnerabilities
Detection
Can be assessed as an additional objective
Red Teaming

Would the whole organisation detect and stop an attack?

Starting point
No access or prior knowledge; Assumed Breach starts inside with an account, device or supplier access
Breadth
People, processes and technology
Detection
Always assessed and a primary objective

Compromised Machine Simulation FAQs

What is Compromised Machine Simulation in plain English?

We assume an attacker has already compromised one employee's computer or account. From that position, we assess what they could access and whether your defences would notice.

How does it differ from an internal penetration test?

An internal penetration test aims for broad coverage of vulnerabilities in the internal network. Compromised Machine Simulation follows one attack path from one ordinary account towards agreed objectives and always assesses detection.

How does it differ from an Assumed Breach Red Team?

A Red Team assesses the whole organisation, including people, processes and technology, and could start with supplier access. Compromised Machine Simulation is narrower: one ordinary account, one attack path and an assessment of detection.

How long does the test take?

It depends on scope and objectives. We will propose a schedule in our proposal after the initial conversation.

What access do you need from us?

Ordinary employee access without elevated privileges. We agree the details during the initial consultation.

Does our IT team or SOC need to know about the test?

You decide. We always assess detection. We agree in advance who knows about the test and whether your SOC will be informed.

Could testing disrupt our operations?

The test starts from one ordinary account and follows an agreed scope, testing window and rules. Our penetration testing overview explains how we reduce the risk of disruption.

How does the retest work?

The retest is priced separately, from 1 person-day for all findings.

Is this test required by law or NIS2?

No. DORA, NIS2 and the Czech Cybersecurity Act (Act No. 264/2025 Coll.) do not require a service of this type. It can help check whether detection works, but does not replace the penetration test required under Decree No. 409/2025 Coll.

Services
Contact

Find out what an attacker could reach in your organisation.

Tell us what you want to protect. We will propose the scope, rules and schedule.

Book a consultation →