Threat Stack Cookbook

Chef recipes to deploy the Threat Stack server agent

Requirements

• chef > 11.0

Platforms

• Amazon Linux
• CentOS
• RedHat
• Ubuntu

Cookbooks

The following Opscode cookbooks are dependencies:

• apt
• yum

Recipes

default

Installs the Threat Stack agent package and register the agent with the service

repo

Sets up the Apt or Yum repo for installing the Threat Stack agent package

Usage

1. Add this cookbook to your Chef Server or add to your Berksfile

cookbook 'threatstack', '~> 1.0.0'

2. Add your deploy api key. The recommended way is to use an encrypted databag with name and item specified by the corresponding attributes. The cookbook will use the 'deploy_key' value from the databag by default. You can also set the key directly or using a wrapper cookbook in the node['threatstack']['deploy_key'] attribute. Setting the key will disable the encrypted data bag lookup.

3. Add this recipe to your runlist or include in another recipe

Attributes

node['threatstack']['version'] - Set to pin to a specific Threat Stack agent release version

node['threatstack']['pkg_action'] - Set to :upgrade if you want to take the latest release (defaults to :install)

node['threatstack']['deploy_key'] - Override this with your deploy key for agent registration.

node['threatstack']['data_bag_name'] - Name of the encrypted databag containing Threat Stack secrets.

node['threatstack']['data_bag_item'] - Name of the encrypted databag item containing Threat Stack secrets.

node['threatstack']['rulesets'] - Set or override this with an array of rulesets to apply to the node

node['threatstack']['hostname'] - register the agent in the UI by a specific name (defaults to hostname)

Encrypted Data Bag Contents

deploy_key - the deploy key for agent registration.