Skip to content

Commit e0d52ab

Browse files
updating description in DLS and FLS docs (#11594) (#11602)
1 parent 2aa2208 commit e0d52ab

File tree

2 files changed

+7
-4
lines changed

2 files changed

+7
-4
lines changed

_security/access-control/document-level-security.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,10 @@ redirect_from:
99
---
1010

1111
# Document-level security
12-
Document-level security lets you restrict a role to a subset of documents in an index. The easiest way to get started with document- and field-level security is to open OpenSearch Dashboards and choose **Security**. Then choose **Roles**, create a new role, and review the **Index Permissions** section, shown in the following image.
12+
13+
Document-level security (DLS) determines the documents that a role can retrieve during read operations, such as search and get. It does not restrict write operations. If a role has permissions to index, update, or delete documents in an index, it can still modify or remove documents that are hidden by DLS. Write behavior is determined solely by index permissions and action groups.
14+
15+
To get started with DLS, open OpenSearch Dashboards and choose **Security**. Then select **Roles**, create a new role, and review the **Index permissions** section shown in the following image.
1316

1417
![Document- and field-level security screen in OpenSearch Dashboards]({{site.url}}{{site.baseurl}}/images/security-dls.png)
1518

@@ -18,7 +21,7 @@ The maximum size for the document-level security configuration is 1024 KB (1,048
1821

1922
## Simple roles
2023

21-
Document-level security uses OpenSearch query domain-specific language (DSL) to define which documents a role grants access to. In OpenSearch Dashboards, choose an index pattern and provide a query in the **Document-level security** section:
24+
DLS uses OpenSearch query domain-specific language (DSL) to define the documents that a role is allowed to retrieve. In OpenSearch Dashboards, choose an index pattern and provide a query in the **Document-level security** section:
2225

2326
```json
2427
{

_security/access-control/field-level-security.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,9 @@ redirect_from:
1010

1111
# Field-level security
1212

13-
Field-level security lets you control which document fields a user can see. Just like [document-level security]({{site.url}}{{site.baseurl}}/security/access-control/document-level-security/), you control access by index within a role.
13+
Field-level security (FLS) controls the document fields that a role can read in an index. It applies only to read operations, such as search and get, and does not prevent users with write or delete permissions from indexing, updating, or deleting data in those fields. Similarly to [document-level security]({{site.url}}{{site.baseurl}}/security/access-control/document-level-security/), you configure FLS per index within a role.
1414

15-
The easiest way to get started with document- and field-level security is open OpenSearch Dashboards and choose **Security**. Then choose **Roles**, create a new role, and review the **Index permissions** section.
15+
The easiest way to get started with FLS is to open OpenSearch Dashboards and choose **Security**. Then choose **Roles**, create a new role, and review the **Index permissions** section.
1616

1717
---
1818

0 commit comments

Comments
 (0)