Atomicorp

Packages are in the testing channel now:

yum upgrade --enablerepo=asl-4.0-testing clamav*

If your reviewing before purchasing, could you PM me what your username is so I can upgrade your demo to the full product. You will want to run the Atomic OSSEC installer after that, and Ill send you instructions and our support team will get you all setup, as well as show you how to use the GUI.

What distro are you using?

For the hub, either Centos or Redhat 7/8. Ubuntu hub support is coming soon.

For agents, any modern Linux distro, or Windows or MacOS.

What version of OSSEC are using?

Please report any bugs directly to support@atomicorp.com.

We've really listened to your feedback and requests for v6, and were happy to announce that v6 of ASL in now ready for beta testing (soon to be called Atomic Protector). Keep in mind this is a beta, so you should expect bugs. Major Changes: * Completely redesigned GUI and architecture for faster per...

To make it easier to download the rules, we've released a new download page youll find at the URL below:

https://atomicorp.com/atomic-modsecurity-rules/

Assuming your script works fine from the command line as root, is there anything OS wise preventing ossec-execd from writing to that file, for example is SELinux blocking ossec-execd from writing to that directory or file?

Could you post the full output of the yum command?

Could you explain a little more about what you want to change?

What I mean is that there seems to be a bug BEFORE the decoders are selected. The IP address is located before the log text itself, so it's not a matter of decoder here, but about the parser that separates the line into the the fields that are later processed by the decoders. The parser is the deco...

I think I understand where you might be having trouble. Think of decoders as translators, so even though a log might be going thru a decoder, if it doesnt understand the log message it wont translate it correctly. You need the right decoder for that specific log format, even if its coming from the s...

It doesnt look like you have a decoder for that application:

**Phase 2: Completed decoding.
No decoder matched.

Without a decoder, OSSEC doesnt know what each field means.

EL8 is officially supported.