Skip to content
Merged
Show file tree
Hide file tree
Changes from 5 commits
Commits
Show all changes
43 commits
Select commit Hold shift + click to select a range
01a1ed3
Create get-started-detect-with-siem.md
jmikell821 Jun 30, 2025
55a8a93
Update get-started-detect-with-siem.md
jmikell821 Jul 2, 2025
1398ade
Changes to GS files.
jmikell821 Jul 3, 2025
5e795ee
Saving changes.
jmikell821 Jul 4, 2025
72ddabb
Adds file to TOC.
jmikell821 Jul 4, 2025
e5a2ea9
Merging feedback + adding some more content
jmikell821 Jul 8, 2025
366b047
Merge branch 'main' into gs-sec-siem-guide
jmikell821 Jul 8, 2025
d620f71
Fixing ref link + more edits.
jmikell821 Jul 8, 2025
c07f7a3
Saving building blocks for cloud security
jmikell821 Jul 10, 2025
f6764e8
Merge branch 'main' into gs-sec-siem-guide
jmikell821 Jul 10, 2025
3a58af1
Saving changes + updating main branch
jmikell821 Jul 10, 2025
eb55753
Merge branch 'gs-sec-siem-guide' of github.com:elastic/docs-content i…
jmikell821 Jul 10, 2025
fc4ca94
Saving...
jmikell821 Jul 13, 2025
698fe10
Some more edits...
jmikell821 Jul 14, 2025
d8ca24b
Merge branch 'main' into gs-sec-siem-guide
lcawl Jul 14, 2025
6e9a726
Update solutions/security/get-started.md
lcawl Jul 15, 2025
d430f21
Update solutions/security/get-started.md
lcawl Jul 15, 2025
8c8db2f
Update solutions/security/get-started/get-started-cloud-security.md
lcawl Jul 15, 2025
1663416
Update solutions/security/get-started/get-started-cloud-security.md
lcawl Jul 15, 2025
726b74b
Update solutions/security/get-started/get-started-cloud-security.md
lcawl Jul 15, 2025
379d2d1
Update solutions/security/get-started/get-started-detect-with-siem.md
lcawl Jul 15, 2025
1da57ed
Update solutions/security/get-started/get-started-detect-with-siem.md
lcawl Jul 15, 2025
ac11df3
Update solutions/security/get-started/get-started-detect-with-siem.md
lcawl Jul 15, 2025
1db831d
Update solutions/security/get-started/get-started-endpoint-security.md
lcawl Jul 15, 2025
c24626c
Update solutions/security/get-started/get-started-endpoint-security.md
lcawl Jul 15, 2025
a7a9d0f
Update solutions/security/get-started/get-started-endpoint-security.md
lcawl Jul 15, 2025
60fb794
Update solutions/security/get-started/get-started-cloud-security.md
lcawl Jul 15, 2025
ae04263
Update solutions/security/get-started/get-started-cloud-security.md
lcawl Jul 15, 2025
e6acf64
Update solutions/security/get-started/get-started-cloud-security.md
lcawl Jul 15, 2025
807ae30
Update solutions/security/get-started/get-started-cloud-security.md
lcawl Jul 15, 2025
3c85d8d
Update solutions/security/get-started/get-started-endpoint-security.md
lcawl Jul 15, 2025
e9e1792
Update solutions/security/get-started/get-started-detect-with-siem.md
lcawl Jul 15, 2025
18eae0c
Update solutions/security/get-started/get-started-cloud-security.md
lcawl Jul 15, 2025
8b48968
Update solutions/security/get-started/get-started-detect-with-siem.md
lcawl Jul 15, 2025
06a7c1d
Update solutions/security/get-started/get-started-detect-with-siem.md
lcawl Jul 15, 2025
b9e32ea
Update solutions/security/get-started/get-started-detect-with-siem.md
lcawl Jul 15, 2025
f9f2951
Revert change in get-started-detect-with-siem.md
lcawl Jul 16, 2025
a314cc5
Merge branch 'main' into gs-sec-siem-guide
lcawl Jul 16, 2025
13643c6
Remove note
lcawl Jul 16, 2025
414dd02
Address policy configuration feedback
lcawl Jul 16, 2025
21bbbe1
Fix typo
lcawl Jul 17, 2025
a34a171
Merge branch 'main' into gs-sec-siem-guide
lcawl Jul 17, 2025
f596630
Merge branch 'main' into gs-sec-siem-guide
lcawl Jul 17, 2025
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added solutions/images/security-gs-siem-view-type.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
135 changes: 135 additions & 0 deletions solutions/security/get-started/get-started-detect-with-siem.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,135 @@
---
navigation_title: Detect and respond to threats with SIEM
description: An introduction to detecting threats with SIEM in {{elastic-sec}}.
applies_to:
serverless:
products:
- id: security
---

