RedELK – Enhancing Red Team Operations And Blue Team Detection Through Centralized SIEM

Short: a Red Team’s SIEM.

Longer: a Red Team’s SIEM that serves two main goals:

1. Enhanced usability and overview for the red team operators by creating a central location where all relevant operational logs from multiple teamservers are collected and enriched.
   • This is great for historic searching within the operation as well as giving a read-only view on the operation (e.g. for the White Team).
     • Especially useful for multi-scenario, multi-teamserver, multi-member and multi-month operations.
       • Also, super easy ways for viewing all screenshots, IOCs, keystrokes output, etc. \o/
2. Spot the Blue Team by having a central location where all traffic logs from redirectors are collected and enriched. Using specific queries its now possible to detect that the Blue Team is investigating your infrastructure.

RedELK uses the typical components Filebeat (shipping), Logstash (filtering), Elasticsearch (storage) and Kibana (viewing).

Rsync is used for a second syncing of teamserver data: logs, keystrokes, screenshots, etc. Nginx is used for authentication to Kibana, as well as serving the screenshots, beaconlogs, keystrokes in an easy way in the operator’s browser.

A set of python scripts are used for heavy enriching of the log data, and for for Blue Team detection.