[PATCH 09/11] Removed description fields in auxilary.xml
Shawn Wells
shawn at redhat.com
Wed May 16 19:35:35 UTC 2012
Just realized we didn't need the <description> tag in the aux files, only the rationale, so deleting them
---
rhel6/src/input/auxiliary/srg_support.xml | 14 --------------
1 files changed, 0 insertions(+), 14 deletions(-)
diff --git a/rhel6/src/input/auxiliary/srg_support.xml b/rhel6/src/input/auxiliary/srg_support.xml
index 1a92060..2fe2c99 100644
--- a/rhel6/src/input/auxiliary/srg_support.xml
+++ b/rhel6/src/input/auxiliary/srg_support.xml
@@ -17,14 +17,12 @@ Red Hat Enterprise Linux meets this requirement by design.
<Rule id="audit_account_termination">
<title>The operating system must notify, as required, appropriate individuals for account termination.</title>
-<description>Monitoring account termination is critical to ensure a denial of service situation does not exist on the operating system. An unexpected account termination can also be a sign of a rogue administrator account that may be deleting traces of activity. In order to facilitate the monitoring, the operating system must notify designated personnel when an account is terminated.</description>
<rationale>The Red Hat Enterprise Linux Auditing Subsystem provides this functionality natively, placing this information in the audit logs for system administrator review.</rationale>
<ref disa="1686" />
</Rule>
<Rule id="audit_account_creation">
<title>The operating system must notify, as required, appropriate individuals when accounts are created.</title>
-<description>Monitoring account creation is critical to ensure only appropriate personnel have access to the operating system. This reduces the possibility a rogue account will be created. In order to facilitate the monitoring, the operating system must notify designated personnel when an account is created.</description>
<rationale>The Red Hat Enterprise Linux Auditing Subsystem provides this functionality natively, placing this information in the audit logs for system administrator review.</rationale>
<ref disa="1683" />
</Rule>
@@ -47,23 +45,12 @@ The requirement is impractical or out of scope.
<Rule id="enforce_remote_connections">
<title>The operating system must enforce requirements for remote connections to the information system</title>
-<description>The organization will define the requirements for connection of remote connections. In order
-to ensure the connection provides adequate integrity and confidentiality of the connection, the operating system must enforce these requirements.
-</description>
<rationale>The technical specifications to meet this policy are organizationally defined, and therefor generic guidance is not availabile.</rationale>
<ref disa="66" />
</Rule>
<Rule id="central_config_management">
<title>The operating system must employ automated mechanisms to centrally manage configuration settings</title>
-<description>Configuration settings are the configurable security-related parameters of information technology
-products that are part of the information system. Security-related parameters are those parameters
-impacting the security state of the system including parameters related to meeting other security control
-requirements. Security-related parameters include, for example, registry settings; account, file, and directory
-settings (i.e., permissions); and settings for services, ports, protocols, and remote connections. Rather
-than visiting each system when making configuration changes, organizations must employ automated tools that
-can make changes across all systems. This greatly increases efficiency and manageability of applications in a
-large scale environment.</description>
<rationale>An organizational configuration management policy is out of scope of this security guide.</rationale>
<ref disa="370" />
</Rule>
@@ -80,5 +67,4 @@ The requirement is impractical or out of scope.
</description>
</Group>
-
</Group>
--
1.7.1
--uAKRQypu60I7Lcqm--
More information about the scap-security-guide
mailing list