Wazuh could replace a number of tools that we are aggregating inside AniNIX/Sharingan:
lynis
arch-audit
graylog+elasticsearch+mongodb
rkhunter
AIDE
However, the agent is heavy, wanting gigs of storage, two cores, and a gig of memory. This is a tradeoff, at the moment -- the syslog aggregation would be the same, but we are using daily inspections with our host tool stack to reduce persistent resource utilization. This makes our current stack more cost-effective. We can revisit this as resources become cheaper.
Note, agent-based security tools tend to require privileged access for the agents, which makes remote access to the dashboard a major issue. In our deployment, agents file data via syslog to the aggregator which prevents compromise of the aggregator from infecting servers. Examples of why this is bad:
Wazuh could replace a number of tools that we are aggregating inside AniNIX/Sharingan:
* lynis
* arch-audit
* graylog+elasticsearch+mongodb
* rkhunter
* AIDE
However, the agent is heavy, wanting gigs of storage, two cores, and a gig of memory. This is a tradeoff, at the moment -- the syslog aggregation would be the same, but we are using daily inspections with our host tool stack to reduce persistent resource utilization. This makes our current stack more cost-effective. We can revisit this as resources become cheaper.
Deployment details: https://documentation.wazuh.com/current/deployment-options/docker/index.html
Example deployment on Arch:
https://wix-doc.com/blog/2024-05-01-secure-your-arch-linux-with-wazuh/
Note, agent-based security tools tend to require privileged access for the agents, which makes remote access to the dashboard a major issue. In our deployment, agents file data via syslog to the aggregator which prevents compromise of the aggregator from infecting servers. Examples of why this is bad:
* https://github.com/wazuh/wazuh/security/advisories/GHSA-hcrc-79hj-m3qh
* https://cybersecuritynews.com/crowdstrike-falcon-windows-sensor-vulnerability
* https://www.techtarget.com/whatis/feature/Explaining-the-largest-IT-outage-in-history-and-whats-next
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Relevant links:
Wazuh could replace a number of tools that we are aggregating inside AniNIX/Sharingan:
However, the agent is heavy, wanting gigs of storage, two cores, and a gig of memory. This is a tradeoff, at the moment -- the syslog aggregation would be the same, but we are using daily inspections with our host tool stack to reduce persistent resource utilization. This makes our current stack more cost-effective. We can revisit this as resources become cheaper.
Deployment details: https://documentation.wazuh.com/current/deployment-options/docker/index.html
Example deployment on Arch:
https://wix-doc.com/blog/2024-05-01-secure-your-arch-linux-with-wazuh/
Note, agent-based security tools tend to require privileged access for the agents, which makes remote access to the dashboard a major issue. In our deployment, agents file data via syslog to the aggregator which prevents compromise of the aggregator from infecting servers. Examples of why this is bad: