Thehive: Playbook/Scripting/Rules for automatic case management

Created on 21 Aug 2017  路  5Comments  路  Source: TheHive-Project/TheHive

Playbook/Scripting/Rules for automatic case management

Request Type

Feature Request

Problem Description

When creating a case or importing a case from an alert, it would be nice if we could automate some of the steps such as running specific analyzers or importing a case tagging it and then closing it immediately after import (for metric collection purposes).

I was thinking this could maybe be done within case templates?

Understand that this would be a large undertaking.

feature request low-pri

Most helpful comment

This is a use case that we need and would be happy to contribute back.
At a high level we are thinking along the lines of

  • Playbooks will be stored in a directory accessible to TheHive. They will be identified by the first part of their filename eg. xxxx.yaml for playbook xxxx.
  • The location of the playbooks directory will be stored in TheHive's application.conf.
  • Playbooks are COPS compatible yaml files describing sequences of running analyzers.
  • A playbook-id will be in the alert data being received by TheHive.
  • When an alert is received by TheHive, if the playbook-id field in the alert is populated, then the playbook is looked up in the playbook directory.

Please let us know what you think about the above.

All 5 comments

Hi @BrevilleBro. While we understand the use case and find it interesting, we concur that this would be a hefty undertaking. And sadly, we do not have enough free cycles to implement such a feature in the foreseeable future.

This is a use case that we need and would be happy to contribute back.
At a high level we are thinking along the lines of

  • Playbooks will be stored in a directory accessible to TheHive. They will be identified by the first part of their filename eg. xxxx.yaml for playbook xxxx.
  • The location of the playbooks directory will be stored in TheHive's application.conf.
  • Playbooks are COPS compatible yaml files describing sequences of running analyzers.
  • A playbook-id will be in the alert data being received by TheHive.
  • When an alert is received by TheHive, if the playbook-id field in the alert is populated, then the playbook is looked up in the playbook directory.

Please let us know what you think about the above.

This would be something that I would interested in contributing too as well. To be competitive with other SOAR products playbooks of actions to take based on type of alert or incident would be useful. This leads to the SOC having standard actions to take and makes those actions consistent across all the members.

@saadkadhi maybe ansible integration could be a fast way to implement playbooks support

This is a huge undertaking (I actually attempted to do parts of this with TheHive), but if you have the willpower, I say do it (and please share your efforts). There is also this issue that's open: https://github.com/TheHive-Project/TheHive/issues/956

I wrote a blog about an open source alternative here: https://medium.com/@Frikkylikeme/automation-for-everyone-with-thehive-and-walkoff-6691f1343238

Was this page helpful?
0 / 5 - 0 ratings