Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prevent access for users with DLS/FLS to the failure store #124634

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

slobodanadamovic
Copy link
Contributor

Failure store collects ingestion and mapping related failures when documents are written to a data stream. Indexing can fail and be captured in the failure store at any point in the ingest process.

The fields may not have been dropped or sanitized during ingestion processing, or the document may not be in the form expected by document/field-level security rules, either of which may lead to the document exposing sensitive information that would otherwise not be exposed if the document was successfully processed and ingested.

Since the DLS/FLS may not be applicable in the expected way, we here prevent access to the failure store for all users that have DLS/FLS restrictions.

Failure store collects ingestion and mapping related failures when
documents are written to a data stream. Indexing can fail and be captured
in the failure store at any point in the ingest process.

The fields may not have been dropped or sanitized during ingestion
processing, or the document may not be in the form expected by
document/field-level security rules, either of which may lead to the
document exposing sensitive information that would otherwise not be
exposed if the document was successfully processed and ingested.

Since the DLS/FLS may not be applicable in the expected way,
we here prevent access to the failure store for all users that have
DLS/FLS restrictions.
@slobodanadamovic slobodanadamovic added >non-issue :Security/Security Security issues without another label Team:Security Meta label for security team labels Mar 12, 2025
@slobodanadamovic slobodanadamovic self-assigned this Mar 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>non-issue :Security/Security Security issues without another label Team:Security Meta label for security team v9.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants