Platform · Tech stack intelligence

Know what you run, and hear first when it becomes vulnerable

Tech stack intelligence identifies the software and versions behind your internet-facing assets and keeps checking them against newly published vulnerabilities. When a new CVE affects something you run, you get the context to decide fast: is it known to be exploited, how likely is exploitation, and is there public exploit code?

01 Fingerprinting

Fingerprinting you can trust

We identify technologies with 120+ hand-tuned signatures and 4,000+ community signatures, matching response headers, cookies, page content and generator tags.

Hand-tuned signatures carry higher confidence; community signatures widen coverage. Each detected technology is kept with its version, so new vulnerabilities can be matched as soon as they are published.

02 Context

The context behind every match

The context behind every match
SignalThe question it answers
CVE matchIs a published vulnerability associated with this product and version?
CISA KEVIs it known to be exploited in the wild?
EPSSHow likely is exploitation in the near term?
Exploit availabilityIs there public exploit code?
CVSSHow severe is it in principle?
03 Alerting

Alerts and notifications

  • New CVE matches

    An email alert when a newly published vulnerability matches a technology you run.

  • High and critical findings

    Sent to your team’s channel through a Slack or Discord webhook.

  • Critical escalations

    Immediate alerts when critical-severity exposure is confirmed.

  • Completion summaries

    A summary when a run or a mission completes.

  • Digests

    A weekly or monthly digest of open findings, trend and progress.

  • Exports and API

    CSV exports and API tokens to pull findings into your own tools.

04 The team's part

A version match is a lead, not a verdict

Backported fixes and custom builds can make a version match misleading. The team checks whether the affected component is actually exposed and whether a fix or mitigation applies, and labels the result Validated or Signal accordingly.

05 FAQ

Questions about tech stack intelligence

Can version matches be wrong?

Yes, which is why matches are reviewed and labelled for what they are rather than reported as confirmed vulnerabilities.

Which channels can receive alerts?

Email, Slack or Discord webhooks, and your own tools through the API.

How quickly do new vulnerabilities show up?

Technologies are re-checked continuously against newly published vulnerabilities, so a match appears once the vulnerability is published and enriched.

Find it before an attacker does.

Tell us what you need covered. We will reply from contact@northboundintelligence.com to arrange a scoping call.

Facts on this page verified 11 November 2026.