Recorded Future
Overview
The Recorded Future integration connects the Praetorian Guard Platform (PGP) with Recorded Future's threat intelligence platform, importing vulnerability risk scores, threat context, and exposure indicators into your attack surface view. Recorded Future collects and analyzes data from open, dark, and technical sources to deliver real-time intelligence on vulnerabilities, threat actors, and indicators of compromise.
By connecting Recorded Future to PGP, you enrich your existing asset and vulnerability data with external threat intelligence. PGP uses Recorded Future's risk scores and threat context to help prioritize which vulnerabilities represent the highest real-world risk, factoring in active exploitation, threat actor interest, and exposure on the dark web alongside your own attack surface data.
This integration operates in a read-only capacity. PGP queries the Recorded Future API to retrieve threat intelligence data but never modifies any data, configurations, or alert rules in your Recorded Future account.
---
What the Integration Does
When enabled, PGP connects to the Recorded Future Connect API and performs the following:
Vulnerability intelligence -- Retrieves risk scores and threat context for CVEs that are relevant to your attack surface, including exploitation evidence and trending threat data.
Risk enrichment -- Augments existing PGP risks with Recorded Future risk scores, risk rules triggered, and evidence summaries to provide deeper prioritization context.
Exposure indicators -- Imports indicators of exposure such as mentions of your organization's assets in paste sites, dark web forums, and underground marketplaces.
Threat context -- Associates threat actor and malware intelligence with vulnerabilities found in your environment, helping you understand who is exploiting what.
All data flows one direction: from Recorded Future into PGP. Threat intelligence enriches your existing PGP assets and risks with additional context for prioritization.
---
Prerequisites
Before setting up the integration, ensure you have:
An active Recorded Future subscription with API access enabled
A Recorded Future API token with read permissions
Access to the relevant Recorded Future modules (Vulnerability Intelligence, Threat Intelligence) based on your subscription tier
Generating an API Token
Log in to the Recorded Future Portal at
https://app.recordedfuture.comNavigate to User Settings > API Access
Click Generate New API Token
Name the token (e.g.,
PGP Integration) and copy the generated tokenStore the token securely -- it will not be displayed again
---
Setup
In PGP, go to Integrations and locate Recorded Future (under Threat Intelligence)
Enter the required credentials
Click Connect -- PGP will validate the API token before saving
Field Reference
Once connected, PGP will begin syncing threat intelligence data on its regular integration schedule.
---
What Data Is Synced
Vulnerability Risk Scores
Risk scores for CVEs found in your PGP environment are imported from Recorded Future.
Threat Context
Threat actor and malware associations linked to vulnerabilities in your environment.
Exposure Indicators
External exposure signals related to your organization's assets.
---
API Endpoints Used
PGP uses the Recorded Future Connect API v2. All requests use token-based authentication and are read-only (GET).
All API requests include the X-RFToken header for authentication.
---
Troubleshooting
---
Security and Data Handling
Read-only access -- PGP only performs GET requests against the Recorded Future API. It never creates, modifies, or deletes any data in your Recorded Future account.
Credential storage -- Your Recorded Future API token is encrypted at rest and never exposed in logs or API responses.
Token-based authentication -- The API token is sent via the
X-RFTokenheader over HTTPS for all requests.Data residency -- Imported threat intelligence data is stored within your PGP tenant and subject to your organization's data retention policies.
Minimal permissions -- Only read-level API access is required. We recommend creating a dedicated API token for the PGP integration.