01 / The challenge
The challenge
During an attack, clues can be scattered across endpoints, servers and security tools. An attempt to delete recovery copies, for example, needs to be linked to the account and process behind it.
02 / How SECNOLOGY helps
How SECNOLOGY helps
Collect useful events
Windows, Sysmon and integrated security tools provide the traces required by your scenarios. Collection quality determines what can be detected.
Recognize a defined behavior
Rules can look for a command that deletes shadow copies or examine a history of encryption operations. Process, account and file context helps you assess the signal and decide what should follow.
Trigger your procedure
Connect the signal to a notification or configured measure. Documented scenarios include restricting permissions on a resource and starting additional network collection. Test the scope and conditions before enabling the response.
03 / Useful data sources
Useful data sources
- Windows, Sysmon and security events
- Process, host and account context
- Detection rules and response procedure
04 / What you get
What you get
- Qualified signals for investigation
- Response organized around your rules
- Evidence to reconstruct the incident
Planning your deployment
This scenario complements existing protections. Coverage depends on logs, enabled rules and integrations; it does not guarantee detection of every ransomware strain or prevention of every attack.
