One thing that occurred to me as I started playing with the module is that I have to be pro-active to go to the site and review the report. I then thought of how I've used the Nagios module to avoid having to do that for the site status report and thought "this should have a nagios hook". Here's an initial "all or nothing" pass at it. It's a critical error if the site does not pass the review 100%, a warning if the review run fails, and an OK status if the review passes all checks.

An enhancement to the module to provide a severity level for specific checks would allow the Nagios check to be a bit more subtle and return a WARNING for less severity security check failures.

Comments

coltrane’s picture

This is a great idea, crdant. I was planning on writing or integrating with a notification system and adding a hook_cron implementation so your security status can be tracked. I like this integration with nagios though, so let me review and think a bit on the severity levels.

greggles’s picture

Is nagios a polling system? I thought it could be a push system that hooked into watchdog. I'd like to solve this generally by watchdogging and letting nagios hook into that if it feels appropriate. Or is that crazy talk because I don't know anything about nagios?

crdant’s picture

Nagios is polling based. You configure plugins that perform checks on systems and services on a periodic basis. kbhahey put together the Nagios module with a hook to allow additional services to be monitored by the initial set he defined. I figured this would be a good additional check to have in their when I'm monitoring with Nagios. You could write a Nagios plugin that watched the watchdog table instead of making a web request (which is how Khalid's module works), but it would still be polling based.

You can also do a push-style notification with Nagios using it's external command functionality, but that's assuming that you can write to a specific file on the Nagios server (or put together a listener that writes to it).

greggles’s picture

Thanks for the explanation - this patch makes perfect sense in that case.

coltrane’s picture

StatusFileSize
new1.46 KB

Here's an updated patch. I haven't tested but I can commit somewhat soon.

coltrane’s picture

StatusFileSize
new1.46 KB

This one over #5, it incorrectly referenced check status.

smustgrave’s picture

Issue summary: View changes
Status: Needs review » Closed (outdated)

As Drupal6 has been EOL https://www.drupal.org/about/drupal6-eol closing as outdated