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

2.5 Examples of Digital Identity Models (was: Change History)

NIST PIV and digital identity SP 800-63-4 against SP 800-63-3
All changes in this version
modified 2 Continuous improvement programs. Establishing a continuous evaluation part of 2

Title changed

Before · SP 800-63-3

Change History

After · SP 800-63-4

ChangeExamples Historyof Digital Identity Models

Control changed

Before · SP 800-63-3

After · SP 800-63-4

The entities and interactions that comprise the non-federated digital identity model are illustrated in Fig. 3 . The general-purpose federated digital identity model is illustrated in Fig. 4 , and a federated digital identity model with a subscriber-controlled wallet is illustrated in Fig. 5 .

In the two cases described in Fig. 3 and Fig. 4 , the verifier does not always need to communicate in real time with the CSP to complete the authentication activity (e.g., digital certificates can be used). Therefore, the line between the verifier and the CSP represents a logical link between the two entities. In some implementations, the verifier, RP, and CSP functions are distributed. However, if these functions reside on the same platform, the interactions between the functions are signals between applications or application modules that run on the same system rather than using network protocols.