Skip to content

[Security] Remove SIEM Readiness export report section - #7977

Open
natasha-moore-elastic wants to merge 1 commit into
mainfrom
issue-6503
Open

[Security] Remove SIEM Readiness export report section#7977
natasha-moore-elastic wants to merge 1 commit into
mainfrom
issue-6503

Conversation

@natasha-moore-elastic

Copy link
Copy Markdown
Contributor

Resolves #6503

Removes the "Export a report" section from the SIEM Readiness page, since the feature isn't implemented.

There's no export or download control in the SIEM Readiness UI on Kibana main. The only implementation work so far is a draft proof of concept (elastic/kibana#269240), so the section didn't apply to 9.4 or 9.5.

Made with Cursor

Co-authored-by: Cursor <cursoragent@cursor.com>
@natasha-moore-elastic
natasha-moore-elastic requested a review from a team as a code owner August 17, 2026 10:41
@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 Aug 17, 2026

Copy link
Copy Markdown
Contributor

🔍 Preview links for changed docs

@github-actions

Copy link
Copy Markdown
Contributor

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!


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.

@niros1

niros1 commented Aug 18, 2026

Copy link
Copy Markdown

@JordanSh @animehart @natasha-moore-elastic I think we should remove the whole documentation of SIEM readiness as its no longer exposed to our users.

@natasha-moore-elastic

natasha-moore-elastic commented Aug 18, 2026

Copy link
Copy Markdown
Contributor Author

@JordanSh @animehart @natasha-moore-elastic I think we should remove the whole documentation of SIEM readiness as its no longer exposed to our users.

Hi @niros1, thanks for letting us know about the change.

I had a quick look, and it seems SIEM Readiness is still in the product, just hidden by default from 9.5 onwards. PR #278934 ("SIEM Readiness Feature Flag Hide") put the experience behind the securitySolution:enableSiemReadiness advanced setting, which defaults to off, and that was backported to 9.5 in #279319. That matches what I'm seeing in a 9.5.1 test environment, where the page appears once I turn the setting on.

If that sounds right to you, here's what we'd propose instead of removing the page:

  • Document the new advanced setting introduced in 9.5 next to other Security solution advanced settings.
  • Expand the requirements section on the SIEM Readiness page to explain that from 9.5 onwards users need to enable the setting to access the feature.

The reason we'd keep the page is that our docs are cumulative: a single page serves every supported version at once. Removing it would take the content away from 9.4 users, who still get SIEM Readiness by default, as well as anyone on 9.5+ who enables the setting.

Also, one process request for next time: for any user-facing changes like this, it would be really helpful if the team could open a docs issue in this repo (elastic/docs-content) against the release the change is going into. That way we will know about upcoming changes and can document them in time for the release. Thanks again! 🙏

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.

[Bug]Documentation contains Information of unimplemented feature Export Report

3 participants