V-237396

Discussion

Without configuring a local cache of revocation data, there is the potential to allow access to users who are no longer authorized (users with revoked certificates). The intent of this requirement is to require support for a secondary certificate validation method using a locally cached revocation data, such as Certificate Revocation List (CRL), in case access to OCSP (required by CCI-000185) is not available. Based on a risk assessment, an alternate mitigation is to configure the system to deny access when revocation data is unavailable. This requirement applies to ALGs that provide user authentication intermediary services (e.g., authentication gateway or TLS gateway). This does not apply to authentication for the purpose of configuring the device itself (device management). The CA API Gateway must implement a local cache of revocation data to support certificate validation in the event network access to the revocation server is unavailable. This cache must be created using a "Revocation Checking Policy" and be configurable to meet organizational requirements.

Check Content

Open the CA API Gateway - Policy Manager, select "Tasks" from the main menu and chose "Manage Certificates". 

Click the "Certificate Validation" button and verify there is at least one Policy in the list of Revocation Checking Policies. 

Double-click one of the listed policies and verify the "Continue processing if server is unavailable" check box is checked. 

If there is no policy listed or the "Continue processing if server is unavailable" check box is not selected within the revocation policy, this is a finding.