Search results

• OASIS SAML Security and Privacy 2.0
  '''Title''': Security and Privacy Considerations for the OASIS Security Assertion Markup Language (SAML) V2.0 '''Category''': Authentication Procotol Specification
  1 KB (171 words) - 04:02, 28 June 2018
• Kantara IAF 1600
  '''Title''': Identity Assurance Framework: Assessor Qualifications Requirements '''Category''': Trust Framework Provider Specification
  681 bytes (65 words) - 04:02, 28 June 2018
• NIST IR 7693
  '''Title''': Specification for Asset Identification 1.1 '''Category''': Security Requirements Specification
  2 KB (204 words) - 04:02, 28 June 2018
• NIST SP 800-73-3 Part 1
  '''Category''': Credential Requirements Specification '''Description''': Describes requirements for PIV client-application programming interface, PIV Card application, and
  1,002 bytes (102 words) - 04:02, 28 June 2018
• NIST SP 800-73-3 Part 2
  '''Category''': Credential Requirements Specification '''Description''': Describes requirements for PIV client application programming interface including information proc
  1 KB (120 words) - 04:02, 28 June 2018
• NIST SP 800-73-3 Part 3
  '''Category''': Credential Requirements Specification '''Security''':
  1 KB (109 words) - 04:02, 28 June 2018
• NIST SP 800-73-3 Part 4
  Specification '''Category''': Credential Requirements Specification
  864 bytes (94 words) - 04:02, 28 June 2018
• NIST SP 800-76-2
  '''Title''': Biometric Data Specification for Personal Identity Verification '''Category''': Credential Requirements Specification
  774 bytes (87 words) - 04:02, 28 June 2018
• OASIS SAML Conformance 2.0
  '''Title''': Conformance Requirements for the OASIS Security Assertion Markup Language (SAML) V2.0 '''Category''': Authentication Protocol Specification
  654 bytes (69 words) - 16:30, 27 May 2020
• Kantara IAF 1300
  '''Category''': Trust Framework Provider Specification '''Description''': Consists of a set of requirements which assessors must fulfill in order to become 'Kantara-Accredited', a
  1 KB (119 words) - 04:02, 28 June 2018
• PIV-I for Non-Federal Issuers
  '''Category''': Credential Requirements Standard '''Description''': Requirements for non-Federal issuers of cards designed to interoperate with the Federal
  1,023 bytes (117 words) - 23:30, 12 January 2021
• Trust Federation Membership Validation
  ...n certain assertions by other actors to fulfill their information security requirements." In this document the objective is simply to allow two digital entities (a ...e proven before an entry is accepted into the federation. That is good for security, but somewhat at odds with interoperability. On the other hand it does make
  21 KB (3,285 words) - 23:37, 15 January 2020
• Phone as Health Care Credential
  ...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 ...rements which are more restrictive than any general state mandated privacy requirements.
  19 KB (3,008 words) - 20:23, 20 March 2021
• Consent to Create Binding
  ...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
  14 KB (2,250 words) - 01:29, 23 December 2020
• High Assurance AZ Token
  Ensure the security of a stand-alone Token to provide high assurance of (1) Identity, (2) Authe ...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
  16 KB (2,576 words) - 19:23, 24 July 2020
• Software Compliance Attestation
  ...ttestation provides the evidence need for meeting the requirements of that specification at the highest levels of assurance. ...oftware and the user had achieved. This would satisfy the TEFCA IAL2, AAL2 requirements at that same time.
  5 KB (771 words) - 19:07, 22 January 2021
• Native Apps for US Healthcare
  There are three sources of requirements for [[Native Apps for US Healthcare]]: ...0] is a specification under development in Kantara.for apps to prove their security to the relying party.
  7 KB (971 words) - 16:33, 30 April 2021
• Identity Assurance Costs
  * National security has always been a leader in assuring the people are who they say they are f ...have been offered to the general public, but none of the industrial grade security measures have been acceptable to the population. The one exception has been
  5 KB (834 words) - 00:18, 24 August 2020
• IDESG Baseline Process Use Case
  ...le process. It defines the lifecycle stages for the Baseline process, the requirements for moving a document between stages and the types of documents used during '''Use Case Category''': IDESG approved baseline process requirements
  23 KB (3,525 words) - 04:00, 28 June 2018
• Device Integrity supporting User Authentication
  ...ish an integrity (aka health) claim for a device that, together with other security measures, is good evidence of the integrity of the information exchanged wi Integrity has two meanings in computer security. The first relates to the device not having been changed in any way since i
  12 KB (1,835 words) - 20:44, 5 November 2020

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)