Skip to content

Commit f82bfbd

Browse files
Apply suggestions from code review
Co-authored-by: shainaraskas <[email protected]>
1 parent 3e9cf0a commit f82bfbd

File tree

4 files changed

+7
-7
lines changed

4 files changed

+7
-7
lines changed

deploy-manage/security/_snippets/cluster-comparison.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,17 +16,17 @@ Select your deployment type below to see what's available and how implementation
1616
:::{tab-item} {{ech}}
1717
:sync: cloud-hosted
1818

19-
| Category | Security feature | Status | Description |
19+
| Category | Security feature | Status | Notes |
2020
|------------------|------------|--------------|-------------|
2121
| **Communication** | TLS (HTTP Layer) | Fully managed | Automatically configured by Elastic |
2222
| | TLS (Transport Layer) | Fully managed | Automatically configured by Elastic |
2323
| **Network** | IP traffic filtering | Configurable | [Configure IP-based access restrictions](/deploy-manage/security/ip-traffic-filtering.md) |
24-
| | Private link | Configurable | [Establish secure VPC connection](/deploy-manage/security/private-link-traffic-filters.md) |
24+
| | Private link | Configurable | [Establish a secure VPC connection](/deploy-manage/security/private-link-traffic-filters.md) |
2525
| | Kubernetes Network Policies | N/A | |
2626
| **Data** | Encryption at rest | Managed | You can [bring your own encryption key](/deploy-manage/security/encrypt-deployment-with-customer-managed-encryption-key.md) |
2727
| | Secure settings | Configurable | Automatically protected by Elastic |
2828
| | Saved object encryption | Fully managed | Automatically encrypted by Elastic |
29-
| **User Session** | Kibana Sessions | Configurable | [Customize session parameters](/deploy-manage/security/kibana-session-management.md) |
29+
| **User session** | Kibana sessions | Configurable | [Customize session parameters](/deploy-manage/security/kibana-session-management.md) |
3030

3131
:::
3232

deploy-manage/security/_snippets/enable-security.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,4 +6,4 @@ For self-managed deployments, security features are automatically configured whe
66
If you want to use your own TLS certificates, then you should manually configure security.
77
:::
88

9-
Deployments managed by {{eck}}, {{ece}}, {{ech}}, and {{serverless-short}} automatically configure security by default. This includes setting the `elastic` user password, generating TLS certificates, and configuring {{kib}} to connect to {{es}} securely. Disabling security is not supported in these deployment types.
9+
Deployments managed by {{eck}}, {{ece}}, {{ech}}, as well as {{serverless-full}} projects, automatically configure security by default. This includes setting the `elastic` user password, generating TLS certificates, and configuring {{kib}} to connect to {{es}} securely. Disabling security is not supported in these deployment types.

deploy-manage/security/data-security.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ For {{ech}} deployments, instead of the default, Elastic-managed encryption, you
1515

1616

1717
:::{note}
18-
There is no encryption at rest out of the box for deployments orchestrated using [{{ece}}](secure-your-elastic-cloud-enterprise-installation.md) and [{{eck}}](secure-your-eck-installation.md), or for self-managed clusters. You must instead configure disk-level encryption on your hosts.
18+
There is no encryption at rest out of the box for deployments orchestrated using {{ece}} and {{eck}}secure-your-eck-installation.md, or for self-managed clusters. You must instead configure disk-level encryption on your hosts.
1919

2020
Configuring dm-crypt or similar technologies is outside the scope of the Elastic documentation, and issues related to disk encryption are outside the scope of support.
2121
:::

deploy-manage/security/self-setup.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ The automatic configuration:
2727

2828
This automatic setup is the quickest way to get started and ensures your cluster is protected by default.
2929

30-
::::{note}
30+
::::{warning}
3131
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).
3232
::::
3333

@@ -47,7 +47,7 @@ Each step builds on the previous one. For production environments, it’s strong
4747

4848
## Kibana security configuration
4949

50-
Refer to [](./using-kibana-with-security.md) for detailed guidance on the following security topics:
50+
Refer to [](./using-kibana-with-security.md) to learn how to implement the following security best practices for {{kib}}:
5151

5252
* Set an encryption key for clients sessions
5353
* Enable TLS on the HTTP service endpoint

0 commit comments

Comments
 (0)