needs mapping/rule: SRG-OS-000375-GPOS-00160, SV-87057r2_rule, RHEL-07-041003 (ocsp_on)

[shawndwells]

No description provided.

[shawndwells]

<Group id="V-72433"><title>SRG-OS-000375-GPOS-00160</title><description>&lt;GroupDescription&gt;&lt;/GroupDescription&gt;</description><Rule id="SV-87057r2_rule" severity="medium" weight="10.0"><version>RHEL-07-041003</version><title>The operating system must implement certificate status checking for PKI authentication.</title><description>&lt;VulnDiscussion&gt;Using an authentication device, such as a CAC or token that is separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device.^M
^M
Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification card and the DoD Common Access Card.^M
^M
A privileged account is defined as an information system account with authorizations of a privileged user.^M
^M
Remote access is access to DoD nonpublic information systems by an authorized user (or an information system) communicating through an external, non-organization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless.^M
^M
This requirement only applies to components where this is specific to the function of the device or has the concept of an organizational user (e.g., VPN, proxy capability). This does not apply to authentication for the purpose of configuring the device itself (management).^M
^M
Requires further clarification from NIST.^M
^M
Satisfies: SRG-OS-000375-GPOS-00160, SRG-OS-000375-GPOS-00161, SRG-OS-000375-GPOS-00162&lt;/VulnDiscussion&gt;&lt;FalsePositives&gt;&lt;/FalsePositives&gt;&lt;FalseNegatives&gt;&lt;/FalseNegatives&gt;&lt;Documentable&gt;false&lt;/Documentable&gt;&lt;Mitigations&gt;&lt;/Mitigations&gt;&lt;SeverityOverrideGuidance&gt;&lt;/SeverityOverrideGuidance&gt;&lt;PotentialImpacts&gt;&lt;/PotentialImpacts&gt;&lt;ThirdPartyTools&gt;&lt;/ThirdPartyTools&gt;&lt;MitigationControl&gt;&lt;/MitigationControl&gt;&lt;Responsibility&gt;&lt;/Responsibility&gt;&lt;IAControls&gt;&lt;/IAControls&gt;</description><reference><dc:title>DPMS Target Red Hat 7</dc:title><dc:publisher>DISA</dc:publisher><dc:type>DPMS Target</dc:type><dc:subject>Red Hat 7</dc:subject><dc:identifier>2777</dc:identifier></reference><ident system="http://iase.disa.mil/cci">CCI-001948</ident><ident system="http://iase.disa.mil/cci">CCI-001953</ident><ident system="http://iase.disa.mil/cci">CCI-001954</ident><fixtext fixref="F-78785r3_fix">Configure the operating system to do certificate status checking for PKI authentication.^M
^M
Modify all of the "cert_policy" lines in "/etc/pam_pkcs11/pam_pkcs11.conf" to include "ocsp_on".</fixtext><fix id="F-78785r3_fix" /><check system="C-72633r2_chk"><check-content-ref name="M" href="DPMS_XCCDF_Benchmark_RHEL_7_STIG.xml" /><check-content>Verify the operating system implements certificate status checking for PKI authentication.^M
^M
Check to see if Online Certificate Status Protocol (OCSP) is enabled on the system with the following command:^M
^M
# grep cert_policy /etc/pam_pkcs11/pam_pkcs11.conf^M
^M
cert_policy =ca, ocsp_on, signature;^M
cert_policy =ca, ocsp_on, signature;^M
cert_policy =ca, ocsp_on, signature;^M
^M
There should be at least three lines returned. All lines must match the example output; specifically that "oscp_on" must be included in the "cert_policy" line.^M
^M
If "oscp_on" is present in all "cert_policy" lines, this is not a finding.</check-content></check></Rule></Group>

[trevor-vaughan]

@shawndwells Is there a OCSP responder that ships with Red Hat (besides the one in openssl hopefully)?

If so, shouldn't we be required to enable that for all local systems to restrict the amount of outbound traffic from systems?

[shawndwells]

On 6/21/17 10:20 PM, Trevor Vaughan wrote: @shawndwells <https://github.com/shawndwells> Is there a OCSP responder that ships with Red Hat (besides the one in openssl hopefully)?

via IdM upstream is dogtag: http://pki.fedoraproject.org/wiki/PKI_Main_Page

If so, shouldn't we be required to enable that for all local systems to restrict the amount of outbound traffic from systems?

Meaning services should be configured to check w/an OCSP responder?

[trevor-vaughan]

@shawndwells Yes, any service that uses PKI should be configured to use either an OCSP or SCVP responder. Any service that does not support this capability should not be used.

Is there an IPA and/or dogtag configuration guide since it appears to be a required infrastructure capability?

[shawndwells]

Mapping previously completed. Ref:

https://github.com/OpenSCAP/scap-security-guide/blob/master/shared/guide/system/accounts/accounts-physical/screen_locking/smart_card_login/smartcard_configure_cert_checking.rule#L34