Alan ve Belge Düzeyinde Güvenlik

In Elasticsearch, you might not want every user to see all data. Sometimes, certain users should only access specific parts of documents or only a subset of documents.

This is where fine-grained security comes in. It allows you to control access at a much more detailed level than just index permissions.

Field Level Security (FLS) lets you restrict which fields within a document a user can see. Imagine a product document with many fields.

• A sales agent might only need to see product_name and price.
• An inventory manager might need quantity and supplier_id.

FLS ensures users only retrieve the fields relevant to their role, hiding sensitive or irrelevant data.

FLS is configured within a user's role definition. You specify which fields are granted (allowed) or excepted (disallowed) for specific indices.

Using grant is generally safer as it follows a whitelist approach, only allowing explicitly listed fields.

Let's create a role named product_viewer. Users with this role can read documents from the products index, but only see the product_name and price fields.

Other fields like internal_cost or supplier_secret would be hidden.

Document Level Security (DLS) allows you to restrict which documents a user can see. Instead of hiding fields, DLS filters entire documents based on a query.

For example, a regional sales manager should only see sales orders from their specific region, not from other regions.

DLS is configured in a role using a query object. This query acts as a filter that is automatically applied to all search requests made by users assigned to that role.

Only documents matching this query will be returned to the user, regardless of their original search request.

Let's create a role named east_sales_manager. Users with this role can read documents from the sales_data index, but only those documents where the region field is east.

This effectively isolates sales data by region.

You can apply both Field Level Security and Document Level Security within a single role definition.

This means a user could be restricted to seeing only specific fields, AND only specific documents that match a filter query. This offers a very powerful way to create fine-grained access control.

When implementing FLS and DLS:

• Design roles carefully: Plan out exactly what each user group needs to see.
• Test thoroughly: Always verify that your roles provide the intended level of access, and nothing more.
• Use `grant` for FLS: Whitelisting fields is generally more secure than blacklisting.
• Keep DLS queries simple: Complex queries can impact performance.
• Least privilege: Always grant the minimum necessary permissions.

Which of the following statements about Elasticsearch Field and Document Level Security are true?

You've learned about Field Level Security (FLS) for restricting visible fields and Document Level Security (DLS) for filtering documents based on queries.

These powerful features, configured within user roles, enable you to create highly granular access control, ensuring users only see the data they are authorized for. This is crucial for maintaining data privacy and security in your Elasticsearch cluster.