Whitelist 'postgres' user from OVAL check for CCE-26966-2 (2.4.1.1.e Ensure That System Accounts Do Not Run a Shell Upon Login)

Shawn Wells shawn at redhat.com
Tue Dec 10 18:29:38 UTC 2013


On 12/10/13, 10:01 AM, Nunez, Luis K wrote:
> This is good "institutional knowledge" usefully for someone troubleshooting a
> system.  It would be nice to somehow capture this knowledge somewhere.   Is
> the STIG Benchmark the right place for such information? Also can the fix
> disruption attribute be leveraged to indicate warnings about potential issues
> to a fix.
>
> Below is the fix disruption attribute excerpt from the XCCDF specification.
> An estimate of the potential for disruption or operational degradation that
> the application of this fix will impose on the target. When specified, the
> attribute SHALL have one of the following values:
> - unknown (disruption not defined) (default)
> -  low (little or no disruption expected)
> - medium (potential for minor or short-lived disruption)
> - high (potential for serious disruption)
>
>
> Thanks.
>
>
> Luis Nunez
> J83B - Industry Collaboration
> The MITRE Corporation
> www.mitre.org


This is reasonable. Opened an RFE to track this. Feel free to add 
yourself @
https://bugzilla.redhat.com/show_bug.cgi?id=1040111


More information about the scap-security-guide mailing list