A new MDR service needs workable incident integrations, clear operating requirements and analysts ready to use them. I was the sole project lead for onboarding the service, taking ownership from integration configuration through operational requirements and acceptance.
I owned the integration configuration for the two SOAR platforms within the Microsoft Sentinel, ServiceNow SecOps/SIR and Cortex XSOAR workflow. I worked through incident and alert ingestion, affected users, observables, ATT&CK mappings, escalation labels, linked incidents and closure so the platforms carried the context analysts needed.
I defined the ServiceNow SecOps measurement model for MTTA, MTTC and MTTR across two queues, five incident states and three substates. I specified the state definitions and KPI requirements that reporting was built around, including how assignment-group movement affected attribution between the MDR and internal SOC. I built dashboards to make that operational performance visible.
I streamlined joiner, mover and leaver processes for MDR analysts and connected service access with the onboarding requirements. Together, this work established the integration configuration, measures and analyst processes needed to operate the new service.
Methods, evidence & technical decisions
Own integration configuration and preserve incident context
I owned the integration configuration for the two SOAR platforms within the Microsoft Sentinel, ServiceNow SecOps/SIR and Cortex XSOAR workflow. I defined the handling of affected users, observables, ATT&CK context and operational labels, including escalation, linking and redirection, so analysts retained the context needed to work the incident.
Open this detail ↗Keep incident resolution consistent across platforms
I validated how incident resolution decisions moved between Sentinel and ServiceNow SIR, addressing closure-mapping issues so the receiving platform preserved the intended investigation outcome.
Open this detail ↗Lead the new MDR onboarding project
I was the sole project lead for onboarding the new MDR service. My ownership connected integration configuration, service requirements, acceptance work and the analyst operating model. I led the work with the relevant platform and service teams.
Open this detail ↗Define performance reporting across two queues and the incident lifecycle
In ServiceNow SecOps, I defined MTTA, MTTC and MTTR requirements across two queues, five states and three substates. I established clear state definitions and KPI requirements so reporting reflected the incident lifecycle and assignment-group movement, distinguishing MDR activity from the internal SOC contribution. The reporting was built around this model, supported by dashboards I built to monitor SOC operations.
Open this detail ↗Streamline the MDR analyst JML process
I streamlined joiner, mover and leaver processes for analysts on the MDR side. This connected onboarding and service-access requirements with the people joining and working the service, alongside the incident workflows and operational handovers.
Open this detail ↗Skills used in this work