Reliance authentication (original) (raw)
Reliance authentication is a part of the trust-based identity attribution process whereby a second entity relies upon the authentication processes put in place by a first entity. The second entity creates a further element that is unique and specific to its purpose, that can only be retrieved or accessed by the authentication processes of the first entity having first being met. The token may be generated by the second party dynamically, and can thus act as a one-time password.
| Property | Value |
|---|---|
| dbo:abstract | Reliance authentication is a part of the trust-based identity attribution process whereby a second entity relies upon the authentication processes put in place by a first entity. The second entity creates a further element that is unique and specific to its purpose, that can only be retrieved or accessed by the authentication processes of the first entity having first being met. Reliance authentication can be achieved by one or more tokens with random characteristics being transmitted to a secure area controlled by the first entity, where such secure area is only accessible by the person authorised to use the account. The secure area may be an online banking portal, telephone banking system, or mobile banking application. The token is often in the form of a single or plural of debit or credits to a financial account, where the numerical values of the debit or credits form the token, whose numeric value is to be confirmed by the account holder. The token are retrieved by the cardholder accessing a secure area from the first entity's secure area, which is protected and accessible only by satisfying the first entity's authentication means. In the case of financial services, authentication to access the secure area normally includes multi-factor and in the SEPA would likely involve strong authentication. The transmission and requirement to retrieve the token adds a further challenge and response factor to the overall authentication process when considered from the point of view of the second party, which generates and transmits the token. The token may be generated by the second party dynamically, and can thus act as a one-time password. The reliance authentication method has particular application with financial instruments such as credit cards, and direct debit transactions, whereby a person may instigate a transaction on a financial instrument, however the financial instrument is not verified as belonging to that person until that person confirms the value of the token. The reliance method often incorporates an out-of-band response means, once the tokens have been retrieved from the secure area. (en) |
| dbo:thumbnail | wiki-commons:Special:FilePath/CAPTCHA_wikibook.png?width=300 |
| dbo:wikiPageExternalLink | http://www.legislation.gov.uk/uksi/2007/2157/contents/made http://www.ffiec.gov/pdf/authentication_guidance.pdf |
| dbo:wikiPageID | 40682382 (xsd:integer) |
| dbo:wikiPageLength | 8825 (xsd:nonNegativeInteger) |
| dbo:wikiPageRevisionID | 1107357918 (xsd:integer) |
| dbo:wikiPageWikiLink | dbr:FFIEC dbr:Mutual_authentication dbr:Credit_cards dbr:One-time_password dbr:Multi-factor_authentication dbr:Strong_authentication dbr:File:Smartcardpixelated.JPG dbr:Authentication dbr:CAPTCHA dbr:Direct_debit dbc:Authentication_methods dbr:Digital_identity dbr:Out-of-band_data dbr:Challenge–response dbr:Single_Euro_Payment_Area dbr:E-mandate dbr:File:CAPTCHA_wikibook.png |
| dbp:wikiPageUsesTemplate | dbt:More_citations_needed dbt:Reflist |
| dct:subject | dbc:Authentication_methods |
| rdf:type | yago:WikicatAuthenticationMethods yago:Ability105616246 yago:Abstraction100002137 yago:Cognition100023271 yago:Know-how105616786 yago:Method105660268 yago:PsychologicalFeature100023100 |
| rdfs:comment | Reliance authentication is a part of the trust-based identity attribution process whereby a second entity relies upon the authentication processes put in place by a first entity. The second entity creates a further element that is unique and specific to its purpose, that can only be retrieved or accessed by the authentication processes of the first entity having first being met. The token may be generated by the second party dynamically, and can thus act as a one-time password. (en) |
| rdfs:label | Reliance authentication (en) |
| owl:sameAs | freebase:Reliance authentication yago-res:Reliance authentication wikidata:Reliance authentication https://global.dbpedia.org/id/fkyk |
| prov:wasDerivedFrom | wikipedia-en:Reliance_authentication?oldid=1107357918&ns=0 |
| foaf:depiction | wiki-commons:Special:FilePath/CAPTCHA_wikibook.png wiki-commons:Special:FilePath/Smartcardpixelated.jpg |
| foaf:isPrimaryTopicOf | wikipedia-en:Reliance_authentication |
| is dbo:wikiPageWikiLink of | dbr:Multi-factor_authentication dbr:Credit_card_fraud dbr:Strong_authentication dbr:Authentication dbr:Digital_identity dbr:Strong_customer_authentication |
| is foaf:primaryTopic of | wikipedia-en:Reliance_authentication |