# Quickstart: Detect and respond to threats with SIEM

Elastic Security is a unified security solution that brings together SIEM, endpoint security, and cloud security into a single platform. This makes it easier to protect, investigate, and respond to security events from all areas within your environment.

In this guide, we'll learn how to use some of {{elastic-sec}}'s SIEM features to detect, investigate, and respond to threats.

## Prerequisites

To get started exploring {{elastic-sec}}, log in to your {{sec-serverless}} project. If you don't have one yet, refer to [Create a Security project](/solutions/security/get-started/create-security-project.md).

:::::{stepper}

::::{step} Add data using Elastic Defend

Before you can start using {{elastic-sec}}, you need to choose an integration to start collecting and analyzing your data. For this guide, we're going to use the {{elastic-defend}} integration. {{elastic-defend}} detects and protects endpoints from malicious activity and provides automated response options before damage and loss occur.

1. On the Get started home page, in the **Ingest your data** section, select **Elastic Defend**, then click **Add Elastic Defend**.
2. On the next page that says, "Ready to add your first integration?", click **Install {{agent}}** in the lower-right corner. Although you *can* skip agent installation, for optimal event collection and threat detection, we recommend that you do not skip it.

3. Select the appropriate operating system tab, then copy the commands.
4. On the host, open a command-line interface and navigate to the directory where you want to install {{agent}}. Paste and run the commands to download, extract, enroll, and start {{agent}}. Once the agent is installed successfully, you'll see an "Agent enrollment confirmed" message.
5. Click **Add the integration**, then Confirm incoming data on the next page.
After a few minutes, you should see the agent receiving data.

:::{image} /solutions/images/security-gs-siem-install-agent.png
:alt: Alerts page with visualizations section collapsed
:screenshot:
:::

:::{important}
If you’re using macOS, some versions may require you to grant {{elastic-endpoint}} Full Disk Access to different kernels, system extensions, or files. Refer to [Elastic Defend requirements](/solutions/security/configure-elastic-defend/elastic-defend-requirements.md) for more information.
:::
::::

::::{step} Add Elastic detection prebuilt rules

Detection rules allow you to proactively monitor your environment by searching for source events, matches, sequences, or machine learning job anomaly results that meet their criteria. When a rule’s criteria are met, {{elastic-sec}} generates an alert. While you can create your own rules tailored for your environment, Elastic ships out-of-the-box prebuilt rules that you can install.

To install and enable Elastic's prebuilt detection rules:
1. On the Get Started page, scroll down to the **Configure rules and alerts** section.
2. At the top of the page, click **Add Elastic rules**. The badge next to it shows the number of prebuilt rules available for installation.

The next pages displays the list of rules. Click on a rule name to view its details before you install it.
3. Use the search bar and **Tags** filter to find the rules you want to install. For example, to filter by operating system, search for the appropriate OS from the **Tags** menu (such as `macOS`). We recommend installing all the rules for your operating system, but you can install whichever rules you're comfortable with to start. You can always install more later.
4. Select the check box next to rules you want to install. To select all rules on the page, select the check box to the left of the **Rule** column heading.
5. Click ![Vertical boxes button](/solutions/images/serverless-boxesVertical.svg "") → **Install and enable** to install and start running the rules. Once you enable a rule, it starts running on its configured schedule.

:::{image} /solutions/images/security-gs-siem-install-rules.png
:alt: Alerts page with visualizations section collapsed
:screenshot:
:::

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.

Is this step also a prerequisite? The current structure suggests that all steps in the guide are prerequisites:
image

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Prereqs are just pre-steps before beginning - but it looks like this on my end:
2025-07-07_11-09-11
I'll double check the formatting.

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


Now that you've installed and enabled rules, it's time to monitor the {{security-app}} to see if you receive any alerts. Remember, an alert is generated if any of the rule's criteria are met. {{elastic-sec}} provides several tools for investigating security events:

* **Alerts table:** View all generated alerts in a comprehensive list, apply filters for a customized view, and drill down into details.
* **Timeline:** Explore alerts in a central, interactive workspace. Create customized queries and collaborate on incident analysis by combining data from various sources.
* **Visual event analyzer:** View a graphical timeline of processes that led up to the alert and the events that occurred immediately after.
* **Session View:** Examine Linux process data and real-time data insights.

To view a quick video tutorial on how to use these features, on the Get Started page, scroll down to **View alerts**, select an alert tool from the list, and click **Play Video** on the right.

For this guide, let's take a closer look at how to visualize and examine alert details by viewing the Alerts page.

:::{note}
If you don't have any alerts yet in your environment, that's great news! You can use the [Elastic demo server](https://demo.elastic.co/) to explore alerts.
:::

To access the Alerts page, do one of the following:
* On the Get Started page, scroll down to the View alerts section, then click **View Alerts** at the bottom.
* From the left navigation menu, select **Alerts**.

:::{image} /solutions/images/security-gs-siem-alerts-pg.png
:alt: Alerts page overview
:screenshot:
:::

At the top of the Alerts page are four filter controls: **Status**, **Severity**, **User**, and **Host** that you can use to filter your alerts view. With the exception of **Status**, you can [edit and customize](/solutions/security/detect-and-alert/manage-detection-alerts.md#drop-down-filter-controls) these to your preference.


In the visualization section, you can group alerts by a specific view type:
* **Summary:** Shows how alerts are distributed across specific indicators.
* **Trend:** Shows the occurrence of alerts over time.
* **Counts:** Shows the count of alerts in each group. Although there are default values, you can change the `Group by` parameters.
* **Treemap:** Shows the distribution of alerts as nested, proportionally-sized and color-coded tiles based on the number of alerts, and the alert's risk score. This view is useful to quickly pinpoint the most critical alerts.

:::{image} /solutions/images/security-gs-siem-view-type.png
:alt: Alerts page, view by type
:screenshot:
:::

View alert details

At the bottom of the Alerts page is the alerts table, which includes a comprehensive list of all generated alerts, as well as inline actions so you can take action directly on the alert. You can customize and filter the table by specific criteria to help drill down and narrow alerts.

:::{tip}
Consider [grouping alerts](/solutions/security/detect-and-alert/manage-detection-alerts.md#group-alerts) by other parameters such as rule name, user name, host name, source IP address, or any other field. You can select up to three fields.
:::

To view specific details about an alert, in the alerts table, click the **View details** button, which opens the alert details flyout. Here, you can view a quick description of the alert, or conduct a deep dive to investigate. Each section of the alert details flyout provides a different insight, and the **Take Action** menu at the bottom provides several options for interacting with the alert.

:::{image} /solutions/images/security-gs-siem-alert-flyout.png
:alt: Alert details flyout
:screenshot:
:::


For a comprehensive overview of the alert details flyout, refer to [View detection alert details](/solutions/security/detect-and-alert/view-detection-alert-details.md#alert-details-flyout-ui).

::::
:::::{stepper}

## Next steps

Once you've had a chance to install detection rules and check out alerts, we recommend exploring the following investigation tools and resources to assist you with threat hunting:

* View and analyze data with out-of-the-box [dashboards](/solutions/security/dashboards.md).
* Explore a graphical timeline of processes that led up to the alert and the events that occurred immediately after with the [visual event analyzer](/solutions/security/investigate/visual-event-analyzer.md).
* Learn how to use [Cases](/solutions/security/investigate/cases.md) to track investigation details.
* Download the "Guide to high-volume data sources for SIEM" [white paper](https://www.elastic.co/campaigns/guide-to-high-volume-data-sources-for-siem?elektra=organic&storm=CLP&rogue=siem-gic).
* Check out [Elastic Security Labs](https://www.elastic.co/security-labs) for the latest on threat research.
% add endpoint getting started guide when it's done
70 changes: 70 additions & 0 deletions solutions/security/get-started/get-started-endpoint-security.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,70 @@
---
navigation_title: Secure my hosts with endpoint security
description: A quick start guide to securing your hosts with endpoint security.
applies_to:
serverless:
products:
- id: security
---

# Quickstart: Secure my hosts with endpoint security

In this guide below, you’ll learn how to use {{elastic-sec}} to protect your hosts from malware, ransomware, and other threats.

## Prerequisites

* Log in to your {{sec-serverless}} project. If you don't have one yet, refer to [Create a Security project](/solutions/security/get-started/create-security-project.md) to learn how to create one.
* Ensure you have the appropriate [{{elastic-defend}} feature privileges](/solutions/security/configure-elastic-defend/elastic-defend-feature-privileges.md).
* Ensure you have the appropriate user role to configure an integration policy and access the Endpoints page.

:::::{stepper}

::::{step} Add the Elastic Defend integration

{{elastic-defend}} detects and protects endpoints from malicious activity and provides automated response options before damage and loss occur.

:::{note}
If you're installing {{elastic-defend}} on macOS, the following instructions apply to hosts without a Mobile Device Management (MDM) profile. If your host has an MDM profile, refer to [Deploy Elastic Defend on macOS with mobile device management](/solutions/security/configure-elastic-defend/deploy-on-macos-with-mdm.md).
:::

1. On the Get started home page, in the **Ingest your data** section, select **Elastic Defend**, then click **Add Elastic Defend**.
2. On the next page that says, "Ready to add your first integration?", click **Add integration only (skip agent installation)**. The integration configuration page appears.
3. Give the Elastic Defend integration a name and optional description.
4. Select the type of environment you want to protect — **Traditional Endpoints** or **Cloud Workloads**. For this guide , we'll select **Traditional Endpoints**.
5. Select a configuration preset, which will differ based on your prior selection. Each preset comes with different default settings for {{agent}}, which you can further customize later by [configuring the {{elastic-defend}} integration policy](/solutions/security/configure-elastic-defend/configure-an-integration-policy-for-elastic-defend.md). For optimal endpoint protection, we recommend selecting **Complete EDR (Endpoint, Detection & Response)**.
6. Enter a name for the agent policy in the **New agent policy name** field.
7. Click **Save and continue**. Next, click **Add {{agent}} to your hosts**.
::::

::::{step} Add the Elastic Agent

{{agent}} is a single, unified way to add monitoring for logs, metrics, and other types of data to a host.

1. In the **Add agent** flyout that appears after you install the {{elastic-defend}} integration, you'll see the policy selected that you previously added. Leave the default enrollment token selected.
2. Ensure that the **Enroll in {{fleet}}** option is selected. {{elastic-defend}} cannot be integrated with {{agent}} in standalone mode.
3. Select the appropriate platform or operating system for the host on which you're installing the agent, then copy the provided commands.
4. On the host, open a command-line interface and navigate to the directory where you want to install {{agent}}. Paste and run the commands from {{fleet}} to download, extract, enroll, and start {{agent}}.
5. (Optional) Return to the **Add agen**t flyout, and observe the **Confirm agent enrollment** and **Confirm incoming data** steps automatically checking the host connection. It may take a few minutes for data to arrive in {{es}}.
6. (Optional) After you have enrolled the {{agent}} on your host, you can click **View enrolled agents** to access the list of agents enrolled in {{fleet}}. Otherwise, select **Close**.

The host will now appear on the **Endpoints** page in the {{security-app}} (**Assets** → **Endpoints**). It may take another minute or two for endpoint data to appear in {{elastic-sec}}.
7. If you’re using macOS, some versions may require you to grant {{elastic-endpoint}} Full Disk Access to different kernels, system extensions, or files. Refer to [Elastic Defend requirements](/solutions/security/configure-elastic-defend/elastic-defend-requirements.md) for more information.
::::

::::{step} (Optional) Configure an integration policy for Elastic Defend

After you install the {{agent}} with {{elastic-defend}}, several endpoint protections — such as preventions against malware, ransomware, memory threats, and other malicious behavior are automatically enabled on protected hosts. However, you can update the policy configuration to meet your organization’s security needs.

To configure an integration policy:

1. From the left navigation menu, go to **Assets** → **Endpoints** → **Policies**.
2. From the list, select the policy you want to configure. The integration policy configuration page appears.
3. On the **Policy settings** tab, review and configure the protection, event collection, and antivirus settings as appropriate.
4. Once you're finished making changes, click **Save** in the lower-right corner to update the policy.
5. Next, click the **Trusted applications**, **Event filters**, **Host isolation exceptions**, and **Blocklist** tabs to review and manage the endpoint policy artifacts assigned to the policy.

For a comprehensive explanation of all endpoint protections and policy settings, refer to [Configure an integration policy](/solutions/security/configure-elastic-defend/configure-an-integration-policy-for-elastic-defend.md).

% insert image
::::
:::::
18 changes: 18 additions & 0 deletions solutions/security/get-started/quickstarts.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
---
applies_to:
serverless: ga
products:
- id: security
---

# {{elastic-sec}} quickstarts

Our quickstarts reduce your time-to-value by offering a fast path to learn about search strategies.
Each quickstart provides:

- A highly opinionated, fast path to a specific use case
- Sensible configuration defaults with minimal configuration required

Follow the steps in these guides to get started quickly:

- [Detect and respond to threats with SIEM](/solutions/security/get-started/get-started-detect-with-siem.md)
4 changes: 4 additions & 0 deletions solutions/toc.yml
Original file line number Diff line number Diff line change
Expand Up @@ -458,6 +458,10 @@ toc:
- file: security/elastic-security-serverless.md
- file: security/get-started.md
children:
- file: security/get-started/quickstarts.md
children:
- file: security/get-started/get-started-detect-with-siem.md
- file: security/get-started/get-started-endpoint-security.md
- file: security/get-started/elastic-security-requirements.md
- file: security/get-started/create-security-project.md
- file: security/get-started/elastic-security-ui.md
Expand Down
Loading