Difference between revisions of "Attested"
From MgmtWiki
m (→Solution) |
(→Context) |
||
| Line 4: | Line 4: | ||
==Context== | ==Context== | ||
| − | *The Context in which an [[Attested|Attestation]] of [[Identity]] applies is typically during the | + | *The Context in which an [[Attested|Attestation]] of [[Identity]] applies is typically during the [[Validated|Validation]] of the security of protection offered to [[User]] secrets, such as [[Credential]]s. in a [[User Agent]]. |
==Problem== | ==Problem== | ||
Revision as of 20:21, 30 August 2018
Full Title or Meme
A statement is Attested if some Trusted Third Party can create a Validated Claim about a User Device used during either Authentication or Authorization.
Context
- The Context in which an Attestation of Identity applies is typically during the Validation of the security of protection offered to User secrets, such as Credentials. in a User Agent.
Problem
- When a secure operation is performed at a user location, the packet returned from that User Device needs to be trusted by the Site that receives it.
- The signing key for that packet will have a certificate that binds that signing key to a particular device.
Solution
- The certificate for the signing key from the User Device, and potentially the configuration information from the device, will need to be Attested by some Trusted Third Party.
- Attestation can be complex for programmable computers, or simple for one function User Devices like Security Tokens.
- An example of a single attestation program with associated metadata is described in the FIDO web site.
- When a simple certificate is used, it typically is accompanied by a metadata statement, an example is this one at Yubico.
References
- Synonyms include: Assurance Corroborated Validated.