Compliance checking

[jvehent]

This set of patches add API code to evaluate compliance. This is a work in progress, not ready to merge yet.

[jvehent]

After some discussions with @netantho, we're gonna go with an output format similar to the one below:

{
    "timestamp": "2014-05-13T21:23:27.536843Z",
    "target": "memcache1.stage.example.net",
    "policy": {
      "name": "system",
      "url": "https: //mana.mozilla.org/wiki/display/SECURITY/System+Security+Policy",
      "level": "medium"
    },
    "check": {
      "description": "compliance check for openssh",
      "name": "check for verbose logging (logs fingerprints)",
      "location": "/etc/ssh/sshd_config",
      "test": {
        "type": "regex",
        "value": "(?i)^loglevelverbose$"
      }
    },
    "compliance": true,
    "link": "http://localhost:1664/api/v1/command?commandid=6013023743752837160&options=verifycompliance"
}

Some processing will be requiring to go from one commands containing multiple checks, to one check per json file. Below is a query that does the initial data retrieval from the DB, before manipulation:

SELECT commands.finishtime as timestamp, agents.name as target,
  actions.name as name, actions.description->>'policy' as policy,
  CAST(commands.results AS TEXT)
FROM commands
  INNER JOIN actions ON (commands.actionid = actions.id)
  INNER JOIN agents ON (commands.agentid = agents.id)
WHERE threat->>'family' = 'compliance';

[jvehent]

github is confused. the set of patches shown here are from the master branch, not sure what happened but this got merged in #15 anyway.