Bug 1377411 - [DOCS] OpenShift docs lack Security Best Practices section
Summary: [DOCS] OpenShift docs lack Security Best Practices section
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.5.z
Assignee: Alex Dellapenta
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-19 15:33 UTC by Joel Smith
Modified: 2021-12-10 14:44 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-06 10:57:17 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Joel Smith 2016-09-19 15:33:24 UTC
Description of problem:

From Insomnia security:

> The OpenShift documentation is extensive and well written,
> however the key security controls are not clearly enumerated
> in one location in the documentation. For example, Insomnia
> was approximately a week into familiarisation with the
> platform before understanding that the Custom Build Strategy
> was inherently dangerous (it is explained in the Securing Builds
> by Strategy section, but this is relatively buried in the Cluster
> Administration). The consequences of setting some of the controls
> (e.g. in the Managing Security Control Constraints section) are
> not clearly illustrated; it is not clear that some of these can
> result in complete failure of containment on the entire platform.

> It may be feasible to create a specific “Security Best Practices”
> section of the document which explains the key security controls,
> their effect on the posture of the platform, and with
> recommendations for these controls.

I agree that the lack of a section that details all of the critical controls in one location is a problem. Could we please remedy this? Perhaps we could query team leads to see if they have any candidate controls to add to the section in addition to the one mentioned above.


Document URL: 

Section Number and Name: 

Describe the issue: 

Suggestions for improvement: 

Additional information:


Note You need to log in before you can comment on or make changes to this bug.