Cloud incident response and forensics

Know what happened.
Take back control.

Invictus specialists investigate attacks across connected cloud identities, applications and services, and help you prepare for the next one.

How we investigate

The experts who train your current responders.

We helped pioneer cloud incident response. Industry and government rely on our expertise to investigate attacks and train their teams. That same expertise leads every incident we take on. Hands-on from the first call, we move quickly to preserve evidence, expose threat actor activity and help you take control.

  1. Know what happened.Where it started, and the trail it left.
  2. Know what was affected.Every identity and resource it reached, in order.
  3. Know what to do next.Where it stopped, and what to close first.

Explore an incidentSee how we investigate

One illustrative incident drawn as rings of time around the first compromised identity; numbered markers match the three points
Illustrative incident · synthetic data · each ring is five minutes

Academy

Build responders, not attendees.

Cloud incident response courses and hands-on Labs, taught by the people who take the call.

Example investigation

One stolen token, three questions.

One credential can connect code, pipelines and cloud resources. Every investigation answers three questions.

Read the article
  1. Reach

    What could it touch?

    Map the repositories, secrets, pipelines and cloud roles the token could reach.

  2. Evidence

    What would the logs show?

    Establish which records exist, for what period, and where the record is missing.

  3. Control

    What does it take to regain control?

    Preserve evidence, revoke and rotate in priority order, and confirm what was accessed before calling it resolved.

Illustrative scenario Synthetic example. No case figures shown.

Open source

Open source. Built for the investigation.

Tools from Invictus for collecting and examining cloud evidence.

Explore our tools
SourcesOutputsExtractor SuitePowerShell
Microsoft 365
Entra ID
AzureUnifiedAuditLogEvidence export · JSON, CSVTimeline-readyYour SIEM or data lake
Extractor Suite

PowerShell tool that collects the logs and configuration you need from Microsoft 365, Entra ID and Azure.

Read the docsTool pageGitHub

SourcesOutputsInvictus-AWSPython
Services
Configuration
Service logsCloudTrailJSON per service · local or S3Athena · one CSV per queryMerged workbook · XLSX
Invictus-AWS

Enumerates an AWS account, collects configuration and available logs, and queries CloudTrail with Amazon Athena.

Read the docsTool pageGitHub

SourcesOutputsKubeForenSysPython
AKS cluster
Pods and events
RBACkubelogs_CLLog Analytics workspaceEight custom tablesQuery with KQL · kept 30 days
KubeForenSys

Collects forensic data from an Azure Kubernetes Service cluster into Azure Log Analytics for analysis with KQL.

Read the docsTool pageGitHub

SourcesOutputsALFAPython
Workspace
Login
Drive · AdminAdmin SDK Reports APIJSON per log typeEvents mapped to ATT&CKRanked attack sequences
ALFA

Acquires Google Workspace audit logs, maps events to MITRE ATT&CK and scores sequences for analyst review.

Read the docsTool pageGitHub

Response Retainer

Agree the response relationship before you need it.

Contacts, access and terms settled in advance, so an incident starts with the investigation.