Page Comparison

TIDE data can be uploaded to a profile associated with an account. Policies are used to control access to your organization's data and can be specified when the data is submitted. Data Policies allow organizations to control how their submitted data is shared with other organizations or groups. Infoblox can enable accessing and data sharing between organizations upon request. Policies can be used for multiple data submissions and are only visible within your organization. Data profiles are used to identify data in the platform from one or many data submissions. A data profile must be specified when data is submitted. Data profiles are associated with policies, which control who can access the data. When a data profile is created it must be associated with a policy.

...

A dedicated service key for each data output is the recommended best practice.

Users can submit threat indicators using the Cloud Services Portal or via the TIDE Data API. In order to submit data, the following is required:

1. A policy: Defines how data is shared. For information on security policies, see Configuring Security Policies.
2. A data profile: Data profiles are associated with policies, which control who has access to your organization’s data, and must be specified when data is submitted. When a data profile is created it must be associated with a policy. Subscribers of BloxOne Threat Defense Advanced can create custom profiles that allow the use of custom-generated TIDE RPZ feeds that are based on an organization's requirements. When creating your own TIDE BYOF RPZ feeds for use with NIOS, keep in mind the practical limits of your NIOS system and its ability to ingest large amounts of data contained within only one RPZ feed. For details, see Creating Data Profiles.

Users can submit data using the following formats: JSON, CSV, XML, and TSV (tab separated values). For all data formats, the submitted data must identify the data/record type in addition to the list of data records. For CSV and TSV, the record type must be provided as one of the columns. For JSON and XML, the record type is defined in a separate top-level field. The record type field can be one of the following values: host, ip, or url. It is not possible to upload data using different profiles or different record types in the same file. Threat data consists of file-level fields and record-level fields. The following table contains descriptions of all available fields:

Data Submission Formats

Note

title	Note

Any unknown fields in a record will automatically go under an “extended” field for that record. This will occur after the submission is done.

...

Threat Data Fields
File-level fields
profile	The data profile id.
record_type	This is either host, ip, url, email, or hash.
external_id	This is a string indicating an external ID to assign to the batch (optional).
record	This surrounds the individual record(s) in the XML and JSON formats.
Record-level fields
Field Name	Description
host	The threat hostname.
ip	The threat IP address.
url	The threat URL.
hash	The hash threat.
email	The email threat.
detected	The date/time the threat was detected

,

in ISO 8601 format. For example, '20231114T124742Z' and '2024-01-12T00:00:00.000Z' are valid ISO 8601 formats.
class

the

The threat's class

, for

. For example: Sinkhole. Note: Either "class" or "property" is required, but not both.
property

the

The threat's property,

for

For example

:

, Sinkhole_SinkholedHost. Note: Either "class" or "property" is required, but not both.
confidence

the

Tthe threat's confidence score ranging from 0 - 100 (optional).
domain	The domain string (optional).
duration	The duration of the threat in Xd format or XyXmXwXdXh

format

- the expiration date will be set to the detected date + this duration (optional).
expiration	The expiration date

, in ISO 8601 format

of the threat in Xd format or XyXmXwXdXh - the expiration date will be set to this detected date + the duration (optional).
threat_level

the

The threat's level

,

ranging from 0 - 100 as an integer (optional).
target	The target of threat (optional). For example: “fakeamazon.com” is a threat targeting “amazon.com”.
tld	The top-level domain, string (optional).

The following listing contains a sample data submission in XML format:

Code Block

language	text
theme	Confluence

<feed>
   <profile>SampleProfile</profile>
   <record_type>ip</record_type>
   <record>
     <ip>127.1.0.1</ip>
    <property>Phishing_Phish</property>
    <detected>20170602T154742Z</detected>
   </record>
   <record>
  <ip>8.8.8.8</ip>
   <property>Scanner_Generic</property>
   <detected>19980927T154242Z</detected>
   <duration>42y0m0w0d42h</duration>
   </record>
  </feed>

sample_xml_file.xml (XML format)

The following listing contains a sample data submission in CSV format:

...

Code Block

language	text
theme	Confluence

{ "feed": {
    "profile": "SampleProfile", 
    "record_type": "host",
    "record": [ 
        { 
            "host": "test-domain.org", 
                        "domain": "test-domain.org", 
                        "class": "CompromisedHost", 
                         "property" : "CompromisedHost_Generic", 
                         "detected": "2024-01-12T00:00:00.000Z",
                         "duration": "90d", 
                         "confidence": 70, 
                         "threat_level": 80 
                }, 
                { 
                         "host": "test-domain.net", 
                         "class": "Sinkhole", 
                         "property" : "Sinkhole_SinkholedHost", 
                         "detected": "2024-01-12T00:00:00.000Z", 
                         "expiration": "2024-03-01T00:00:00.000Z", 
                         "confidence": 30, 
                         "threat_level": 50 
                 }] 
     } 
}

Tide-Data.json (JSON format)

For additional information, see the following:

...

Versions Compared

Old Version 59

New Version 60

Key

Data Submission Formats