Under attack right now? Skip the queue: a responder reads incident reports first.Open an incident

Section
Platform
Ref
BM-PL
Updated

Everything that runs overnight.

Eight capabilities on one timeline: detection, response, remediation and compliance reporting. The AI proposes. A person signs. The record keeps itself.

Section 1

Command Centre

The board and the SOC read the same page.

What goes wrong
During an incident, leadership asks for a summary while analysts are still reading raw alerts. Two audiences end up with two versions of the truth.
Action
One view holds the executive summary, live attack-surface posture and every open incident. Analysts drill in; executives read the top line. Both are looking at the same record.
Evidence produced
  • Incident summary at any moment, timestamped
  • Posture snapshot per briefing
  • Who viewed what, and when
Exhibit 1.1 · Command Centre, schematic
  1. Executive summary, written for a non-specialist
  2. Attack-surface posture against your approved baseline
  3. Open incidents, highest severity first

Section 2

Asset Discovery

You cannot contain what you have not listed.

What goes wrong
Workloads, services and data stores appear faster than any spreadsheet can track. The breach usually starts in the one nobody listed.
Action
Continuous discovery across your cloud accounts, with each asset classified and tagged by risk the moment it appears.
Evidence produced
  • Asset inventory, versioned daily
  • Classification and owner per asset
  • First-seen and last-changed dates
Exhibit 2.1 · Asset Discovery, schematic
  1. Every workload, service and data store, discovered
  2. Classification tags applied automatically
  3. Risk flag where exposure meets sensitive data

Section 3

AI Threat Detection

Most alerts are noise. The record shows which ones were not.

What goes wrong
Streaming telemetry produces thousands of events an hour. Analysts triage by instinct and fatigue.
Action
Anomaly clustering groups related events, maps them to MITRE ATT&CK techniques and scores severity, so the few that matter rise to the top with their reasoning attached.
Evidence produced
  • Cluster membership, and why
  • ATT&CK technique mapping
  • Severity score with its inputs
Exhibit 3.1 · AI Threat Detection, schematic
  1. Related events clustered into one anomaly
  2. Techniques mapped on the MITRE ATT&CK matrix
  3. Background events, kept but not escalated

Section 4

Threat Analysis

Behaviour first, then signatures.

What goes wrong
Signature-only detection misses attackers who use valid credentials and ordinary tools.
Action
Behavioural analytics, live intelligence feeds and heuristics tuned to your environment reconstruct the attack path, one step at a time.
Evidence produced
  • Reconstructed attack path
  • Intelligence sources consulted
  • Confidence for each step
Exhibit 4.1 · Threat Analysis, schematic
  1. Initial access: a valid credential, used oddly
  2. The step where containment cuts the path
  3. Intelligence that matched, with its source

Section 5

Database Remediation Workflow

Engineers and security sign the same timeline.

What goes wrong
Database fixes stall between teams: security finds the problem, engineering schedules it, and nobody owns the rollback.
Action
Patch queues, rollback coordination and an immutable audit trail on one shared timeline, with sign-off tracked at every step.
Evidence produced
  • Patch queue with owners
  • Rollback plan per change
  • Immutable sign-off trail
Exhibit 5.1 · Database Remediation Workflow, schematic
  1. Steps completed, in order
  2. The engineer’s sign-off, captured in place
  3. Rollback plan, attached before anything runs

Section 6

Automated Patching

Fast, inside the change window, with a way back.

What goes wrong
Patches wait weeks for a window, then go out untested at 2 a.m.
Action
Fixes are queued, tested and deployed inside your change windows, with rollback safeguards built in. Anything that touches production still waits for a signature.
Evidence produced
  • Test results per patch
  • Change window used
  • Rollback, if triggered, and why
Exhibit 6.1 · Automated Patching, schematic
  1. Your approved change window
  2. The deployment, inside it
  3. One-step rollback, staged in advance

Section 7

Compliance Reporting

The audit pack writes itself while you work.

What goes wrong
Evidence is gathered by hand in the weeks before an audit, from memory and screenshots.
Action
Audit-ready packs, board decks and customer trust reports, generated on demand across SOC 2, ISO 27001, HIPAA and GDPR from evidence collected as you operate.
Evidence produced
  • Control-by-control evidence
  • Board deck, on request
  • Customer trust report
Exhibit 7.1 · Compliance Reporting, schematic
  1. The pack, assembled from live evidence
  2. Each control, checked against its evidence
  3. Framework cover sheet: SOC 2, ISO 27001, HIPAA or GDPR

Section 8

Governance Engine

Policy, risk and approval in one register.

What goes wrong
Policies live in documents, risks in spreadsheets and approvals in email. Nobody can show the chain.
Action
Policies, risk registers and approvals across business units in one place, each decision signed and linked to the evidence behind it.
Evidence produced
  • Policy versions and owners
  • Risk register with decisions
  • Approval chain per change
Exhibit 8.1 · Governance Engine, schematic
  1. Each policy, with its owner
  2. An approval still waiting: flagged, not assumed
  3. Signed approvals, linked to evidence

Appendix A

Extensions: Boardroom and SurfaceGuard.

Extension 01

Boardroom

Turns vulnerabilities into financial exposure, using the Ponemon cost-per-record loss model, then writes the C-suite briefing and a 30, 60 and 90-day roadmap to go with it.

Extension 02

SurfaceGuard

Audits your public web estate against WCAG 2.1 AA, estimates statutory exposure under the California Unruh Act and ADA Title III, and prepares a pre-litigation defence pack.

Open the equipment manifest

Appendix B

Native integrations.

BreachModal connects to the cloud and DevSecOps tooling you already run. No custom connectors to build first.

  1. B.01AWS
  2. B.02Microsoft Azure
  3. B.03Google Cloud
  4. B.04Kubernetes
  5. B.05Terraform
  6. B.06Slack
  7. B.07PagerDuty
  8. B.08ServiceNow

Also: Jira, GitHub, Okta, Datadog, Splunk, and anything else you can reach over a REST API.

Appendix C

Zero to containment: the playbook.

A practical incident response playbook written by our team, with a one-page SEV-1 quick card. No email gate.

  1. Chapter 1Preparation: the decisions to make before an incident
  2. Chapter 2The first 15 minutes: triage and declaration
  3. Chapter 3Containment without destroying evidence
  4. Chapter 4Communications, evidence preservation and close-out
Download the playbookPDF · 5 pages · 119 KB

See it for yourself

See it against your own estate.

We do not run canned tours. Bring your infrastructure profile and we will replay a live scenario on it, with every action waiting for you.