---
title: "Threat Intelligence for Threat Modeling | Clearly AI"
description: "Threat models that know about today's attacks. Clearly AI applies threat intelligence feeds to every review and flags past reviews a new threat affects."
canonical: https://clearly-ai.com/platform/threat-intelligence
---

_Threat intelligence · Coming soon_

# Threat models that know about today's attacks

Clearly AI applies the threat intelligence feeds you trust to every threat model that it runs, so findings cover attacks published last week as well as the ones your reviewer already knows about. When a new threat lands, Clearly AI also revisits your past reviews and shows you what changed.

- [Contact Enterprise Sales](https://clearly-ai.com/demo)

- HID
- Ericsson
- PayPal
- Modern Health
- Hagerty
- Rivian
- Infineon
- Bastion

## A threat model is a snapshot. Attackers keep moving.

Most threat models are only as current as the person who wrote them. They reflect the attacks and techniques your reviewer knew about on the day of the review. Then something new gets published like a compromised update channel, a poisoned package, or a new way to pull tokens out of a browser extension. The review you signed off on last quarter doesn't know it now exists.

Finding out what's exposed is manual. Someone reads the advisory, tries to remember which products use the affected component, digs up the old reviews, and redoes the analysis by hand. With more shipping every week, and AI-generated code adding to it, most teams can't keep up. The old reviews stay signed, and nobody goes back to them.

## How threat intelligence works in Clearly AI

### 01: Choose the sources you trust

Subscribe to threat intelligence feeds as sources of truth for your reviews. Start with curated feeds like CVE and CWE, CISA Cybersecurity Alerts, Zero Day Initiative, and VulNow PreCVE, which flags likely open source vulnerabilities before a CVE is published. Add vendor feeds like Cisco Security, the Microsoft Security Response Center, and Red Hat Security Advisories. Subscribe to custom sources like Krebs on Security, and bring in your own internal intelligence. Turn each feed on or off in one place.

- **Curated feeds:** CVE & CWE (on), VulNow PreCVE (off), CISA Cybersecurity Alerts (on), Zero Day Initiative (off)
- **Vendor feeds:** Cisco Security (on), Microsoft Security Response Center (on), Red Hat Security Advisories (off)
- **Custom feeds:** Internal threat intelligence (on), Krebs on Security (off)

### 02: Apply current threats to every threat model

When Clearly AI runs a threat model, it maps the system's attack surfaces, from components and integrations to auth flows and dependency versions, against your threat intelligence library. Relevant threats appear as findings alongside the rest of the review, with the intelligence source cited.

### 03: Look back when a new threat lands

When new intelligence arrives, Clearly AI checks it against the systems you've already reviewed and re-reviews the ones it affects without a manual trigger required. Clearly AI automatically runs targeted re-reviews where the threat applies, flags significant new risks, and shows what changed since the original review. A lookback can also start a workflow, so a risk increase opens a Jira ticket and/or posts to Slack on its own.

### 04: See why every threat was, or wasn't, included

Ask about any threat and get an answer with the evidence behind it.

**Project Acme Desktop**

**Attack surfaces:**
- Desktop application
- Browser Extension
- Encrypted token storage
- Cloud secrets manager
- Automatic update channel (updater-lib 6.8.9)
- OAuth sign-in (oauth-client 6.0.3)

**Match to threats**

**Threat Intelligence Library**

**Threat Model**

**Low · High**

## Find every past review a new threat touches

When a new attack vector is disclosed, the first question is where you're exposed. Clearly AI answers it from the reviews you've already run.

Every review captures the system's attack surfaces, down to the component and version. When a new threat arrives in one of your feeds, Clearly AI checks it against all of them, re-reviews only the systems where it applies, and flags the ones where risk went up. Each re-review shows what changed since the original, so your reviewer can confirm the new findings and sign.

A lookback can also start a workflow that opens Jira tickets for new high-risk findings or notifies owners in Slack.

[See how workflows route review results](https://clearly-ai.com/platform/workflows)

![Clearly AI checks Project Acme Desktop's attack surfaces against a new vendor advisory, an update signature bypass in updater-lib before 7.0. The automatic update channel runs updater-lib 6.8.9, so it matches, and its risk changed from Medium to High since the original review.](https://clearly-ai.com/threat-intelligence/figma/lookback-diagram-v2.svg)

## Ask why a threat is, or isn't, in your threat model

A threat model you can't explain is hard to defend. For every threat, included or missing, Clearly AI explains itself:

- **Where it came from.** The feed and intelligence entry behind the finding.
- **Why it applies.** The attack surface and project context that matched.
- **Whether the source was on.** If a relevant feed was disabled, you'll know.
- **Whether there was enough context.** If the project was missing the information needed to match a threat, Clearly AI flags the gap.
- **Whether a signal was missed.** If the information was available and the threat still wasn't matched, that's surfaced too.

That gives your reviewers something to challenge, and your auditors a clear record of why the threat model says what it says.

Learn how Clearly AI keeps findings traceable

![A Clearly AI threat model finding opened from the findings list, with its cited source, reasoning, review history and the Publish to Risk Registry action.](https://clearly-ai.com/home/figma/findings-animation-still-v4.webp)

## Part of the threat model your team already approves

A feed tells you a threat exists. Clearly AI tells you which of your systems it affects and why, inside the review your team already works from.

- **Matches the design as well as the dependencies.** Matching uses design docs, tickets, and code, so an auth flow or trust boundary can match a threat even when no package version does.
- **Your intelligence counts.** Internal feeds, like incident learnings or red team findings, apply to reviews alongside public and vendor sources.
- **Findings stay sourced.** Every threat-driven finding cites the intelligence it came from, the same way every other Clearly AI finding cites its document, ticket, or code.
- **One queue.** Threat-driven findings appear in the threat model with everything else, and lookback results route through the same workflows as every other review.

## What Clearly AI customers are seeing today

- **100%** of new features triaged and threat modeled
- **85%** of assessment portions automated
- **~90%** reduction in time per review

> Weeks to minutes, literally.
>
> — William Brown, Sr. Director of Product Security and Privacy, HID Global

[Read the HID Global story](https://clearly-ai.com/customer-stories/hid-global)

![HID Global team in a modern office lobby.](https://clearly-ai.com/threat-intelligence/figma/hid-team.png)

_FAQ_

## Answers to your top questions

### What is threat intelligence in threat modeling?

It's the practice of applying current information about real attacks, techniques, and vulnerable components to a threat model, so the model reflects today's threat landscape instead of only a static framework. In Clearly AI, threat intelligence feeds are matched against each system's attack surfaces during a review, and relevant threats appear as sourced findings.

### What threat intelligence sources does Clearly AI support?

Clearly AI supports four kinds of feeds. Curated feeds include CVE and CWE, CISA Cybersecurity Alerts, Zero Day Initiative, and VulNow PreCVE for early warning on open source vulnerabilities before a CVE is published. Vendor feeds include Cisco Security, the Microsoft Security Response Center, and Red Hat Security Advisories. You can also subscribe to custom feeds, like Krebs on Security, and add your organization's internal intelligence. Each feed can be turned on or off.

### How does Clearly AI know whether a new threat affects a past review?

Every review captures the system's attack surfaces, like components, integrations, auth flows, and dependency versions. When new intelligence arrives in one of your feeds, Clearly AI maps it to those attack surfaces across your reviewed portfolio and runs targeted re-reviews where it applies. Each re-review shows what changed since the original.

### Can a new threat automatically open Jira tickets?

Yes. A lookback can trigger a Clearly AI workflow, which can open Jira tickets for new high-risk findings, post to Slack, and route results to the other tools your team uses.

[Learn more about workflows](https://clearly-ai.com/platform/workflows)

### Does Clearly AI re-run every review when a new threat is published?

No. Clearly AI only re-reviews the systems where the new threat maps to an attack surface. That keeps the lookback focused on real exposure and keeps your reviewers' queue short.

### Is this continuous monitoring?

No. Clearly AI doesn't monitor your systems, networks, or dashboards. It checks the threat intelligence feeds you subscribe to for new entries. When a new threat arrives, Clearly AI maps it to your past reviews and runs a point-in-time, targeted re-review where it applies.

### Can I see why a threat wasn't included in a threat model?

Yes. Clearly AI explains both included and missing threats: where a threat came from, why it applied, whether the relevant source was enabled, whether the project had enough context, and whether an available signal was missed.

### Can we add our own internal threat intelligence?

Yes. Internal feeds, like incident learnings or red team findings, can be added as sources and applied to your reviews alongside curated and vendor feeds. Clearly AI never trains on customer data.

See trust and security

### When is threat intelligence available?

Threat intelligence is coming soon. Get a demo to see it in action and join the early access list.

## Learn more

- [Secure everything that ships](https://clearly-ai.com)
- [We built the tool we wished we had](https://clearly-ai.com/about-us)
- [One platform. From intake to remediation.](https://clearly-ai.com/platform)
- [Know everything that needs a review. Skip the 300-question form.](https://clearly-ai.com/platform/security-intake)
- [Ask only what matters. Get it right the first time.](https://clearly-ai.com/platform/conversational-intake)
- [Every finding, tracked to a decision](https://clearly-ai.com/platform/resolve/risk-registry)
- [Show leadership and auditors exactly what security reviewed](https://clearly-ai.com/platform/resolve/reporting)
- [Security reviews you can stand behind, every time](https://clearly-ai.com/platform/quality)
- [Threat models built from the tools you already use](https://clearly-ai.com/integrations)
- [Threat models that know about today's attacks](https://clearly-ai.com/platform/threat-intelligence)
- [Automate every step around the review](https://clearly-ai.com/platform/workflows)
- [Threat models your teams can work on together](https://clearly-ai.com/platform/collaboration)
- [Understand the system before the review starts](https://clearly-ai.com/platform/enterprise-context-graph)
- [Trust, security, and deployment](https://clearly-ai.com/platform/trust-security-and-deployment)
- [Every plan reviewed. Every risky change threat modeled.](https://clearly-ai.com/platform/ide-and-mcp)
- [Verify what actually shipped](https://clearly-ai.com/platform/control-and-remediation-verification)
- [A current threat model for everything that ships](https://clearly-ai.com/solutions/continuous-threat-modeling)
- [Prove every product that ships meets your security bar](https://clearly-ai.com/solutions/product-security-assurance)
- [Privacy reviews your team can stake decisions on](https://clearly-ai.com/solutions/privacy)
- [Every vendor reviewed against your standards](https://clearly-ai.com/solutions/third-party-risk)
- [Review every design before it's built](https://clearly-ai.com/solutions/design-and-architecture-reviews)
- [Secure the AI you build, buy, and code with](https://clearly-ai.com/solutions/ai-agentic-security)
- [Every regulation you answer to. One review process.](https://clearly-ai.com/solutions/compliance)
- [Every product ready for the Cyber Resilience Act without growing your team](https://clearly-ai.com/solutions/compliance/cyber-resilience-act)
- [Build vs. buy for security review automation](https://clearly-ai.com/compare/claude-chatgpt)
- [The ThreatModeler alternative built from your own docs, code, and policies](https://clearly-ai.com/compare/threatmodeler)
- [The Clover Security alternative with findings your team can trust](https://clearly-ai.com/compare/clover)
- [The Prime Security alternative for every review your team runs](https://clearly-ai.com/compare/prime)
- [Security and Privacy](https://clearly-ai.com/trust/security-privacy)
- [Clearly AI Privacy Policy](https://clearly-ai.com/trust/privacy-policy)
- [Clearly AI Subprocessors](https://clearly-ai.com/trust/subprocessors)
- [AI Risk Reviews](https://clearly-ai.com/use-cases/ai-risk-reviews)
- [Automate Triage](https://clearly-ai.com/use-cases/automate-triage)
- [Privacy Impact Assessments](https://clearly-ai.com/use-cases/privacy-impact)
- [Vendor Risk Assessments](https://clearly-ai.com/use-cases/vendor-risk)
- [Threat Modeling](https://clearly-ai.com/use-cases/threat-modeling)
- [Contact](https://clearly-ai.com/contact)
- [Contact Enterprise Sales](https://clearly-ai.com/demo)
- [Latest from the Clearly AI blog](https://clearly-ai.com/blog)
- [In the news](https://clearly-ai.com/press)
- [How Ericsson Enterprise Wireless Solutions cut review times by up to 80%](https://clearly-ai.com/customer-stories/ericsson)
- [How HID Global reviews 300+ products for the Radio Equipment Directive with the team it already has](https://clearly-ai.com/customer-stories/hid-global)
- [How Rivian scaled privacy and AI governance reviews 4x without adding headcount](https://clearly-ai.com/customer-stories/rivian)
- [Part 2! Okay, privacy is different from security. Now what?](https://clearly-ai.com/blog/part-2-okay-privacy-is-different-from-security-now-what)
- [How AI is rewiring our product engineering workflow](https://clearly-ai.com/blog/how-ai-is-rewiring-our-product-engineering-workflow)
- [Good Data Scientists and Bad Outcomes, Part 1: What's the difference between security and privacy work?](https://clearly-ai.com/blog/good-data-scientists-and-bad-outcomes-what-s-the-difference-between-security-and-privacy-work)
- [Why I Joined Clearly AI](https://clearly-ai.com/blog/why-vp-marketing-joined-clearly-ai)
- [Skip the Marketing: Clearly AI for Technical People](https://clearly-ai.com/blog/clearly-ai-technical-explanation)
- [Clearly AI Raises $8.4M Seed Round to Scale Product Security](https://clearly-ai.com/blog/seed-round)
- [Why We Started Clearly AI](https://clearly-ai.com/blog/why-we-started-clearly-ai)
- [Applying AI to Threat Modeling - Where AI Thrives, Survives, and Dies](https://clearly-ai.com/blog/applying-ai-to-threat-modeling)
- [Why We Build in Public](https://clearly-ai.com/blog/why-we-build-in-public)
- [Solving the Threat Modeling Bottleneck with AI Workflows](https://clearly-ai.com/blog/solving-the-threat-modeling-bottleneck-with-ai-workflows)
- [Clearly AI Named Finalist in the 2025 Okta Startup Challenge](https://clearly-ai.com/blog/clearly-ai-named-finalist-in-the-2025-okta-startup-challenge)
- [Security, SOC 2, & Startups](https://clearly-ai.com/blog/security-soc-2-startups)
- [Building Reliable AI Systems for Security and Privacy Reviews](https://clearly-ai.com/blog/building-reliable-ai-systems-for-security-and-privacy-reviews)
- [How to Automate Security and Privacy Reviews with Clearly AI](https://clearly-ai.com/blog/how-to-automate-security-and-privacy-reviews-with-clearly-ai)
- [One Year of Clearly AI](https://clearly-ai.com/blog/one-year-of-clearly-ai)
- [Navigating EU RED Compliance: Meeting the August 2025 Deadline](https://clearly-ai.com/blog/navigating-eu-red-compliance-meeting-the-august-2025-deadline)
- [The AI Engineer Cheat Sheet](https://clearly-ai.com/blog/the-ai-engineer-cheat-sheet)
- [Intelligent Vendor Risk Assessments](https://clearly-ai.com/blog/intelligent-vendor-risk-assessments)
- [Clearly AI wins the AWS Bedrock Builder's Challenge](https://clearly-ai.com/blog/clearly-ai-wins-the-aws-bedrock-builder-s-challenge)
- [Reviews, reviews, reviews!](https://clearly-ai.com/blog/reviews-reviews-reviews)
- [Halfway through YC](https://clearly-ai.com/blog/halfway-through-yc)
- [llms.txt — site overview for LLMs](https://clearly-ai.com/llms.txt)
- [llms-full.txt — full site content for LLMs](https://clearly-ai.com/llms-full.txt)
- [sitemap.xml — all public routes](https://clearly-ai.com/sitemap.xml)
- [Documentation](https://docs.clearly-ai.com/docs)

[Canonical page](https://clearly-ai.com/platform/threat-intelligence)