BaselineWatch
Desk

3.5 Home Agency IdPs 738

NIST PIV and digital identity SP 800-217 (Draft)
All changes in this version
first version loaded 3 Trust Agreements 574 part of 3

Title

Home Agency IdPs 738

Control

739 740 741

742 743 744 745

746

747

748

749 750 751 752 753 754 755

756 757 758 759

760

761

762 763

764 765

766

767 768 Only the home agency responsible for issuing PIV identity accounts SHALL declare the home agency IdP for those accounts. Operation of the home agency IdP MAY be outsourced to a third party, if the IdP meets the requirements in this section.

A home agency IdP SHALL have access to the PIV identity accounts that it represents through the home agency IdMS. Current access SHALL be available throughout the lifecycle of the PIV identity account while the home agency IdP is in operation. The access includes the following:

• All attributes available for federation,

• All PIV credentials bound to the account, and

• The current status of the PIV identity account (i.e., active/terminated).

The effect of these requirements is that the home agency IdP needs to be coupled to the home agency IdMS. This can be accomplished through a variety of technological means, such as direct attachment to the home agency IdMS or the use of a provisioning protocol to synchronize account state with the IdP system. In all cases, a home agency IdP is expected to have current, accurate, and authoritative information for all of the PIV identity accounts that it represents. Additionally, the IdP SHALL inform the home agency IdMS of any results of processing shared signals, as discussed in Sec. 3.4 .

When declaring a home agency IdP, the home agency SHALL publish its home agency IdP record in a publicly available location that is securely associated with the home agency, such as on an HTTPS URL on the agency’s domain or in a trusted directory service. The publication of the home agency IdP record SHALL include all of the following:

• A canonical issuer identifier for the IdP (generally a URI in federation protocols),

• A list of agency identifiers and organizational affiliations covered by the IdP,

• A list of federation protocols supported by the IdP along with any profiles of those protocols,

• The location of a machine-readable discovery document for each federation protocol supported by the IdP, and

• Technical contact information for the IdP.

The format for this record and the means by which it is published are out of scope for this specification and subject to technical profiles and federation trust agreements.