forked from elastic/cloudbeat
-
Notifications
You must be signed in to change notification settings - Fork 0
/
cloudbeat.yml
317 lines (269 loc) · 9.91 KB
/
cloudbeat.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
###################### Cloudbeat Configuration Example #########################
# This file is an example configuration file highlighting only the most common
# options. The cloudbeat.reference.yml file from the same directory contains all the
# supported options with more comments. You can use it as a reference.
#
# You can find the full configuration reference here:
# https://www.elastic.co/guide/en/beats/cloudbeat/index.html
# For more available modules and options, please see the cloudbeat.reference.yml sample
# configuration file.
cloudbeat:
type: cloudbeat/cis_k8s
streams:
# Defines how often an event is sent to the output
period: 4h
fetchers:
- name: kube-api
- name: process
directory: "/hostfs"
processes:
etcd:
kube-apiserver:
kube-controller:
kube-scheduler:
kubelet:
config-file-arguments:
- config
- name: file-system
patterns: [
"/hostfs/etc/kubernetes/scheduler.conf",
"/hostfs/etc/kubernetes/controller-manager.conf",
"/hostfs/etc/kubernetes/admin.conf",
"/hostfs/etc/kubernetes/kubelet.conf",
"/hostfs/etc/kubernetes/manifests/etcd.yaml",
"/hostfs/etc/kubernetes/manifests/kube-apiserver.yaml",
"/hostfs/etc/kubernetes/manifests/kube-controller-manager.yaml",
"/hostfs/etc/kubernetes/manifests/kube-scheduler.yaml",
"/hostfs/etc/systemd/system/kubelet.service.d/10-kubeadm.conf",
"/hostfs/etc/kubernetes/pki/*",
"/hostfs/var/lib/kubelet/config.yaml",
"/hostfs/var/lib/etcd",
"/hostfs/etc/kubernetes/pki"
]
runtime_cfg:
activated_rules:
cis_k8s:
- cis_1_1_1
- cis_1_1_2
- cis_1_1_3
- cis_1_1_4
- cis_1_1_5
- cis_1_1_6
- cis_1_1_7
- cis_1_1_8
- cis_1_1_11
- cis_1_1_12
- cis_1_1_13
- cis_1_1_14
- cis_1_1_15
- cis_1_1_16
- cis_1_1_17
- cis_1_1_18
- cis_1_1_19
- cis_1_1_20
- cis_1_1_21
- cis_1_2_2
- cis_1_2_4
- cis_1_2_5
- cis_1_2_6
- cis_1_2_7
- cis_1_2_8
- cis_1_2_9
- cis_1_2_10
- cis_1_2_11
- cis_1_2_12
- cis_1_2_13
- cis_1_2_14
- cis_1_2_15
- cis_1_2_16
- cis_1_2_17
- cis_1_2_18
- cis_1_2_19
- cis_1_2_20
- cis_1_2_21
- cis_1_2_22
- cis_1_2_23
- cis_1_2_24
- cis_1_2_25
- cis_1_2_26
- cis_1_2_27
- cis_1_2_28
- cis_1_2_29
- cis_1_2_32
- cis_1_3_2
- cis_1_3_3
- cis_1_3_4
- cis_1_3_5
- cis_1_3_6
- cis_1_3_7
- cis_1_4_1
- cis_1_4_2
- cis_2_1
- cis_2_2
- cis_2_3
- cis_2_4
- cis_2_5
- cis_2_6
- cis_4_1_1
- cis_4_1_2
- cis_4_1_5
- cis_4_1_6
- cis_4_1_9
- cis_4_1_10
- cis_4_2_1
- cis_4_2_2
- cis_4_2_3
- cis_4_2_4
- cis_4_2_5
- cis_4_2_6
- cis_4_2_7
- cis_4_2_8
- cis_4_2_9
- cis_4_2_10
- cis_4_2_11
- cis_4_2_12
- cis_4_2_13
- cis_5_1_3
- cis_5_1_5
- cis_5_1_6
- cis_5_2_2
- cis_5_2_3
- cis_5_2_4
- cis_5_2_5
- cis_5_2_6
- cis_5_2_7
- cis_5_2_8
- cis_5_2_9
- cis_5_2_10
# # EKS Fetchers configuration
# - name: kube-api
# - name: process
# directory: "/hostfs"
# processes:
# kubelet:
# config-file-arguments:
# - config
# - name: aws-ecr
# - name: aws-elb
# - name: file-system
# patterns: [
# "/hostfs/etc/kubernetes/kubelet/kubelet-config.json",
# "/hostfs/var/lib/kubelet/kubeconfig",
# ]
# ================================== General ===================================
# The name of the shipper that publishes the network data. It can be used to group
# all the transactions sent by a single shipper in the web interface.
#name:
# The tags of the shipper are included in their own field with each
# transaction published.
#tags: ["service-X", "web-tier"]
# Optional fields that you can specify to add additional information to the
# output.
#fields:
# env: staging
# ================================= Dashboards =================================
# These settings control loading the sample dashboards to the Kibana index. Loading
# the dashboards is disabled by default and can be enabled either by setting the
# options here or by using the `setup` command.
#setup.dashboards.enabled: false
# The URL from where to download the dashboards archive. By default this URL
# has a value which is computed based on the Beat name and version. For released
# versions, this URL points to the dashboard archive on the artifacts.elastic.co
# website.
#setup.dashboards.url:
# =================================== Kibana ===================================
# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# This requires a Kibana endpoint configuration.
setup.kibana:
# Kibana Host
# Scheme and port can be left out and will be set to the default (http and 5601)
# In case you specify and additional path, the scheme is required: http://localhost:5601/path
# IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
#host: "localhost:5601"
# Kibana Space ID
# ID of the Kibana Space into which the dashboards should be loaded. By default,
# the Default Space will be used.
#space.id:
# =============================== Elastic Cloud ================================
# These settings simplify using Cloudbeat with the Elastic Cloud (https://cloud.elastic.co/).
# The cloud.id setting overwrites the `output.elasticsearch.hosts` and
# `setup.kibana.host` options.
# You can find the `cloud.id` in the Elastic Cloud web UI.
#cloud.id:
# The cloud.auth setting overwrites the `output.elasticsearch.username` and
# `output.elasticsearch.password` settings. The format is `<user>:<pass>`.
#cloud.auth:
# ================================== Outputs ===================================
# Configure what output to use when sending the data collected by the beat.
# ---------------------------- Elasticsearch Output ----------------------------
output.elasticsearch:
# Array of hosts to connect to.
hosts: ["localhost:9200"]
# Protocol - either `http` (default) or `https`.
#protocol: "https"
# Authentication credentials - either API key or username/password.
#api_key: "id:api_key"
#username: "elastic"
#password: "changeme"
# ------------------------------ Logstash Output -------------------------------
#output.logstash:
# The Logstash hosts
#hosts: ["localhost:5044"]
# Optional SSL. By default is off.
# List of root certificates for HTTPS server verifications
#ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
# Certificate for SSL client authentication
#ssl.certificate: "/etc/pki/client/cert.pem"
# Client Certificate Key
#ssl.key: "/etc/pki/client/cert.key"
# ================================= Processors =================================
# Configure processors to enhance or manipulate events generated by the beat.
processors:
- add_host_metadata: ~
- add_cloud_metadata: ~
- add_docker_metadata: ~
- add_cluster_id: ~
# ================================== Logging ===================================
# Sets log level. The default log level is info.
# Available log levels are: error, warning, info, debug
#logging.level: debug
# At debug level, you can selectively enable logging only for some components.
# To enable all selectors use ["*"]. Examples of other selectors are "beat",
# "publisher", "service".
#logging.selectors: ["*"]
# ============================= X-Pack Monitoring ==============================
# Cloudbeat can export internal metrics to a central Elasticsearch monitoring
# cluster. This requires xpack monitoring to be enabled in Elasticsearch. The
# reporting is disabled by default.
# Set to true to enable the monitoring reporter.
#monitoring.enabled: false
# Sets the UUID of the Elasticsearch cluster under which monitoring data for this
# Cloudbeat instance will appear in the Stack Monitoring UI. If output.elasticsearch
# is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch.
#monitoring.cluster_uuid:
# Uncomment to send the metrics to Elasticsearch. Most settings from the
# Elasticsearch output are accepted here as well.
# Note that the settings should point to your Elasticsearch *monitoring* cluster.
# Any setting that is not set is automatically inherited from the Elasticsearch
# output configuration, so if you have the Elasticsearch output configured such
# that it is pointing to your Elasticsearch monitoring cluster, you can simply
# uncomment the following line.
#monitoring.elasticsearch:
# ============================== Instrumentation ===============================
# Instrumentation support for the cloudbeat.
#instrumentation:
# Set to true to enable instrumentation of cloudbeat.
#enabled: false
# Environment in which cloudbeat is running on (eg: staging, production, etc.)
#environment: ""
# APM Server hosts to report instrumentation results to.
#hosts:
# - http://localhost:8200
# API Key for the APM Server(s).
# If api_key is set then secret_token will be ignored.
#api_key:
# Secret token for the APM Server(s).
#secret_token:
# ================================= Migration ==================================
# This allows to enable 6.7 migration aliases
#migration.6_to_7.enabled: true