Managing Sensors
Introduction
Sensors are managed by your local administrator or the ThreatX SOC depending on if you self-host or are hosted within the ThreatX cloud, respectively.
You can view the on-premises deployed sensors and their status from the ThreatX user interface,
. The Sensor Keys tab lists the keys used with the sensors. You add a key only when deploying a sensor and delete a key when the associated sensor is no longer in use.The sensor IP addresses are available in the ThreatX user interface, as described in the Firewall settings section. These addresses must be added to the whitelist in your environment to ensure traffic can reach your application.
If the ThreatX SOC hosts your sensors, you might notice the number of sensors fluctuate, or that an individual sensor’s uptime has changed. This is because sensors are designed to be added, removed, upgraded, and replaced as needed to ensure optimal site availability and protection. For the latest information, see our release notes.
If you are contemplating deploying new sites, new tech stacks, or new architecture, contact the ThreatX SOC.
For more information about deploying sensors, see the Deployment guides in the navigation bar to the left.
Firewall settings
Service IP addresses
IP addresses that represent the ThreatX sensors. These IP addresses must be whitelisted in your environment to ensure traffic can reach your application.
Sensor DNS Targets
CNAME records you can use to ensure HTTP and HTTPS traffic reaches your sensors. The CNAME provided for your tenant is all you need for all your sites. The ThreatX sensor is Server Name Indication (SNI) aware and refers to the hostname provided in each request when visualizing and routing traffic. Request traffic for each of your sites is routed to the backend you defined for that site on the site’s details page.
The ThreatX api.threatx.com/tx_api/v2/services endpoint list command returns the service IP addresses, but not the CNAME records.
== Configuring notifications
|
There are two types of notifications:
-
Analytical events
-
Maintenance and system status events
For information about receiving logs, Observability. |