Home
Threat Intelligence
Learn how Threat Intelligence quickly detects threats to OT/IoT systems and defends against cyberattacks.
Configuration
Details on how to configure Threat Intelligence.
Threat Intelligence Feed
Troubleshooting
Error message: HTTP 406 Not Acceptable

Threat Intelligence
Learn how Threat Intelligence quickly detects threats to OT/IoT systems and defends against cyberattacks.
- Introduction
  An overview of Threat Intelligence.
- Requirements
  A description of the requirements that are necessary to install and use Threat Intelligence.
- Configuration
  Details on how to configure Threat Intelligence.
  - Configure a Threat Intelligence license
    Before you can use the Threat Intelligence, you must install a license.
  - Enable automatic updates
    If you are connected to Vantage, or a Central Management Console (CMC), you can enable automatic Threat Intelligence updates.
  - Configure manual updates
    If your sensor, or Central Management Console (CMC), is not connected to the internet, you can update Threat Intelligence manually.
  - Sensor-level contents management
    By default, Threat Intelligence contents can only be managed on the top-level sensor. However, this policy can be customized to allow any sensor in the solution to add, edit, enable or disable individual contents.
  - Manage contents at sensor level
    You can change the status of the Enable local contents toggle to change how the Threat Intelligence contents are managed.
  - Threat Intelligence Feed
- Maintenance
  Information on how to maintain Threat Intelligence.
- Print format documentation
  A list of all the print-format documentation that is available for Threat Intelligence.

Error message: HTTP 406 Not Acceptable

This error will show if the client sent a hypertext transfer protocol (HTTP) header, which the server cannot accept. The expected header can be found in the official TAXII 2.0 specification. This might happen if the client is not correctly configured to use TAXII 2.0 as its protocol, and instead uses TAXII 1.x or TAXII 2.1.

Procedure

Make sure that you specify that the server is TAXII 2.0.
If this does not solve the problem, contact our Customer Support team with this information:
- The name of the client
- The version of the client
- All logs that you can export
- A timestamp of when the error occurred
Note:
This information will be extremely valuable for further debugging.