## Information A valid API Token for XSOAR from Recorded Future needed to fetch information. [Get help with Recorded Future for Cortex XSOAR](https://www.recordedfuture.com/integrations/palo-alto). **Version:** 2.4.2 --- ### Collective Insights The Recorded Future Platform tracks trends and facilitates new insights on detections to better identify threats. See trends and track metrics over time using the Recorded Future Platform. This feature will store XSOAR enrichments based on playbooks. This feature permits additional analytics to track trends and identify new insights with the Recorded Future Intelligence Cloud. The following data points are collected as part of Collective Insights: 1. Incident - ID, Type, Name 2. Playbook - Name 3. Instance ID 4. Command executed 5. Indicator - Type, Name 6. Recurrence 7. Schedule ## Configuration | Parameter | Description | |------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Server URL | The URL to the Recorded Future ConnectAPI. | | API Token | Valid API Token from Recorded Future. | | Classifier | Select "Recorded Future - Classifier". | | Mapper (Incoming) | Select "Recorded Future - Incoming Mapper". | | IP/Domain/URL/File/CVE Suspicious Threshold | Minimum risk score from Recorded Future needed to mark the IOC as suspicious when doing reputation or intelligence lookups. | | IP/Domain/URL/File/CVE Malicious Threshold | Minimum risk score from Recorded Future needed to mark the IOC as malicious when doing reputation or intelligence lookups. | | Vulnerability Threshold | Minimum risk score from Recorded Future needed to mark the vulnerability as critical when doing reputation or intelligence lookups. | | Trust any certificate (not secure) | - | | Use system proxy settings | - | | First fetch time | This threshold will be used during first fetch of the incidents. | | Rule names to fetch alerts by | Rule names to fetch alerts by, separated by semicolon. If empty, all alerts will be fetched. | | Alert Statuses to include in the fetch | Alert Statuses to include in the fetch, separated by a comma. If empty, the default value of 'no-action' will be used. The value should be comma-separated alert statuses (e.g. "unassigned,assigned,pending,actionable,no-action,tuning"). | | Update alert status on fetch | If selected, alerts with a status of 'no-action' will be updated to 'pending' once fetched by the integration. | | Collective Insights | The Recorded Future Intelligence Cloud aggregates data related to indicators, incidents and detections from correlations, driving collective insights to better identify threats. Unattributable data is collected for analytical purposes to identify trends and insights with the Intelligence Cloud. Go to the Recorded Future support site to learn more about [Collective Insights](https://support.recordedfuture.com/hc/en-us/articles/11633413141779). | | Maximum number of incidents per fetch | - | | Incidents Fetch Interval | - | | Indicator Expiration Method | - | | Source Reliability | Reliability of the source providing the intelligence data. | --- ## Available Actions * Reputation actions * Using the new Recorded Future SOAR Enrichment API. * Available actions: ip, domain, url, file(hashes), cve. * Intelligence action * Fetches full information for the entity. * Supports IPs, Domains, URLs, Files(hashes), Vulnerabilities(cve), Malwares. * Malware search action * Alert actions * Fetch alerting rules defined at Recorded Future. * Fetch alert summaries from one or more alerting rules. * Set alert status in Recorded Future * Set alert note in Recorded Future * Threat assessment action * Takes a context, such as phishing or malware and one or more IOC as input. * Outputs a verdict (true/false) and related evidence (risk rules) for this context. --- ## Verdict / DBotScore mapping Reputation and intelligence lookups translate the Recorded Future risk score into a Cortex DBotScore: | Condition | Verdict | DBotScore | | --- | --- | --- | | Risk score at or above the configured Malicious threshold | Malicious | 3 (Bad) | | Risk score at or above the configured Suspicious threshold | Suspicious | 2 | | Recorded Future reports "No Risk Observed" (the `noKnownRisk` risk rule, available for files, URLs and domains) | Benign | 1 (Good) | | No risk data available | Unknown | 0 | Note: the Benign verdict is signal-driven (it requires the "No Risk Observed" risk rule), not threshold-driven. An indicator that simply has no risk data remains Unknown rather than Benign. Copyright 2020-2022 Recorded Future, Inc.