Deployment

Introduction to TX Protect Deployment

The ThreatX platform is an agentless deployment that supports both AppSec and DevOps teams without locking either into architectural decisions or sacrificing their autonomy and flexibility. Our agentless architecture ensures that there is no need to disrupt either your applications or your operations.

The ThreatX platform is built for hybrid-cloud and on-premise environments and is application agnostic. If deploying the sensors in your environment, it deploys in minutes via Docker containers and blocks in hours, combining WAF, DDoS, bot, and API protection capabilities into one solution for all your applications and API endpoints.

We regularly update the sensors to provide you with the latest protection against the latest emerging attack patterns, new features, and better insights to the risk profile of your web applications and APIs For the latest information, see TX Protect Documentation.

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.

The ThreatX sensors were not designed to monitor site uptime. The ThreatX sensors only see and act on ingress HTTP(s) traffic. Due to the WAFs position in front of your inbound traffic, it is not afforded the same level of insight that a purpose-built monitoring solution would be able to provide.

How Can I Install TX Protect?

Purpose-built for the modern application landscape, ThreatX’s web stack agnostic, cloud-native, container-based options deploy in minutes and block in hours, combining WAF, DDoS, bot, and API protection capabilities into one solution for all your applications and API endpoints. TX Protect sensors work with web all stacks

Unlike other sensors such as plugins or source code scanners that need to be installed and upgraded frequently, the TX Protect sensor operates a reverse proxy. This means it decrypts traffic between web clients (such as browsers) on your network with APIs/origin servers before re-encrypting them for you – all without any complicated maintenance.

The TX Protect sensor containers are decoupled from the ThreatX Cloud Analytics platform and can be deployed virtually anywhere, delivering global flexibility and enterprise-grade scalability across complex, geographically dispersed application environments.

waap sensor

The ThreatX platform is flexible, adaptive to customer preference, and compliant with a range of customer network and computing infrastructures. Our agentless architecture lets us deploy our sensors into ThreatX’s globally hosted cloud environment, a public cloud infrastructure, and servers hosted by our customers in their data centers. We can honestly say “We’ve never met an application or API we can’t protect!”

Sensor Deployment Options

ThreatX offers four simple deployment methods for the Protect sensor.

ThreatX Cloud (managed)

ThreatX hosts and manages sensor deployment.

Virtual Machine (self-hosted)

ThreatX provides the customer with a machine image compatible with the customer’s cloud provider and the customer manages the image deployment, cloud hosting parameters, and cloud-specific support.

Docker (self-hosted)

ThreatX provides the customer with a Docker-based TX Protect sensor container deployed in the customer’s data center, and the customer manages the container deployment, container and node parameters, and container-specific support.

Hybrid Deployment

Mix of the ThreatX cloud, public cloud, and Docker deployments deployed when a single deployment model is not feasible. ThreatX will work with the customer to map out the optimal configurations and support models.

On-boarding Checklist

✔️ TX Protect Pre-Installation Checklist

Check the box next to any of the requirements that apply to your application…​

  • Processes requests with well-formed SQL queries (E.g., some help desk or bug-tracking software)

  • Processes requests with well-formed HTML (E.g., some content management systems)

  • Requires Two-way SSL/TLS (client authentication)

  • Uses web sockets

  • Requires a specific TLS version or cipher suite restriction (Default is TLS 1.2 and 1.3)

  • Supports unique business requirements necessitating custom WAF rules (E.g, blocking traffic from foreign countries)

  • Is located behind a firewall or content delivery network (CDN) in which connections from ThreatX service IP addresses would need to be explicitly allowed

If you checked one or more boxes, please contact ThreatX support for assistance with your TX Protect installation.