-
Notifications
You must be signed in to change notification settings - Fork 179
Documents new RBAC for value reports #3817
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
Changes from 10 commits
379e164
c23c007
6f777b5
9409e81
5881e0a
5046908
51da14b
7796dc2
2e6db25
ef68d09
a206241
df53f89
9cb7ded
dd25dd2
b3999e5
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3,11 +3,12 @@ navigation_title: Value report | |
| applies_to: | ||
| serverless: | ||
| security: preview | ||
| stack: preview 9.3 | ||
| --- | ||
|
|
||
| # EASE Value Report | ||
| # Value report | ||
|
|
||
| The **Value report** page estimates your savings from using Elastic AI SOC Engine (EASE) for alert triage, in terms of **Analyst time saved** and **Cost Savings**. The message at the top of the page explains how those numbers were determined, and how many alerts were **Escalated** and **Filtered** by AI. | ||
| The **Value report** page estimates your savings from using Elastic's AI SOC features for alert triage, in terms of **Analyst time saved** and **Cost Savings**. The message at the top of the page explains how those numbers were determined, and how many alerts were **Escalated** and **Filtered** by AI. | ||
benironside marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| You can interact with the page in the following ways: | ||
|
|
||
|
|
@@ -18,3 +19,22 @@ You can interact with the page in the following ways: | |
| :::{image} /solutions/images/security-ease-value-report.png | ||
| :alt: The Value Report in an EASE project | ||
| ::: | ||
benironside marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| ## Requirements | ||
|
|
||
| ```{applies_to} | ||
| serverless: preview | ||
| stack: preview 9.3 | ||
| ``` | ||
|
Comment on lines
+16
to
+19
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nice usage of applies_to. One thing though:
Can you look into this? Happy to provide input about what to do once we know more exactly what is available where and what do we need to call out (or locate things) exactly
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good point Florent. This page was initially introduced just for the EASE feature tier of the Serverless Security project type. It's now available in the security analytics complete feature tier of Serverless Security — and also planned for Stack 9.3. I've added
What do you think?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Also, to address your comment about possibly linking to this page from this section, I'd recommend against it. The pages in that section are dedicated specifically to requirements — they aren't feature pages with requirements sections, such as the one this PR updates. I think the link would be out of place there.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Fine by me, thanks for explaining!
I understand your reasoning here but this isn't well supported in our docs system (it creates 2 pages with the same URL, especially in this case where the 2 pages are close in the TOC, could impair linking, etc.). So we must work around this. Since it's a core feature of EASE security projects, one approach we could take is:
Happy to hear your thoughts on this but I believe we have to find a way to keep only one occurrence of this page, that using snippets wouldn't make sense either here since the entirety of the page makes sense, and that better referencing it from the EASE docs should be sufficient.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Love this. Implemented it. Thanks!
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I reused much of the content from the EASE value reports page in the Features section. I think it works, but it might be a bit repetitive since the content now appears on both pages. Thoughts? |
||
|
|
||
| * To access the **Value report** page, your subscription must include AI-powered features. For {{sec-serverless}}, this means you need either the Elastic AI SOC Engine (EASE) or Security Analytics Complete [feature tier](https://www.elastic.co/pricing/serverless-security). | ||
|
|
||
| * To access the **Value report** page, you need the **SOC Management** Security sub-feature [{{kib}} privilege](/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-privileges.md). | ||
|
|
||
|  | ||
|
|
||
| ::::{note} | ||
| The following default roles have the **SOC Management** privilege by default: | ||
| - EASE feature tier: ` _search_ai_lake_soc_manager` | ||
| - Security Analytics Complete: `admin` and `soc_manager` | ||
| :::: | ||
Uh oh!
There was an error while loading. Please reload this page.