See Intercept in Use

Where is our risk today, and what do I fix first?

One Intercept Score across every repository, with the grade and trend

Open findings by severity, and by stack: code, packages, containers, pipelines, IaC

Top Risks ranks repositories by weighted exposure — start at the top

The repository's posture at a glance: GitHub security features, counts by severity and ecosystem

Every finding for this repo in one list — filter to what matters

Pick a critical finding and decide: fix, accept, or mark false positive

Full context: what it is, where it lives, how to fix it

A new CVE drops — are we affected, where, and how do we fix it?

Live feed from NVD, OSV, GitHub Advisories and CISA KEV — matched against our actual inventory

Confirmed Affected: CVEs that match a package version we really ship

Severity and CISA KEV status — is it being exploited in the wild?

Your Exposure: every affected repository — and developer machine — carrying the vulnerable version

The fixed version and remediation guidance, ready to hand to the owning team

Blast radius: search the whole SBOM for the affected package

Expand any package: every repository and version using it, in one place

Search the vulnerable package and see exactly which repos ship it

Package detail: vulnerable range, fixed version, affected repositories and the upgrade path

Triage a vulnerability across every repository in one move

Findings are grouped by CVE across the whole fleet

Expand a group to see every repository it hits

Verify before you decide: affected component, vulnerable range and fixed version

Multi-select, then categorize across all affected repos at once

Each decision is recorded with a reason, an expiry and an audit trail

What does our build chain trust, and what could be hijacked?

Every pipeline across GitHub Actions, Azure Pipelines, GitLab and CircleCI — tagged by what it does. Jenkins pipelines are inventoried too

Full stage → job → step structure, straight from the file

Third-party Actions — verified vs unverified publishers

Unpinned Actions: a tag can be moved to malicious code. Pin these to a commit SHA

Base images across all Dockerfiles — find stale or untrusted images

Containers running as root

Platform posture: branch protection, code review, token permissions — plus OpenSSF Scorecard checks for public repositories

Show the auditor where we stand on SSDF, SLSA and Scorecard

SSDF (NIST SP 800-218) and SLSA controls mapped to real evidence from the scans

Every repository graded — drill into the weakest

Control-by-control gap analysis with evidence

Compensating control? Record an override with justification

Each gap links to a step-by-step fix guide

And for leadership: a one-click Executive Report

Are we fixing things fast enough?

Fix velocity, SLA compliance and the repo leaderboard

Everything past its SLA — who owns it and how late it is

Accepted risks expire — see what lapses soon and needs re-review

Assign findings to an owner

What's on our engineers' laptops — IDEs, extensions, AI tools?

The Posture Agent reports each machine's tooling — fleet-wide distribution here

Per machine: disk encryption, firewall, IDE extensions, AI tools, package managers

AI-BOM: which repositories use which LLM SDKs, models and AI services

Understand an unfamiliar repo and get a prioritized plan

AI Insights: business purpose, architecture, security posture and threat model

AI Advisors: six domain specialists, plus an AI application security specialist when the repo uses AI, and a Lead Advisor that turns findings into an action plan

Bring it into the IDE: Intercept MCP server and Claude Code plugin — triage and fix findings from the editor

The tour opens on the public pricing page: Starter, Team, and Business plans priced per active developer, an Enterprise option, and the list of what every plan includes.

It continues through the security and legal pages, including the privacy policy, and ends on account creation, where you can sign up with email or continue with GitHub.

The dashboard leads with the Intercept Score and grade, then breaks open findings down by severity and by stack: code, secrets, packages, containers, pipelines, and infrastructure.

Below that are the top-risk repositories, trend charts over time, and an inventory of the developer tools in use.

The repositories list shows every connected repository with its risk level, and severity filter tabs narrow it down.

Global search finds repositories, findings, and packages from anywhere in the app.

Opening a repository walks through the tabs that describe what it's built from: Files, Platform, Code, Dependencies, AI-BOM, Containers, Pipelines, and Infrastructure.

Each tab lists what was detected in that layer, along with the findings for it.

The repository's security tabs come next: Vulnerabilities, Compliance, AI Insights with its threat model, and AI Advisors.

The AI Advisors write-ups explain how individual findings could chain into an attack, and rank what to fix first.

The Vulnerabilities page shows findings across all repositories, split into tabs by type and grouped by CVE or rule.

Several findings are selected and categorized together in one bulk action.

The Code view breaks repositories down by language. The Packages view lists the full SBOM, with every package and the repositories that use it.

Opening a CVE shows its detail, the affected repositories, and a preview of the lockfile where the vulnerable version is pinned.

Containers lists base images across every Dockerfile and drills into a single Dockerfile, including images that run as root.

Pipelines shows a table of GitHub Actions that aren't pinned to a commit SHA, followed by the infrastructure-as-code findings.

The Platform page shows repository and organization posture checks, with counts of passing, failing, and warning checks.

Results are grouped into configuration, supply chain, repository assessment, and OpenSSF Scorecard checks, which apply to public repositories.

Threat Intel shows the advisory sources being monitored and a timeline of new advisories by severity.

Opening a CVE shows its detail and the repositories confirmed affected, with the evidence behind each match.

Compliance maps repositories to SSDF and SLSA controls based on scan evidence, and an A to F filter narrows the list by grade.

Opening a repository shows its controls one by one, and an override records a compensating control with a justification.

The Remediations dashboard shows fix velocity, SLA compliance, and a repository leaderboard.

Below it is the full list of remediations, including accepted risks that will soon expire.

Developers lists the people committing to your repositories and the machines enrolled through the Posture Agent.

A machine detail view shows its security settings and installed tooling. The AI inventory shows which AI tools and models each repository uses.

Learn has step-by-step guides for hardening repositories, pipelines, and AI coding tools, shown here with the guide to setting up branch protection.

Settings covers General, Team, Integrations, AI Provider, Schedules, a grid of scanners, Security, API keys, Agent enrollment, MCP, Alerts, Export, Billing, and the audit log.

The tour ends on the setup checklist, with every step complete.