← All use cases

Cloud Security Platform · Threat Intelligence & Attack Simulation

Threat intelligence mapped to the systems you run

Aribot joins MITRE ATT&CK techniques and CVE data to the components and resources you have connected, so a new threat shows which systems it reaches.

1. Collect intelligence · 2. Map to your components · 3. Track CVE status · 4. Feed the threat model1Collectintelligence2Map to yourcomponents3Track CVE status4Feed the threatmodel

The problem

Our threat feeds are full of campaigns and CVEs, and most have nothing to do with what we run. Working out which ones touch our systems is manual, so it happens late. By the time we know a technique reaches us, the window to act has passed.

How Aribot handles it

  1. 1

    Collect intelligence

    Entries come from MITRE ATT&CK, CVE and NVD data, your cloud accounts and your repositories.

  2. 2

    Map to your components

    Each technique or CVE is joined to the components and resources it could reach.

  3. 3

    Track CVE status

    Affected CVEs are tracked as active, mitigated or patched.

  4. 4

    Feed the threat model

    Mapped threats land on the architecture, next to the controls that stop them.

What you get

  • Threat intelligence filtered to what you run
  • CVE status tracked against affected components
  • Threats placed on the architecture with their controls
  • A starting point for attack simulation on new techniques

Related use cases