Using Scout with Intelligence
When Intelligence is on for your organization, Scout can read the same intel you see in the Intelligence tabs: your shared and private feeds, your watch lists, your watchers and your coverage. Ask it in plain language, for example "Have we seen 185.220.101.4?" or "Which threats matter most to us, and what don't we cover?".
Scout's Intelligence tools are part of Intelligence, which is in beta. Access is by request, so they may not be enabled for your organization. When Intelligence is off, Scout doesn't have them.
What Scout can look up
| Ask about | What Scout does |
|---|---|
| Indicators | Looks up IPs, domains, URLs, hashes and emails (up to 50 at a time) in your intel and in public sources, and says whether each was sighted in your environment. It can also search your indicators by actor, malware, feed or type, and list where they were seen: the host or user that saw each value, the log source, and the hunt it opened. Ask "Which host talked to 193.233.20.122?" and Scout names the host, the source and the hunt. |
| Threat context | Explains a threat actor, malware family or campaign: what it is, its ATT&CK techniques, and your known exploited vulnerabilities. |
| Relevance | Lists the threats most relevant to your organization, with their badges (Seen, Vulnerable, Targeted, Gap), the reasons behind them and the techniques you don't cover yet. |
| Watchers and coverage | Finds the watchers that cover a technique, reports a watcher's health, and summarizes your ATT&CK coverage. |
| Feeds | Reports feed health and the Intelligence overview. |
Answers show as compact cards in the chat. Each card links to the matching Intelligence page, such as the indicator or the threat.
Scout only reads intel your organization can see. It follows your TLP markings: TLP:RED values are never sent to outside services such as web search or external enrichment. Text that comes from a feed is treated as data, never as instructions.
What Scout can propose
Scout can suggest a change, but it can't make one. When it proposes one of these, the chat shows a card with Confirm and Cancel, and nothing happens until someone selects Confirm:
- Create watch list or Add to watch list: watch for a set of values from now on. See Watch lists.
- Start look back: search your stored telemetry for indicators over a past window. See Look back. Once confirmed, the card shows the look back's progress in place, and See sightings opens the indicators seen in your environment.
- Save watcher: keep a watcher Scout drafted as a Sigma rule and tested. It's created in Shadow and enters its rollout. It's never switched straight to On.
- Propose response action: a response action on a managed endpoint where an indicator was sighted. As with Respond… on a sighting, it still needs a second person to approve it in the hunt. See Respond to a sighting.
Confirming needs permission to manage watchers in the organization.
Threat briefings
When a threat becomes relevant to your organization, Scout can write you a short briefing: what the threat is, why it matters to you (the products it targets, the vulnerabilities you own, sighted indicators and uncovered techniques) and what to do next.
Briefings are off by default. They need Scout's threat briefings to be enabled for your deployment and the Threat relevant to your environment watcher to be on for your organization. You get at most one briefing for each threat each week.
A briefing is not a page of its own and has no navigation entry. It arrives as an insight marked Scout briefing in Activity (under Insights), and in the daily digest. On Pulse, the Relevant threats card, which replaced the earlier briefings card, lists the same threats with Hunt this or Open hunt. To see which threats reach you right now, use Relevant threats on the Intelligence Overview.