IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

Use APM securely

edit

When setting up Elastic APM, it’s critical to ensure that application data is secure from start to finish. You should approach securing your application data from different perspectives:

What kind of data is collected?

Ensure that data doesn’t contain sensitive information like passwords, credit card numbers, health data, or other identifiable information.

Read more in Secure data.

How do APM agents and Elastic Agent communicate?

Ensure that any communication between APM agents and Elastic Agent are both encrypted and authenticated.

Read more in Secure communication with APM agents.

How do APM Server and the Elastic Stack communicate?

Use role-based access control to grant APM Server users access to secured resources. The roles that you set up depend on your organization’s security requirements and the minimum privileges required to use specific features.

Read more in Secure communication with the Elastic Stack.

Is FIPS compatibility available for APM Server?

[preview] This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Yes! FIPS compatible binaries are available for download. Look for the Linux x86_64 (FIPS) or Linux aarch64 (FIPS) platform option on the APM Server download page. Get more details about FIPS compatibility for APM Server and other ingest tools in FIPS mode for Ingest tools.

Who can use the Applications UI?

Use role-based access control to grant users access to features of the Applications UI.

Read more in Secure access to the Applications UI.