-
Notifications
You must be signed in to change notification settings - Fork 110
[Onboarding] Security quickstart guides #2017
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
base: main
Are you sure you want to change the base?
Conversation
I'm loving it! One suggestion: I would put the substeps inside a |
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.
Left some minor, mostly formatting suggestions – overall looks great!
solutions/security/get-started/get-started-endpoint-security.md
Outdated
Show resolved
Hide resolved
solutions/security/get-started/get-started-endpoint-security.md
Outdated
Show resolved
Hide resolved
solutions/security/get-started/get-started-endpoint-security.md
Outdated
Show resolved
Hide resolved
solutions/security/get-started/get-started-endpoint-security.md
Outdated
Show resolved
Hide resolved
solutions/security/get-started/get-started-endpoint-security.md
Outdated
Show resolved
Hide resolved
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.
Looks like a great start! Added suggestions for the rules section.
To learn how to view and manage all detection rules, refer to [Manage detection rules](/solutions/security/detect-and-alert/manage-detection-rules.md). | ||
:::: | ||
|
||
::::{step} Visualize and examine alert details |
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.
Part of me feels like this might be more appropriate under "Next steps" since all of the initial environment setup is complete. I also noticed that event analyzer is mentioned in step 3 here and later under "Next steps" here. If you decide to keep step 3 under the "Prerequisites" section, maybe remove the event analyzer mention from "Next steps"?
Contributes to https://github.com/elastic/docs-projects/issues/513.
Previews: