Real external attackers discovered the Azure lab environment's RDP port exposed to the internet and launched a sustained distributed brute force campaign targeting the Administrator account. 273 unique IPs across 38 countries generated 14,661 failed authentication attempts over 10 days.
Root cause: Azure NSG rule permitted inbound RDP from 0.0.0.0/0. Upon detection the NSG was restricted to authorized IPs — attack traffic dropped to zero immediately and verifiably.
No successful unauthorized logons confirmed across the entire 10-day attack window. Incident closed at Tier 1.
| ID | Technique | Evidence |
|---|---|---|
| T1110.001 | Brute Force: Password Guessing | 14,661 failed logon attempts against Administrator |
| T1133 | External Remote Services | RDP port 3389 targeted as primary access vector |
No breach occurred. The following documents what would have triggered escalation and the exact response actions.
Evidence collected during investigation — screenshots from Splunk, ServiceNow, Azure NSG, VirusTotal, and AbuseIPDB.








Suricata IDS detected a comprehensive multi-vector attack — RDP brute force, SSH scanning, MySQL, PostgreSQL, MSSQL, VoIP/SIP, SNMP, and active Nmap reconnaissance all firing simultaneously. 23 distinct signatures revealed a fully automated framework probing every available service.
Primary attacker 194.165.16.167 hosted on Flyservers S.A. (AS48721) — documented bulletproof hosting in Lithuania. 15,422 AbuseIPDB reports at 100% confidence. Same IP confirmed actively attacking other organizations during the investigation window.
No lateral movement, no breach, no malicious execution detected across all 6 alert categories.
| Signature | Count | Category |
|---|---|---|
| ET INFO RDP Response To External | 1,385 | Misc Activity |
| ET POLICY MS RDP Admin Login | 662 | Protocol Decode |
| ET DROP Dshield Block Listed | 209 | Misc Attack |
| ET SCAN Potential SSH Scan | 6 | Network Scan |
| ET SCAN RDP Connection from Nmap | 1 | Network Scan |
| ID | Technique | Evidence |
|---|---|---|
| T1595 | Active Scanning | Nmap sig — multi-port across 8+ services |
| T1046 | Network Service Discovery | SSH, MySQL, MSSQL, VoIP, SNMP probed simultaneously |
| T1110.001 | Brute Force | 662 RDP Administrator login signatures |
No breach occurred. The following shows what compromise indicators would have looked like and the exact response.
Evidence collected — Suricata alerts, threat intelligence, ServiceNow ticket documentation.






A simulated phishing campaign delivered a convincing Microsoft 365 password expiry notification to an internal user. The spoofed sender and urgency messaging caused the target to click within 55 seconds and submit credentials within 3 minutes — a textbook demonstration of how social engineering bypasses technical controls.
GoPhish captured the full credentials in cleartext. An 8-phase post-compromise investigation confirmed no unauthorized credential use, no lateral movement, no malicious process execution, and no data exfiltration.
Credential theft confirmed. No post-compromise activity detected. Critical gap identified: absence of MFA means stolen credentials would allow immediate account takeover with no additional barriers.
| ID | Technique | Evidence |
|---|---|---|
| T1566.001 | Spearphishing Link | Email with malicious link to credential harvesting page |
| T1078 | Valid Accounts | Legitimate internal credentials captured in cleartext |
| T1056.003 | Web Portal Capture | Fake M365 login page captured submitted credentials |
| T1204.001 | User Execution: Malicious Link | Target clicked 55 seconds after delivery |
Credentials harvested but never used maliciously. Each phase shows what real compromise would have looked like and the exact response.
Evidence collected — GoPhish dashboard, Papercut inbox, credential capture, Splunk investigation queries.
SOC Analyst with hands-on experience building and operating an enterprise-grade security operations environment. I designed, deployed, and integrated a full detection and response stack from scratch — SIEM, IDS, ticketing, Active Directory, and phishing simulation — on Azure cloud infrastructure.
My investigations use real external attack telemetry, not simulated lab traffic. Real attackers hit my environment. I detected them, investigated them, and documented the analyst workflow from first alert to resolved ticket.
I built this because I wanted to show what I can actually do — not just what I've studied. Every detection, every investigation, every case study in this portfolio reflects how I'd operate in a real SOC environment.