SIEM Tactics, Techiques, and Procedures
These resources are intended to guide a SIEM team to... * ... develop a workflow for content creation (and retirement) in the SIEM and other security tools. * ... illustrate detection coverage provided and highlight coverage gaps as goals to fill. * ... eliminate or add additional layers of coverage based on organizational needs. * Ensure proper logs are generated and recorded for sufficient detection, investigation, and compliance.
Without covering the basics, there isn't much point in having a SIEM. Harden your environment and configure appropriate auditing on all endpoints.
To detect an attacker, one must be equipped with the necessary logs to reveal their activities. Here we use a matrix to map detection tactics to attacker tactics (Mitre ATT&CK).
Once necessary logs are collected (detection tactics), use various methods to reveal anomalous, suspicious, and malicious activity.
Use Cases provide a means to document solutions for many reasons including tracking work, uniform response, content recreation, metrics & reporting, making informed decisions, avoiding work duplication, and more.
These efforts can provide significant benefits to some ingested logs. Typically enrichment will result in either adding a new field to events or a lookup table for use in filtering or filling in a field.
Metrics requiring fields, queries, and manual work. This section also suggests which ticketing system and form fields are recommended to allow proper recording/reporting of metrics.
Set up a lab with a Windows system, a SIEM, and an attacking system to aid in detection research and development.