AI Blue · Module 2 · The Craft

Anticipate: Threat Intelligence and Exposure at Machine Speed

The lesson treats B1 Anticipate and the part of B2 Detect it feeds. Participants follow the five-stage pipeline from report to hypothesis, keep intelligence as code with STIX, TAXII and ATT&CK identifiers, join EPSS, the KEV catalogue and the EUVD with local asset context, learn the five characteristic faults of AI extraction, and design verification by grounding, sampling and seeded errors when sources may be written by adversaries.

Lesson 5 of 28Chapter 575 minutes

Read the chapterThe whitepaperThe slides

All courses / AI Blue / Module 2 / Chapter 5

Learning objectives

After the lesson the participant can:

Key concepts

Hypothesis
A statement about adversary behaviour that could be true in this estate and can be tested. An accepted hypothesis is routed to a detection requirement, a hunt, a patch priority or a recorded decision to do nothing, with the reason.
Grounding check
Every technique, indicator and claim in an extraction links to a quoted span of the source. A proposal without a span is rejected without further discussion.
The join
The B1 task of combining each vulnerability from the public feeds with local asset context, such as internet reachability, the data and business process carried and compensating controls, because the feeds know nothing about the organisation.
Seeded errors
Known errors inserted into a share of batches, such as an altered indicator, a neighbouring technique or an unsupported attribution, to measure whether review catches them. The routine seeds one in every batch of twenty proposals.
Conversion rate
The share of accepted hypotheses that reached a deployed detection, a completed hunt or a changed priority within 30 days, measured monthly and reported at team level.

Interactive exercises

Do them here and get feedback at once. Choose a card and then where it belongs, or drag it.

Interactive exercise 1 · Put in order

From report to routed hypothesis

Put the five stages of the chapter's intelligence pipeline in the order in which an item passes through them.

Interactive exercise 2 · Scenario

The hedge that became a statement

Apply the chapter's verification checks to an extraction proposed by an AI system.

Teaching plan

15 minTeacher walks the pipeline of Figure 5.1 using the record INTEL-HM-0142, pointing out the rejected attribution, the expiry on indicators and the routing to a hunt and a detection requirement.
10 minShort input on exposure: what KEV, EPSS and the EUVD each say, and why patch velocity is reported by median and 90th percentile.
15 minReview drill: pairs check a prepared extraction against its source text and find the seeded faults before the teacher reveals them.
25 minExercise: groups write the routine file and three intelligence requirements for their own organisation or for Nordvik Region.
10 minPlenary on hostile sources and the sharing duty: what may leave, who may release and under what handling.

Discussion

  1. The decision to accept a hypothesis is described as the one least suited to automation. What does your organisation know about itself that an extraction system would not have been told?
  2. Hansa Mutual's risk is that extraction outruns the engineering capacity to use it. How would you recognise a flood of accepted but unused hypotheses, and what would you change?
  3. A grounding check does not catch tampered provenance, because the quoted text is genuine. Which of the chapter's controls covers that hazard, and how strong is it?

Written exercise

Exercise · 25 minutes

A weekly intelligence-to-detection routine

Following the eight steps of the practical guide, write three to five intelligence requirements for your organisation, or for Nordvik Region, which has no intelligence analyst and consumes national CSIRT and sharing-group reporting. List the sources by tier with their handling rules. Specify the extraction at Level 1 Assisted with the grounding check on and no tools that act. Define the review meeting, the reviewer who differs from the analyst, the seeding of one error in every twenty proposals, the routing deadline and the monthly conversion measure. State how measures are reported at team level and when the routine is reviewed. For Nordvik, adapt the cadence to what the chapter calls realistic.

Deliverable: A routine specification with requirements, tiered sources, extraction level, review and seeding rules, routing options, conversion measure and review triggers.

Self-test

Choose an answer to see whether it is right, or open the answer below each question.

  1. Why does the extraction system in the chapter's pipeline hold no tools that act, such as updating a block list?

    Show the answer

    A. Because adversaries write some of what it reads, so a hostile document must end as no more than a bad proposal
    The chapter's controls for hostile sources do not depend on the model behaving well: at Level 1 Assisted the extractor writes a proposed record to a queue and cannot change any control.

  2. What does the EPSS feed provide, according to the chapter?

    Show the answer

    C. A probability that a published CVE will be exploited in the wild in the next 30 days
    EPSS estimates the likelihood of exploitation in the next 30 days; KEV says exploitation has happened, and the EUVD adds European coverage. None knows anything about the organisation.

  3. In the routine's defaults, what does the seeded-error catch rate control?

    Show the answer

    D. Whether the team may move from full review to sampled review
    The routine keeps full review until the catch rate is established, and the summary states that a catch rate that falls returns the team to full review.