{"id":651,"date":"2017-10-04T03:19:23","date_gmt":"2017-10-04T01:19:23","guid":{"rendered":"https:\/\/blog.unetresgrossebite.com\/?p=651"},"modified":"2017-10-05T01:21:13","modified_gmt":"2017-10-04T23:21:13","slug":"wazuh","status":"publish","type":"post","link":"https:\/\/blog.unetresgrossebite.com\/?p=651","title":{"rendered":"Wazuh"},"content":{"rendered":"

As a follow-up to our previous OSSEC<\/a> post, and to complete the one on Fail2ban & ELK<\/a>, we’ll review today Wazuh.<\/p>\n

\"netstat<\/a>

netstat alerts<\/p><\/div>\n

As their documentation states it, “Wazuh is a security detection, visibility, and compliance open source project. It was born as a fork of OSSEC HIDS, later was integrated with Elastic Stack and OpenSCAP evolving into a more comprehensive solution<\/em>“. We could remark that OSSEC packages used to be distributed on some Wazuh repository, while Wazuh is still listed as OSSEC official training, deployment and assistance services provider. You might still want to clean up some defaults, as you would soon end up receiving notifications for any connection being established or closed …<\/p>\n

OSSEC is still maintained, last commit to their GitHub project was a couple days ago as of writing this post<\/a>, while other commits are being pushed to Wazuh repository<\/a>. If both products are still active, my last attempts configuring Kibana integration with OSSEC was a failure, due to Kibana5 not being supported. Considering Wazuh offers enterprise support, we could assume their sample configuration & ruleset are at least as relevant as those you’ld find with OSSEC.<\/p>\n

\"wazuh<\/a>

wazuh manager status<\/p><\/div>\n

Wazuh documentation is pretty straight-forward<\/a>, a new service wazuh-api (NodeJS) would be required on your managers, which would then be used by Kibana querying Wazuh status. Debian packages were renamed from ossec-hids & ossec-hids-agent to wazuh-manager & wazuh-agent respectively. Configuration is somewhat similar, although you won’t be able to re-use those you could have installed alongside OSSEC. Note the wazuh-agent package would install an empty key file: you would need to drop it, prior to registering against your manager.<\/p>\n

 <\/p>\n

\"wazuh-agents\"<\/a>

wazuh agents<\/p><\/div>\n

Configuring Kibana integration, note Wazuh documentation misses some important detail, as reported on GitHub<\/a>. That’s the single surprise I had reading through their documentation, the rest of their instructions work as expected: having installed and started wazuh-api service on your manager, then installed Kibana wazuh plugin on your all your Kibana instances, you would find some Wazuh menu showing on the left. Make sure your wazuh-alerts index is registered in the Management section, then go to Wazuh.<\/p>\n

If uninitialized, you would be offered to enter your Wazuh backend URL, a port, a username and corresponding password, connecting to wazuh-api. Note that configuration would be saved into some new\u00a0.wazuh<\/em>\u00a0index. Once configured, you would have some live view of your setup, which agents are connected, what alerts you’re receiving, … eventually, set up new dashboards.<\/p>\n

Comparing this to OSSEC PHP web interface, marked as deprecated since years, … Wazuh takes the lead!<\/p>\n

\"CIS<\/a>

CIS compliance<\/p><\/div>\n

\"OSSEC<\/a>

OSSEC alerts<\/p><\/div>\n

\"Wazuh<\/a>

Wazuh Overview<\/p><\/div>\n

\"PCI<\/a>

PCI Compliance<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"

As a follow-up to our previous OSSEC post, and to complete the one on Fail2ban & ELK, we’ll review today Wazuh. As their documentation states it, “Wazuh is a security detection, visibility, and compliance open source project. It was born as a fork of OSSEC HIDS, later was integrated with Elastic Stack and OpenSCAP evolving […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[8,10,7,2],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/posts\/651"}],"collection":[{"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=651"}],"version-history":[{"count":3,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/posts\/651\/revisions"}],"predecessor-version":[{"id":661,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=\/wp\/v2\/posts\/651\/revisions\/661"}],"wp:attachment":[{"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=651"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=651"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.unetresgrossebite.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=651"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}