Intel 471 Intelligence Engine Integration User Guide
  • 24 Sep 2025
  • 12 Minutes to read
  • Dark
    Light
  • PDF

Intel 471 Intelligence Engine Integration User Guide

  • Dark
    Light
  • PDF

Article summary

Software Version
This guide applies to the Intel 471 Intelligence Engine App version 1.0.7.

Overview

The ThreatConnect® integration with Intel 471 Intelligence ingests Reports, Adversaries, Breaches, Malware, Vulnerabilities, and Indicators from Intel 471 into ThreatConnect. These Groups and Indicators are stored and associated in ThreatConnect with select relevant context.

Important

The first time you set up the Feed API Service for the Intel 471 Intelligence Engine App, the data will backfill to 30 days. During the process of backfilling data for the prior 30 days, you may reach your Intel 471 API daily limit. To increase the API limit for your account, contact Intel 471. Note that this daily limit resets at midnight GMT.

If you continue to reach the Intel 471 API daily limit after the App backfills data for the last 30 days, it is recommended to select a greater value for the App’s Advanced Settings parameter to increase the interval at which Intel 471 data are ingested. See the first FAQ in the "Frequently Asked Questions (FAQ)" section for more information.

Dependencies

ThreatConnect Dependencies

  • Active ThreatConnect Application Programming Interface (API) key
Note
All ThreatConnect dependencies will be provided by default to subscribing ThreatConnect Cloud customers. Customers on Dedicated Cloud and On-Premises instances can enable these settings on the Account Settings screen within their ThreatConnect instance.

Intel 471 Dependencies

  • Active Intel 471 API key
  • Active Intel 471 report subscriptions
    • Adversary Intelligence
    • Breach Intelligence
    • Malware Intelligence
    • Vulnerability Intelligence
Note
The Intel 471 Intelligence Engine App may seem like it is running for a subscription that you may not have. In this scenario, contact Intel 471 for assistance with subscribing to a new report.

Application Setup and Configuration

Follow these steps to install and configure the Intel 471 Intelligence Engine App via  TC Exchange™:

  1. Log into ThreatConnect with a System Administrator account.
  2. From the SettingsA blue and white gear

Description automatically generatedmenu on the navigation bar, select TC Exchange Settings. Then select the Catalog tab on the TC Exchange Settings screen.
  3. Locate the Intel 471 Intelligence Engine App on the Catalog tab. Then click Install Plus icon_Dark bluein the Options column to install the App.
  4. After you install the Intel 471 Intelligence Engine App, the Feed Deployer will open automatically. Use the Feed Deployer to set up and configure the Intel 471 Intelligence Engine App. See the “Configuration Parameters” section for more information on the parameters available during the configuration and deployment process.

Configuration Parameters

Parameter Definitions

The parameters defined in Table 1 apply to the configuration parameters available when using the Feed Deployer to configure the App.

 

NameDescriptionRequired?
Source Tab
Sources to CreateEnter the name of the source for the feedRequired
OwnerSelect the organization in which the Source is created.Required
Activate DeprecationSelect this checkbox to allow confidence deprecation rules to be created and applied to Indicators in the Source.Optional
Create AttributesSelect this checkbox to allow custom Attribute Types to be created in the Source.Optional
Parameters Tab
Launch ServerSelect tc-job as the launch server for the Service corresponding to the Feed API Service App. Required
Intel Reports to IngestSelect one or more Intel 471 report subscriptions from which data will be ingested. Available choices include the following:
  • Adversary
  • Breach
  • Malware
  • Vulnerability
