The BIG-IP APM module must accept FICAM-approved third-party credentials.

From F5 BIG-IP Access Policy Manager 11.x Security Technical Implementation Guide

Associated with: CCI-002011

SV-74489r1_rule The BIG-IP APM module must accept FICAM-approved third-party credentials.

Vulnerability discussion

Access may be denied to legitimate users if Federal Identity, Credential, and Access Management (FICAM)-approved third-party credentials are not accepted.Third-party credentials are those credentials issued by non-federal government entities approved by the FICAM Trust Framework Solutions initiative.This requirement typically applies to organizational information systems that are accessible to non-federal government agencies and other partners. This allows federal government relying parties to trust such credentials at their approved assurance levels.This requirement only applies to components where this is specific to the function of the device or has the concept of a non-organizational user, (e.g., ALG capability that is the front end for an application in a DMZ). This does not apply to authentication for the purpose of configuring the device itself (i.e., device management).

Check content

If the BIG-IP APM module does not provide user authentication intermediary services to non-organizational users, this is not applicable. Verify the BIG-IP APM module is configured as follows: Navigate to the BIG-IP System manager >> Access Policy >> Access Profiles. Click "Edit..." in the "Access Policy" column for an Access Profile used to identify and authenticate non-organizational users. Verify the Access Profile is configured to accept FICAM-approved third-party credentials. If the BIG-IP APM module is not configured to accept FICAM-approved third-party credentials, this is a finding.

Fix text

If the BIG-IP APM module provides user authentication intermediary services to non-organizational users, configure a profile in the BIG-IP APM module to accept FICAM-approved third-party credentials.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.