Search results

• ABADSG
  '''Interoperability''':
  433 bytes (45 words) - 19:46, 21 October 2019
• Consent Receipt
  '''Interoperability''': It is expected that Consent Receipts can be interchanged between [[Data
  3 KB (380 words) - 17:28, 25 July 2020
• Device Integrity supporting User Authentication
  Integrity, Privacy, Compliance, Interoperability ===Interoperability Considerations===
  12 KB (1,835 words) - 20:44, 5 November 2020
• FBCA CP 2.25
  '''Interoperability''': The document supports interoperation of digital certficates between dif document provides a PKI repository interoperability profile based on LDAP and HTTP and the naming
  4 KB (377 words) - 22:59, 18 February 2021
• FBCA Cross-certification Methodology 3.0
  ...: The purpose of the document is to provide a method for achieving trusted interoperability between the U.S.
  2 KB (230 words) - 23:00, 18 February 2021
• FICAM Privacy Guidance for Assessors
  '''Interoperability''': This document supports interoperation between Federal and non-Federal e
  1 KB (123 words) - 00:49, 31 May 2020
• FICAM TFPAP 1.0.1
  '''Interoperability''': The document promotes an interoperable approach to evaluating Trust Fra
  3 KB (373 words) - 23:01, 18 February 2021
• FIDO Universal 2nd Factor (U2F) 1.x
  '''Interoperability''':
  345 bytes (34 words) - 03:58, 28 June 2018
• FIDO Universal Authentication Framework (UAF) 1.x
  '''Interoperability''':
  374 bytes (34 words) - 20:10, 15 October 2019
• FIPS 140-2
  '''Interoperability''': The document promotes interoperability by providing a baseline set of requirements for cryptographic
  3 KB (379 words) - 03:58, 28 June 2018
• FIPS 186-3
  '''Interoperability''':
  440 bytes (44 words) - 03:58, 28 June 2018
• FIPS 201-1
  Federally-Assisted Organizations; SP 800-96, PIV Card to Reader Interoperability Guidelines; SP 800-156, '''Interoperability''':
  1 KB (173 words) - 03:58, 28 June 2018
• FIPS 201-2
  Federally-Assisted Organizations; SP 800-96, PIV Card to Reader Interoperability Guidelines; SP 800-156, '''Interoperability''': The purpose of the standard is to promote interoperability among PIV system components, across
  3 KB (374 words) - 00:25, 24 August 2020
• February 5, 2015 Meeting Page
  ...y agnostic at one level, but not in regards to semantics of exchanges when interoperability is involved. **Someone mentioned he had a request for the FMO. It will be brought up at interoperability meeting later today. Adam said to write it up and submit to Lionel, Cathy a
  5 KB (766 words) - 03:58, 28 June 2018
• Four Party Authentication and Authorization Use Case
  ===Interoperability Considerations===
  7 KB (1,007 words) - 03:58, 28 June 2018
• Functional Model Work in Process
  *Federation and Interoperability
  3 KB (394 words) - 18:52, 27 September 2019
• Functional Requirements
  ...the full scope of the ID ecosystem as described in NSTIC. Only very basic interoperability is possible here based on common internet protocols. No new trust mark woul
  8 KB (1,315 words) - 19:29, 30 July 2020
• GGG
  Core E-Authentication Federation principles (i.e., interoperability, auditing, and privacy) that RPs and CSPs must comply with. The multi-industry partnership working on enabling interoperability among public and private electronic authentication (eauthentication) system
  845 KB (86,833 words) - 04:00, 28 June 2018
• GGG-R-Z
  ...ucts that have demonstrated basic interoperability in the E-Authentication Interoperability Lab and are approved by the E-Authentication Initiative for use in the Fede
  135 KB (15,051 words) - 04:00, 28 June 2018
• General IDESG Use Case
  Trust, Assurance, Authentication, Interoperability, Privacy ===Interoperability Considerations===
  5 KB (810 words) - 04:00, 28 June 2018

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