Difference between revisions of "Security Token"
From MgmtWiki
(→Context) |
(→Problem) |
||
Line 5: | Line 5: | ||
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]]. | 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== | ==Problem== | ||
− | [[Trust]] | + | Generating [[Trust]] when the trust guarantor is not physically present. |
+ | |||
==Hardware Token Solutions== | ==Hardware Token Solutions== | ||
==Software Token Solutions== | ==Software Token Solutions== | ||
==References== | ==References== |
Revision as of 15:05, 8 August 2018
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.