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
  • '''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 B (82 words) - 03:58, 28 June 2018
  • '''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
  • '''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
  • **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
  • ...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
  • <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
  • ==== 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
  • ...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
  • '''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
  • '''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
  • ...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
  • '''Title''': ISO/IEC 29100:2011 Information technology -- Security techniques -- Privacy framework '''Description''': This International Standard provides a high-level framework for the protection of personally identifiab
    1,022 B (130 words) - 04:00, 28 June 2018
  • ...ology -- Security Techniques -- Information security management systems -- Requirements (ISO 27001) '''Category''': Security
    2 KB (270 words) - 04:00, 28 June 2018
  • .../index.php?title=Baseline_Functional_Requirements_v1.0 Baseline Functional Requirements v1.0 (BFR)]. ...dations] were published in 1984 (Red Book). They were designed to become a standard for identifying users, but that role has been assumed by internet email add
    56 KB (9,154 words) - 00:16, 30 October 2020
  • ==SECURITY COMMITTEE / FUNCTIONAL MODEL MEETING NOTES - '''''draft'''''== ** Plenary planning for Security Committee breakout
    4 KB (617 words) - 04:01, 28 June 2018
  • **ISO 29115 the Security Committee had already submitted this standard to the Standards Committee. ...OK to include if there are no endorsement of products. We have a minimum standard for quality and it has to help people in a more general way. Mary will add
    3 KB (460 words) - 04:01, 28 June 2018
  • ==SECURITY COMMITTEE / FUNCTIONAL MODEL MEETING NOTES - '''''draft'''''== * Plenary planning for Security Committee breakout
    3 KB (481 words) - 04:01, 28 June 2018
  • ==SECURITY COMMITTEE MEETING NOTES - '''''draft'''''== ...ry is being worked: the FMO will provide an update on the cross committee requirements, a number of mini sessions are being planned, updates from pilots and a goo
    4 KB (609 words) - 04:01, 28 June 2018
  • ==SECURITY COMMITTEE / FUNCTIONAL MODEL MEETING NOTES - '''''draft'''''== ...oup of volunteers has been identified to work on a standards list that the Security Committee would like to put forward for potential adoption by IDESG. These
    4 KB (555 words) - 04:02, 28 June 2018
  • ==SECURITY COMMITTEE / FUNCTIONAL MODEL MEETING NOTES - '''''draft'''''== ...nts will be changed to MUST statements. The task force has discussed four requirements out of the total of 15. There is no formal deadline to finish, but the tas
    5 KB (750 words) - 04:02, 28 June 2018
  • ==SECURITY COMMITTEE / FUNCTIONAL MODEL MEETING NOTES - '''''draft'''''== ...d a copy to the Security Committee. The proposal is currently listed as a Security Committee initiative, but that will change. The comment was made that the
    5 KB (880 words) - 04:02, 28 June 2018
  • ...king on supplemental guidance and a new reference page. They will vote on standard 80063 and the committee is recommending approval. **Security Committee will not be meeting this week.
    3 KB (522 words) - 04:02, 28 June 2018
  • ...that LOA is not appropriate for attributes. But should we get RP current requirements on how they decide to trust attribute providers? ...ew is that assurance should be left to market and not formalized in single standard. There seemed to be a consensus on this among those present.
    3 KB (498 words) - 04:02, 28 June 2018
  • **Mary has asked for a copy of the third standard on usability and is waiting for a response. The two standards applications ...est practices to achieve certification. Tom had asked where the Functional requirements are posted and they are here: **https://wiki.idesg.org/wiki/index.php?title
    6 KB (932 words) - 04:02, 28 June 2018
  • '''10/6/14 [[Privacy Requirements]] Working Group Meeting Notes''' '''Function Requirements'''
    2 KB (278 words) - 04:02, 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
  • '''Category''': Security Control Implementation Guide technical requirements for the four levels assurance defined in OMB M-04-04 in the areas of identi
    4 KB (459 words) - 23:02, 18 February 2021
  • Security Assertion Markup Language (SAML) v2.0 http://docs.oasis-open.org/security/saml/v2.0/saml-2.0-os.zip
    2 KB (258 words) - 04:02, 28 June 2018
  • ==SECURITY COMMITTEE / FUNCTIONAL MODEL MEETING NOTES - '''''draft'''''== #** the TFTM committee will be charged with consolidating requirements and all the other work required to roll out the self-attestation program
    3 KB (412 words) - 04:02, 28 June 2018
  • ...to the UXC requirements. UXC is proposing to change 1, 2 and 7, but other requirements may change as well, including supplemental guidance. ...rs, Intermediaries, Attribute Providers and Relying Parties roles. The UXC requirements update will focus on these four roles from the Functional Model.
    5 KB (745 words) - 04:02, 28 June 2018
  • '''Category''': Credential Requirements Standard '''Description''': Requirements for non-Federal issuers of cards designed to interoperate with the Federal
    1,023 B (117 words) - 23:30, 12 January 2021
  • ==Requirements Documents for Phase II== * Security [[file:Secure_Requirements_Update.docx]]
    2 KB (284 words) - 18:45, 7 January 2019
  • ...laims for the relying party that is designed specifically to meet both the requirements of the relying party and the user's privacy directives. It is important tha # The RP uses a standard protocol and taxonomy to request the information needed from the user.
    12 KB (2,056 words) - 20:35, 27 November 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
  • The UXC Dictionary defines words used in the UXCs Requirements and Supplemental Guidance and should be considered apart of the Guidance. < ...ed to service providers, and they often must calculate the tradeoffs among security, privacy, and gaining access to a service they desire." Page 12
    8 KB (1,190 words) - 16:21, 27 May 2020
  • ...is page follows the [[Taxonomy AHG Glossary]] from the IDESG standards and security committees where they were able to reach consensus. ...|| DEVICE INTEGRITY SUPPORTING USER AUTHENTICATION – this case assumes a security component contained in the user device, but it could be a separate dongle i
    16 KB (2,511 words) - 23:58, 11 May 2016
  • ...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
  • The contents of this page are based upon evolving requirements for IDESG participants. Improving the security, privacy, usability, and interoperability of everyday online transactions
    17 KB (2,583 words) - 16:45, 10 June 2016
  • ...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 ...a user understandable name for a digital entity. In particular there is no standard way for the RP to acquire display name of the IdP using dynamic registratio
    21 KB (3,285 words) - 23:37, 15 January 2020
  • ...ns or, in some cases, all residents. The US has determined that the social security number (SSN) is not a secure means of identification and has mandated that ...[[Identifier]] for users of Medicare that is not tied to the user's social security number.
    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
  • ## Testing must include all 4 IDEF components of: Security, Privacy, User Experience and Interoperability. ...This requirement likely goes beyond a strict reading of the HIPAA security requirements.
    28 KB (4,415 words) - 17:28, 21 March 2021
  • ...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
  • ...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
  • 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
  • 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

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