Required
Advanced SettingsUse this field to specify the interval, in days, at which the App will ingest Intel 471 data. The default interval is 1 day. 
Important
While you may use this field to modify your data ingest interval, doing so is not recommended, as it may result in application timeout. See the first FAQ in the “Frequently Asked Questions (FAQ)” section for details about a situation for which an adjustment to this parameter is appropriate.
Optional
Variables Tab
Intel 471 Intelligence API KeyThe Intel 471 Intelligence API key. Required
Intel 471 Intelligence API UsernameThe Intel 471 Intelligence API username.Required
Confirm Tab
Run Feeds after deploymentSelect this checkbox to run the Intel 471 Intelligence Engine App immediately after the deployment configuration is complete (i.e., after you click DEPLOY on the Feed Deployer window).Optional
Confirm Deployment Over Existing SourceThis checkbox will be displayed if the Source entered in the Sources to Create field has previously been deployed to the Organization selected in the Owner dropdown on the Source tab. Select this checkbox to confirm that you want the Intel 471 Intelligence Engine App to write data to the same Source. This process will create a new Service for the Intel 471 Intelligence Engine App. As such, it is recommended that you delete the old Service associated with the Intel 471 Intelligence Engine App after the new one is created.
Important
If you do not select this checkbox, the DEPLOY button will be grayed out, and you will not be able to deploy the Service. Return to the Source tab and enter a different Source or select a different Organization and then proceed through the tabs of the Feed Deployer window again.
Optional

Intel 471 Intelligence Engine App UI

After successfully configuring and activating the Feed API Service, you can access the Intel 471 Intelligence Engine App user interface (UI). This UI allows you to interact with and manage ThreatConnect’s Intel 471 Intelligence integration.

Follow these steps to access the Intel 471 Intelligence Engine App UI:

    1. Log into ThreatConnect with a System Administrator account.
    2. From the Automation & Feeds dropdown on the top navigation bar, select Services
    3. Locate and turn on the Intel 471 Intelligence Engine Feed API Service.
    4. Click the link in the Service’s API Path field. The Intel 471 Intelligence Engine App will open in a new browser tab.

The following screens are available in the Intel 471 Intelligence Engine App UI:

  • Dashboard
  • Jobs
  • Tasks
  • Download
  • Batch Errors
  • Attachment Status

Dashboard

The Dashboard screen (Figure 1) provides an overview of the total number of Adversary Reports, Breach Reports, Indicators, Malware Reports, Signatures, and Vulnerabilities retrieved from Intel 471.

Note
The numbers displayed on the Dashboard screen represent the count of threat intelligence objects that were processed by the App, including objects that were updated or processed again, and may not match the count of objects in ThreatConnect.

Figure 1_Intel 471 Intelligence Engine Integration User Guide_Software Version 1.0.7

 

Jobs

The Jobs screen (Figure 2) breaks down the ingestion of Intel 471 Intelligence Engine data into manageable Job-like tasks, displaying all processes that are pending, in progress, complete, and failed. The menu in a Job’s row provides the following options:

  • Details: View details for the Job, such as download, convert, and upload start and complete times and counts of downloaded and batched Groups and Indicators.
  • Download Files: Download metadata files for all Jobs and data (convert, download, and upload) files for completed Jobs.
  • Batch Errors: View errors that have occurred for the Job on the Batch Errors screen.

Figure 2_Intel 471 Intelligence Engine Integration User Guide_Software Version 1.0.7

 

You can filter Intel 471 Intelligence Engine App Jobs by the following elements:

  • Job ID: Enter text into this box to search for a Job by its Job ID.
  • Job Type: Select Job types to display on the Jobs screen.
  • Status: Select Job statuses to display on the Jobs screen.

Add a Job

You can add ad-hoc Jobs on the Jobs screen. Follow these steps to create a request for an ad-hoc Job for the Intel 471 Intelligence Engine App:

  1. Click Add Job (Figure 2).
  2. Fill out the fields on the Add Job drawer (Figure 3) as follows:

Figure 3_Intel 471 Intelligence Engine Integration User Guide_1.0.7

 

  • Start Time: (Optional) Enter the time at which the Job should start.
  • End Time: (Optional) Enter the time by which the Job should end.
  • Types: (Optional) Select the object types to include in the Job. 
  • Click Submit to submit the request for the ad-hoc Job.

Tasks

The Tasks screen (Figure 4) displays all Tasks that may be part of a Job, including each step of the download, convert, and upload processes, as well as Tasks for the ThreatConnect Intel 471 Intelligence Engine App, such as Monitor, Schedule Downloads, and Cleaner. The current status (Idle, Paused, or Running), name, description, and heartbeat timeout length, in minutes, are displayed for each Task. The menu in a Task’s row provides the following options, depending on the Task’s status:

  • Run (idle and paused Tasks only)
  • Pause (idle and running Tasks only)
  • Resume (paused Tasks only)
  • Kill (running Tasks only)

Under the table is a dashboard where you can view runtime analytics.

Figure 4_Intel 471 Intelligence Engine Integration User Guide_Software Version 1.0.7

 

Download

The Download screen (Figure 5) lets you download JavaScript® Object Notation (JSON) data for Intel 471 objects and then upload the data into ThreatConnect. 

Figure 5_Intel 471 Intelligence Engine Integration User Guide_Software Version 1.0.7

 

Follow these steps to download JSON data for an Intel 471 Intelligence object on the Download screen and then upload the data into ThreatConnect:

  1. Type: Select an Intel 471 Intelligence object type to download.
  2. External ID: Enter one or more Intel 471 External IDs for the objects to download, separating each ID with a comma.
  3. Click Download. The JSON data will be displayed in two columns: Results (raw JSON data) and Converted (JSON data in ThreatConnect batch format) (Figure 6).
  4. Click Upload to submit the converted Threat intelligence data via the ThreatConnect Batch API.Figure 6_Intel 471 Intelligence Engine Integration User Guide_Software Version 1.0.7

 

Batch Errors

The Batch Errors screen (Figure 7) displays an overview of the batch error types that have occurred for Job requests. You can enter keywords to filter by Job ID.

Figure 7_Intel 471 Intelligence Engine Integration User Guide_Software Version 1.0.7

 

Select an error type to open a drawer containing a table with details on all batch errors of that type (Figure 8). You can enter keywords to filter by reason for error.

Figure 8 _Intel 471 Intelligence Engine Integration User Guide_1.0.7

 

Attachment Status

The AttachmentStatus screen (Figure 9) displays a table with details on ThreatConnect's attempts to download Report attachments from Intel 471 Intelligence. You can enter Intel 471 External IDs for Groups to filter the table by Group ID, which can be useful if you do not see an Intel 471 Intelligence attachment in ThreatConnect as expected, or by status.

Figure 9_Intel 471 Intelligence Engine Integration User Guide_Software Version 1.0.7

 

Data Mappings

The data mappings in Table 2 through Table 11 illustrate how data are mapped from Intel 471 Intelligence API endpoints into the ThreatConnect data model.

Actor

ThreatConnect object type: Adversary Group

 

Intel 471 API FieldThreatConnect Field
uidAttribute: "External ID"
handlesAttribute: "Aliases" (one Attribute per handle)
links/forumTotalCountAttribute: "Total Count of Forums"
links/forumPrivateMessageTotalCountAttribute: "Total Count of Private Messages"
links/forumPostTotalCountAttribute: "Total Count of Posts"
links/reportTotalCountAttribute: "Total Count of Reports"
links/instantMessageServerTotalCountAttribute: "Total Count of IM Servers"
links/instantMessageChannelTotalCountAttribute: "Total Count of IM Topics"
links/instantMessageTotalCountAttribute: "Total Count of IMs"
links/instantMessageServers/{index}/uidAttribute: "IM Server" (one concatenated Attribute per grouping)
  • uid: %uid%
  • serviceType: %serviceType%
  • name: %name%
