Integration Details

ThreatQuotient provides the following details for this integration:

Current Integration Version	1.0.0
Compatible with ThreatQ Versions	>= 5.12.1
Support Tier	ThreatQ Supported

Introduction

The ReliaQuest CDF integration enables organizations to ingest curated threat intelligence from ReliaQuest directly into ThreatQ, leveraging its Open XDR platform, dark web monitoring, and threat research capabilities to enhance visibility into emerging threats and overall security posture. By delivering intelligence such as weekly summary reports and threat research blog content into a centralized platform, the integration helps analysts stay informed of the latest adversary activity and industry developments, supporting more informed and proactive security decision making.

The integration provides the following feeds 

• ReliaQuest Threat Research - ingests ReliaQuest Threat Research blog posts as ThreatQ report objects.
• ReliaQuest Weekly Intelligence Reports - ingests ReliaQuest Weekly Intelligence Reports blog posts as ThreatQ report objects.

The integration ingests report and report attribute object types into ThreatQ. 

Installation

Perform the following steps to install the integration:

The same steps can be used to upgrade the integration to a new version.

1. Log into https://marketplace.threatq.com/.
2. Locate and download the integration yaml file.
3. Navigate to the integrations management page on your ThreatQ instance.
4. Click on the Add New Integration button.
5. Upload the integration yaml file using one of the following methods:
   • Drag and drop the file into the dialog box
   • Select Click to Browse to locate the file on your local machine
6. Select the individual feeds to install, when prompted, and click Install.

   ThreatQ will inform you if the feed already exists on the platform and will require user confirmation before proceeding. ThreatQ will also inform you if the new version of the feed contains changes to the user configuration. The new user configurations will overwrite the existing ones for the feed and will require user confirmation before proceeding.

The feed(s) will be added to the integrations page. You will still need to configure and then enable the feed(s).

Configuration

ThreatQuotient does not issue API keys for third-party vendors. Contact the specific vendor to obtain API keys and other integration-related credentials.

To configure the integration:

1. Navigate to your integrations management page in ThreatQ.
2. Select the OSINToption from the Category dropdown (optional).

   If you are installing the integration for the first time, it will be located under the Disabled tab.

3. Click on the integration entry to open its details page.
4. Enter the following parameters under the Configuration tab:

   Parameter	Description
   Enable SSL Certificate Verification	Enable this parameter if the feed should validate the host-provided SSL certificate.
   Disable Proxies	Enable this parameter if the feed should not honor proxies set in the ThreatQ UI.

5. Review any additional settings, make any changes if needed, and click on Save.
6. Click on the toggle switch, located above the Additional Information section, to enable it.

ThreatQ Mapping

ReliaQuest Threat Research

The ReliaQuest Threat Research pulls threat research posts from the ReliaQuest Threat Research blog, https://www.reliaquest.com/blog/category/threat-research/, and ingests them into ThreatQ as Report Objects.

GET https://www.reliaquest.com/blog/category/threat-research/

This request returns HTML. The HTML is parsed for the title, date, links, etc. The blog itself is then fetched.

GET https://www.reliaquest.com/blog/{{ uri }}

ThreatQuotient provides the following default mapping for this feed based on the information parsed out of the blog's HTML content.

Feed Data Path	ThreatQ Entity	ThreatQ Object Type or Attribute Key	Published Date	Examples	Notes
N/A	Report Value	N/A	N/A	Citrix Bleed Vulnerability: Background and Recommendations	Parsed from the HTML
N/A	Report Description	N/A	N/A	N/A	Parsed from the HTML
N/A	Report Attribute	External Reference	N/A	https://www.reliaquest.com/blog/citrix-bleed-vulnerability-background-and-recommendations/	Parsed from HTML
N/A	Report Attribute	Published At	N/A	9 November 2023	Parsed from the HTML
N/A	Report Tag	N/A	N/A	Emerging Threats	Parsed from the HTML
N/A	Report Attachment	N/A	N/A	Blog post content captured via Fetch Blog Post	Defined in YAML

ReliaQuest Weekly Intelligence Reports

The ReliaQuest Weekly Intelligence Reports feed pulls the Weekly Intelligence Summary Reports from ReliaQuest, https://go.reliaquest.com/FY24ILPIIntsumWeeklyReportSend_LP-New.html, and ingests the PDF reports into ThreatQ as File Objects.

GET https://go.reliaquest.com/FY24ILPIIntsumWeeklyReportSend_LP-New.html

This request returns HTML. The HTML is parsed for the direct link to the PDF.

GET https://go.reliaquest.com/rs/{{ id }}/images/{{ uri }}

ThreatQuotient provides the following default mapping for this feed based on the information parsed out of the blog's HTML content.

Feed Data Path	ThreatQ Entity	ThreatQ Object Type or Attribute Key	Published Date	Examples	Notes
N/A	File Title	N/A	N/A	RQTR 040124 WeeklyIntsumReport	Parsed from the HTML
N/A	File Name	N/A	N/A	RQTR_040124_WeeklyIntsumReport.pdf	Parsed from the HTML
N/A	File Attribute	External Reference	N/A	N/A	Parsed from the HTML

Average Feed Run

Object counts and Feed runtime are supplied as generalities only - objects returned by a provider can differ based on credential configurations and Feed runtime may vary based on system resources and load.

ReliaQuest Threat Research

Metric	Result
Run Time	1 minute
Reports	5
Report Attributes	10

Known Issues / Limitations

• The integration relies on HTML scraping and curl User-Agent spoofing because the site's standard RSS feed and Sitemap are currently broken/empty, making the feed sensitive to future changes in the website's layout or stricter security blocking policies.
• The feed utilizes since and until dates to make sure entries are not re-ingested if they haven't been updated.
• If you need to ingest historical blog posts, run the feed manually by setting the since date back.

Change Log

• Version 1.0.0
  • Initial release