Instructions
Based on the scenario, use the dropdown selectors to select the best option to analyze the threat incident, conduct threat hunting, and harden the network against threat vectors.
Initial Access
Initial access could have been prevented by . Management should also .
Execution
can prevent execution through API. based IAM, requiring multifactor authentication, and strong before executing code are also recommended by MITRE ATT&CK as mitigations in the execution phase.
Privilege Escalation
In the scenario, escalation to system-level access privileges was accomplished by directly accessing hardware modules through API hooking. First, any must be . If the servers are Windows-based, must be .
Evasion
Mitigations such as or may have prevented unknown code from executing or masquerading as good code.
Command and Control (C2)
Command and control was achieved by obtaining access through commonly used ports, which could be prevented by .
Persistence and Lateral Movement
Mitigations for preventing persistent access and lateral movement through abusing valid accounts include or a change to the . Secure verification of may have protected the module firmware.
Impair Process Controls and Inhibit Response Function
Inhibiting security response via alarm suppression could have been mitigated by setting up a(n) . The intruders attempted to impair process control with report spoofing. Module firmware replacement may have been detected with the use of .