Skip to content

[Security] Add EA entry to Stack and Serverless release notes#6967

Open
natasha-moore-elastic wants to merge 2 commits into
mainfrom
ea-br-change
Open

[Security] Add EA entry to Stack and Serverless release notes#6967
natasha-moore-elastic wants to merge 2 commits into
mainfrom
ea-br-change

Conversation

@natasha-moore-elastic

@natasha-moore-elastic natasha-moore-elastic commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

Summary

Replaces elastic/kibana#273264. Adds a missing Entity Analytics breaking change entry to Security Stack and Serverless release notes.

Generative AI disclosure

  1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?
  • Yes
  • No

@github-actions

Copy link
Copy Markdown
Contributor

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

  • Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

@github-actions

github-actions Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

Elastic Docs Style Checker (Vale)

Summary: 1 suggestion found

💡 Suggestions (1): Optional style improvements. Apply when helpful.
File Line Rule Message
release-notes/elastic-cloud-serverless/breaking-changes.md 21 Elastic.WordChoice Consider using 'can, might' instead of 'May', unless the term is in the UI.

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.


```yaml
- names:
- ".entities.v2.latest.security_*"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@uri-weisman @jaredburgettelastic should .entities.v2.updates.security_* also be listed here, since it's mentioned in the list of index patterns above?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The .entities.v2.updates.security_* indices are for our internal use, and it's important that customers who enable Entity Analytics have read permissions on them.
That said, they're not critical for customers who only use the Entity Analytics overview page, since requests from that page don't target these indices.

@vishaangelova vishaangelova left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a tiny question/comment. LGTM!

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there an issue we could link to?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That was a while ago, and many PR were involved, but if I'm picking one, I think it will be this one.
CC @jared.burgett

privileges:
- read
```
::::

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
::::
For more information, view [#255800]({{kib-pull}}255800).
::::

Comment thread release-notes/elastic-security/breaking-changes.md
Co-authored-by: Visha Angelova <91186315+vishaangelova@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants