Skip to content

Latest commit

 

History

History
129 lines (97 loc) · 6.6 KB

threat_intelligence.md

File metadata and controls

129 lines (97 loc) · 6.6 KB

ToC

Must read

Generic workflow

Here is an example of what we could expect to have:

image

Platform

TIP choice

Here are my recommendations:

Common TIP integrations (dataflow)

As per Forrester article, here is a drawing about examples of common integration between threat intel sources, TIP, and security solutions:

image

Architecture example

Here is an example of an architecture with:

  • SIEM: Elastic;
  • TIP: MISP / OpenCTI;
  • SIRP: TheHive;
  • Threat intel orchestrator: Cortex.

image

Sources

Threat intelligence and automation

Threat intel program and automation

As per ThreatConnect article:

As threat intelligence drives your orchestrated actions, the result of those actions can be used to create or enhance existing threat intelligence. Thus, a feedback loop is created — threat intelligence drives orchestration, orchestration enhances threat intelligence.

image

Identity-based detections

  • Correlate identity-related detections (from sensors like EDR, CASB, proxies, WAF, AD, ...) with identity intelligence (for instance, passwords leak/sell detection);

    • Here is an example of the global detection process (with courtesy of RecordedFuture):

    Capture9

End

Go to main page.