Skip to content

[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

Merged
merged 43 commits into from
Jul 17, 2025
Merged

[Onboarding] Security quickstart guides #2017

merged 43 commits into from
Jul 17, 2025

Conversation

jmikell821
Copy link
Contributor

@jmikell821 jmikell821 commented Jul 3, 2025

@jmikell821 jmikell821 self-assigned this Jul 3, 2025
@jmikell821 jmikell821 requested review from a team as code owners July 3, 2025 04:20
@jmikell821 jmikell821 requested a review from a team July 3, 2025 04:39
@theletterf
Copy link
Contributor

I'm loving it! One suggestion: I would put the substeps inside a dropdown directive to reduce cognitive load and make the procedure look leaner.

Copy link
Contributor

@natasha-moore-elastic natasha-moore-elastic left a 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!

Copy link
Contributor

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

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"?

@jmikell821 jmikell821 changed the title [Onboarding] SIEM guide [Onboarding] Security quickstart guides Jul 10, 2025
Copy link
Contributor

@natasha-moore-elastic natasha-moore-elastic left a comment

Choose a reason for hiding this comment

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

Mostly minor suggestions, looks good overall!

4. Give the integration a name and enter an optional description.
5. Next, choose your deployment option. An agent-based deployment requires you to deploy and manage {{agent}} in the cloud account you want to monitor, whereas an agentless deployment allows you to collect cloud posture data without having to manage the {{agent}} deployment in your cloud. For simplicity, select **Agentless**.
6. Next, in the **Setup Access** section, choose your preferred authentication method — direct access keys (recommended) or temporary keys. For this guide, we'll use direct access keys.
7. Expand the Steps to Generate AWS Account Credentials, and follow the instructions.
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
7. Expand the Steps to Generate AWS Account Credentials, and follow the instructions.
7. Expand the Steps to Generate AWS Account Credentials, and follow the instructions.

I would either bold or lowercase "Steps to Generate AWS Account Credentials"


::::{step} Modify policy configuration settings

After you install the {{agent}} with {{elastic-defend}}, the Endpoint Security ({{elastic-defend}}) detection rule is automatically enabled, which also enables several endpoint protections—such as preventions against malware, ransomware, memory threats, and other malicious behavior—on protected hosts. This means that not only does {{elastic-defend}} monitor for these behaviors and generates an alert if any are detected, but it also blocks it. Due to this maximum level of protection, we recommend modifying the policy to _detect_ instead of _prevent_ so that only an alert will be generated, and you can decide how to respond to the threat. Then, closely monitor which alerts and how many are generating over a specific time period before enabling higher protection, if needed.
Copy link
Contributor

Choose a reason for hiding this comment

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

At the Defend installation, Endpoint Security (Elastic Defend) is automatically installed and enabled. The rule does not enable endpoint protections, those need to be set up by the user. The rules will just create SIEM alerts for either - detection or protection alerts.


:::{note}
You must install _and_ enable the rule for it to start running; therefore, do not select the **Install _x_ rules** option.
:::
Copy link
Contributor

Choose a reason for hiding this comment

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

I think "do not select the Install x rules option" is a bit too strong statement, I suggest saying something "to speed up the process for the quick start, select Install and Enable option. The alternative is to enable a rule once it is installed from Installed rules table.

Copy link
Contributor

Choose a reason for hiding this comment

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

I've edited this text in 13643c6. If it's not what you had in mind, lmk!

Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
lcawl and others added 15 commits July 15, 2025 12:08
Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
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.

Don't see any major issues to fix. The guides look great!

@lcawl
Copy link
Contributor

lcawl commented Jul 16, 2025

I've taken a crack at #2017 (comment) in 414dd02. If it's not what you had in mind, @approksiu lmk and worst case we can comment it out for now.

Copy link
Contributor

@approksiu approksiu left a comment

Choose a reason for hiding this comment

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

Looks good to me from the detection POV, just 1 dot is missing.

@lcawl lcawl enabled auto-merge (squash) July 17, 2025 15:53
@lcawl lcawl merged commit c6a7542 into main Jul 17, 2025
8 of 9 checks passed
@lcawl lcawl deleted the gs-sec-siem-guide branch July 17, 2025 16:03
jmikell821 added a commit that referenced this pull request Jul 25, 2025
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.

6 participants