links/instantMessageServers/{index}/serviceType
links/instantMessageServers/{index}/name
links/forums/{index}/forumAttribute: "Forum" (one concatenated Attribute per grouping)
  • Forum ID: %uid%
  • Forum Name: %name%
  • Actor Handle: %actorHandle%
  • Contact Type: %type%
  • Contact Value: %value%
  • TimeZone: %timeZone%
links/forums/{index}/uid
links/forums/{index}/name
links/forums/{index}/actorHandle
links/forums/{index}/timeZone
links/forums/{index}/contactInfo
links/forums/{index}/contactInfo/{index}/item/value
links/forums/{index}/contactInfo/{index}/itemN/A
links/forums/{index}/contactInfo/{index}/item/typeN/A
links/reportsAdversary-to-Report Association
links/reports/{index}/report
links/reports/{index}/actorHandleAttribute: "Aliases" (one Attribute per handle)
activeFromAttribute: "First Seen"
activeUntilAttribute: "Last Seen"
lastUpdatedAttribute: "External Date Last Modified"

Adversary Intelligence Report

ThreatConnect object type: Report Group

 

Intel 471 API FieldThreatConnect Field
uidAttribute: "External ID"
documentFamilyN/A
documentTypeAttribute: "Report Type"
admiraltyCodeAttribute: "Admiralty Code"
motivationAttribute: "Adversary Motivation Type"
subjectName/Summary
researcherCommentsAttribute: "Additional Analysis and Context"
rawTextUploaded File
rawTextTranslatedN/A
executiveSummaryAttribute: "Description"
createdAttribute: "External Date Created"
dateOfInformationAttribute: "Date of Information"
sourceCharacterizationAttribute: "Source Characterization"
relatedReports/{index}/uidReport-to-Report Association
relatedReports/{index}/documentFamily
entities/{index}/type See Table 11
locations/{index}/linkAttribute: "Region & Country"
  • Region: %: % (region)
  • Country: % (country)
  • Link: % (link)
locations/{index}/region
locations/{index}/country
tags/{index}Tag
portalReportUrlAttribute: "Report URL"
lastUpdatedLast Modified
sources/{index}/urlAttribute: "Sources" (one concatenated Attribute per grouping)
  • URL: %: % (url)
  • Title: % (title)
  • Type: % (type)
sources/{index}/title
sources/{index}/type
sources/{index}/indexN/A
actorSubjectOfReport/{index}/handleN/A
actorSubjectOfReport/{index}/aliasesAttribute: "Aliases"
classification/intelRequirementsTag: "GIR: %"
reportAttachments/{index}/fileNameAttribute: "Report Attachment"
  • File Name: filename
  • URL: url
  • File Size: fileSize
  • Mime Type: mimeType
  • Description: description
  • Malicious: malicious
reportAttachments/{index}/url
reportAttachments/{index}/fileSize
reportAttachments/{index}/mimeType
reportAttachments/{index}/description
reportAttachments/{index}/malicious

Malware Intelligence Report

ThreatConnect object type: Report Group

 

Intel 471 API FieldThreatConnect Field
malwareReportTotalCountN/A
malwareReportsPartialResultN/A
malwareReportsN/A
malwareReports/{index}/uidAttribute: "External ID"
malwareReports/{index}/activity/firstAttribute: "First Seen"
malwareReports/{index}/activity/lastAttribute: "Last Seen"
malwareReports/{index}/meta/versionN/A
malwareReports/{index}/data/threat/uidN/A
malwareReports/{index}/data/threat/typeN/A
malwareReports/{index}/data/threat/data/familyN/A
malwareReports/{index}/data/threat/data/
malware_family_profile_uid
N/A
malwareReports/{index}/data/threat/data/versionN/A
malwareReports/{index}/malware_report_data/titleName/Summary
malwareReports/{index}/malware_report_data/textN/A
malwareReports/{index}/malware_report_data/
attachments
Attribute: "Report Attachment"
  • File Name: fileName
  • URL: url
  • File Size: fileSize
  • Mime Type: mimeType
  • Description: description
  • Malicious: malicious
malwareReports/{index}/malware_report_data/
related_reports
N/A
malwareReports/{index}/malware_report_data/
released_at
Publish Date
malwareReports/{index}/last_updatedAttribute: "External Date Last Modified"

Related Indicators

ThreatConnect object type: Indicator (all types)

 

Intel 471 API FieldThreatConnect Field
indicatorTotalCountN/A
indicatorsN/A
indicators/{index}/data/uidN/A
indicators/{index}/data/source_idN/A
indicators/{index}/data/threat/typeN/A
indicators/{index}/data/threat/uidIndicator-to-Malware Association
indicators/{index}/data/threat/data/
malware_family_profile_uid
Indicator-to-Malware Association
indicators/{index}/data/threat/data/familyIndicator-to-Malware Association
indicators/{index}/data/threat/data/versionN/A
indicators/{index}/data/expirationAttribute: "External Date Expires"
indicators/{index}/data/confidenceAttribute: "Confidence"
indicators/{index}/data/context/descriptionAttribute: "Description"
indicators/{index}/data/mitre_tacticsTag: "MITRE Tactic: %"
indicators/{index}/data/indicator_typeIndicator Type
indicators/{index}/data/indicator_data/addressAddress Indicator
indicators/{index}/data/indicator_data/urlURL Indicator
indicators/{index}/data/indicator_data/domainHost Indicator
indicators/{index}/data/indicator_data/mutexMutex Indicator
indicators/{index}/data/indicator_data/
windows_registry_key
Registry Key Indicator
indicators/{index}/data/indicator_data/fileFile Indicator
indicators/{index}/data/indicator_data/file/sha1File Indicator
indicators/{index}/data/indicator_data/file/sha256File Indicator
indicators/{index}/data/indicator_data/file/md5File Indicator
indicators/{index}/data/indicator_data/file/typeAttribute: "File Type"
indicators/{index}/data/indicator_data/file/sizeFile Indicator: File Size
indicators/{index}/data/indicator_data/file/
download_url
Attribute: "Sample Download Link"
indicators/{index}/data/intel_requirementsTag: "GIR: %"
indicators/{index}/meta/versionN/A
indicators/{index}/last_updatedLast Modified
indicators/{index}/uidAttribute: "External ID"
indicators/{index}/activity/firstAttribute: "First Seen"
indicators/{index}/activity/lastAttribute: "Last Seen"

GIR Tags

ThreatConnect object type: Tags

 

Intel 471 API FieldThreatConnect Field
girs/{index}/data/gir/pathTag: "GIR: % %" (path, name)
girs/{index}/data/gir/name

Malware 

ThreatConnect object type: Malware Group

 

Intel 471 API FieldThreatConnect Field
malwareReportTotalCountN/A
malwareReports/data/threat/uidAttribute: "External ID"
malwareReports/data/threat/typeAttribute: "Malware Threat Type"
malwareReports/data/threat/data/familyName/Summary
malwareReports/data/threat/data/
malware_family_profile_uid
Attribute: "External ID"
malwareReports/data/malware_report_data/textAttribute: "Malware Report Text"
malwareReports/data/malware_report_data/
released_at
Attribute: "Report Published Date"
malwareReports/meta/versionN/A
malwareReports/last_updatedLast Modified
malwareReports/uidN/A
malwareReports/classification/intelRequirements[]Tag: "GIR: %"
activity/firstAttribute: "First Seen"
activity/lastAttribute: "Last Seen"

Malware Family YARA Signatures

ThreatConnect object type: Signature Group

 

