--- title: "NIST NVD API Integration" slug: "nist-nvd-api" updated: 2026-11-15T06:41:03Z published: 2026-11-15T06:41:03Z canonical: "docs.hunters.ai/nist-nvd-api" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.hunters.ai/llms.txt > Use this file to discover all available pages before exploring further. # NIST NVD API Integration ## TL;DR | Supported data types | 3rd party detection | Hunters detection | IOC search | Search | Table name | Log format | Collection method | | --- | --- | --- | --- | --- | --- | --- | --- | | NIST NVD CVE Vulnerabilities | | | | ✅ | `nist_nvd_cves` | JSON | S3, GCP Bucket List, Azure Block Storage List | ## Overview The National Vulnerability Database (NVD), maintained by NIST, is the U.S. government's repository of standards-based vulnerability management data, most notably the Common Vulnerabilities and Exposures (CVE) catalog. The NVD API is polled on a schedule to retrieve newly published or modified CVE records, each containing the CVE identifier, publication/modification timestamps, status, textual description, affected vendor/product/version data, CVSS metrics and severity scores, CWE weakness classifications, and external references. Integrating NVD CVE data with Hunters provides authoritative, structured vulnerability intelligence that security teams can correlate against their asset inventory to drive vulnerability management, patch prioritization, and risk scoring based on CVSS severity and exploitability. ## Supported data types ### NIST NVD CVE Vulnerabilities **Table name:** `nist_nvd_cves` This data type contains CVE records retrieved from the NVD API, including the CVE identifier, publication and last-modified timestamps, vulnerability status, textual description, affected vendor/product/version information, CVSS v3.1/v4.0 metrics, SSVC decision data, CWE weakness classifications, and external references. It enables security teams to track newly disclosed or updated vulnerabilities and correlate them against their own asset and software inventory for risk-based prioritization. **Expected format** Logs are expected in JSON format. `{"host":"host-a1b2c3","source":"https://services.nvd.nist.gov/rest/json/cves/2.0","_raw":"{\"cve\":{\"id\":\"CVE-2026-117474\",\"sourceIdentifier\":\"security@example.com\",\"published\":\"2026-11-12T10:17:28.020\",\"lastModified\":\"2026-11-12T10:17:28.020\",\"vulnStatus\":\"Rejected\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"Rejected reason: none\"}],\"metrics\":{},\"references\":[]}}","cve":{"id":"CVE-2026-117474","sourceIdentifier":"security@example.com","published":"2026-11-12T10:17:28.020","lastModified":"2026-11-12T10:17:28.020","vulnStatus":"Rejected","cveTags":[],"descriptions":[{"lang":"en","value":"Rejected reason: none"}],"metrics":{},"references":[]},"_time":1794478648.02,"cribl_breaker":"nist_cve:nist_vulnerabilities","cribl_pipe":"passthru"}` ## Send data to Hunters Hunters supports the collection of NIST NVD logs using S3 List, S3 Notifications, GCP Bucket List, and Azure Block Storage List. **To connect NIST NVD logs:** ### Connect using S3 List or S3 Notifications 1. Route NIST NVD logs into an AWS S3 bucket. 2. Once logs are in S3, follow the steps in [this section](https://docs.hunters.ai/docs/connect-data-through-aws-s3). ### Connect using Azure Block Storage List 1. Route NIST NVD logs into an Azure Storage container as block blobs. 2. Once logs are in the container, follow the steps in [this section](https://docs.hunters.ai/docs/connect-data-through-azure-storage). ### Connect using GCP Bucket List 1. Route NIST NVD logs into a Google Cloud Storage bucket. 2. Once logs are in the bucket, follow the steps in [this section](https://docs.hunters.ai/docs/connect-data-through-gcp).