openstack/barbican

Barbican is a ReST API designed for the secure storage, provisioning and management of secrets, including in OpenStack environments.

Go to file

Jarret Raim f8b70aa972 Update LICENSE		2013-03-25 11:09:25 -05:00
examples	Added Agent API and Agent WebUI	2013-03-12 09:54:08 -05:00
static	Update Web UI for event display	2013-03-08 20:18:12 -06:00
templates	Added Agent API and Agent WebUI	2013-03-12 09:54:08 -05:00
.gitignore	Adding SQLAlchemy persistence	2013-02-16 19:10:11 -06:00
barbican_api_test.py	Added Agent API and Agent WebUI	2013-03-12 09:54:08 -05:00
barbican_api.py	Adding PANIC log type	2013-03-21 16:34:21 -05:00
barbican_tests.py	Simple formatting fixes	2013-02-16 18:03:06 -06:00
barbican.py	PEP8 Fixes	2013-03-14 20:52:24 -05:00
database.py	Added Pairing Call	2013-02-26 20:53:08 -06:00
LICENSE	Update LICENSE	2013-03-25 11:09:25 -05:00
models.py	PEP8 Fixes	2013-03-14 20:52:24 -05:00
README.md	Basic Readme	2013-03-25 08:16:52 -05:00
requirements.txt	Added missing dependency	2013-03-14 20:52:53 -05:00

README.md

Barbican

Barbican is a ReST API designed for the secure storage, provisioning and management of secrets. It is aimed at being useful for all environments, including large ephemeral Clouds. The project is supported by Rackspace Hosting.

Barbican is part of a set of applications that make up the CloudKeep ecosystem. The other systems are:

Postern - Go based agent that provides access to secrets from the Barbican API.
Palisade - AngularJS based web ui for the Barbican API.
Keep - A python-based command line client for the Barbican API.

Additional documentation can be found on the Github Wiki. For questions, comments or concerns, hop on the mailing list and let us know what you think.

Getting Started

Installation
Contributing
API Documentation
Technology
FAQ

Why Should You Use Barbican?

The current state of key management is atrocious. While Windows does have some decent options through the use of the Data Protection API (DPAPI) and Active Directory, Linux lacks a cohesive story around how to manage keys for applicaiton use.

Barbican was designed to solve this problem. The system was motivated by internal Rackspace needs, requirements from OpenStack and a realization that the current state of the art could use some help.

Barbican will handle many types of secrets, including:

Symmetric Keys - Used to perform reversible encryption of data at rest, typically using the AES algorithm set. This type of key is required to enable features like encrypted Swift containers and Cinder volumes, encrypted Cloud Backups, etc.
Asymmetric Keys - Asymmetric key pairs (sometimes referred to as public / private keys) are used in many scenarios where communication between untrusted parties is desired. The most common case is with SSL/TLS certificates, but also is used in solutions like SSH keys, S/MIME (mail) encryption and digital signatures.
Raw Secrets - Barbican stores secrets as a base64 encoded block of data (encrypted, naturally). Clients can use the API to store any secrets in any format they desire. The Postern agent is capable of presenting these secrets in various formats to ease integration.

For the symmetric and asymmetric key types, Barbican supports full lifecycle management including provisioning, expiration, reporting, etc. A plugin system allows for multiple certificate authority support (including public and private CAs).

Design Goals

Provide a central key-store capable of distributing keying material to all types of deployments including ephemeral Cloud instances.
Support reasonable compliance regimes through reporting and auditability.
Application adoption costs should be minimal or non-existent.
Build a community and ecosystem by being open-source and extensible.
Improve security through sane defaults and centralized management of key policies.
Out of band communication mechanism to notify and protect sensitive assets.