Security Guide Overhaul

Registered by Alexandra Settle on 2017-03-10

After the 2017 Atlanta PTG, there was a discussion and a consensus surrounding the current state of the Security Guide published on docs.o.o.

As it stands, the Security Guide has been lacking in a proper maintenance plan by both the doc and security teams, and now requires updates to the pre-existing content.

The aim over the next two cycles is to overhaul the Security Guide to be a more maintainable guide and to target an appropriate audience.

Blueprint information

Status:
Started
Approver:
Robert Clark
Priority:
Undefined
Drafter:
Alexandra Settle
Direction:
Needs approval
Assignee:
None
Definition:
Approved
Series goal:
Proposed for pike
Implementation:
Started
Milestone target:
None
Started by
Alexandra Settle on 2017-03-10

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:442739,n,z

Addressed by: https://review.openstack.org/442739
    [sec-guide] Elaborating on QoSaaS

Gerrit topic: https://review.openstack.org/#q,topic:bug/1632050,n,z

Addressed by: https://review.openstack.org/443368
    Added checklist item for cinder volume encryption

Gerrit topic: https://review.openstack.org/#q,topic:new,n,z

Addressed by: https://review.openstack.org/445053
    Listing all types of supported tokens

Gerrit topic: https://review.openstack.org/#q,topic:bug/1411327,n,z

Addressed by: https://review.openstack.org/445237
    Modify introduction to SSL TLS

Gerrit topic: https://review.openstack.org/#q,topic:bug/1447702,n,z

Addressed by: https://review.openstack.org/445571
    Elaborating on the use of Memcached

Gerrit topic: https://review.openstack.org/#q,topic:bp/sec-guide-overhaul,n,z

Addressed by: https://review.openstack.org/445911
    Edits to the security-doc

Addressed by: https://review.openstack.org/446033
    Edits to the compute chapter

Addressed by: https://review.openstack.org/451794
    [sec-guide] Edits to the compliance chap

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.