Search results

Jump to: navigation, search
  • ==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

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