Lateral movement, data theft and ransomware impact
V09 · reusable vector · version 1.0HIGH · proposed test impact
After an initial foothold, an adversary seeks more systems or privileges, copies valuable data or disrupts operation. This guide concerns validation of containment and impact, not deployment of destructive malware.
Attacker tools and payload types
A remote-control component, data-transfer action or encryption/destruction program may be involved in a real attack. The assessment uses benign telemetry and synthetic files.
The entries below are tools that can support assessment or emulate aspects of this vector in an authorised fixture. They are not claims that these exact products were used in every linked incident. Native platform availability and Armory installation are different from tested capability.
- Wireshark · Armory · Existing local tool notes · Maintained official user guide
- Network Map (nmap) · Armory · Existing local tool notes · Maintained official user guide
- Sliver · native service; handoff is not automatic execution
- Timesketch · native service; handoff is not automatic execution
Repository and operating guides
incident-injects.csv · RES-018 · published synthetic fixture in the assessment collection linked from the Repository.
Methodology and Resources/Windows - Defenses.md · existing Repository reference; choose only relevant approved checks.
Read the selected tool’s guide for installation and operation rather than recreating it here. Pin the deployed version and reviewed configuration in the task record. Some local guides are autogenerated inventory notes and contain stale commands or broad prerequisite lists; they require validation before use. The official manuals linked above were checked during this review.
Reusable controlled test
Use approved lab paths, controlled benign events and an isolated restore/tabletop. No live encryption, persistence or bulk customer-data export is required.
- Required permission
- Specific lab hosts, event types, controller/operator and cleanup; production execution requires a separate reviewed method.
- Parent supplies
- Scenario/risk ID; business question; exact targets; named permitted people; channel; current policy revision; tool/resource versions; limits; expected result and reviewer.
- Output
- One result per approved case, with run and target IDs, permission decision, evidence, actual outcome and coverage limits.
- Measure
- Paths blocked; events collected/detected/acknowledged; measured recovery time/data age and business-validation results. No client result has been collected here.
- Failure handling
- Blocked, not authorised, failed, inconclusive and not tested remain visible. A refused route cannot be replaced by another agent, channel or target without fresh applicable approval.
What the vector returns to the scenario
| Result | What it means |
|---|---|
| Control held | The evidenced attempted action was prevented under the tested conditions. This is not a universal security guarantee. |
| Control failed | Describe the exact observed boundary failure and its business consequence, without inflating it into a wider compromise. |
| Unknown / not tested | Record the missing capability, evidence, permission or coverage. Do not invent a score. |
Mitigation recommendations
Reduce likelihood: Reduce initial access opportunities and cross-system privilege paths.
Reduce impact: Segment services, protect recovery assets and rehearse detection, containment and business recovery.
Define how a later retest would verify the recommendation; implementation assignments, scheduling and pricing are Part 2.