Sentinel SOC Lab
Container-based attack simulation lab with a vulnerable PHP app, MySQL, Kali, and a syslog collector forwarding events to Microsoft Sentinel. Includes attack scripts and KQL examples for examining failed logins and SQL injection attempts.
- Focus
- Cloud SIEM
- Scope
- attack simulation
- Source
- Public repository
The purpose
Connect local attack simulation to Microsoft Sentinel, then use KQL to examine the events generated by a deliberately vulnerable application.
How it fits together
- 01
Kali attacker container
- 02
Vulnerable PHP app / MySQL
- 03
Syslog collector and forwarding
- 04
Microsoft Sentinel / SecurityLab_CL
Engineering choices
Generate controlled attack traffic
Containerised scripts exercise SQL injection, brute-force logins, port scanning, and web scanning against the lab application.
Separate collection from analysis
A syslog collector forwards local events to the configured Azure workspace for analysis in Sentinel.
Start with inspectable KQL
The README includes queries to list incoming events, inspect failed logins, and search for SQL injection-like activity.
What the project documents
The README documents the container architecture, attack script commands, Azure workspace setup, and KQL checks.
The examples query SecurityLab_CL and inspect RawMessage_s and EventType_s fields.
Inspect failed logins
SecurityLab_CL
| where RawMessage_s contains "LOGIN_FAILED"
| project TimeGenerated, RawMessage_s
| order by TimeGenerated descA query from the project README for examining authentication events in Sentinel.
Current scope & limitations
A learning lab for log forwarding and KQL-based analysis. The intentionally vulnerable application belongs in a contained environment. The README does not establish automated response playbooks, UEBA, or threat intelligence integration.