This is a cookbook contributed by the Barricade community.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
attributes
recipes
templates/default
CHANGELOG.md
CONTRIBUTORS.md
LICENSE.md
README.md
metadata.rb

README.md

chef-barricade

========================

This cookbook allows you to automate the setup of the Barricade.io agent so that you can have confidence in your infrastructure's security and gain immediate completely visibility into your security operations and continuously test your security as you develop and build.

## Requirements

  • Ubuntu 12.04 (64-bit)
  • Ubuntu 14.04 LTS (64-bit)
  • Ubuntu 14.10 (64-bit)
  • CentOS 6.5 (64-bit)
  • CentOS 7.0 (64-bit)

Attributes

barricade::default

See the attributes/default.rb for more advanced attributes related to the agent.

Key Type Description Default
['barricade']['barricade_key'] String Your Barricade.io automation license retrievable from [your team page](https://app.barricade.io/dashboard/settings/team/profile) Required
['barricade']['install_script'] String The URL from which to fetch the Barricade install script. Dependent on your Barricade automation key.
['barricade']['tags'] String An arbitrary scalar value taht will be used by your and your team to effectively tag results sent to the Barricade platform. Use comma-separation to set multiple tags prod, chef

Usage

barricade::default

Make sure to retrieve your automation key from your Barricade dashboard and edit the attributes/default.rb file to specifiy your barricade_key.

If you want to tag your deployments, you can also modify the tags key to contain any string. A comma-delimited string means you'll have multiple tags.

e.g. Just include barricade in your node's run_list:

{
  "run_list": [
    "recipe[barricade]"
  ]
}

TODO

Including, but not limited to ...

  • Fully support all of the standard Chef-supported distributions
  • Support additonal build configurations
  • Support additonal configuration file attributes

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

License

See LICENSE