Intel 471 Adversary Intelligence

Updated 4 months ago by Elvis Hovor


TruSTAR is a cyber intelligence platform designed to accelerate incident analysis process and exchange of intelligence among various internal and external teams. This document provides a description of how paying customers of Intel 471 Adversary Intelligence can ingest reports and indicators from Intel 471 into the enclave in TruSTAR and correlate with other data sources in TruSTAR. 


This integration requires TruSTAR users to be paying customers of Intel471 and have access to Intel 471 Adversary Intelligence API keys. Users can generate their API keys from the Intel 471 Titan portal or reach out to the Intel 471 support team.

Configure Integration

After you have retrieved your Intel 471 Adversary Intelligence API key follow these steps:

  1. Log into TruSTAR Station and go the Explore->Marketplace (
  2. Click on Closed Sources.
  3. Click on Intel 471 Adversary Intelligence logo and fill in your API key.
  4. Click Submit.

TruSTAR will validate and enable your Intel 471 Adversary Intelligence integration within 48 hours. You will receive an email from us informing you as soon as it is enabled.

After the integration in enabled you should see reports from Intel 471 Adversary Intel being submitted into an enclave you control.


Do i have to be a company admin in TruSTAR to configure integration? 

Yes, a user needs to have company admin privilege in TruSTAR to be able to setup Intel 471 Adversary Intelligence Integration

What data do you currently pull from Intel 471 Adversary Intelligence? 

Our integration currently pulls reports from Intel 471 Adversary Intelligence and can extract and correlate the cyber IOC’s listed below

These include:

  • IP
  • Domain
  • URL (Domains are extracted from URL)
  • SHA256
  • SHA1
  • MD5
  • Malware
  • Bitcoin Addresses

Please contact us if you would like to discuss additional indicators that should be extracted and correlated.

How often is the data pulled?

Our integration retrieves data from Intel 471 Adversary Intelligence every 15mins.

Technical Details 

Intel471 Adversary List
  • Fetch records from below API as per checkpoint timestamp.
  • Submit individual item/record response as TruSTAR report
For any record, which has more than 400 ioc's (e.g 1000 ioc's count), create multiple reports and split ioc's like first report with 400 ioc, second report with 400 ioc and third report with 200 ioc's.
Report Update logic

If the same report needs to be updated, we will update only the original report with latest fetched IOC's from current record.




Reports created

Report Updation

Reports Unchanged

SC -1

Feed1 record - 200 iocs

Feed1 : 1 report with 200 iocs - ReportA

SC -1.1

Feed1 record - 100 iocs

Update 1st report (100 IOCs)- ReportA

SC -2

Feed2 record - 1000 iocs

Feed2 : 3 reports for Feed2 - ReportA(1st 400 IOC), ReportB(Subsequent 400 IOC), ReportC(Remaining 200 IOCs)

SC -2.1

Feed2 record - 100 iocs

Update 1st report - ReportA

ReportB, ReportC

SC -2.2

Feed2 record - 500 iocs

Update 1st report - ReportA, ReportB


Max number of indicators pulled will be 1,000.

Report API -

TruSTAR Report - Content is json formatted.

Report Title - UID: Subject field of response(e.g xxxx: Actor partners with regular client)

(For subsequent report Report Title - UID-{incremental No}: subject field of response(e.g xxxx: Actor plans to privatize, partner with regular client))

External ID - encoded value of (uid field of response(e.g daf8a134ce1654fe934ca3))

(For subsequent report External ID - encoded value of (UID-{incremental No}(e.g. daf8a134ce1654fe934ca384bf82e63c1cc-1)))

Report Body - individual item of json response(fields to be added in report body - uid, subject, created , Tags , portalReportUrl, reportIOCs - list of report indicators : ReportIOCs - List of unique values from {entities + derivedEntities} field of json response

Time Begun - created field of response(e.g. 1539060642000)

Tags - Tags field of response(e.g. ["Malware - Usage", "Vulnerabilities & Exploits"])

Deeplink - portalReportUrl field of response(e.g.

How Did We Do?