Greetings All,
New to this list!
I think I might have found an issue with the SSG policy content.
Summary: If you do not have telnet installed on the system it causes Rule ID: disable_telnet_service to fail.
In no place in this rule does it consider that telnet might not be installed at all, so it fails (rather than errors, or even better does a check as a precursor to see if its installed at all and if not passes!)
grep 'id="oval:ssg:tst:231"' ssg-rhel6-oval.xml.result.xml <ind-def:textfilecontent54_test id="oval:ssg:tst:231" version="1" check_existence="all_exist" check="all" comment="Disable Telnet Service"> <test test_id="oval:ssg:tst:231" version="1" check_existence="all_exist" check="all" result="false"/>
<Rule id="disable_telnet_service" selected="false" severity="high"> <title xml:lang="en-US">Disable telnet Service</title> <description xmlns:xhtml="http://www.w3.org/1999/xhtml" xml:lang="en-US">
The xhtml:codetelnet</xhtml:code> service can be disabled with the following command:
xhtml:pre# chkconfig telnet off</xhtml:pre> </description> <reference href="http://csrc.nist.gov/publications/nistpubs/800-53-Rev3/sp800-53-rev3-final.pdf">AC-17(8)</reference> <reference href="http://csrc.nist.gov/publications/nistpubs/800-53-Rev3/sp800-53-rev3-final.pdf">CM-7</reference> <reference href="http://csrc.nist.gov/publications/nistpubs/800-53-Rev3/sp800-53-rev3-final.pdf">IA-5(1)(c)</reference> <reference href="http://iase.disa.mil/cci/index.html">68</reference> <reference href="http://iase.disa.mil/cci/index.html">1436</reference> <reference href="http://iase.disa.mil/cci/index.html">197</reference> <reference href="http://iase.disa.mil/cci/index.html">877</reference> <reference href="http://iase.disa.mil/cci/index.html">888</reference> <reference xmlns:dc="http://purl.org/dc/elements/1.1/" href="test_attestation"> dc:contributorDS</dc:contributor> dc:date20121026</dc:date> </reference>
<rationale xmlns:xhtml="http://www.w3.org/1999/xhtml" xml:lang="en-US">
The telnet protocol uses unencrypted network communication, which means that data from the login session, including passwords and all other information transmitted during the session, can be stolen by eavesdroppers on the network. The telnet protocol is also subject to man-in-the-middle attacks.
</rationale>
<ident system="http://cce.mitre.org">CCE-26836-7</ident> <check system="http://oval.mitre.org/XMLSchema/oval-definitions-5"> <check-content-ref name="oval:ssg:def:230" href="ssg-rhel6-oval.xml"/> </check>
<check system="ocil-transitional"> <check-export export-name="the service is running" value-id="conditional_clause"/> <check-content xmlns:xhtml="http://www.w3.org/1999/xhtml">
To check that the xhtml:codetelnet</xhtml:code> service is disabled in system boot configuration, run the following command: xhtml:pre# chkconfig xhtml:codetelnet</xhtml:code> --list</xhtml:pre> Output should indicate the xhtml:codetelnet</xhtml:code> service has either not been installed, or has been disabled at all runlevels, as shown in the example below: xhtml:pre# chkconfig xhtml:codetelnet</xhtml:code> --list xhtml:codetelnet</xhtml:code> 0:off 1:off 2:off 3:off 4:off 5:off 6:off</xhtml:pre>
Run the following command to verify xhtml:codetelnet</xhtml:code> is disabled through current runtime configuration:
xhtml:pre# service telnet status</xhtml:pre>
If the service is disabled the command will return the following output:
xhtml:pretelnet is stopped</xhtml:pre> </check-content> </check> </Rule>
Cheers, Stu
Welcome to the list :-)
There is a ticket for this that Sawn Wells entered for me. See https://fedorahosted.org/scap-security-guide/ticket/409
https://lists.fedorahosted.org/pipermail/scap-security-guide/2013-May/003330...
R/ BP
On Wed, 31 Jul 2013 16:15:42 +0100, Stuart Green stuart.green@doccentrics.com wrote: Greetings All,
New to this list!
I think I might have found an issue with the SSG policy content.
Summary: If you do not have telnet installed on the system it causes Rule ID: disable_telnet_service to fail.
In no place in this rule does it consider that telnet might not be installed at all, so it fails (rather than errors, or even better does a check as a precursor to see if its installed at all and if not passes!)
grep 'id="oval:ssg:tst:231"' ssg-rhel6-oval.xml.result.xml <ind-def:textfilecontent54_test id="oval:ssg:tst:231" version="1" check_existence="all_exist" check="all" comment="Disable Telnet Service"> <test test_id="oval:ssg:tst:231" version="1" check_existence="all_exist" check="all" result="false"/>
<Rule id="disable_telnet_service" selected="false" severity="high"> <title xml:lang="en-US">Disable telnet Service</title> <description xmlns:xhtml="http://www.w3.org/1999/xhtml"
xml:lang="en-US">
The <xhtml:code>telnet</xhtml:code> service can be disabled with
the following command:
<xhtml:pre># chkconfig telnet off</xhtml:pre> </description> <reference
href="http://csrc.nist.gov/publications/nistpubs/800-53-Rev3/sp800-53-rev3-final.p...)</reference> <reference href="http://csrc.nist.gov/publications/nistpubs/800-53-Rev3/sp800-53-rev3-final.pdf">CM-7</reference> <reference href="http://csrc.nist.gov/publications/nistpubs/800-53-Rev3/sp800-53-rev3-final.pdf">IA-5(1)(c)</reference> <reference href="http://iase.disa.mil/cci/index.html">68</reference> <reference href="http://iase.disa.mil/cci/index.html">1436</reference> <reference href="http://iase.disa.mil/cci/index.html">197</reference> <reference href="http://iase.disa.mil/cci/index.html">877</reference> <reference href="http://iase.disa.mil/cci/index.html">888</reference> <reference xmlns:dc="http://purl.org/dc/elements/1.1/" href="test_attestation"> dc:contributorDS</dc:contributor> dc:date20121026</dc:date> </reference>
<rationale xmlns:xhtml="http://www.w3.org/1999/xhtml"
xml:lang="en-US">
The telnet protocol uses unencrypted network communication, which means that data from the login session, including passwords and all other information transmitted during the session, can be stolen by eavesdroppers on the network. The telnet protocol is also subject to man-in-the-middle attacks.
</rationale>
<ident system="http://cce.mitre.org">CCE-26836-7</ident> <check
system="http://oval.mitre.org/XMLSchema/oval-definitions-5%22%3E <check-content-ref name="oval:ssg:def:230" href="ssg-rhel6-oval.xml"/> </check>
<check system="ocil-transitional"> <check-export export-name="the service is running"
value-id="conditional_clause"/> <check-content xmlns:xhtml="http://www.w3.org/1999/xhtml">
To check that the <xhtml:code>telnet</xhtml:code> service is
disabled in system boot configuration, run the following command: xhtml:pre# chkconfig xhtml:codetelnet</xhtml:code> --list</xhtml:pre> Output should indicate the xhtml:codetelnet</xhtml:code> service has either not been installed, or has been disabled at all runlevels, as shown in the example below: xhtml:pre# chkconfig xhtml:codetelnet</xhtml:code> --list xhtml:codetelnet</xhtml:code> 0:off 1:off 2:off 3:off 4:off 5:off 6:off</xhtml:pre>
Run the following command to verify
xhtml:codetelnet</xhtml:code> is disabled through current runtime configuration:
<xhtml:pre># service telnet status</xhtml:pre> If the service is disabled the command will return the following output: <xhtml:pre>telnet is stopped</xhtml:pre> </check-content> </check> </Rule>
Cheers, Stu
scap-security-guide mailing list scap-security-guide@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
Ah-ha!! Thanks, I was looking for the buglist actually and couldn't find it!
Glad to be aboard :)
Stu
Welcome to the list :-)
There is a ticket for this that Sawn Wells entered for me. See https://fedorahosted.org/scap-security-guide/ticket/409
https://lists.fedorahosted.org/pipermail/scap-security-guide/2013-May/003330...
R/ BP
On Wed, 31 Jul 2013 16:15:42 +0100, Stuart Green stuart.green@doccentrics.com wrote: Greetings All,
New to this list!
I think I might have found an issue with the SSG policy content. Summary: If you do not have telnet installed on the system it causes Rule ID: disable_telnet_service to fail.
In no place in this rule does it consider that telnet might not be installed at all, so it fails (rather than errors, or even better does a check as a precursor to see if its installed at all and if not passes!)
grep 'id="oval:ssg:tst:231"' ssg-rhel6-oval.xml.result.xml <ind-def:textfilecontent54_test id="oval:ssg:tst:231" version="1" check_existence="all_exist" check="all" comment="Disable Telnet Service"> <test test_id="oval:ssg:tst:231" version="1" check_existence="all_exist" check="all" result="false"/>
<Rule id="disable_telnet_service" selected="false"
severity="high"> <title xml:lang="en-US">Disable telnet Service</title> <description xmlns:xhtml="http://www.w3.org/1999/xhtml" xml:lang="en-US">
The <xhtml:code>telnet</xhtml:code> service can be disabled with
the following command:
<xhtml:pre># chkconfig telnet off</xhtml:pre> </description> <reference
href="http://csrc.nist.gov/publications/nistpubs/800-53-Rev3/sp800-53-rev3-final.p...)</reference> <reference href="http://csrc.nist.gov/publications/nistpubs/800-53-Rev3/sp800-53-rev3-final.pdf">CM-7</reference> <reference href="http://csrc.nist.gov/publications/nistpubs/800-53-Rev3/sp800-53-rev3-final.pdf">IA-5(1)(c)</reference> <reference href="http://iase.disa.mil/cci/index.html">68</reference> <reference href="http://iase.disa.mil/cci/index.html">1436</reference> <reference href="http://iase.disa.mil/cci/index.html">197</reference> <reference href="http://iase.disa.mil/cci/index.html">877</reference> <reference href="http://iase.disa.mil/cci/index.html">888</reference> <reference xmlns:dc="http://purl.org/dc/elements/1.1/" href="test_attestation"> dc:contributorDS</dc:contributor> dc:date20121026</dc:date> </reference>
<rationale xmlns:xhtml="http://www.w3.org/1999/xhtml"
xml:lang="en-US">
The telnet protocol uses unencrypted network communication, which means that data from the login session, including passwords and all other information transmitted during the session, can be stolen by eavesdroppers on the network. The telnet protocol is also subject to man-in-the-middle attacks.
</rationale>
<ident system="http://cce.mitre.org">CCE-26836-7</ident> <check
system="http://oval.mitre.org/XMLSchema/oval-definitions-5%22%3E <check-content-ref name="oval:ssg:def:230" href="ssg-rhel6-oval.xml"/> </check>
<check system="ocil-transitional"> <check-export export-name="the service is running"
value-id="conditional_clause"/> <check-content xmlns:xhtml="http://www.w3.org/1999/xhtml">
To check that the <xhtml:code>telnet</xhtml:code> service is
disabled in system boot configuration, run the following command: xhtml:pre# chkconfig xhtml:codetelnet</xhtml:code> --list</xhtml:pre> Output should indicate the xhtml:codetelnet</xhtml:code> service has either not been installed, or has been disabled at all runlevels, as shown in the example below: xhtml:pre# chkconfig xhtml:codetelnet</xhtml:code> --list xhtml:codetelnet</xhtml:code> 0:off 1:off 2:off 3:off 4:off 5:off 6:off</xhtml:pre>
Run the following command to verify
xhtml:codetelnet</xhtml:code> is disabled through current runtime configuration:
<xhtml:pre># service telnet status</xhtml:pre> If the service is disabled the command will return the following
output:
<xhtml:pre>telnet is stopped</xhtml:pre> </check-content> </check> </Rule>
Cheers, Stu
scap-security-guide mailing list scap-security-guide@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
On 7/31/13 11:31 AM, Stuart Green wrote:
Ah-ha!! Thanks, I was looking for the buglist actually and couldn't find it!
Glad to be aboard :)
Hm. Perhaps this whole thing can be simplified.
Right now we have two checks: - package_telnet-server_removed.xml - service_telnetd_disabled.xml
They seem redundant, and I'm failing to find reasons against just deleting service_telnetd_disabled. There's no way telnet can be enabled if the package isn't installed, right?
Is there a reason to continue maintaining both checks?
On 7/31/13 1:36 PM, "Shawn Wells" shawn@redhat.com wrote:
On 7/31/13 11:31 AM, Stuart Green wrote:
Ah-ha!! Thanks, I was looking for the buglist actually and couldn't find it!
Glad to be aboard :)
Hm. Perhaps this whole thing can be simplified.
Right now we have two checks: - package_telnet-server_removed.xml - service_telnetd_disabled.xml
They seem redundant, and I'm failing to find reasons against just deleting service_telnetd_disabled. There's no way telnet can be enabled if the package isn't installed, right?
Is there a reason to continue maintaining both checks?
Shawn, I don't think so. I believe there are other checks that have the same redundancy also R/ Brian
On 7/31/13 2:24 PM, Brian Peake wrote:
On 7/31/13 1:36 PM, "Shawn Wells"shawn@redhat.com wrote:
On 7/31/13 11:31 AM, Stuart Green wrote:
Ah-ha!! Thanks, I was looking for the buglist actually and couldn't find it!
Glad to be aboard:)
Hm. Perhaps this whole thing can be simplified.
Right now we have two checks: - package_telnet-server_removed.xml - service_telnetd_disabled.xml
They seem redundant, and I'm failing to find reasons against just deleting service_telnetd_disabled. There's no way telnet can be enabled if the package isn't installed, right?
Is there a reason to continue maintaining both checks?
Shawn, I don't think so. I believe there are other checks that have the same redundancy also
Everything in the 'Obsolete Services' can trivially be migrated away to a 'uninstall' rule: http://people.redhat.com/swells/scap-security-guide/RHEL6/output/rhel6-guide...
These would be: - xinetd - telnet-server - rsh-server - ypserv - tftp-server
I'd wager much of the 'Base Services' fall under this too: http://people.redhat.com/swells/scap-security-guide/RHEL6/output/rhel6-guide... - abrt - acpid - certmonger - cgconfig - cgred - cpuspeed - haldaemon - irqbalance - kdump - mdmonitor - messagebus - netconsole - ntpdate - oddjobd - portreserve - psacct - quota_nld - rdisc - rhnsd - rhsmcertd - saslauthd - smartd - sysstat
Can anyone think of why we'd want to have checks for*both* uninstall and disabled?
On 08/01/2013 05:09 AM, Shawn Wells wrote:
On 7/31/13 2:24 PM, Brian Peake wrote:
On 7/31/13 1:36 PM, "Shawn Wells" shawn@redhat.com wrote:
On 7/31/13 11:31 AM, Stuart Green wrote:
Ah-ha!! Thanks, I was looking for the buglist actually and couldn't find it!
Glad to be aboard :)
Hm. Perhaps this whole thing can be simplified.
Right now we have two checks: - package_telnet-server_removed.xml - service_telnetd_disabled.xml
They seem redundant, and I'm failing to find reasons against just deleting service_telnetd_disabled. There's no way telnet can be enabled if the package isn't installed, right?
Is there a reason to continue maintaining both checks?
Shawn, I don't think so. I believe there are other checks that have the same redundancy also
Everything in the 'Obsolete Services' can trivially be migrated away to a 'uninstall' rule: http://people.redhat.com/swells/scap-security-guide/RHEL6/output/rhel6-guide...
These would be: - xinetd - telnet-server - rsh-server - ypserv - tftp-server
I'd wager much of the 'Base Services' fall under this too: http://people.redhat.com/swells/scap-security-guide/RHEL6/output/rhel6-guide... - abrt - acpid - certmonger - cgconfig - cgred - cpuspeed - haldaemon - irqbalance - kdump - mdmonitor - messagebus - netconsole - ntpdate - oddjobd - portreserve - psacct - quota_nld - rdisc - rhnsd - rhsmcertd - saslauthd - smartd - sysstat
Can anyone think of why we'd want to have checks for*both* uninstall and disabled?
I can think of a case why you may want to have both checks (although I am not sure If the reason will be appealing enough for you).
The SSG is the most comprehensive and mature source of SCAP guidance for Linux. As such, SSG might be often taken as a starting point to build a guidance in an organization (ACME Corp).
There will never be policy which fits them all. And some of the organizations will need to amend SSG here-and-there.
OpenSCAP recently introduced tailoring feature, which allows you to have Profile element outside the Benchmark. That way you can have stock (signed) guidance (SSG presumably) and keep your own modification separated. This also allows for easier rebases (update of the SSG rpm).
And here is my take: There might be organization which will need to have a package (like acpid) installed (for some inevitable monthly use-case) but they would agree that it should not be run by deafult. Such organization could easily use tailoring feature to turn-off the `uninstall` check.
And here is my take: There might be organization which will need to have a package (like acpid) installed (for some inevitable monthly use-case) but they would agree that it should not be run by deafult. Such organization could easily use tailoring feature to turn-off the `uninstall` check.
+1
I tried to come up with a way of saying this earlier, but couldn't figure out a good way. I do know that people do use these guides for some in-house policy creation stuff.
That being said - I don't know if I am convinced the good (rare cases like this) outweighs the harm (false positives and redundancy to the masses).
- Chad
On 08/01/2013 06:44 PM, Truhn, Chad M CTR NSWCDD, CXA30 wrote:
And here is my take: There might be organization which will need to have a package (like acpid) installed (for some inevitable monthly use-case) but they would agree that it should not be run by deafult. Such organization could easily use tailoring feature to turn-off the `uninstall` check.
+1
I tried to come up with a way of saying this earlier, but couldn't figure out a good way. I do know that people do use these guides for some in-house policy creation stuff.
That being said - I don't know if I am convinced the good (rare cases like this) outweighs the harm (false positives and redundancy to the masses).
The false positives can be easily avoided: Add a criterion to the `disabled` definition. That will point out to the test of `uninstalled` test.
- Chad
scap-security-guide mailing list scap-security-guide@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
Right, I recently pushed a fix for this bug, it just hasn't made the current build yet. Good catch though, false positives stink.
Andrew
On Wed, Jul 31, 2013 at 9:15 AM, Stuart Green stuart.green@doccentrics.comwrote:
Greetings All,
New to this list!
I think I might have found an issue with the SSG policy content.
Summary: If you do not have telnet installed on the system it causes Rule ID: disable_telnet_service to fail.
In no place in this rule does it consider that telnet might not be installed at all, so it fails (rather than errors, or even better does a check as a precursor to see if its installed at all and if not passes!)
grep 'id="oval:ssg:tst:231"' ssg-rhel6-oval.xml.result.xml <ind-def:textfilecontent54_**test id="oval:ssg:tst:231" version="1" check_existence="all_exist" check="all" comment="Disable Telnet Service"> <test test_id="oval:ssg:tst:231" version="1" check_existence="all_exist" check="all" result="false"/>
<Rule id="disable_telnet_service" selected="false" severity="high"> <title xml:lang="en-US">Disable telnet Service</title> <description xmlns:xhtml="http://www.w3.**org/1999/xhtml<http://www.w3.org/1999/xhtml>"
xml:lang="en-US">
The <xhtml:code>telnet</xhtml:**code> service can be disabled with
the following command:
<xhtml:pre># chkconfig telnet off</xhtml:pre> </description> <reference href="http://csrc.nist.gov/**
publications/nistpubs/800-53-**Rev3/sp800-53-rev3-final.pdfhttp://csrc.nist.gov/publications/nistpubs/800-53-Rev3/sp800-53-rev3-final.pdf ">**AC-17(8)</reference> <reference href="http://csrc.nist.gov/** publications/nistpubs/800-53-**Rev3/sp800-53-rev3-final.pdf<http://csrc.nist.gov/publications/nistpubs/800-53-Rev3/sp800-53-rev3-final.pdf> ">**CM-7</reference> <reference href="http://csrc.nist.gov/** publications/nistpubs/800-53-**Rev3/sp800-53-rev3-final.pdf<http://csrc.nist.gov/publications/nistpubs/800-53-Rev3/sp800-53-rev3-final.pdf> ">**IA-5(1)(c)</reference> <reference href="http://iase.disa.mil/**cci/index.html<http://iase.disa.mil/cci/index.html> ">68</reference> <reference href="http://iase.disa.mil/**cci/index.html<http://iase.disa.mil/cci/index.html> ">1436</**reference> <reference href="http://iase.disa.mil/**cci/index.html<http://iase.disa.mil/cci/index.html> ">197</**reference> <reference href="http://iase.disa.mil/**cci/index.html<http://iase.disa.mil/cci/index.html> ">877</**reference> <reference href="http://iase.disa.mil/**cci/index.html<http://iase.disa.mil/cci/index.html> ">888</**reference> <reference xmlns:dc="http://purl.org/dc/**elements/1.1/<http://purl.org/dc/elements/1.1/>" href="test_attestation"> dc:contributorDS</dc:**contributor> dc:date20121026</dc:date> </reference>
<rationale xmlns:xhtml="http://www.w3.**org/1999/xhtml<http://www.w3.org/1999/xhtml>"
xml:lang="en-US">
The telnet protocol uses unencrypted network communication, which means that data from the login session, including passwords and all other information transmitted during the session, can be stolen by eavesdroppers on the network. The telnet protocol is also subject to man-in-the-middle attacks.
</rationale>
<ident system="http://cce.mitre.org">**CCE-26836-7</ident> <check system="http://oval.mitre.org/**
XMLSchema/oval-definitions-5http://oval.mitre.org/XMLSchema/oval-definitions-5 "> <check-content-ref name="oval:ssg:def:230" href="ssg-rhel6-oval.xml"/> </check>
<check system="ocil-transitional"> <check-export export-name="the service is running"
value-id="conditional_clause"/**> <check-content xmlns:xhtml="http://www.w3.**org/1999/xhtml<http://www.w3.org/1999/xhtml> ">
To check that the <xhtml:code>telnet</xhtml:**code> service is
disabled in system boot configuration, run the following command: xhtml:pre# chkconfig xhtml:codetelnet</xhtml:**code> --list</xhtml:pre> Output should indicate the xhtml:codetelnet</xhtml:**code> service has either not been installed, or has been disabled at all runlevels, as shown in the example below: xhtml:pre# chkconfig xhtml:codetelnet</xhtml:**code> --list xhtml:codetelnet</xhtml:**code> 0:off 1:off 2:off 3:off 4:off 5:off 6:off</xhtml:pre>
Run the following command to verify <xhtml:code>telnet</xhtml:**code>
is disabled through current runtime configuration:
<xhtml:pre># service telnet status</xhtml:pre> If the service is disabled the command will return the following
output:
<xhtml:pre>telnet is stopped</xhtml:pre> </check-content> </check> </Rule>
Cheers, Stu
______________________________**_________________ scap-security-guide mailing list scap-security-guide@lists.**fedorahosted.orgscap-security-guide@lists.fedorahosted.org https://lists.fedorahosted.**org/mailman/listinfo/scap-**security-guidehttps://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
scap-security-guide@lists.fedorahosted.org