8dbacc7b42
Current description is incorrect, since barbican does not store each projects KEK in HSM. As eventually, that would mean having thousand of keys, while Thales Luna Network HSM has limit of 100 keys for DPoD, so it will be unable to use big part of HSM solutions with that approach. Instead only MKEK and HMAC are stored in HSM and used to encrypt/decrypt KEKs. Change-Id: I8c4eaaa42262797632ce4c4296c04a4fe62b8fcf |
||
|---|---|---|
| case-studies | ||
| common | ||
| security-guide | ||
| security-notes | ||
| security-threat-analysis/source | ||
| tools | ||
| .gitignore | ||
| .gitreview | ||
| .zuul.yaml | ||
| bindep.txt | ||
| doc-tools-check-languages.conf | ||
| README.rst | ||
| test-requirements.txt | ||
| tox.ini | ||
Team and repository tags
OpenStack Security Documentation
This repository contains the OpenStack Security documentation.
For details on how to contribute to the documentation, see the OpenStack Documentation Contributor Guide.
It includes these manuals:
- Security Guide
- Security Notes
- Security Threat Analysis
The Security Notes are published by the OpenStack Security Project (OSSP) to advise users of security related issues. For more information refer to the Security Notes and Security Note Process.
Security Advisories are issued by the Vulnerability Management Team (VMT). For more information about OpenStack's Vulnerability Management Team (VMT) refer to the Vulnerability Management Process.
Directory Structure
Security Guide is in the directory security-guide, which
source files in RST format in the directory
security-guide/source.
Security Threat Analysis is in the directory
security-threat-analysis, which source files in RST format
in the directory security-threat-analysis/source.
The security notes are in the directory
security-notes.
Testing of changes and building of the guides
Install the python tox package and run tox from the
top-level directory to use the same tests that are done as part of our
Jenkins gating jobs.
tox
Contributing
Our community welcomes all people interested in open source cloud computing, and encourages you to join the OpenStack Foundation.
The best way to get involved with the community is to talk with
others online or at a meet up and offer contributions through our
processes, the OpenStack wiki,
blogs, or on IRC at #openstack on
irc.freenode.net.
We welcome all types of contributions, from blueprint designs to documentation to testing to deployment scripts.
If you would like to contribute to the documents, please see the OpenStack Documentation contributor guide.
Bugs
Bugs should be filed on Launchpad, not GitHub:
If you find a security issue in OpenStack, not in the contents of the Security Guide, please see How to Report Security Issues to OpenStack.
Release Notes
https://docs.openstack.org/releasenotes/openstack-manuals
Installing
Refer to the OpenStack Security Guide to see where these documents are published and to learn more about the OpenStack Security Guide.