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

[Suggestion] Workarounds for case-insensitive exceptions use cases #6439

Open
banderror opened this issue Jan 21, 2025 · 2 comments
Open

[Suggestion] Workarounds for case-insensitive exceptions use cases #6439

banderror opened this issue Jan 21, 2025 · 2 comments
Assignees

Comments

@banderror
Copy link
Contributor

banderror commented Jan 21, 2025

What can we change to make the docs better?

We have this docs page that mentions that exceptions are case-sensitive and suggests only one workaround:

Rule exceptions are case-sensitive, which means that any character that’s entered as an uppercase or lowercase letter will be treated as such. In the event you don’t want a field evaluated as case-sensitive, some ECS fields have a .caseless version that you can use.

But there are many other workarounds that our users could use and should know about. It would be great to document them on a single consolidated page, so that our users don't have to learn the whole Elastic stack to come up with this list themselves.

This list of workarounds could be used as a starting point for collecting and documenting all of them.

Doc URL

Doc URL: https://www.elastic.co/guide/en/security/current/add-exceptions.html

Which documentation set needs improvement?

ESS and serverless

Software version

N/A

@banderror
Copy link
Contributor Author

@nastasha-solomon nastasha-solomon self-assigned this Jan 21, 2025
@nastasha-solomon
Copy link
Contributor

Thanks, @banderror! Assigning this to myself and will add it to a future sprint once I have a clear plan for docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants