You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: deploy-manage/deploy/cloud-enterprise/configure.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ Other sections of the documentation describe important ECE features to consider:
33
33
*[Configure allocator affinity](configure-allocator-affinity.md) - Determine how ECE distributes your Elastic Stack deployments across allocators.
34
34
*[Change allocator disconnect timeout](change-allocator-disconnect-timeout.md) - Configure how long ECE waits before considering allocators to be disconnected.
35
35
*[Migrate ECE to Podman hosts](./migrate-ece-to-podman-hosts.md) - If you are running a Docker based installation and you need to migrate to Podman.
36
-
*[Migrate ECE on Podman hosts to SELinux in enforcing mode](migrate-ece-on-podman-hosts-to-selinux-enforce.md) - Migrate ECE to SELinux in `enforcing` mode using Podman.
36
+
*[Migrate ECE on Podman hosts to SELinux in enforcing mode](../../security/secure-your-elastic-cloud-enterprise-installation/migrate-ece-on-podman-hosts-to-selinux-enforce.md) - Migrate ECE to SELinux in `enforcing` mode using Podman.
Copy file name to clipboardExpand all lines: deploy-manage/deploy/cloud-enterprise/deploy-an-orchestrator.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,5 +52,5 @@ To start orchestrating your {{es}} clusters, refer to [](./working-with-deployme
52
52
The following tasks are only needed on certain circumstances:
53
53
54
54
*[Migrate ECE to Podman hosts](./migrate-ece-to-podman-hosts.md)
55
-
*[Migrate ECE on Podman hosts to SELinux enforce](./migrate-ece-on-podman-hosts-to-selinux-enforce.md)
55
+
*[Migrate ECE on Podman hosts to SELinux enforce](./../../security/secure-your-elastic-cloud-enterprise-installation/migrate-ece-on-podman-hosts-to-selinux-enforce.md)
Copy file name to clipboardExpand all lines: deploy-manage/deploy/cloud-enterprise/enable-custom-endpoint-aliases.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,6 +29,7 @@ After installing or upgrading to version 2.10 or later:
29
29
* For Kibana, the certificate needs to allow for ***.kb.<your-domain>**
30
30
* For APM, the certificate needs to allow for ***.apm.<your-domain>**
31
31
* For Fleet, the certificate needs to allow for ***.fleet.<your-domain>**
32
+
* For Universal Profiling, the certificate needs to allow for ***.profiling.<your-domain>** and ***.symbols.<your-domain>**
32
33
33
34
3. In the **Platform** menu, select **Settings**.
34
35
4. Under the **Enable custom endpoint alias naming**, toggle the setting to allow platform administrators and deployment managers to choose a simplified, unique URL for the endpoint.
Copy file name to clipboardExpand all lines: deploy-manage/monitor/stack-monitoring/collecting-log-data-with-filebeat.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ If you’re using {{agent}}, do not deploy {{filebeat}} for log collection. Inst
27
27
28
28
2. Identify which logs you want to monitor.
29
29
30
-
The {{filebeat}} {{es}} module can handle [audit logs](../logging-configuration/logfile-audit-output.md), [deprecation logs](../logging-configuration/elasticsearch-log4j-configuration-self-managed.md#deprecation-logging), [gc logs](elasticsearch://reference/elasticsearch/jvm-settings.md#gc-logging), [server logs](../logging-configuration/elasticsearch-log4j-configuration-self-managed.md), and [slow logs](elasticsearch://reference/elasticsearch/index-settings/slow-log.md). For more information about the location of your {{es}} logs, see the [path.logs](../../deploy/self-managed/important-settings-configuration.md#path-settings) setting.
30
+
The {{filebeat}} {{es}} module can handle [audit logs](../../security/logging-configuration/logfile-audit-output.md), [deprecation logs](../logging-configuration/elasticsearch-log4j-configuration-self-managed.md#deprecation-logging), [gc logs](elasticsearch://reference/elasticsearch/jvm-settings.md#gc-logging), [server logs](../logging-configuration/elasticsearch-log4j-configuration-self-managed.md), and [slow logs](elasticsearch://reference/elasticsearch/index-settings/slow-log.md). For more information about the location of your {{es}} logs, see the [path.logs](../../deploy/self-managed/important-settings-configuration.md#path-settings) setting.
31
31
32
32
::::{important}
33
33
If there are both structured (`*.json`) and unstructured (plain text) versions of the logs, you must use the structured logs. Otherwise, they might not appear in the appropriate context in {{kib}}.
@@ -190,7 +190,7 @@ After you’ve enabled log delivery on your deployment, you can [add the Elastic
190
190
191
191
#### For Kibana: [ece-extra-logging-features-kibana]
192
192
193
-
* [Audit logging](../logging-configuration/enabling-audit-logs.md) - logs security-related events on your deployment
193
+
* [Audit logging](../../security/logging-configuration/enabling-audit-logs.md) - logs security-related events on your deployment
194
194
195
195
After you’ve enabled log delivery on your deployment, you can [add the Kibana user settings](../../deploy/cloud-enterprise/edit-stack-settings.md) to enable this feature.
This section covers how to secure your Elastic environment. Learn how to implement TLS encryption, network security controls, and data protection measures.
78
+
This overview page helps you understand Elastic's security capabilities across different deployment types. You'll find:
79
+
80
+
- Key security features for protecting your Elastic deployment
81
+
- Security capabilities specific to each deployment type
82
+
- Comparison tables showing feature availability and configurability by deployment type
83
+
- Links to detailed implementation guides
79
84
80
85
## Security overview
81
86
82
-
An Elastic implementation comprises many moving parts: {es} nodes forming the cluster, {kib} instances, additional stack components such as Logstash and Beats, and various clients and integrations communicating with your deployment.
87
+
An Elastic implementation comprises many moving parts: {{es}} nodes forming the cluster, {{kib}} instances, additional stack components such as Logstash and Beats, and various clients and integrations communicating with your deployment.
83
88
84
89
To keep your data secured, Elastic offers comprehensive security features that:
85
90
- Prevent unauthorized access to your deployment
86
91
- Encrypt communications between components
87
92
- Protect data at rest
88
93
- Secure sensitive settings and saved objects
89
94
90
-
Security requirements and capabilities vary by deployment. Features may be managed automatically by Elastic, require configuration, or must be fully self-managed. Refer to [Security by deployment type](#security-by-deployment-type) for details.
95
+
:::{note}
96
+
The availability and configurability of security features vary by deployment type. Refer to [Security by deployment type](#security-features-by-deployment-type) for a comparison table.
97
+
:::
91
98
92
-
::::{tip}
93
-
See the [Deployment overview](/deploy-manage/deploy.md) to understand your options for deploying Elastic.
94
-
::::
99
+
## Security topics
95
100
96
-
### Security by deployment type
101
+
The documentation is organized into three main areas.
97
102
98
-
Security features have one of these statuses across deployment types:
103
+
On every page, you'll see deployment type indicators that show which content applies to specific deployment types. Focus on sections tagged with your deployment type and look for subsections specifically addressing your deployment model.
99
104
100
-
| Status | Description |
101
-
|--------|-------------|
102
-
|**Managed**| Handled automatically by Elastic with no user configuration needed |
103
-
|**Configurable**| Built-in feature that needs your configuration (like IP filters or passwords) |
104
-
|**Self-managed**| Infrastructure-level security you implement and maintain |
105
-
|**N/A**| Not available for this deployment type |
105
+
### 1. Secure your orchestrator
106
106
107
-
#### Communication security
107
+
The [security of your orchestrator](security/secure-hosting-environment.md) forms the foundation of your overall security posture. This section covers environment-specific security controls:
-[**Elastic Cloud on Kubernetes**](security/secure-your-eck-installation.md)
113
112
114
-
#### Network security
113
+
:::{note}
114
+
There is no orchestration layer for self-managed deployments because you directly control the host environment. Refer to [](security/manually-configure-security-in-self-managed-cluster.md) to learn more about securing self-managed installations.
[Secure your clients and integrations](security/secure-clients-integrations.md) to ensure secure communication between your applications and Elastic:
136
131
137
-
### Using this documentation
132
+
-[**Client security**](security/httprest-clients-security.md): Best practices for securely connecting applications to {{es}}
133
+
-**Integration security**: Secure configuration for Beats, Logstash, and other integrations
138
134
139
-
Throughout this security documentation, you'll see deployment type indicators that show which content applies to specific deployment types. Each section clearly identifies which deployment types it applies to, and deployment-specific details are separated within each topic.
135
+
## Security features by deployment type
140
136
141
-
To get the most relevant information for your environment, focus on sections tagged with your deployment type and look for subsections specifically addressing your deployment model.
137
+
Security feature availability varies by deployment type, with each feature having one of the following statuses:
142
138
143
-
## Security topics
139
+
|**Status**|**Description**|
140
+
|--------|-------------|
141
+
|**Managed**| Handled automatically by Elastic with no user configuration needed |
142
+
|**Configurable**| Built-in feature that needs your configuration (like IP filters or passwords) |
143
+
|**Self-managed**| Infrastructure-level security you implement and maintain |
144
+
|**N/A**| Not available for this deployment type |
144
145
145
-
This security documentation is organized into four main areas:
146
+
Select your deployment type below to see what's available and how implementation responsibilities are distributed:
146
147
147
-
% TODO: Add links to the sections below
148
+
::::{tab-set}
149
+
:group: deployment-type
148
150
149
-
### 1. Secure your hosting environment
151
+
:::{tab-item} Elastic Cloud Hosted
152
+
:sync: cloud-hosted
150
153
151
-
The security of your hosting environment forms the foundation of your overall security posture. This section covers environment-specific security controls:
0 commit comments