There are 1 security vulnerabilities found in gopkg.in/yaml.v3 v3.0.0-20210107192922-496545a6307b CVE-2022-28948 What did I do? Upgrade gopkg.in/yaml.v3 from v3.0.0-20210107192922-496545a6307b to 3.0.0 for vulnerability fix What did you expect to happen? Ideally, no insecure libs should be used. How can we automate the detection of these types of issues? By using the GitHub Actions configurations provided by murphysec, we can conduct automatic code security checks in our CI pipeline. The specification of the pull request PR Specification from OSCS
Beats output plugin
Compatibility
This output is developed and tested using Beats 7.3.1
How to build
go build -o filebeat filebeat/filebeat.go
go build -o metricbeat metricbeat/metricbeat.go
go build -o winlogbeat winlogbeat/winlogbeat.go
go build -o packetbeat packetbeat/packetbeat.go
go build -o auditbeat auditbeat/auditbeat.go
go build -o heartbeat heartbeat/heartbeat.go
How to use
See: