openstack/openstack-manuals
Code Issues Proposed changes

ch012_configuration_management clean up - minor

Browse Source 
merged into 1 sentence "then work to define how to handle the various severity levels."
changed This complexity brings with it additional security concerns.
subject and predicate change

Change-Id: Ia7260bb99842118413f8b8c9543651e12ad657df
This commit is contained in:
Shilla Saebi 2014-01-24 15:47:57 -05:00 committed by Diane Fleming
parent 0d5847775f
commit 3864851a2c
1 changed files with 7 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/security-guide/ch012_configuration-management.xml
View File

@ -149,18 +149,17 @@
</tr>
</tbody>
</informaltable>
<para>The previous table illustrates a generic approach to
<para>This table illustrates a generic approach to
measuring the impact of a vulnerability based on where it
occurs in your deployment and the effect. For example, a
single level privilege escalation on a Compute API node
potentially allows a standard user of the API to escalate to
have the same privileges as the root user on the node.</para>
<para>We suggest cloud administrators customize and expand this
table to suit their needs. Then work to define how to handle
the various severity levels. For example, a critical-level
security update might require the cloud to be upgraded on a
specified time line, whereas a low-level update might be more
relaxed.</para>
<para>We suggest that cloud administrators use this table as a
model to help define which actions to take for the various
security levels. For example, a critical-level security update
might require the cloud to be upgraded on a specified time
line, whereas a low-level update might be more relaxed.</para>
</section>
<section xml:id="ch012_configuration-management-idp100864">
<title>Testing the Updates</title>
@ -317,7 +316,7 @@
ranging from basic hardening to compliance validation.</para>
<para>Configuration management and security auditing tools will
introduce another layer of complexity into the cloud.  This
complexity brings with it additional security concerns. We view
complexity brings additional security concerns with it. We view
this as an acceptable risk trade-off, given their security
benefits. Securing the operational use of these tools is beyond
the scope of this guide.</para>