Academy
TermData

Leak impact analysis

Determining which data, accounts and systems were affected by a leak and prioritising what needs to be done.

Flow

  1. 1Scope
  2. 2Freshness
  3. 3Prioritisation
Related families
—
MITRE ATT&CK
T1005 · Data from Local System
Sources
4 sources
01

Overview

An infostealer log contains more than passwords: browser cookies, autofill entries, device information and files are there too. Impact analysis works out what each of these means for the organisation. MITRE ATT&CK

The key question is the date of the leak: if the password was changed after that date, the risk drops; if not, it can still be used years later. Google Cloud (Mandiant)

02

How it works

  1. 1

    Scope

    Which accounts, which sign-in URLs, which device.

  2. 2

    Freshness

    The infection date and whether the password has changed since then. Google Cloud (Mandiant)

  3. 3

    Prioritisation

    Administrator and remote access accounts are handled first. MITRE ATT&CK

03

Real-world examples

Snowflake: passwords never changed

Mandiant reported that some of the credentials used in the attack had been stolen years earlier and had not been changed since. Google Cloud (Mandiant)

04

How to detect it

05

What to do

  • Change the password, end sessions and re-enrol multi-factor authentication. MITRE ATT&CK
06

MITRE ATT&CK

07

Related terms

08

Sources

  1. 1Data from Local System (T1005) · MITRE ATT&CK
  2. 2UNC5537 targets Snowflake customer instances · Google Cloud (Mandiant), 2024
  3. 3Privileged Account Management (M1026) · MITRE ATT&CK
  4. 4Multi-factor Authentication (M1032) · MITRE ATT&CK