What it covers

  • Alerts from the endpoint detection and response tool you already run
  • Identity sign-ins, account changes and suspicious authentication
  • Cloud control-plane activity and audit logs
  • Triage and investigation of the alerts your connected sources raise
  • Containment actions limited to the playbooks you have approved
  • Escalation to the contacts you name for anything outside those playbooks

How an engagement runs

  1. Agree the ground rules

    We agree which sources to connect, who we contact and how, and which containment playbooks we may run without calling you first.

  2. Connect your sources

    You grant the access needed for the telemetry in scope. We connect it to the shared console and confirm events are arriving.

  3. Tune before relying on it

    We review early alerts with your team and tune out known-good activity, so analysts spend their time on what matters.

  4. Monitor and respond

    Analysts investigate in the console your team can see. They act within approved playbooks, and anything outside them goes to your named contact first.

  5. Review together

    Each month we send a written report and walk through it with you, including the recommendations that are still open.

What you receive

  • Access to the shared console, with alerts, evidence and analyst notes
  • A written summary for each confirmed incident
  • A record of every containment action and the playbook that allowed it
  • A monthly report on incidents, actions taken, detection coverage and open recommendations
  • A review call to go through the report

Talk to us about managed detection and response.

Tell us about your environment and what you need covered, and we will talk you through how it would work for you.