Cyber threat intelligence: maturity and metrics

From SANS Cyber Threat Intelligence Summit 2016. What are the characteristics of a mature cyber threat intelligence program, and how do you develop meaningful metrics? Traditionally, intelligence has been about providing decision
support to executives whilst the field of cyber threat intelligence supports this customer, and network defenders, who have different requirements. By using the intelligence cycle, this talk will
seek to help attendees understand how they can identify what a mature intelligence program looks like and the steps to take their program to the next level.

Cyber threat intelligence: maturity and metrics

2.
Intelligence definition
 “… intelligence is information that has been
analyzed and refined so that it is useful to
policymakers in making decisions—specifically,
decisions about potential threats …”
 https://www.fbi.gov/about-us/intelligence/defined

3.
I have IOCs!
Everything is targeted at me and unique to me! Cant share!
IOCs or not actionable!
IP blocked!
Only able to consume tactical intelligence products

4.
I have IOCs with grouping and some context!
This is China APT - Ugly Panda!
I mostly copy content from vendor threat intel reports
Have some pre-determined requirements documented
It’s not relevant unless it hits us!

5.
I have prioritized intelligence requirements
I produce unique, timely and relevant intelligence products to different internal consumers
I look at threats to my vertical/sector, not just my org
My intelligence program is expensive!

8.
Relevance
 Relevance: does this intelligence (collection) satisfy one
or more of my intelligence requirements
 If I don’t have intelligence requirements (you should),
does this impact me or my sector/vertical

15.
Planning, Direction, Needs,
Requirements
 Three requirements lists to build and maintain:
 Production requirements – What will be delivered to
the intelligence customer/consumer.
 Intelligence requirements – What we need to collect to
meet our production requirements.
 Collection requirements – The observables/data inputs
we need to answer our intelligence requirements.

16.
Production requirements
• What is needed to be
delivered to the
intelligence customer
(the end consumer of
the intelligence).
Intelligence
requirements
• What we need to collect
to be able to meet our
production
requirements.

17.
Production requirement Intelligence requirements
What vulnerabilities are
being exploited in the world
that we can't defend against
or detect?
- What vulnerabilities are
currently being exploited in
the wild?
- What exploited
vulnerabilities can my
organization defend?
- What exploited
vulnerabilities can my
organization detect?
- What vulnerabilities are
being researched by cyber
threat actors?

18.
Intelligence
requirements
• What we need to collect
to be able to meet our
production
requirements.
Collection requirements
• The observables/data
inputs we need to
answer the intelligence
requirement.

19.
Intelligence requirements Collection requirements
What vulnerabilities are
currently being exploited in
the wild?
- Liaison with other
organizations in the same
market sector.
- Liaison with other
members of the
information security
industry.
- Open source feeds of
malicious URLs, exploit
packs, etc mapped to
vulnerability/vulnerabilities
being exploited.
- Online forum monitoring
where exploitation of
vulnerabilities are

22.
Once you have your collection requirements
 Look at what is feasible.
 Consider risk/cost/time of doing something in-house versus using an
external provider
 Task out individual collection requirements internally or to external
providers as guidance.
 Track internal team/capability and external provider ability to
collect against the assigned guidance.

26.
Intelligence analysis
 Intelligence style guide
 Defines format and meanings of specific terms within your
intelligence products
 Analysts who are able to deal with incomplete information
and predict what has likely occurred and what is likely to
happen.
 Encourage analysts to suggest multiple hypothesizes.

28.
Words of estimative probability
 Consistency in words used to estimate probability of
things occurring or not occurring, i.e.
100% Certainty
The General Area of Possibility
93% give or take about 6% Almost certain
75% give or take about
12%
Probable
50% give or take about
10%
Chances about even
30% give or take about
10%
Probably not
7% give or take about 5% Almost certainly notGoogle search for: CIA words of estimative probability

29.
Dissemination
 Intelligence products written with each piece of
collection used graded and linked to source.
 Intelligence products sent to consumers based on
topic and requirements met.
 What information gaps do we have?

30.
Feedback loop
 We need to receive information from our intelligence
customers on:
 Timeliness
 Relevance
 What requirements were met?
 This will allow identification of intelligence (collection)
sources that are supporting your requirements and which
aren’t

33.
Item Yes/
No
Intelligence collection is easily consumable, i.e. in a TIP
Intelligence style guide
Have an intelligence review and editing process
Intelligence produced includes future predictions and doesn’t just report
on facts
Sources used in intelligence products are linked and graded
Knowledge gaps are identified in intelligence products and pushed back
into the requirements part of the intelligence cycle
Feedback is received from intelligence consumer/customer

34.
Item Yes/
No
KPIs are generated for the intelligence program
KPIs are generated for each part of the intelligence cycle including for
internal and external sources of intelligence collection
Have an intelligence (collection) management function that handles
requirements to assigned guidance