This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links
Impersonation-resistant...nobody
Impersonation-resistant

Version management

Difference between version and

At line 1 added 259 lines
!!! Overview
[{$pagename}] requires use a [authentication] [protocol] ([authenticators] and [Verifier]) to prevent possible [phishing] [attacks].
There are a number of ways to do this, including various [encryption] [protocols] and [Digital Signature] technologies that bind the [authenticator] output to a specific protected [channel].
One example of a verifier [{$pagename}] [authentication] [protocol] is [Mutual Authentication] [Transport Layer Security] ([TLS]). In this [protocol], the client signs the [authenticator] output and earlier messages that are unique to the particular [TLS] connection being negotiated.
At [AAL3], [NIST.SP.800-63B] requires authenticators that use a [verifier] [{$pagename}] [authentication] [protocol].
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthorTop