Class BGuidanceAuthenticators must be compliant with the most recent NIST Digital Identity Guidelines IAL, AAL, FAL level 1. IA-5 Guidance: FedRAMP requires that authentication assertions be encrypted when passed through third parties, such as a browser. For example, a SAML assertion can be encrypted using XML-Encryption, or an OpenID Connect ID Token can be encrypted using JSON Web Encryption (JWE). Class CGuidanceAuthenticators must be compliant with the most recent NIST Digital Identity Guidelines IAL, AAL, FAL level 2. IA-5 Guidance: FedRAMP requires that authentication assertions be encrypted when passed through third parties, such as a browser. For example, a SAML assertion can be encrypted using XML-Encryption, or an OpenID Connect ID Token can be encrypted using JSON Web Encryption (JWE). Class DGuidanceAuthenticators must be compliant with the most recent NIST Digital Identity Guidelines IAL, AAL, FAL level 3. IA-5 Guidance: FedRAMP requires that authentication assertions be encrypted when passed through third parties, such as a browser. For example, a SAML assertion can be encrypted using XML-Encryption, or an OpenID Connect ID Token can be encrypted using JSON Web Encryption (JWE).
|