Current ThreatQ Version Filter

Palo Alto Unit 42 Reports CDF

The web format of this guide reflects the most current release.  Guides for older iterations are available in PDF format.  

Integration Details

ThreatQuotient provides the following details for this integration:

Introduction

The Palo Alto Unit 42 Reports CDF for ThreatQ enables an analyst to automatically ingest OSINT intelligence published by Palo Alto Networks.

The integration provides the following feed:

  • Palo Alto Unit 42 Reports - ingests public STIX reports from the Palo Alto Unit 42 GitHub Repository.

The integration ingests the following system objects:

  • Attack Patterns
  • Campaigns
  • Courses of Action
  • Indicators
  • Intrusion Sets
  • Reports
  • Signatures

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 file.
  3. Navigate to the integrations management page on your ThreatQ instance.
  4. Click on the Add New Integration button.
  5. Upload the integration file using one of the following methods:
    • Drag and drop the file into the dialog box
    • Select Click to Browse to locate the integration 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.

  6. If prompted, select the individual feeds to install and click Install. 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
    GitHub API Token Enter your GitHub API Token (personal Access Token). 

    The public API only allows 60 request per hour.  Using your GitHub Personal Access Token will increase that value to 5,000 per hour.  

    Ingest STIX Patterns as Signatures  Enable this parameter to exclude STIX Indicator Pattern signatures and only ingest atomic indicators. By default, ThreatQ ingests Palo Alto STIX 2.1 Indicator objects as both Signatures (STIX Indicator Patterns) and atomic Indicators. This parameter is disabled by default. 
    Disable Proxies Enable this option if the feed should not honor proxies set in the ThreatQ UI. 
    Enable SSL Verification Enable this parameter for the feed to validate the host-provided SSL certificate.  This option is enabled by default.

    Palo Alto Unit 42 Reports Configuration Screen
  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

Palo Alto Unit 42 Reports

The Palo Alto Unit 42 Reports feed automatically pulls public STIX reports from the Palo Alto Unit 42 GitHub Repository.

GET https://api.github.com/repos/pan-unit42/iocs/contents/stix2-reports/report_json

Sample Response:

[
  {
    "name": "CodeCov_Breach.json",
    "path": "stix2-reports/report_json/CodeCov_Breach.json",
    "sha": "4167ae1042f55117e3b914527be5865626f27c5c",
    "size": 26793,
    "url": "https://api.github.com/repos/pan-unit42/iocs/contents/stix2-reports/report_json/CodeCov_Breach.json?ref=master",
    "html_url": "https://github.com/pan-unit42/iocs/blob/master/stix2-reports/report_json/CodeCov_Breach.json",
    "git_url": "https://api.github.com/repos/pan-unit42/iocs/git/blobs/4167ae1042f55117e3b914527be5865626f27c5c",
    "download_url": "https://raw.githubusercontent.com/pan-unit42/iocs/master/stix2-reports/report_json/CodeCov_Breach.json",
    "type": "file",
    "_links": {
      "self": "https://api.github.com/repos/pan-unit42/iocs/contents/stix2-reports/report_json/CodeCov_Breach.json?ref=master",
      "git": "https://api.github.com/repos/pan-unit42/iocs/git/blobs/4167ae1042f55117e3b914527be5865626f27c5c",
      "html": "https://github.com/pan-unit42/iocs/blob/master/stix2-reports/report_json/CodeCov_Breach.json"
    }
  },
  {
    "name": "Defray777_TA.json",
    "path": "stix2-reports/report_json/Defray777_TA.json",
    "sha": "52cc89146040292b17a9a1d740ba6c1f4da710f0",
    "size": 86057,
    "url": "https://api.github.com/repos/pan-unit42/iocs/contents/stix2-reports/report_json/Defray777_TA.json?ref=master",
    "html_url": "https://github.com/pan-unit42/iocs/blob/master/stix2-reports/report_json/Defray777_TA.json",
    "git_url": "https://api.github.com/repos/pan-unit42/iocs/git/blobs/52cc89146040292b17a9a1d740ba6c1f4da710f0",
    "download_url": "https://raw.githubusercontent.com/pan-unit42/iocs/master/stix2-reports/report_json/Defray777_TA.json",
    "type": "file",
    "_links": {
      "self": "https://api.github.com/repos/pan-unit42/iocs/contents/stix2-reports/report_json/Defray777_TA.json?ref=master",
      "git": "https://api.github.com/repos/pan-unit42/iocs/git/blobs/52cc89146040292b17a9a1d740ba6c1f4da710f0",
      "html": "https://github.com/pan-unit42/iocs/blob/master/stix2-reports/report_json/Defray777_TA.json"
    }
  }
]

Each JSON file in the response is passed to ThreatQ's STIX parser, and the results are passed directly to the API. As such, there are no custom mappings for this feed.

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 3 minutes
Attack Patterns 88
Attack Pattern Attributes 1,830
Campaigns 11
Campaign Attributes 11
Courses Of Action 69
Course Of Action Attributes 69
Indicators 1,663
Indicator Attributes 5,190
Reports 25
Report Attributes 75
Signatures 1,670
Signature Attributes 5,013

Known Issues / Limitations

  • The feed may encounter rate limiting when retrieving a large number of reports if a GitHub API token is not provided. The likelihood of this occurring depends on the configured timeframe interval for the feed.

Change Log

  • Version 1.1.0
    • Improved feed workflow to reduce rate limiting issues and enhance delta processing efficiency.
    • Implemented inheritance of STIX Pattern Signature descriptions to associated Indicators.
    • Enhanced error handling to ensure all STIX objects and attributes are parsed safely without causing feed failures. 
    • Added the following new configuration parameters:
      • Ingest STIX Patterns as Signatures - control ingestion of STIX Indicator Pattern signatures, allowing the feed to ingest both signatures and atomic indicators or only atomic indicators.
      • Disable Proxies - allows you to determine whether or not the feed honors the proxy configuration set in the ThreatQ UI.  
      • Enable SSL Verification - allows you to determine if the feed should validate the host-provided SSL certificate.  
    • Updated the minimum ThreatQ version to 5.12.1.
  • Version 1.0.0
    • Initial release

PDF Guides

Document ThreatQ Version
Palo Alto Unit 42 Reports CDF Guide v1.1.0 5.12.1 or Greater
Palo Alto Unit 42 Reports CDF Guide v1.0.0 4.35.0 or Greater