Adding IOCs Export

To add a new IOCs export, follow the below steps:

  1. Navigate to the “Exports” tab by clicking on the “Settings” link in the sidebar.

  2. Click on the “Exports” tab.

  3. Click on the “Add Export” button.

  4. Enter the export name, this name will be used to identify the export in the exports list.

  5. Select the export type, in this case select “Indicators of Compromise (IOCs)”.

  6. Select the export format, IDSTower supports exporting IOCs in several formats:

    • Text format, this format exports the IOCs in a text file, one per line. All IOC types are included, each written as it is stored in IDSTower.

    • STIX 2.1 format, which is a JSON format used in TAXII-based Threat Intelligence Platforms. All IOC types are included, each as a STIX indicator.

    • Suricata Dataset format, used with Suricata Dataset feature for efficient IOCs alerting in Suricata. IPs and MD5, SHA1 and SHA256 hashes are written as they are (an IP:Port IOC is written as its IP only), and FQDN, Email and URL IOCs are Base64-encoded.

    • Suricata Datarep format, used with Suricata Datarep feature for IP Reputation alerting in Suricata. The same values as the Dataset format, each followed by a comma and the IOC’s score.

    • As Suricata Rules, This allows you to convert IOCs to Suricata Rules and normally used for compatibility reasons (Text). Only IP, IP:Port and FQDN IOCs are converted: each IP or IP:Port IOC becomes two rules (outbound and inbound connections) and each FQDN three (DNS query, HTTP host and TLS SNI). MD5, SHA1, SHA256, Email and URL IOCs are left out of this format.

    In this guide, we will select the “Text” format.

    Note

    The Dataset and Datarep formats write every IOC type that matches the export’s filters into the same file, while Suricata loads each dataset or datarep file as a single type. Use the Filtration settings (step 8) to limit such an export to one “Indicator Type”.

  7. If you selected the “As Suricata Rules” format, set the “SID Range Start”: the signature ID (SID) of the first generated rule, the following rules are numbered consecutively from it. It defaults to 500000000 and must be greater than 0, choose a range that no other ruleset loaded on the receiving Suricata uses. The SIDs are assigned every time the export is generated, so the SID of a given IOC’s rule can change when IOCs are added or removed.

  8. Choose the IOCs Filtration settings that you want to be applied to this export, you can either use the default settings (Exporting all enabled IOCs) or customize them for this export, filtering on the Indicator Value, Score, Type and Status.

    For this guide, we will use the default settings.

  9. Set the export’s Authentication Key. IDSTower fills in a random key, which you can keep or replace: the “show”, “copy” and “regenerate” links next to the field display, copy or replace it. A key you enter yourself must be 12 to 256 characters long and contain only letters, digits, - and _.

    The key becomes the authKey parameter of the export URL, so every system that downloads the export needs it. If you change the key later, the old URL stops working.

  10. Click on the “Add” button to save the export.

  11. Now you can see the newly added export in the exports list.

  12. Click on “view” link under “Export URL” Column to view the exported IOCs, now you can use this URL, which includes the authentication key, to download the IOCs file in any system. See Export URL for the URL format and the error responses.

    Note

    The export might take some time to generate, depending on the number of IOCs, once it is generated, it will be cached and served instantly until the IOCs or the export change. Append &disableCache=true to the URL to force a fresh file, see Caching.

    Note

    On a Standard license the export contains at most 10 IOCs (for the “As Suricata Rules” format, the rules generated from at most 10 IOCs). In every format except STIX 2.1, the comment line at the top of the file says so when the limit was reached.

    Note

    You can disable the export with the toggle switch in the “Status” column: switch it to “Disabled” to stop the export from being generated and served (requests to it are refused with HTTP 400), and switch it back to “Enabled” to serve it again.