System Requirements
This document lists the supported Operating Systems (OSs) for the Linux Agent and the Windows Agent.
Tip
Ensure your environment is compatible with the supported OSs.
An explanation of the Threat Stack support policy is available in the Threat Stack Support Policy article.
Threat Stack supports the following Agents:
- 2.3.4 (Host and Containerized). For more information, see Linux Agent Release Changelog.
- 2.3.3 (Host and Containerized). For more information, see Linux Agent Release Changelog.
- 2.3.2 (Host and Containerized). For more information, see Linux Agent Release Changelog.
Notes
- Due to a known Linux limitation, only one audit socket can be opened at a time to connect to the kernel’s audit system. As a result, any applications that create audit sockets, such as the auditd.service, conflict with the Threat Stack Agent over access to the audit system. The Linux Host Agent post-install scripts automatically disable auditd.service; however, due to Docker limitations, you need to manually disable auditd.service for the Container Agent. If you need to continue using auditd.service, then we suggest this workaround.
- Based on the Threat Stack Support Policy, on August 15, 2020, Threat StackⓇ removed publicly available packages for Linux Agents versions 1.8.0, 1.8.0.C, and all previous versions. Publicly available packages for Linux Agent version 1.9.0 and later remain accessible.
Threat Stack validates performance against the supported OS list. Customers who choose to use a different Linux OS will fall outside the Threat Stack Support Policy.
Threat Stack supports the following 64-bit Linux OSs:
Threat Stack validates performance against the supported OS list. Customers who choose to use a different Linux OS will fall outside the Threat Stack Support Policy.
Threat Stack supports the following ARM 64-bit architecture for AWS Graviton2 processors:
Threat Stack offers support for behavior and event monitoring on Docker containers running natively on the host.
| Version | Minimum Kernel | Notes |
|---|---|---|
| Docker 1.8.0 - 17.03-ce | 3.10 | Supported for Linux Agent 2.3.3c and newer versions |
| Docker 1.8.0 - 19.03-ce | 3.10 | Supported for Linux Agent 2.3.2c and older versions |
An explanation of the Threat Stack support policy is available in the Threat Stack Support Policy article.
Threat Stack supports the following Agents:
- 2.2.2w (Host). For more information, see Windows Agent Release Changelog.
- 2.2.1w (Host). For more information, see Windows Agent Release Changelog.
- 2.2.0w (Host). For more information, see Windows Agent Release Changelog.
An explanation of the Threat Stack support policy is available in the Threat Stack Support Policy article.
Threat Stack supports the following Windows Server OSs:
- Windows Server 2012
- Windows Server 2012 R2
- Windows Server 2016
- Windows Server 2019
An explanation of the Threat Stack support policy is available in the Threat Stack Support Policy article.
Threat Stack supports the following versions of the Threat Stack Container Security Monitoring for AWS Fargate:
- 1.0.0. For more information, see Threat Stack Container Security Monitoring for AWS Fargate Changelog.
An explanation of the Threat Stack support policy is available in the Threat Stack Support Policy article.
Threat Stack supports the following AWS Fargate distributions:
- 1.3.0
- 1.4.0
Threat Stack AppSec Monitoring supports the following versions of Node.js, Python and Ruby on the following operating systems (OSs):
The Threat Stack Cloud Security Platform (CSP) supports the latest versions of the following browsers:
- Preferred: Google Chrome (latest stable release)
- macOS Safari (latest stable release)
- Mozilla Firefox (latest stable release)
- Microsoft Edge (latest stable release)
Threat Stack Agents require outbound access (TCP 443) to communicate to the platform.
- app.threatstack.com (TCP 443)
- cssensors.threatstack.com (TCP 443)
Review Configure Agent Network Access article for additional whitelisting instructions.
Note
Threat Stack does not support proxying our platform with customer environments.