Difference between revisions of "Security Token"
From MgmtWiki
(→References) |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 10: | Line 10: | ||
==Hardware Token Solutions== | ==Hardware Token Solutions== | ||
| − | As with the software token solution, the result of use of the hardware token will be some information sent over an internet connection, perhaps as a token, or perhaps embedded in the connection protocol. | + | * Early hardware token were little more than a non-volatile memory chip embedded in plastic. These looked like, and could be used like a metal key, including when stolen and could be copied with little effort. |
| + | * As with the software token solution, the result of use of the hardware token will be some information sent over an internet connection, perhaps as a token, or perhaps embedded in the connection protocol. | ||
| + | |||
==References== | ==References== | ||
| + | |||
| + | [[Category:Glossary]] | ||
| + | [[Category:Security]] | ||
Revision as of 12:20, 30 March 2019
Contents
Full Title or Meme
Security Tokens come in two radically different forms, as hardware fobs, or as protected software packets.
Context
The first Security Token was a letter of introduction, typically with some complex wax seal, or an unclonable chop with an inked impression to show authenticity with an Unclonable Identity.
Problem
Generating Trust when the trust guarantor is not physically present.
Software Token Solutions
Hardware Token Solutions
- Early hardware token were little more than a non-volatile memory chip embedded in plastic. These looked like, and could be used like a metal key, including when stolen and could be copied with little effort.
- As with the software token solution, the result of use of the hardware token will be some information sent over an internet connection, perhaps as a token, or perhaps embedded in the connection protocol.
