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

8.1.5.1.1 Distribution of Public Keys (was: Distribution of Static Public Keys)

NIST platform security: roots of trust, firmware and secure enclaves SP 800-57 Part 1 Rev. 5 against SP 800-57 Part 1 Rev. 4
All changes in this version
modified 8 Transition: A transition plan should be developed and followed so that the changeover part of 8.1.5.1

Title changed

Before · SP 800-57 Part 1 Rev. 4

Distribution of Static Public Keys

After · SP 800-57 Part 1 Rev. 5

Distribution of Static Public Keys

Control changed

Before · SP 800-57 Part 1 Rev. 4

Static public keys are relatively long-lived and are typically used for several executions of an algorithm. The distribution of the public key should provide assurance to the receiver of the public key that the true owner of the key is known (i.e., the claimed owner is the actual owner); this requirement may be disregarded if anonymity is acceptable. However, the strength of the overall architecture and trust in the validity of the protected data depends, in large part, on the assurance of the public-key owner’s identity. In addition, the distribution of the public key shall provide assurance to the receiver that:

After · SP 800-57 Part 1 Rev. 5

Static public keys are relatively long-lived and are typically used for several executions of an algorithm. Ephemeral public keys are short-lived. The distribution of the static or ephemeral public key should provide assurance to the receiver of the public key that the true owner of the key is known (i.e., the claimed owner is the actual owner); this requirement may be disregarded if anonymity is acceptable. However, the strength of the overall architecture and trust in the validity of the protected data depends, in large part, on the assurance of the public-key owner’s identity. In addition, the distribution of the public key shall provide assurance to the receiver that: