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
|**Network**| IP traffic filtering | Configurable |[Configure IP-based access restrictions](/deploy-manage/security/ip-traffic-filtering.md)|
22
+
|**Network**| IP traffic filtering | Configurable |[Configure IP-based access restrictions](/deploy-manage/security/ip-filtering-cloud.md)|
24
23
|| Private link | Configurable |[Establish a secure VPC connection](/deploy-manage/security/private-link-traffic-filters.md)|
25
24
|| Kubernetes Network Policies | N/A ||
26
25
|**Data**| Encryption at rest | Managed | You can [bring your own encryption key](/deploy-manage/security/encrypt-deployment-with-customer-managed-encryption-key.md)|
@@ -33,31 +32,31 @@ Select your deployment type below to see what's available and how implementation
33
32
:::{tab-item} Serverless
34
33
:sync: serverless
35
34
36
-
| Category| Security feature | Status |Description|
{{kib}} instances are automatically configured to connect securely to {{es}}, without requiring manual setup.
114
-
:::
114
+
::::
115
115
116
-
:::{tab-item} ECK
116
+
::::{tab-item} ECK
117
117
:sync: eck
118
118
119
119
HTTP TLS is automatically enabled for {{es}} and {{kib}} using self-signed certificates, with [several options available for customization](./k8s-https-settings.md), including custom certificates and domain names.
120
120
121
121
{{kib}} instances are automatically configured to connect securely to {{es}}, without requiring manual setup.
122
-
:::
122
+
::::
123
123
124
-
:::{tab-item} Self-managed
124
+
::::{tab-item} Self-managed
125
125
:sync: self
126
126
127
127
HTTP TLS certificates for {{es}} can be [automatically configured](self-auto-setup.md), or manually set up by following the steps in [Set up HTTP SSL](./set-up-basic-security-plus-https.md).
128
128
129
129
{{kib}} acts as both an HTTP client to {{es}} and a server for browser access. It performs operations on behalf of users, so it must be properly configured to trust the {{es}} certificates, and to present its own TLS certificate for secure browser connections. These configurations must be performed manually in self-managed deployments.
130
130
131
-
For environments with stricter security requirements, refer to [Mutual TLS authentication between {{kib}} and {{es}}](./kibana-es-mutual-tls.md).
131
+
:::{note}
132
+
The automatic configuration does not enable TLS on the {{kib}} HTTP endpoint. To encrypt browser traffic to {{kib}}, follow the steps in [](./set-up-basic-security-plus-https.md#encrypt-kibana-browser).
132
133
:::
133
134
135
+
For environments with stricter security requirements, refer to [Mutual TLS authentication between {{kib}} and {{es}}](./kibana-es-mutual-tls.md).
134
136
::::
135
137
138
+
:::::
139
+
136
140
## Certificates lifecycle [generate-certificates]
137
141
138
142
Managing certificates is critical for secure communications. Certificates have limited lifetimes and must be renewed before expiry to prevent service disruptions. Each deployment type provides different tools or responsibilities for managing certificates lifecycle.
0 commit comments