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-slack issue on server-agents configuration #2052

Closed
NathanFRuiz opened this issue May 31, 2022 · 1 comment
Closed

ossec-slack issue on server-agents configuration #2052

NathanFRuiz opened this issue May 31, 2022 · 1 comment

Comments

@NathanFRuiz
Copy link

I'm testing Ossec as our IDPS solution, I chose the one-server-multiple-agents configuration as the agents will be installed on instances within an autoscaling group, I've managed to make everything work however the slack integration doesn't seem to work on the agents:

These are the configurations I've tried with little success

   <command>
    <name>ossec-slack</name>
    <executable>ossec-slack.sh</executable>
    <expect></expect> <!-- no expect args required -->
    <timeout_allowed>no</timeout_allowed>
  </command>

  <active-response>
    <command>ossec-slack</command>
    <location>local</location>
    <level>3</level>
  </active-response>

with this on the server I'll get the alerts for server related logs only, and adding this directly to agent will trigger empty alerts on slack.

   <command>
    <name>ossec-slack</name>
    <executable>ossec-slack.sh</executable>
    <expect></expect> <!-- no expect args required -->
    <timeout_allowed>no</timeout_allowed>
  </command>

  <active-response>
    <command>ossec-slack</command>
    <location>all</location>
    <level>3</level>
  </active-response>

This do not work at all, and the same with <agent_id>

The closest I got were empty alerts on slack sent from the agent ossec-slack.sh script, but for my understanding it doesn't make sense as the alert should be sent from the server and not from the agent itself

@NathanFRuiz
Copy link
Author

NathanFRuiz commented May 31, 2022

I Got it
<local>server<local/> is the right way to do it

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

No branches or pull requests

1 participant