甲方安全建立之日志采集实操干货

前言

没有永远的安全，如安在被攻击的情况下，快速响应和快速溯源分析攻击动作是个重要的话题。想要分析攻击者做了什么、怎么攻击进来的、还攻击了谁，那么日志是必不可少的一项，因此我们必要尽大概采集多的日志来进行分析攻击者的动作，甚至在攻击者刚落脚的时候就阻断攻击者。
安装Elastic+Kibana

Docker安装

这边根据官方文档：https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html 使用Docker安装了Elastic和Kibana

1. # 安装es
2. docker network create elastic
3. ​
4. docker pull docker.elastic.co/elasticsearch/elasticsearch:8.12.1
5. ​
6. docker run --name es01 --net elastic -p 9200:9200 -it -m 1GB docker.elastic.co/elasticsearch/elasticsearch:8.12.1
7. ​
8. # 记录es的密码和注册kibana所需要的token
9. ​
10. # 测试es是否正确运行
11. export ELASTIC_PASSWORD="es_your_password"
12. ​
13. docker cp es01:/usr/share/elasticsearch/config/certs/http_ca.crt .
14. ​
15. curl --cacert http_ca.crt -u elastic:$ELASTIC_PASSWORD https://localhost:9200
16. ​
17. # 安装kibana
18. docker pull docker.elastic.co/kibana/kibana:8.12.1
19. ​
20. docker run --name kib01 --net elastic -p 5601:5601 docker.elastic.co/kibana/kibana:8.12.1
21. ​
22. 会给出kibana的注册地址，访问填入上述记录的token即可。
23. ​

复制代码

不知道是机器性能问题照旧Docker安装的问题，es容器经常会挂掉。
RPM安装

根据https://www.elastic.co/guide/en/elasticsearch/reference/current/rpm.html、https://www.elastic.co/guide/en/kibana/current/rpm.html官方文档，可以yum install安装。由于公司访问镜像源被封，因此使用上述文档中下载rpm安装：

1. # 安装es
2. wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-8.12.1-x86_64.rpm
3. wget https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-8.12.1-x86_64.rpm.sha512
4. shasum -a 512 -c elasticsearch-8.12.1-x86_64.rpm.sha512
5. sudo rpm --install elasticsearch-8.12.1-x86_64.rpm
6. ​
7. 安装kibana
8. wget https://artifacts.elastic.co/downloads/kibana/kibana-8.12.1-x86_64.rpm
9. wget https://artifacts.elastic.co/downloads/kibana/kibana-8.12.1-x86_64.rpm.sha512
10. shasum -a 512 -c kibana-8.12.1-x86_64.rpm.sha512
11. sudo rpm --install kibana-8.12.1-x86_64.rpm

复制代码

依然在安装es的rpm时，会吐出es/kibana的密码：

1. The generated password for the elastic built-in superuser is : Fq*S7jxCjFfPu6nN8NG8

复制代码

es服务大概启动不了，但是安装时会给出启动命令：

1. sudo systemctl daemon-reload
2. sudo systemctl enable elasticsearch.service

复制代码

测试es启动是否正常：

1. export ELASTIC_PASSWORD="Fq*S7jxCjFfPu6nN8NG8"
2. curl --cacert /etc/elasticsearch/certs/http_ca.crt -u elastic:$ELASTIC_PASSWORD https://localhost:9200

复制代码

记得改下配置文件，使其监听在0.0.0.0上面：

1. # /etc/elasticsearch/elasticsearch.yml
2. ​
3. # Allow HTTP API connections from anywhere
4. # Connections are encrypted and require user authentication
5. http.host: 0.0.0.0
6. ​
7. # Allow other nodes to join the cluster from anywhere
8. # Connections are encrypted and mutually authenticated
9. transport.host: 0.0.0.0

复制代码

kibana一样，记得改下配置文件，使其监听在0.0.0.0上面：

1. # /etc/kibana/kibana.yml
2. server.host: "0.0.0.0"

复制代码

安装Fleet和Elastic Agent

在Kibana上，Management->Fleet->Add Fleet Server，先安装Fleet Server，URL填写https协议，端口可以填默认的8220。装好Fleet Server后再装Elastic Agent，Fleet Server也是一个Agent，因此不能在同一台机器上同时装Fleet Server和Elastic Agent。

[img=720,373.4439834024896]https://m-1254331109.cos.ap-guangzhou.myqcloud.com/202404071311824.jpg[/img]

为了使其Elastic Agent附带Security能力，可以添加各式各样的integrations集成，如到Security->Manage->Get started->Add security integrations安装安全集成：

[img=720,348.984]https://m-1254331109.cos.ap-guangzhou.myqcloud.com/202404071311826.png[/img]

[img=720,477.4736842105263]https://m-1254331109.cos.ap-guangzhou.myqcloud.com/202404071311827.png[/img]

测试告警

留意，如果有如下错误需解决，否则会无法查阅规则：

[img=720,337.78367617783675]https://m-1254331109.cos.ap-guangzhou.myqcloud.com/202404071311828.png[/img]

[img=720,374.1694462975317]https://m-1254331109.cos.ap-guangzhou.myqcloud.com/202404071311829.png[/img]

【----帮助网安学习，以下全部学习资料免费领！加vx：dctintin，备注 “博客园” 获取！】
　① 网安学习成长路径思维导图
　② 60+网安经典常用工具包
　③ 100+SRC毛病分析陈诉
　④ 150+网安攻防实战技术电子书
　⑤ 最权威CISSP 认证测验指南+题库
　⑥ 超1800页CTF实战技巧手册
　⑦ 最新网安大厂面试题合集（含答案）
　⑧ APP客户端安全检测指南（安卓+IOS）
有些规则没开，记得开下，比如我把reverse shell规则打开后：Security->Dashboards->Detection & Response可以看到一些概览：

[img=720,325.7963089542037]https://m-1254331109.cos.ap-guangzhou.myqcloud.com/202404071311830.png[/img]

记载Windows事件管理器日志

安装

Windows事件管理器日志不是单纯的文本，因此必要借助一些工具来帮助我们完成采集的目的。这里使用winlogbeat（https://www.elastic.co/cn/beats/winlogbeat）完成。官方提供了很详细的安装文档（https://www.elastic.co/guide/en/beats/winlogbeat/current/winlogbeat-installation-configuration.html），核心就是配置想要记载的日志类型和对外传输的方案，这里我使用的方案为：

• 记载的日志类型，我没改，默认就是Security、Application，甚至另有Sysmon
  
• 对外传输，我使用了传输到elastic
  

配置好winlogbeat.yml后可以进行测试配置文件对不对：

1. .\winlogbeat.exe test config -c .\winlogbeat.yml -e

复制代码

下面为我的配置文件信息：

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

复制代码

数据检索

这时候，大概elastic上面搜不到数据，是由于winlogbeat使用了他自己的索引，默认为winlogbeat-version，笔者测试时，发现kibana上迟迟出现不了该索引，还以为数据传输没成功呢，因此通过如动手段进行排查，先获取es上面的索引信息：

1. http://your_ip:9200/_cat/indices?v

复制代码

发现有类似winlogbeat的索引信息：

1. yellow open   .ds-winlogbeat-8.12.0-2024.02.03-000001   UpWhWCpdR-2WgMVe_kiH9A   1   1     192705            0    131.1mb        131.1mb
2. ​

复制代码

后面尝试在kibana上创建一个新的索引即可，v7.17.12版本的kibana创建索引的过程如下：discover->选项->View Discover settings

[img=720,277.0705725699068]https://m-1254331109.cos.ap-guangzhou.myqcloud.com/202404071410669.jpg[/img]

找到“索引模式”创建一个新的索引即可：

[img=720,282.4258064516129]https://m-1254331109.cos.ap-guangzhou.myqcloud.com/202404071410670.jpg[/img]

[img=720,179.86813186813185]https://m-1254331109.cos.ap-guangzhou.myqcloud.com/202404071410671.png[/img]

这时候就可以检索事件管理器日志了：

[img=720,371.90619362597715]https://m-1254331109.cos.ap-guangzhou.myqcloud.com/202404071410672.png[/img]

更多网安技能的在线实练习习，请点击这里>>
  
  

免责声明：如果侵犯了您的权益，请联系站长，我们会及时删除侵权内容，谢谢合作！更多信息从访问主页：qidao123.com:ToB企服之家，中国第一个企服评测及商务社交产业平台。