-
Notifications
You must be signed in to change notification settings - Fork 206
[DOCS] Elastic Security UI updates #2594
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
Conversation
|
Documentation previews: |
Might need adjusting once security-docs#2526 merges
nastasha-solomon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀🚀🚀
benironside
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple of minor line edits, otherwise LGTM!
| [float] | ||
| === Intelligence | ||
|
|
||
| The Intelligence section contains the Indicators page, which collects data from enabled threat intelligence feeds and provides a centralized view of indicators of compromise (IoCs). Refer to <<investigate-events>> to learn more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| The Intelligence section contains the Indicators page, which collects data from enabled threat intelligence feeds and provides a centralized view of indicators of compromise (IoCs). Refer to <<investigate-events>> to learn more. | |
| The Intelligence section contains the Indicators page, which displays data from enabled threat intelligence feeds and provides a centralized view of indicators of compromise (IoCs). Refer to <<investigate-events>> to learn more. |
Collect seems to me like something that server agents do
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@benironside I think it's trying convey that the page gathers data from disparate sources/feeds and presents them in a single place. "Displays" sounds more general, like the data might have already been there, it just needed to be displayed.
@nastasha-solomon Any preference? This description was lifted from your PR on the Indicators page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm, I see your point @benironside but think I'd still prefer to keep "collects". The second part of the sentence already tells users that the Indicators page displays data ingested from enabled threat feeds.
Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com>
This comment was marked as resolved.
This comment was marked as resolved.
* First draft * Placeholder image for Indicators page Might need adjusting once security-docs#2526 merges * Apply suggestions from Ben's review Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com> * Remove extra line Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com> (cherry picked from commit 51c93f8)
* First draft * Placeholder image for Indicators page Might need adjusting once security-docs#2526 merges * Apply suggestions from Ben's review Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com> * Remove extra line Co-authored-by: Benjamin Ironside Goldstein <91905639+benironside@users.noreply.github.com> (cherry picked from commit 51c93f8) Co-authored-by: Joe Peeples <joe.peeples@elastic.co>
Resolves #2547.
main). The link currently points to the Investigate landing page to keep CI from breaking.Preview: These subsections in the Elastic Security UI topic: