Virtus Group logo

Virtus Group - Incident Response Plan

v1.2 FINAL • Standardised 2025-09-04
Owner: Virtus Group Ltd • Audience: Clients, Reviewers & Operations • Classification: Public • Next Review: 2026-09-04

Executive Summary

This document describes Virtus Group’s standard for this area and how it is applied in practice. It is derived from our internal policies and standards and is intended for both reviewers and operations.

Scope & Assumptions

Requirements (Key Controls)

Procedures / Playbooks

RoleResponsibility
Incident CommanderOwns decisions, comms, and timeline
Core Infra LeadIdentity, directory, DNS/DHCP, virtualization
Network LeadWAN/SD-WAN, firewalls, VPN
Apps/Data LeadDB/app restores, file services, integrity
Comms LeadStakeholder updates; client liaison

Roles & RACI

RoleResponsibility
Incident CommanderOwns decisions, comms, and timeline
Core Infra LeadIdentity, directory, DNS/DHCP, virtualization
Network LeadWAN/SD-WAN, firewalls, VPN
Apps/Data LeadDB/app restores, file services, integrity
Comms/Privacy OfficerStakeholder & regulatory notifications

Baseline Targets

  • P1 alert triage ≤ 1 hour; target containment ≤ 24 hours where feasible
  • SIEM coverage for critical systems; high‑fidelity detections tuned and documented
  • Log retention: hot 90 days; archive 12 months (or client‑specific)
  • Post‑Incident Review (PIR): completed within 10 business days with tracked actions

KPIs & Reporting

Evidence & Records

Records are maintained per the VGL Document & Record Control guidelines, including logs, approvals, test outputs, meeting minutes, and reports.

© Virtus Group Ltd — Final version.