mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 17:28:26 -04:00
94cbef5c49
* security docs 7.9 updates * terminology * updates advanced settings * terminology * corrections
102 lines
3.2 KiB
Text
102 lines
3.2 KiB
Text
[role="xpack"]
|
|
[[siem-ui]]
|
|
== Using Elastic Security
|
|
|
|
Elastic Security is a highly interactive workspace designed for security
|
|
analysts. It provides a clear overview of events and alerts from your
|
|
environment, and you can use the interactive UI to drill down into areas of
|
|
interest.
|
|
|
|
[float]
|
|
[[hosts-ui]]
|
|
=== Hosts
|
|
|
|
The Hosts page provides key metrics regarding host-related security events, and
|
|
data tables and histograms that let you interact with the Timeline Event Viewer.
|
|
You can drill down for deeper insights, and drag and drop items of interest from
|
|
the Hosts page to Timeline for further investigation.
|
|
|
|
[role="screenshot"]
|
|
image::siem/images/hosts-ui.png[]
|
|
|
|
|
|
[float]
|
|
[[network-ui]]
|
|
=== Network
|
|
|
|
The Network page displays key network activity metrics in an interactive map,
|
|
and provides network event tables that enable interaction with Timeline.
|
|
|
|
[role="screenshot"]
|
|
image::siem/images/network-ui.png[]
|
|
|
|
[float]
|
|
[[detections-ui]]
|
|
=== Detections (beta)
|
|
|
|
The Detections feature automatically searches for threats and creates
|
|
alerts when they are detected. Detection rules define the conditions
|
|
for when alerts are created. Elastic Security comes with prebuilt rules that
|
|
search for suspicious activity on your network and hosts. Additionally, you can
|
|
create your own rules.
|
|
|
|
See {security-guide}/detection-engine-overview.html[Detections] for information
|
|
on managing detection rules and alerts.
|
|
|
|
[role="screenshot"]
|
|
image::siem/images/detections-ui.png[]
|
|
|
|
[float]
|
|
[[cases-ui]]
|
|
=== Cases (beta)
|
|
|
|
Cases are used to open and track security issues directly in Elastic Security.
|
|
Cases list the original reporter and all users who contribute to a case
|
|
(`participants`). Case comments support Markdown syntax, and allow linking to
|
|
saved Timelines. Additionally, you can send cases to external systems from
|
|
within Elastic Security.
|
|
|
|
For information about opening, updating, and closing cases, see
|
|
{security-guide}/cases-overview.html[Cases] in the Elastic Security Guide.
|
|
|
|
[role="screenshot"]
|
|
image::siem/images/cases-ui.png[]
|
|
|
|
[float]
|
|
[[timelines-ui]]
|
|
=== Timeline
|
|
|
|
Timeline is your workspace for threat hunting and alert investigations.
|
|
|
|
[role="screenshot"]
|
|
image::siem/images/timeline-ui.png[Elastic Security Timeline]
|
|
|
|
You can drag objects of interest into the Timeline Event Viewer to create
|
|
exactly the query filter you need. You can drag items from table widgets within
|
|
Hosts and Network pages, or even from within Timeline itself.
|
|
|
|
A timeline is responsive and persists as you move through Elastic Security
|
|
collecting data.
|
|
|
|
For detailed information about Timeline, see
|
|
{security-guide}/timelines-ui.html[Investigating events in Timeline].
|
|
|
|
[float]
|
|
[[sample-workflow]]
|
|
=== Sample workflow
|
|
|
|
An analyst notices a suspicious user ID that warrants further investigation, and
|
|
clicks a URL that links to Elastic Security.
|
|
|
|
The analyst uses the tables, histograms, and filtering and search capabilities in
|
|
Elastic Security to get to the bottom of the alert. The analyst can drag items of
|
|
interest to Timeline for further analysis.
|
|
|
|
Within Timeline, the analyst can investigate further - drilling down,
|
|
searching, and filtering - and add notes and pin items of interest.
|
|
|
|
The analyst can name the timeline, write summary notes, and share it with others
|
|
if appropriate.
|
|
|
|
|
|
|