Elastic Defend requirements
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless Security
Generally available
Stack
Generally available
To properly deploy Elastic Defend on macOS without a Mobile Device Management (MDM) profile, you must manually enable additional permissions on the host before Elastic Endpoint—the installed component that performs Elastic Defend's threat monitoring and prevention—is fully functional. For more information, refer to Enable Elastic Defend access on macOS.
For information about supported operating systems, refer to the Elastic Support Matrix.
| Requirement | Value |
|---|---|
| CPU | Under 2% |
| Disk space | 1 GB |
| Resident set size (RSS) memory | 500 MB |
Elastic Endpoint writes log files on the host. These logs rotate automatically and are not configurable. Each file can grow to 25 MB, and Elastic Endpoint keeps up to 4 files.
Elastic Endpoint supports Elliptic Curve (EC) keys and all standard TLS common configuration options.
Elastic Endpoint does not support Elliptic Curve (EC) keys for SSL certificates. If an EC key is configured, the policy response displays the error: Unsupported or invalid PEM format.