Search results

'''Title''': Security and Privacy Considerations for the OASIS Security Assertion Markup Language (SAML) V2.0 '''Category''': Authentication Procotol Specification

'''Title''': Identity Assurance Framework: Assessor Qualifications Requirements '''Category''': Trust Framework Provider Specification

'''Title''': Specification for Asset Identification 1.1 '''Category''': Security Requirements Specification

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

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

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

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

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

'''Title''': Conformance Requirements for the OASIS Security Assertion Markup Language (SAML) V2.0 '''Category''': Authentication Protocol Specification

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

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

...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

...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.

...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

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

...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.

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.

* 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

...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

...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

'''Category''': Security Requirements Specification participants are complying with FICAM privacy requirements.

'''Title''': SECURITY REQUIREMENTS FOR CRYPTOGRAPHIC MODULES '''Category''': Security Requirements Standard

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

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

<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>

<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>

==== SECURITY CONTROL ==== ...rds employed within an entity to ensure compliance with applicable privacy requirements and manage privacy risks.

https://kantarainitiative.org/confluence/display/infosharing/Consent+Receipt+Specification Consent Receipt Specification

International Standards, Technical Specification, Publicly Available Specifications, Technical Reports or introduction, scope, references, terms and definitions, and (optionally) requirements. Attention is paid to

...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

.../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

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

'''Category''': Trust Framework Provider Specification '''Description''': Defines requirements for InCommon Silver and Bronze identity assurance certification. These prof

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

'''Category''': Trust Framework Provider Specification ...defines a set of assurance levels involving increasing levels of security requirements for both