BaselineWatch
Desk
Your fleet and your work Fleetyour releases and the hardware they run onTriagewhat needs a decisionWatchlistthe products and platforms you runSaved searchesthe lists you come back to
This instance Sourceswhat is read, how often, under what termsDigestthe daily or weekly summary, and alerts
How it is drawn Appearancethe look and the colour schemeBrandingthe mark this instance wears
Owner sign-in

6.2 Assertion Contents

NIST PIV and digital identity SP 800-217 (Draft)
All changes in this version
first version loaded 6 Protocol Requirements 996 part of 6

Title

Assertion Contents

Control

As specified in [SP800-63C] , the successful validation of a federated assertion is required to begin an authenticated session at the RP. The assertion contains a combination of attributes about the subscriber as well as attributes about the authentication event that the assertion represents.

At a minimum, the assertion in PIV federation SHALL contain the following attributes of the PIV identity account:

• Flag indicating that this assertion represents a PIV federation transaction

• Last updated timestamp for the PIV identity account

• Identifier for the home agency of the PIV identity account

• IAL for the PIV identity account (note that all PIV identity accounts are established at IAL3)

• Federated identifier for the PIV identity account at this IdP, as defined in Sec. 6.2.1

As an assertion is a short-lived message from the IdP to the RP, the assertion itself SHOULD only contain the minimum attributes required for its processing. To preserve privacy and minimize the information sent with each request, the assertion SHOULD NOT contain non-required or stable attributes from the PIV identity account (e.g., email address, display name). Additional attributes SHOULD be made available to the RP through a standard identity API.

At a minimum, the assertion in PIV federation SHALL contain the following attributes of the authentication event:

• AAL for the latest successful authentication event for the subscriber’s current session at the IdP

• Timestamp of the latest successful authentication event for the subscriber’s current session at the IdP

• Flag indicating whether the PIV Card or a derived PIV credential was used at the authentication event for the subscriber’s current session at the IdP

• Intended FAL for the current transaction For FAL3 assertions in PIV federation, the assertion SHALL contain either: 1096

1097 1098

1099

1100 1101

1102 1103 1104 1105 1106

1107 1108

1109 1110 1111

1112 1113 1114 1115

1116 1117 1118 1119 1120 1121

1122 1123 1124

1125 1126 1127 1128
• A reference to an IdP-managed bound authenticator to be verified by the RP (e.g., a certificate identifier, as discussed in Sec 6.2.3 ), or

• A flag indicating that an RP-managed bound authenticator is required at the RP.

The mapping of these required attributes to specific fields within a given federation protocol is out of scope for this specification.