Work

Four kinds of work.

These are starting points, not fixed packages. Scope depends on the system, the access available and the decision the test has to support.

01

Adversary simulation

A red-team exercise built around one agreed objective.

When it helps
You need to know whether an assumed foothold can reach a sensitive system or business action, and how the security team responds on the way.
What we test
We agree the starting access, target, allowed actions, prohibited actions and stop conditions. The exercise follows only the route needed to answer the question.
You receive
A scoping record, timestamped activity log, evidence for each finding, observations on control behaviour and a technical readout.
02

Detection testing

A controlled test of the path from source event to response.

When it helps
A rule looks correct on paper, a control has changed, or a team cannot tell why expected activity did not become an alert.
What we test
We use a named test system and marker, then inspect event creation, collection, field mapping, analytic selection, alert content and triage.
You receive
The first failed stage, the evidence behind that diagnosis, any timing gaps and a repeatable check for the corrected path.
03

Attack-path review

A review of the trust decisions that make an important route possible.

When it helps
Identity, cloud and on-premise relationships produce many apparent paths and you need to know which ones are reachable and worth fixing first.
What we test
Each important edge is written as a testable claim. Required knowledge, privileges and environmental conditions are checked before edges are joined.
You receive
A smaller set of verified paths, their prerequisites, shared choke points and an ordered list of changes with retest criteria.
04

Remediation and retest

Technical help after a finding, through to a checked correction.

When it helps
A team needs help changing a control, query, configuration or validation tool and wants proof that the original route is closed.
What we test
We work from the original evidence, agree acceptance criteria, make or review the smallest practical change and repeat the relevant control and test case.
You receive
Implementation notes, the corrected configuration or logic where agreed, test results and any remaining limitation.

Contact

Tell us what you need to find out.

Email CYSTRIKE