Skip to content
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

ossec test notifications do not generate ossec alerts #4339

Closed
emkll opened this issue Apr 12, 2019 · 1 comment · Fixed by #4340
Closed

ossec test notifications do not generate ossec alerts #4339

emkll opened this issue Apr 12, 2019 · 1 comment · Fixed by #4340

Comments

@emkll
Copy link
Contributor

emkll commented Apr 12, 2019

Description

Errors in Apache logs no longer trigger an ossec alert / email notification.

Steps to Reproduce

  1. Navigate to a Journalist Interface on a SecureDrop instance that has email notifications set up
  2. Click on Admin, and navigate to Instance Config
  3. Click on "Send Test OSSEC Alert"
  4. Observe no emails are sent to the admin mailbox

Expected Behavior

Email should be sent shortly after the button is clicked.

Comments

Test ossec notification relies on triggering an app error, that is caught by apache logs and then sent to ossec.

Default rule is set to 0, which mean it won't appear in alerts.log (requires level 1) or in emails (requires level 7)

https://github.com/ossec/ossec-hids/blob/master/etc/rules/apache_rules.xml#L173

@emkll emkll added the OSSEC label Apr 12, 2019
@emkll emkll added this to the 0.12.2 milestone Apr 12, 2019
@emkll emkll self-assigned this Apr 12, 2019
@redshiftzero
Copy link
Contributor

More extensive testing of OSSEC rules could help us catch issues like this (relevant: #2134 #2137)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants