Well, I don't know about your first question, but I asked something
similar to your second question a while back. You can specify
multiple ossec servers in your client config. If you do so, the
agents communicate with them in the order you specify. If the first
server goes down, the agent will communicate with the second server.
If the second server goes down, the agents will switch to the third
server and so on. That is:
<client>
<server-ip>10.11.12.1</server-ip>
<server-ip>10.11.12.2</server-ip>
<server-ip>10.11.12.3</server-ip>
</client>
For the server end, since 1.6 ossec has supported multiple servers.
See:
http://www.ossec.net/main/manual/manual-muti-server-architecture
--cryogen
Hello, Macker. Welcome to the list. You'll find this to be a friendly place.
> 1) user accounts: ossec requires 3 seperate user accounts and 1 group
> account. Due to my internal linux patch management system, it would be
> preferrable not to need 3 sperate user accounts. Is there a way to have
> it run as 1 user account, or is that lowering the security/segregation
> of duty, etc?
It may be possible, but it's not recommended. OSSEC does this as a
matter of proper privilege separation between the daemons. This reduces
the chance of a remote exploit leading to a full compromise. It is
designed to be secure by default and any changes would have to be
weighed very carefully.
> 3) Anyone have success/horror stories I should be aware about with this
> amount of servers? Perhaps helpful advice, lessons learned.
This amount of servers is no problem for OSSEC. It can handle a load
like this with very minimal hardware. My advice would be to implement
with a slow, methodical approach. Tune as you go. You don't want to be
bombarded with alerts and start to mentally tune them out.