Intel 471 API FieldThreatConnect Field
yaraTotalCountN/A
yaras/{index}/uidAttribute: "External ID"
yaras/{index}/data/threat/typeSignature-to-Malware Association
yaras/{index}/data/threat/uid
yaras/{index}/data/threat/data/
malware_family_profile_uid
yaras/{index}/data/threat/data/family
yaras/{index}/data/yara_data/titleName/Summary
yaras/{index}/data/yara_data/signatureSignature File Contents
yaras/{index}/data/confidenceAttribute: "Confidence"
yaras/{index}/data/intel_requirementsTag: "GIR: %"
yaras/{index}/meta/versionN/A
yaras/{index}/last_updatedLast Modified
yaras/{index}/activity/firstAttribute: "First Seen"
yaras/{index}/activity/lastAttribute: "Last Seen"

Vulnerability Report Search

ThreatConnect object type: Vulnerability Group

 

Intel 471 API FieldThreatConnect Field
cveReportsTotalCountN/A
partialResultN/A
cveReports/{index}/uidAttribute: "External ID"
cveReports/{index}/data/cve_report/nameName/Summary
cveReports/{index}/data/cve_report/cve_typeAttribute: "CVE Type"
cveReports/{index}/data/cve_report/risk_levelAttribute: "CVE Threat Level"
cveReports/{index}/data/cve_report/vendor_nameAttribute: "Vulnerable Vendor"
cveReports/{index}/data/cve_report/product_nameAttribute: "Vulnerable Product"
cveReports/{index}/data/cve_report/cve_statusAttribute: "CVE Status"
cveReports/{index}/data/cve_report/interest_level/
disclosed_publicly
Attribute: "Interest Level" (one Attribute per grouping)
cveReports/{index}/data/cve_report/interest_level/
researched_publicly
cveReports/{index}/data/cve_report/interest_level/
exploit_sought
cveReports/{index}/data/cve_report/activity_location/
location_opensource
Attribute: "Activity Location" (one Attribute per grouping)
cveReports/{index}/data/cve_report/activity_location/
location_underground
cveReports/{index}/data/cve_report/activity_location/
location_private
cveReports/{index}/data/cve_report/exploit_status/
available
Attribute: "Exploits" (one Attribute per grouping)
cveReports/{index}/data/cve_report/exploit_status/
weaponized
cveReports/{index}/data/cve_report/exploit_status/
productized
cveReports/{index}/data/cve_report/exploit_status/
not_observed
cveReports/{index}/data/cve_report/cvss_score/v2Attribute: "CVSS v2 Score"
cveReports/{index}/data/cve_report/cvss_score/v3Attribute: "CVSS v3 Score"
cveReports/{index}/data/cve_report/patch_statusAttribute: "Patch Status"
cveReports/{index}/data/cve_report/detectionAttribute: "Detection"
cveReports/{index}/data/cve_report/
underground_activity
Attribute: "Underground Activity"
cveReports/{index}/data/cve_report/
underground_activity_summary
Attribute: "Summary"
cveReports/{index}/data/cve_report/summaryAttribute: "Description"
cveReports/{index}/data/cve_report/titan_links/
{index}/title

Attribute: "External References"

Note
Due to this Attribute Type's length limit, each link will be in its own Attribute.
cveReports/{index}/data/cve_report/titan_links/
{index}/url
cveReports/{index}/data/cve_report/poc
Attribute: "External References"

Note
Due to this Attribute Type's length limit, each link will be in its own Attribute.
cveReports/{index}/data/cve_report/poc_links/
{index}/title
cveReports/{index}/data/cve_report/poc_links/
{index}/url
cveReports/{index}/data/cve_report/
counter_measures
Attribute: "Course of Action Recommendation" (one concatenated Attribute per grouping)
  • Counter Measures: counter_measures
  • Counter Measure Title: title
  • Counter Measure URL:URL
cveReports/{index}/data/cve_report/
counter_measure_links/{index}/title
cveReports/{index}/data/cve_report/
counter_measure_links/{index}/url
cveReports/{index}/data/cve_report/
patch_links/{index}/title
Attribute: "Course of Action Taken" (one concatenated Attribute per grouping)
  • Patch Links Title: title
  • Patch Links URL: URL
cveReports/{index}/data/cve_report/
patch_links/{index}/url
cveReports/{index}/data/cve_report/cpe/
cve_data_version
Attribute: "Vulnerable CPE" (one concatenated Attribute per grouping)
  • CVE Data Version: cve_data_version
  • Operator: operator
  • CPE Match Vulnerable: vulnerable
  • CPE Match 23 uri: cpe23Uri
cveReports/{index}/data/cve_report/cpe/
nodes/{index}/operator
cveReports/{index}/data/cve_report/cpe/
nodes/{index}/cpe_match/{index}/vulnerable
cveReports/{index}/data/cve_report/cpe/
nodes/{index}/cpe_match/{index}/cpe23Uri
cveReports/{index}/classification/
intel_requirements
Tags: "GIR: %"
cveReports/{index}/last_updatedLast Modified
cveReports/{index}/activity/firstAttribute: "First Seen"
cveReports/{index}/activity/lastAttribute: "Last Seen"

Breach Alerts

ThreatConnect object type: Report Group

 

Intel 471 API FieldThreatConnect Field
breach_alerts/activity/firstAttribute: "First Seen"
breach_alerts/activity/lastAttribute: "Last Seen"
breach_alerts/lastupdatedAttribute: "External Date Last Modified"
breach_alerts/uidAttribute: "External ID"
breach_alerts/data/uidN/A
data/breach_alerts/date_of_informationAttribute: "Date of Discovery"
data/breach_alerts/confidence/levelAttribute: "Confidence"
data/breach_alerts/summaryAttribute: "Description"
data/breach_alerts/intel_requirementsTags: "GIR: %"
data/breach_alerts/released_atPublish Date
data/breach_alerts/titleAttribute: "Report Title"
data/breach_alerts/victimAttribute: "Breach Alert Victim" (one concatenated Attribute per grouping)
  • Name: name
  • Industry: industry
  • Sector: sector
  • URL: urls
  • Country: country
  • Revenue: revenue
  • Region: region

data/breach_alert/victim/name
data/breach_alert/victim/industries/industry
data/breach_alert/victim/industries/sector
data/breach_alert/victim/urls
data/breach_alert/victim/country
data/breach_alert/victim/revenue
data/breach_alert/victim/region
data/breach_alerts/sources/urlAttribute: "Source" (one concatenated Attribute per grouping)
  • Date: date
  • Source Type: source type
  • Title: title
  • Urls: urls
  • Type: type
data/breach_alerts/sources/source_type
data/breach_alerts/sources/date
data/breach_alerts/sources/title
data/breach_alerts/sources/type
data/breach_alerts/actor_or_groupAttribute: "Actor or Group"
data/entities/typeAttribute: "Additional Analysis and Context"
  • Entity Type: type
  • Entity value: value
data/entities/value
data/breach_alerts/N/A

Entity

 

Intel 471 EntityThreatConnect Object
ActorDomainHost Indicator
ActorOtherWebsiteURL Indicator
AIMAttribute: "Social Media: AIM"
AutonomousSystemASN Indicator
BitcoinAddressAttribute: "Bitcoin Address"
BitcoinTransactionIDAttribute: "Bitcoin Transaction ID"
CveIDVulnerability Group
DiscordAttribute: "Social Media: Discord"
EcurrencyAttribute: "Ecurrency"
EmailAddressEmail Address Indicator
FacebookAttribute: "Social Media: Facebook"
FileNameAttribute: "File Name"
FileSizeAttribute: "File Size"
FileTypeAttribute: "File Type"
GitHubAttribute: "Github"
HandleAdversary Group
ICQAttribute: "Social Media: ICQ"
InstagramAttribute: "Social Media: Instagram"
IPAddressAddress Indicator
IPv4PrefixAttribute:" IPv4 Prefix"
IPv6PrefixAttribute: "IPv6 Prefix"
JabberAttribute: "Social Media: Jabber"
LinkedInAttribute: "Social Media: LinkedIn"
MaliciousDomainHost Indicator
MaliciousURLURL Indicator
MD5File Indicator
MoiMirAttribute: "Social Media: Moimir"
MSNAttribute: "MSN"
OdnoklassnikiAttribute: "Social Media: Odnoklassniki"
OtherCryptoCurrenciesAttribute: "Other CryptoCurrencies"
PasswordAttribute: "Password"
PasswordHashAttribute: "Password Hash"
PerfectMoneyIDAttribute: "Perfect Money ID"
PGPKeyAttribute: "PGP Key"
PGPKeyIDAttribute: "PGP Key ID"
PhoneAttribute: Phone
QiwiWalletAttribute: "QIWI Wallet"
QQAttribute: "Social Media: QQ"
SHA1File Indicator
SHA256File Indicator
SkypeAttribute: "Social Media: Skype"
SSLCertificateAttribute: "SSL Certificate"
SSLCertificateFingerprintAttribute: "SSL Certificate Fingerprint"
SSLCertificateIDAttribute: "SSL Certificate ID"
TagTag
TelegramAttribute: "Social Media: Telegram"
ToxAttribute: "Social Media: Tox"
TwitterAttribute: "Social Media: Twitter"
URLURL Indicator
VKAttribute: "Social Media: VK"
WebMoneyIDAttribute: "WebMoney ID"
WebMoneyPurseAttribute: "WebMoney Purse"
WeChatAttribute: "Social Media: WeChat"
WickrAttribute: "Social Media: Wickr"
YahooIMAttribute: "Social Media: YahooIM"
YandexMoneyAttribute: "Yandex.Money"

Frequently Asked Questions (FAQ)

Are there any limitations I should be aware of?

The first time you set up the Feed API Service for the Intel 471 Intelligence Engine App, the data will backfill to 30 days. During the process of backfilling data for the prior 30 days, you may reach your Intel 471 API daily limit. To increase the API limit for your account, contact Intel 471. Note that this daily limit resets at midnight GMT.

If you continue to reach the Intel 471 API daily limit after the App backfills data for the last 30 days, it is recommended to select a greater value for the App's Advanced Settings parameter to increase the interval at which Intel 471 data are ingested.

Follow these steps to update the Advanced Settings parameter for the Intel 471 Intelligence Engine App:

  1. From the menu for the Intel 471 Intelligence Engine App on the Services screen, select Edit.
  2. On Step 3 (Parameters) of the Edit Service drawer, increase the value of the Advanced Settings parameter. The unit for this field is days. If the field for this parameter is blank, then the current value is the default of 1 day.
  3. Click SAVE.

Why are no new data are being ingested from Intel 471 into my ThreatConnect instance?

As you approach your Intel 471 API daily limit, Intel 471 will handle only one request per minute and then eventually return a 429 error until the daily limit resets at midnight GMT. Similarly, if there are multiple requests occurring at the same time, Intel 471 will handle one request per minute until the daily limit resets at midnight GMT. To increase the API limit for your account, contact Intel 471.

How can I tell which Intel 471 report an Indicator is from?

Any data ingested from Intel 471 will have one of these four Tags applied to them:

  • "Source: Intel 471 Adversary Intelligence Feed"
  • "Source: Intel 471 Breach Intelligence Feed"
  • "Source: Intel 471 Malware Intelligence Feed"
  • "Source: Intel 471 Vulnerability Intelligence Feed"

When would I use the Add Job feature on the Jobs screen?

The Add Job feature on the Jobs screen allows you to make ad-hoc requests for one or more of the Intel 471 products in a certain date range. If you want to retrieve specific reports or other objects, use the Downloads screen.


ThreatConnect® is a registered trademark, and TC Exchange™ is a trademark, of ThreatConnect, Inc.
JavaScript® is a registered trademark of Oracle Corporation.

30078-03 EN Rev. A


Was this article helpful?