Skip to content

Conversation

@joepeeples
Copy link
Contributor

@joepeeples joepeeples commented Oct 18, 2022

Resolves #2547.

‼️ Note: Depends on #2526 being merged and published first, so that we can link from the Elastic Security UI page to the Indicators page (which doesn't exist yet in main). The link currently points to the Investigate landing page to keep CI from breaking.

Preview: These subsections in the Elastic Security UI topic:

@github-actions
Copy link

Documentation previews:

Might need adjusting once security-docs#2526 merges
@joepeeples joepeeples marked this pull request as ready for review October 18, 2022 17:47
Copy link
Contributor

@nastasha-solomon nastasha-solomon left a comment

Choose a reason for hiding this comment

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

🚀🚀🚀

Copy link
Contributor

@benironside benironside left a 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.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
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

Copy link
Contributor Author

@joepeeples joepeeples Oct 18, 2022

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.

Copy link
Contributor

@nastasha-solomon nastasha-solomon Oct 18, 2022

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>
@mergify

This comment was marked as resolved.

@joepeeples joepeeples merged commit 51c93f8 into main Oct 19, 2022
mergify bot pushed a commit that referenced this pull request Oct 19, 2022
* 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)
@joepeeples joepeeples deleted the 2547-UI-overview-updates branch October 19, 2022 00:25
joepeeples added a commit that referenced this pull request Oct 19, 2022
* 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[DOCS] Elastic Security UI updates

4 participants