A multi-client SOC needs to turn alert activity into decisions that fit each organisation. At Growing MSSP with Offensive Services, I combined shift leadership and hands-on incident response in a seven-person team. The service monitored 70,000+ endpoints across 150+ organisations, including hospitality, aviation, education, law, finance and retail.
I used MSSP SIEM and SOAR for triage and investigation, then followed the evidence through packet captures, process execution trees and endpoint, network, cloud and SaaS logs. Timelines and frequency analysis helped me connect individual events to lateral movement, ransomware and other suspicious activity.
For confirmed threats, I worked with clients through containment and eradication, explaining the observed activity, root cause and impact supported by the evidence. My reports translated the investigation into remediation decisions for technical contacts, managers and executives.
The linked VPN, mailbox, vishing and malware cases show the detailed investigation behind that wider operational responsibility.
Methods, evidence & technical decisions
Responsibility across a varied client estate
I combined SOC shift management, alert and email triage, deeper investigation and client communication within a seven-person team. The provider served 150+ organisations and monitored 70,000+ endpoints.
Open this detail ↗Moving from an alert to a response decision
I followed SIEM and SOAR events into packet captures, process trees and host, network, cloud and SaaS records. I used timelines and frequency analysis to assess suspicious activity and explained the supported root cause, impact and remediation to the client.
Open this detail ↗Evidence from the investigations
The linked cases show VPN-session attribution, Microsoft 365 persistence analysis, reconstruction of a remote-support intrusion and staged PowerShell malware analysis. Each demonstrates a different form of investigation within the SOC and incident-response responsibility.
Open this detail ↗Skills used in this work