Search results

Jump to: navigation, search
  • '''Title''': SECURITY REQUIREMENTS FOR CRYPTOGRAPHIC MODULES '''Category''': Security Requirements Standard
    3 KB (379 words) - 03:58, 28 June 2018
  • <center>'''National Security Telecom Advisory Comm.(NSTAC) Report to the President on Identity Managemen <center>'''Oasis: Glossary for the OASIS Security Assertion Markup Language (SAML) V2.0'''</center>
    845 KB (86,833 words) - 04:00, 28 June 2018
  • <center>'''National Security Telecom Advisory Comm.(NSTAC) Report to the President on Identity Managemen <center>'''Oasis: Glossary for the OASIS Security Assertion Markup Language (SAML) V2.0'''</center>
    135 KB (15,051 words) - 04:00, 28 June 2018
  • ...rity Assertion Markup Language (SAML) 2.0 Web Browser Single Sign-on (SSO) Profile '''Category''': Authentication Protocol Interoperability Profile
    2 KB (214 words) - 04:00, 28 June 2018
  • .../index.php?title=Baseline_Functional_Requirements_v1.0 Baseline Functional Requirements v1.0 (BFR)]. The [https://en.wikipedia.org/wiki/Security_Assertion_Markup_Language Security Assertion Markup Language (SAML)] based on XML was introduced in 2003 and w
    56 KB (9,154 words) - 00:16, 30 October 2020
  • '''Description''': Defines requirements for InCommon Silver and Bronze identity assurance certification. These prof Process,Levels of Assurance 1 and 2. The requirements are directly applicable to Identity Provider
    1 KB (156 words) - 04:01, 28 June 2018
  • '''Category''': Security Control Implementation Guide '''Description''': A set of documentation requirements that can be used to express the design of a cryptographic key
    3 KB (390 words) - 04:02, 28 June 2018
  • '''Title''': Requirements and Desirable Features of U.S. Federal Cryptographic Key Management Systems '''Category''': Security Requirements Profile
    1 KB (170 words) - 04:02, 28 June 2018
  • ...ll ensure this data is made available and follow certain interoperability, security, and privacy (HIPAAHIPPA) standards Both the patient EHR and data holder a Requirements:
    6 KB (949 words) - 18:39, 27 April 2019
  • ==Requirements Documents for Phase II== * Security [[file:Secure_Requirements_Update.docx]]
    2 KB (284 words) - 18:45, 7 January 2019
  • Privacy is considered as one of the core requirements of the IDESG and yet it has proven difficult to accommodate in the trust fr ...new framework is chosen, that may change the PET to meet those particular requirements.
    14 KB (2,167 words) - 01:45, 15 May 2021
  • ...nternet. This section uses the "Entity" definition of the IDESG Functional Requirements as any organization providing or using identity services. Before all of thi ...utions that have been tried, but failed, to deliver on a promise of better security for privacy in the past. The latter items are those that violate accepted u
    24 KB (3,858 words) - 17:49, 4 March 2021
  • ...of the user may be limited to a radius of miles, or feet, depending on the requirements of the app. Similarly the home address may be precise, or limited to just t ...new framework is chosen, that may change the PET to meet those particular requirements.
    17 KB (2,712 words) - 19:20, 28 November 2021
  • ...dify the terms that apply to the [[User Private Information]] based on new requirements of either the RP or the user. *Legal requirements for user notification exist, for example for data breaches or due to other
    13 KB (2,151 words) - 00:14, 30 October 2020
  • ...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
  • This [[Health Care Profile]] is one of the [[Framework Profiles]] that will allow developers of code a # Creation of a profile for the use of the [[UXC NSTIC Principles]] in the US Healthcare community.
    18 KB (2,580 words) - 18:52, 7 December 2020
  • ...ying its principles to specific vertical industry and horizontal community requirements. ...Functional Requirements (as amended from time to time) and add additional requirements in those four areas plus the potential for a trusted laboratory validation
    7 KB (988 words) - 21:22, 15 December 2018
  • ==Requirements for Phase III== ===Requirements Documents===
    5 KB (788 words) - 16:34, 16 April 2019
  • # Provide in-line guidance in the example code of the IDEF requirements that a developer of any web site can apply. ...intent. This is in keeping with the [[Usable Best Practice A]] of the SALS requirements.
    24 KB (3,980 words) - 19:57, 13 November 2020
  • # Profile of IDEF (Trusted Identifiers in Cyberspace) for healthcare industry in US. ## Testing must include all 4 IDEF components of: Security, Privacy, User Experience and Interoperability.
    28 KB (4,415 words) - 17:28, 21 March 2021

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