Skip to content

Commit 0156c2d

Browse files
authored
Merge pull request #189 from karenzone/secops
Initialize docs for secops
2 parents 1fb573f + 3242a41 commit 0156c2d

File tree

5 files changed

+93
-0
lines changed

5 files changed

+93
-0
lines changed
27 KB
Loading

docs/en/secops/index.asciidoc

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
:doctype: book
2+
:sec: SecOps
3+
:sec-soln: security monitoring
4+
:sec-ui: SecOps
5+
6+
= Security Monitoring Guide
7+
8+
include::{asciidoc-dir}/../../shared/versions.asciidoc[]
9+
10+
include::{asciidoc-dir}/../../shared/attributes.asciidoc[]
11+
12+
include::overview.asciidoc[]
13+
14+
include::installation.asciidoc[]
15+
16+
include::sec-ui.asciidoc[]
17+

docs/en/secops/installation.asciidoc

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
[[install-sec-monitoring]]
2+
[role="xpack"]
3+
== Get up and running
4+
5+
beta[]
6+
7+
To get up and running with security monitoring, you need:
8+
9+
* An Elasticsearch cluster and Kibana (version 6.x or later) with a basic
10+
license. To learn how to get started quickly, see
11+
{stack-gs}/get-started-elastic-stack.html[Getting started with the {stack}].
12+
+
13+
[TIP]
14+
==============
15+
You can skip installing {es} and {kib} by using our
16+
https://www.elastic.co/cloud/elasticsearch-service[hosted {es} Service] on
17+
Elastic Cloud. The {es} Service is available on both AWS and GCP.
18+
https://www.elastic.co/cloud/elasticsearch-service/signup[Try the {es}
19+
Service for free].
20+
==============
21+
22+
* {beats} shippers (version 6.x or later) installed on each system you want to
23+
monitor
24+
25+
You might need to modify UI settings in {kib} to change default behaviors,
26+
such as the index pattern used to query the data, and the timestamp field used
27+
for sorting. For more information, see {kib}.
28+
29+
[float]
30+
[[install-beats-for-sec]]
31+
=== Install {beats} shippers
32+
33+
To populate the security UI with metrics and
34+
log data, you need to install and configure the following shippers:
35+
36+
* https://www.elastic.co/products/beats/packetbeat[{packetbeat}] for analyzing
37+
network packets
38+
* https://www.elastic.co/products/beats/filebeat[{filebeat}] for forwarding and
39+
centralizing logs and files
40+
* https://www.elastic.co/products/beats/auditbeat[{auditbeat}] for monitoring
41+
directories for file changes
42+

docs/en/secops/overview.asciidoc

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
[[sec-monitoring-overview]]
2+
[role="xpack"]
3+
== Overview
4+
5+
beta[]
6+
7+
{sec} gives you a comprehensive view into your security operations.
8+
9+
The UI in {kib} UI to brings together data
10+
from a variety of sources, making it easier for you
11+
to identify and resolve security issues.
12+
13+
[float]
14+
[[secops-components]]
15+
=== Security monitoring components
16+
17+
Security monitoring requires the following {stack} components.
18+
19+
image::images/secops-architecture.png[]
20+

docs/en/secops/sec-ui.asciidoc

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
[[sec-ui-overview]]
2+
[role="xpack"]
3+
== {sec-ui} UI
4+
5+
beta[]
6+
7+
After you have security monitoring <<install-sec-monitoring,up and
8+
running>> and data is streaming to {es}, use the {sec-ui} UI in {kib} to monitor
9+
and identify security problems in real time.
10+
11+
For more information about working with the {sec-ui} UI, see the
12+
{kib} documentation.
13+
14+

0 commit comments

Comments
 (0)