- Observability: other versions:
- What is Elastic Observability?
- What’s new in 8.8
- Get started
- Application performance monitoring (APM)
- Logs
- Infrastructure monitoring
- Synthetic monitoring
- Get started
- Scripting browser monitors
- Configure lightweight monitors
- Manage monitors
- Work with params and secrets
- Analyze monitor data
- Monitor resources on private networks
- Use the CLI
- Configure projects
- Configure Synthetics settings
- Grant users access to secured resources
- Manage data retention
- Use Synthetics with traffic filters
- Migrate from the Elastic Synthetics integration
- Synthetics support matrix
- Synthetics Encryption and Security
- Uptime monitoring
- Real user monitoring
- Universal Profiling (beta)
- Alerting
- Service-level objectives (SLOs) (beta)
- Cases
- CI/CD observability
- Troubleshooting
- Fields reference
- Tutorials
- Monitor Amazon Web Services (AWS) with Elastic Agent
- Monitor Amazon Web Services (AWS) with Beats
- Monitor Google Cloud Platform
- Monitor a Java application
- Monitor Kubernetes
- Monitor Microsoft Azure with Elastic Agent
- Monitor Microsoft Azure with the Azure Native ISV Service
- Monitor Microsoft Azure with Beats
Synthetics Encryption and Security
editSynthetics Encryption and Security
editElastic Synthetics was designed with security in mind encrypting both persisted and transmitted data. This page catalogs the points within the Elastic Synthetics app data is either stored or transmitted in an encrypted fashion.
Synthetics UI (Kibana App)
editData is stored in Kibana Secure Saved Objects, with sensitive fields encrypted. These fields include your script source, params, and global params.
Synthetics Service
editThe Global Elastic Synthetics Service performs all communication of sensitive data (both internally, and with Kibana) over encrypted connections and encrypts all data persisted to disk as well.
Synthetics Private Locations
editIn Kibana configuration for private locations is stored in two places, Synthetics saved objects which always encrypt sensitive fields using Kibana Secure Saved Objects and also in Fleet, which uses unencrypted saved objects restricted by user permissions. For Elastic Cloud customers all data is secured on disk regardless of whether additional saved object encryption is present. See our Cloud Security Statement for more information. We recommend that self-managed customers encrypt disks for their Elasticsearch instances if this is a concern.
All data is encrypted in transit. See Elastic Agent configuration encryption for more details.