Search results

'''Category''': Trust Framework Provider Specification '''Description''': Consists of a set of requirements which assessors must fulfill in order to become 'Kantara-Accredited', a

...fied. The value "0" indicates the End-User authentication did not meet the requirements of ISO/IEC 29115 [ISO29115] level 1. Authentication using a long-lived brow ...particular values to be used in the amr Claim is beyond the scope of this specification. Parties using this claim will need to agree upon the meanings of the value

...ipt and authorization in response to this message which meets the security requirements of the intended purpose. * This specification applies only to service providers that have determined that they need to ac

Using a Patient's Cell Phone as the holder of their (1) Health Care Credential and (2) personal healthcare Information store. ...ticipant Member, or Individual User such as by means of burdensome testing requirements that are applied in a discriminatory manner or other means that limit the a

'''Category''': Credential Requirements Standard '''Description''': Requirements for non-Federal issuers of cards designed to interoperate with the Federal

'''Title''': Biometric Data Specification for Personal Identity Verification '''Category''': Credential Requirements Specification

Specification '''Category''': Credential Requirements Specification

'''Category''': Credential Requirements Specification [[Category:Credential Requirements Specification]]

'''Category''': Credential Requirements Specification '''Description''': Describes requirements for PIV client application programming interface including information proc

'''Category''': Credential Requirements Specification '''Description''': Describes requirements for PIV client-application programming interface, PIV Card application, and

'''Category''': Credential Requirements Specification '''Description''': Specifies the architectural and technical requirements for the Personal Identity Verification (PIV) card

'''Title''': Identity Assurance Framework: Additional Requirements for Credential Service Providers: US Federal '''Category''': Trust Framework Provider Specification

'''Category''': Trust Framework Provider Specification consent for sharing PII. No requirements though.

.../index.php?title=Baseline_Functional_Requirements_v1.0 Baseline Functional Requirements v1.0 (BFR)]. .../index.php?title=Baseline_Functional_Requirements_v1.0 Baseline Functional Requirements v1.0 (BFR)].

...f abstraction of the IDESG functions has been proposed in the [[Functional Requirements]]. This page describes the use of design patterns for user experiences in p ...ific types of roles they use, as long as the role adheres to the interface specification

CREDENTIAL AUTHENTICATION: Process of determining the validity of one or more CREDENTI ...rds employed within an entity to ensure compliance with applicable privacy requirements and manage privacy risks.

An identity credential; previously stored personal questions and answers. Also known as Challenge/ ...g the structure and content for an implementation-specific set of security requirements for an IT product or system.

...tion and service application), each interface with distinct authentication requirements is considered a stand-alone AA. AAs manage all Business Transactions and al ...nder that their conformity to the appropriate agreement, and therefore the requirements of the AAS, remains their obligation.

'''Category''': Credential Requirements Specification '''Description''': Specifies the architectural and technical requirements for the Personal Identity Verification (PIV) card