· 5 years ago · Oct 20, 2020, 09:28 PM
1###################### Winlogbeat Configuration Example ########################
2
3# This file is an example configuration file highlighting only the most common
4# options. The winlogbeat.reference.yml file from the same directory contains
5# all the supported options with more comments. You can use it as a reference.
6#
7# You can find the full configuration reference here:
8# https://www.elastic.co/guide/en/beats/winlogbeat/index.html
9
10# ======================== Winlogbeat specific options =========================
11
12# event_logs specifies a list of event logs to monitor as well as any
13# accompanying options. The YAML data type of event_logs is a list of
14# dictionaries.
15#
16# The supported keys are name (required), tags, fields, fields_under_root,
17# forwarded, ignore_older, level, event_id, provider, and include_xml. Please
18# visit the documentation for the complete details of each option.
19# https://go.es.io/WinlogbeatConfig
20
21winlogbeat.event_logs:
22 - name: Application
23 ignore_older: 72h
24
25 - name: System
26
27 - name: Security
28 processors:
29 - script:
30 lang: javascript
31 id: security
32 file: ${path.home}/module/security/config/winlogbeat-security.js
33
34 - name: "Windows PowerShell"
35
36 - name: Microsoft-Windows-Sysmon/Operational
37 processors:
38 - script:
39 lang: javascript
40 id: sysmon
41 file: ${path.home}/module/sysmon/config/winlogbeat-sysmon.js
42
43 - name: ForwardedEvents
44 tags: [forwarded]
45 processors:
46 - script:
47 when.equals.winlog.channel: Security
48 lang: javascript
49 id: security
50 file: ${path.home}/module/security/config/winlogbeat-security.js
51 - script:
52 when.equals.winlog.channel: Microsoft-Windows-Sysmon/Operational
53 lang: javascript
54 id: sysmon
55 file: ${path.home}/module/sysmon/config/winlogbeat-sysmon.js
56
57# ====================== Elasticsearch template settings =======================
58
59setup.template.enabled: true
60setup.template.settings:
61 index.number_of_shards: 1
62 #index.codec: best_compression
63 #_source.enabled: false
64
65
66# ================================== General ===================================
67
68# The name of the shipper that publishes the network data. It can be used to group
69# all the transactions sent by a single shipper in the web interface.
70#name:
71
72# The tags of the shipper are included in their own field with each
73# transaction published.
74#tags: ["service-X", "web-tier"]
75
76# Optional fields that you can specify to add additional information to the
77# output.
78#fields:
79# env: staging
80
81# ================================= Dashboards =================================
82# These settings control loading the sample dashboards to the Kibana index. Loading
83# the dashboards is disabled by default and can be enabled either by setting the
84# options here or by using the `setup` command.
85
86setup.dashboards.enabled: true
87
88# The URL from where to download the dashboards archive. By default this URL
89# has a value which is computed based on the Beat name and version. For released
90# versions, this URL points to the dashboard archive on the artifacts.elastic.co
91# website.
92#setup.dashboards.url:
93
94# =================================== Kibana ===================================
95
96# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
97# This requires a Kibana endpoint configuration.
98setup.kibana:
99
100 # Kibana Host
101 # Scheme and port can be left out and will be set to the default (http and 5601)
102 # In case you specify and additional path, the scheme is required: http://localhost:5601/path
103 # IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
104 host: "192.168.2.120:5601"
105
106 # Kibana Space ID
107 # ID of the Kibana Space into which the dashboards should be loaded. By default,
108 # the Default Space will be used.
109 #space.id:
110
111# =============================== Elastic Cloud ================================
112
113# These settings simplify using Winlogbeat with the Elastic Cloud (https://cloud.elastic.co/).
114
115# The cloud.id setting overwrites the `output.elasticsearch.hosts` and
116# `setup.kibana.host` options.
117# You can find the `cloud.id` in the Elastic Cloud web UI.
118#cloud.id:
119
120# The cloud.auth setting overwrites the `output.elasticsearch.username` and
121# `output.elasticsearch.password` settings. The format is `<user>:<pass>`.
122#cloud.auth:
123
124# ================================== Outputs ===================================
125
126# Configure what output to use when sending the data collected by the beat.
127
128# ---------------------------- Elasticsearch Output ----------------------------
129#output.elasticsearch:
130 # Array of hosts to connect to.
131 #hosts: ["192.168.2.120:9200"]
132
133 # Protocol - either `http` (default) or `https`.
134 #protocol: "https"
135
136 # Authentication credentials - either API key or username/password.
137 #api_key: "id:api_key"
138 #username: "elastic"
139 #password: "changeme"
140
141# ------------------------------ Logstash Output -------------------------------
142output.logstash:
143 # The Logstash hosts
144 hosts: ["192.168.2.120:5044"]
145
146 # Optional SSL. By default is off.
147 # List of root certificates for HTTPS server verifications
148 #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
149
150 # Certificate for SSL client authentication
151 #ssl.certificate: "/etc/pki/client/cert.pem"
152
153 # Client Certificate Key
154 #ssl.key: "/etc/pki/client/cert.key"
155
156# ================================= Processors =================================
157processors:
158 - add_host_metadata:
159 when.not.contains.tags: forwarded
160 - add_cloud_metadata: ~
161
162# ================================== Logging ===================================
163
164# Sets log level. The default log level is info.
165# Available log levels are: error, warning, info, debug
166logging.level: error
167
168# At debug level, you can selectively enable logging only for some components.
169# To enable all selectors use ["*"]. Examples of other selectors are "beat",
170# "publish", "service".
171#logging.selectors: ["*"]
172
173# ============================= X-Pack Monitoring ==============================
174# Winlogbeat can export internal metrics to a central Elasticsearch monitoring
175# cluster. This requires xpack monitoring to be enabled in Elasticsearch. The
176# reporting is disabled by default.
177
178# Set to true to enable the monitoring reporter.
179#monitoring.enabled: false
180
181# Sets the UUID of the Elasticsearch cluster under which monitoring data for this
182# Winlogbeat instance will appear in the Stack Monitoring UI. If output.elasticsearch
183# is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch.
184#monitoring.cluster_uuid:
185
186# Uncomment to send the metrics to Elasticsearch. Most settings from the
187# Elasticsearch output are accepted here as well.
188# Note that the settings should point to your Elasticsearch *monitoring* cluster.
189# Any setting that is not set is automatically inherited from the Elasticsearch
190# output configuration, so if you have the Elasticsearch output configured such
191# that it is pointing to your Elasticsearch monitoring cluster, you can simply
192# uncomment the following line.
193#monitoring.elasticsearch:
194
195# ================================= Migration ==================================
196
197# This allows to enable 6.7 migration aliases
198#migration.6_to_7.enabled: true
199
200
201