Technical methods and evidence
Use the relevant existing technique skills for implementation details. These notes explain technical prerequisites and evidentiary limits; they do not define an engagement stage order, dispatch policy, or report lifecycle. Tool availability and argument names come from the live schema. Authorization comes from the RoE.
Access and credential evidence
For a shell, associate the actual user/token, host, effective privileges and network position. A successful TCP connection or a shell-like banner is not proof of code execution. For credentials, record protected artifact paths, source identity, credential type, validity window and the service where use was actually validated. A ticket's SPN, realm and delegation constraints affect where it can work; a hash or credential stored in a graph is not proof of usable access.
State changes and transport
Privilege and lateral-access claims require before/after identity and a concrete observable at each claimed hop. Reuse the existing credential, privilege and lateral technique skills for platform-specific prerequisites. For an authorized file transfer, record source/destination paths, hash and byte count. For a requested C2 check, record session/implant identity, callback timestamp and last check-in; a generated implant or configured listener does not prove callback. Separate attempted actions, observed defender events and unavailable telemetry. Modification/cleanup evidence must refer to the exact files, services, tickets or sessions actually changed.
