Search results

Jump to navigation Jump to search

  • Usable Consents
    common digital Consent Receipt Format standard. We of a standard ‘Consent Receipt’ schema. The Consent
    17 KB (2,526 words) - 01:18, 21 February 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
    ...puting device. This attestation provides the evidence need for meeting the requirements of that specification at the highest levels of assurance. ...velopers to coalesce around the development and implementation of a common standard for application registration with an API's authorization server. - - - Howe
    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]]: ...velopers to coalesce around the development and implementation of a common standard for application registration with an API's authorization server. - - - Howe
    7 KB (971 words) - 16:33, 30 April 2021
  • Mobile Driver's License Criteria
    ...nt of Homeland Security (DHS) has issued a RFC] for security standards and requirements to enable Federal agencies to accept them if compliant with the REAL ID. Co **This includes comments relating to the economic, privacy, security, environmental, energy, or federalism impacts that might result from a futu
    30 KB (4,866 words) - 16:56, 9 June 2021
  • ISO/IEC 27018 Privacy in the Cloud
    ...ity objectives and controls in ISO/IEC 27002, is to create a common set of security categories and controls that can be implemented by a public cloud computing ...technically and might increase risks to those physical and logical network security controls in place.
    4 KB (531 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
  • FIPS 140-2
    '''Title''': SECURITY REQUIREMENTS FOR CRYPTOGRAPHIC MODULES '''Category''': Security Requirements Standard
    3 KB (379 words) - 03:58, 28 June 2018
  • FIPS 140-2 Derived Test Requirements
    '''Title''': Derived Test Requirements for FIPS PUB 140-2, Security Requirements for Cryptographic Modules ...S 140-2 and a framework for testing whether implementations conform to the standard. Every assertion from FIPS 140-2 is identified and given a requirement num
    589 bytes (82 words) - 03:58, 28 June 2018
  • FIPS 201-1
    '''Category''': Credential Requirements Specification '''Description''': Specifies the architectural and technical requirements for the Personal Identity Verification (PIV) card
    1 KB (173 words) - 03:58, 28 June 2018
  • FIPS 201-2
    '''Category''': Credential Requirements Specification '''Description''': Specifies the architectural and technical requirements for the Personal Identity Verification (PIV) card
    3 KB (374 words) - 00:25, 24 August 2020
  • February 16, 2016 UXC Meeting Page
    **Chat from Paul Knight: Please also add brief entry per standard in Standards Inventory list at https://wiki.idesg.org/wiki/index.php?title= (note the "Add Standard" button there. The other two standards will be submitted shortly by Mary, I
    3 KB (532 words) - 03:58, 28 June 2018
  • February 9, 2016 UXC Meeting Page
    ...unreasonable. If there are the IDEF requirements, then you have additional requirements based on the trust mark you are planning to use. **For things were we don’t have requirements, we should be using “should.”
    5 KB (760 words) - 03:58, 28 June 2018
  • GGG
    <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
  • GGG-R-Z
    <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
  • IDEF Glossary
    ==== SECURITY CONTROL ==== ...rds employed within an entity to ensure compliance with applicable privacy requirements and manage privacy risks.
    11 KB (1,496 words) - 23:48, 5 September 2020
  • IDESG Deliverables Dashboard
    ...e-Requirement-v1.0-with-Supplemental-Guidance.pdf IDEF Baseline Functional Requirements and Supplemental Guidance v1.0]] :* NIST 800-63-2 (Standard approval)
    5 KB (599 words) - 04:00, 28 June 2018
  • IETF RFC 3647
    '''Description''': A standard framework for Certificate Policies (CPs) and Certification Practice Stateme document is intended to provide a structure but not the requirements for what the policies should be. A
    2 KB (297 words) - 04:00, 28 June 2018
  • ISO-IEC Directives Part 2
    '''Category''': Document Development Standard introduction, scope, references, terms and definitions, and (optionally) requirements. Attention is paid to
    2 KB (217 words) - 04:00, 28 June 2018
  • Best Practices and Example for RP System
    # 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

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

Retrieved from "https://wiki.idesg.org/wiki/Special:Search"