← Security

Data sources and attribution

ExposureIQ connects public security intelligence with the technology we observe on your external footprint. This page lists every third-party source we use, what we take from it, and the acknowledgement each is owed. We use official feeds and APIs only; we do not scrape pages, and where a source is a news or blog feed we keep only the title, a short excerpt and a link back to the original.

  • The relevance levels, confidence scores and explanations you see are ExposureIQ's own assessment built from these sources. They are not statements by the publishers.
  • No publisher listed here endorses, certifies or is affiliated with ExposureIQ. Product and company names belong to their owners.
  • A source's data can be incomplete or out of date. Each item shows which sources reported it and when; follow the link to the original for the authoritative version.
  • National Vulnerability Database (NVD)

    NIST

    What we use: Vulnerability descriptions, CVSS severity scores, references and affected-version data for each CVE.

    This product uses data from the NVD API. It is not endorsed or certified by NIST or the NVD.

    Terms: NVD developer terms

  • Known Exploited Vulnerabilities (KEV) Catalog

    CISA

    What we use: Which vulnerabilities are confirmed as exploited in the wild, with CISA's required-action guidance.

    Source: CISA Known Exploited Vulnerabilities Catalog. ExposureIQ is not affiliated with, endorsed by or certified by CISA.

    Terms: KEV catalog

  • Cybersecurity Advisories

    CISA

    What we use: Advisory titles, short excerpts and links back to the original advisory.

    Advisory titles and short excerpts are from CISA, with a link to the original. ExposureIQ is not affiliated with, endorsed by or certified by CISA.

    Terms: CISA advisories

  • Exploit Prediction Scoring System (EPSS)

    FIRST.org

    What we use: A statistical estimate of the likelihood that a vulnerability will see exploitation activity. Shown as context only; it never changes a relevance level and is not evidence of exploitation.

    EPSS scores are provided by FIRST.org. ExposureIQ is not affiliated with, endorsed by or certified by FIRST.

    Terms: EPSS

  • GitHub Advisory Database

    GitHub, Inc.

    What we use: Advisory text, severity and the affected packages with their vulnerable version ranges, including the advisories that report a package as malicious (malware advisories).

    Contains data from the GitHub Advisory Database, licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). ExposureIQ summarises and combines this data with other sources; it has not been reviewed or endorsed by GitHub.

    Terms: CC BY 4.0

  • OSV.dev

    Google Open Source Security Team and contributing databases

    What we use: Open-source package vulnerability records for the JavaScript libraries ExposureIQ can detect, and, only for packages an organization has explicitly allowed to be looked up, advisories for those package names (the name and ecosystem are sent; never a version or an organization).

    Records are provided through OSV.dev. Each record remains under the licence of the database it comes from (for example CC BY 4.0). ExposureIQ is not affiliated with or endorsed by Google or the contributing databases.

    Terms: OSV data licences

  • Microsoft Security Update Guide

    Microsoft Security Response Center

    What we use: Vulnerability titles, severity and affected-product information for Microsoft products.

    Microsoft and its product names are trademarks of the Microsoft group of companies. ExposureIQ is not affiliated with, endorsed by or certified by Microsoft.

    Terms: Microsoft terms of use

  • Cisco Security Advisories

    Cisco Systems, Inc.

    What we use: Advisory titles, summaries, affected releases and any exploitation Cisco states, for Cisco products.

    Cisco and the Cisco logo are trademarks of Cisco Systems, Inc. ExposureIQ is not affiliated with, endorsed by or certified by Cisco.

    Terms: Cisco terms of use

  • NCSC News and Advisories

    UK National Cyber Security Centre

    What we use: Publication titles, short excerpts and links back to the original.

    Contains public sector information licensed under the Open Government Licence v3.0. ExposureIQ is not affiliated with, endorsed by or certified by the NCSC.

    Terms: Open Government Licence v3.0

  • Microsoft Security Blog

    Microsoft

    What we use: Titles, short excerpts and links back to the original post. The full article is not copied.

    Titles and short excerpts are from the Microsoft Security Blog feed and belong to Microsoft. Read the full post at the source.

    Terms: Microsoft terms of use

  • The Hacker News

    The Hacker News

    What we use: Titles, short excerpts and links back to the original article. The full article is not copied.

    Titles and short excerpts are from The Hacker News feed and belong to their publisher. Read the full article at the source.

    Terms: The Hacker News

  • Certificate Transparency search

    SSLMate (Cert Spotter) and Sectigo (crt.sh)

    What we use: Public certificate names for domains you have confirmed you are authorized to assess, to discover subdomains and names that share a certificate with your domain.

    Certificate Transparency data is searched through Cert Spotter (SSLMate) and crt.sh (Sectigo). Only the public domain name being assessed is sent. Names that merely share a certificate are shown as observed related and are never presented as owned by you.

    Terms: SSLMate terms

  • MITRE ATT&CK®

    The MITRE Corporation

    What we use: Reference information about named threat groups and the techniques ATT&CK lists for them, shown only where a report names the group.

    MITRE ATT&CK® is a registered trademark of The MITRE Corporation. © The MITRE Corporation. ATT&CK data is used under MITRE's Terms of Use (https://attack.mitre.org/resources/terms-of-use/). ExposureIQ is not affiliated with or endorsed by MITRE.

    Terms: ATT&CK terms of use

  • CERT-In advisories and vulnerability notes (manual import)

    Indian Computer Emergency Response Team (CERT-In), Ministry of Electronics and Information Technology

    What we use: Advisories and vulnerability notes that an ExposureIQ operator has entered by hand from the original page, each with a link back to it. Nothing is fetched automatically, because CERT-In publishes no feed or reuse terms that we could find.

    CERT-In advisories are summarised by ExposureIQ with a link to the original. ExposureIQ is not affiliated with or endorsed by CERT-In.

    Terms: CERT-In website (no reuse terms found)

  • CVE Program records (CVE JSON 5)

    The CVE Program (MITRE and CISA) and the CVE Numbering Authorities that publish each record

    What we use: The affected-version ranges and unaffected versions a vendor publishes in its own CVE record, and CISA's SSVC decision points. Used to fill version ranges that NVD has not published, and always shown as vendor-reported. A list of exact versions is never treated as proof that other versions are safe.

    CVE® is a registered trademark of The MITRE Corporation. CVE Records are used under the CVE Program Terms of Use. CISA's enrichment (the ADP container) is published by the Cybersecurity and Infrastructure Security Agency. ExposureIQ is not affiliated with or endorsed by MITRE, CISA or the CVE Program.

    Terms: CVE Program terms of use (not yet legally reviewed for this use)

  • Threat Watch (public Telegram channels)

    The channels' own operators (information_security_channel, thehackernews, VulnerabilityNews, PentestingNews, ctinow)

    What we use: Early-warning leads only: a short excerpt and a link to what the post points at. A post is never evidence; nothing reaches your dashboard, findings or alerts until it is corroborated by an authoritative record or by independent research publishers. Not shown to customers as posts.

    Early-warning leads are read from public Telegram channels and are never treated as evidence on their own. ExposureIQ is not affiliated with or endorsed by Telegram or the channel operators.

    Terms: Telegram terms of service (not yet legally reviewed for this use)

If you are a publisher and would like an acknowledgement changed, or a source removed, please contact us. See also the subprocessor list.