Secure Packetbeat
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. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. 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
Generally available
Stack
Generally available
The following topics provide information about securing the Packetbeat process and connecting to a cluster that has security features enabled.
You can use role-based access control and optionally, API keys to grant Packetbeat users access to secured resources.
After privileged users have been created, use authentication to connect to a secured Elastic cluster.
On Linux, Packetbeat can take advantage of secure computing mode to restrict the system calls that a process can issue.