Integration Details

ThreatQuotient provides the following details for this integration:

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

Introduction

The ESET WeLiveSecurity CDF integration ingests blog posts from the WeLiveSecurity website, https://www.welivesecurity.com/, enabling analysts to stay up-to-date on advisories, bulletins, and analyses from the WeLiveSecurity team. 

The integration provides the following feed:

• ESET WeLiveSecurity - ingests ESET articles as ThreatQ Report objects.

The integration ingests the following system object types:

• Indicators
• Reports
• Vulnerabilities

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

   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 will be added to the integrations page. You will still need to configure and then enable the feed.

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 OSINT option 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.
   Parsed IOC Types	Select the IOC types you would like to automatically parse from the content. The only option available at this time is CVE.
   Ingest CVEs As	Select the entity type to ingest CVE IDs as into the ThreatQ platform. Options include: Vulnerabilities (default) Indicators  This parameter is only accessible if the CVE option is selected for the Parsed IOC Types parameter.

   
   
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

ESET WeLiveSecurity

The ESET WeLiveSecurity feed pulls blog posts from the WeLiveSecurity website and ingests them into ThreatQ as report objects.

GET https://www.welivesecurity.com/en/eset-research/

The output of this request is HTML which is parsed for links to the actual blog posts. These links will be fetched to get the content of each blog post.

GET https://www.welivesecurity.com/{{ uri }}

Only blog posts marked as ESET Research will be ingested.

ThreatQuotient provides the following default mapping for this feed:

Feed Data Path	ThreatQ Entity	ThreatQ Object Type or Attribute Key	Published Date	Examples	Notes
N/A	Report.Title	Report	Published At	The slow Tick‑ing time bomb: Tick APT group compromise of a DLP software developer in East Asia	Parsed from HTML
N/A	Report.Attribute	Published At	Published At	N/A	Parsed from HTML
N/A	Report.Attribute	External Reference	Published At	https://www.welivesecurity.com/2023/03/14/slow-ticking-time-bomb-tick-apt-group-dlp-software-developer-east-asia/	Parsed from HTML
N/A	Report.Description	N/A	Published At	<HTML content>	Parsed from HTML
N/A	Indicator/Vulnerability	CVE/Vulnerability	Published At	CVE-2023-41232	Parsed from HTML. Parsed from HTML. Ingested according to Ingest CVEs As

This mapping does not include feed data paths as there is no structured data.

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.

Metric	Result
Run Time	1 minute
Indicators	2
Reports	12
Report Attributes	24

Known Issues / Limitations

• ThreatQuotient recommends running this integration every 2 days based on the publication pace of the site.  
• 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.
• The integration can fetch a maximum of 4 pages. 

Change Log

• Version 1.0.0
  • Initial release