-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add new rules and decoders for macOS sshd logs #590
Comments
This was referenced Mar 30, 2020
MiguelCasaresRobles
added a commit
that referenced
this issue
Apr 6, 2020
Add macOS sshd rules and decoders (Branch: 3.12-feature-macOS) (Issue: #590)
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See #348
Introduction
Currently, SSH events (and others) from MacOS do not trigger alerts on Wazuh. The logs provided by
/var/log/system.log
provide next to no information besides the fact that an SSHD process has started or stopped. They are readable by the predecoder and sshd decoder but do not trip any relevant rules. The goal of this issue is to create new rules and decoders to parse the full logs of the SSHD process on MacOS which as of MacOS 10.12 Sierra are no longer stored by default in an easily readable .log text file and must be dumped via a command such aslog
.Details
Logs collected from
/var/log/system.log
have the following format:MacOS provides much more complete logs via the
log
command, and offers them in a variety of formats. We will be using the--style syslog
and--info
options to obtain the necessary logs in the following format:Due to the predecoder not recognizing the MacOS date format (and subsequently the program name), the SSH decoder fails to pick them up. Thus, a specialized MacOS date format decoder, alongside child decoders for SSH would be necessary to decode these logs. In addition, while many logs on Mac are identical to their Linux counterparts, not all are and even without the date format issue some still fail to trip the proper rules.
The text was updated successfully, but these errors were encountered: