Search results

Jump to navigation Jump to search

Page title matches

  • Privacy Req 2 Supplemental Guidance
    ''<< Back to [[Privacy_Req_2|Privacy Requirement 2]]'' ...ntity stakeholders) when applying and evaluating IDEF Baseline Requirement PRIVACY-2.
    2 KB (257 words) - 04:03, 28 June 2018
  • Privacy Req 3
    == PRIVACY-3. ATTRIBUTE MINIMIZATION == ...eleased as claims as well as detailed attributes; see also [[Privacy Req 1|PRIVACY-1
    3 KB (438 words) - 04:03, 28 June 2018
  • Privacy Req 3 Supplemental Guidance
    ''<< Back to [[Privacy_Req_3|Privacy Requirement 3]]'' ...ntity stakeholders) when applying and evaluating IDEF Baseline Requirement PRIVACY-3.
    1 KB (143 words) - 04:03, 28 June 2018
  • Privacy Req 4
    == PRIVACY-4. CREDENTIAL LIMITATION == ...ements [[Privacy Req 1|PRIVACY-1 (DATA MINIMIZATION)]] and [[Privacy Req 2|PRIVACY-2 (PURPOSE LIMITATION)]] on the application of limitations to, and scope of
    3 KB (356 words) - 04:03, 28 June 2018
  • Privacy Req 4 Supplemental Guidance
    ''<< Back to [[Privacy_Req_4|Privacy Requirement 4]]'' ...ntity stakeholders) when applying and evaluating IDEF Baseline Requirement PRIVACY-4.
    789 bytes (93 words) - 04:03, 28 June 2018
  • Privacy Req 5
    == PRIVACY-5. DATA AGGREGATION RISK == Entities MUST assess the privacy risk of aggregating [[IDEF Glossary PERSONAL INFORMATION|personal informati
    4 KB (480 words) - 04:03, 28 June 2018
  • Privacy Req 5 Supplemental Guidance
    ''<< Back to [[Privacy_Req_5|Privacy Requirement 5]]'' ...ntity stakeholders) when applying and evaluating IDEF Baseline Requirement PRIVACY-5.
    1 KB (147 words) - 04:03, 28 June 2018
  • Privacy Req 6
    == PRIVACY-6. USAGE NOTICE == ...rmation", see [[APPENDIX_A-Defined_Terms|Appendix A]], and [[Privacy Req 1|PRIVACY-1 (DATA MINIMIZATION)]].
    3 KB (368 words) - 04:03, 28 June 2018
  • Privacy Req 7
    == PRIVACY-7. USER DATA CONTROL == ...rmation", see [[APPENDIX_A-Defined_Terms|Appendix A]], and [[Privacy Req 1|PRIVACY-1 (DATA MINIMIZATION)]] and
    3 KB (374 words) - 04:03, 28 June 2018
  • Privacy Req 8
    == PRIVACY-8. THIRD-PARTY LIMITATIONS == ...rmation", see [[APPENDIX_A-Defined_Terms|Appendix A]], and [[Privacy Req 1|PRIVACY-1 (DATA MINIMIZATION)]].
    3 KB (370 words) - 04:03, 28 June 2018
  • Privacy Req 9
    == PRIVACY-9. USER NOTICE OF CHANGES == ...se USERS, and provide them with compensating controls designed to mitigate privacy risks that may arise from those changes, which may include seeking express
    3 KB (457 words) - 04:03, 28 June 2018
  • Privacy Requirements
    The Privacy Requirements Work Group is drafting privacy requirements to support the development of the [[Identity Ecosystem Framewo ...ns understand the guidance for Version 1 of the IDEF can be found in the [[Privacy References and Guides]] page.
    9 KB (1,100 words) - 04:03, 28 June 2018
  • Privacy Req 2
    == PRIVACY-2. PURPOSE LIMITATION == See also Requirement [[Privacy Req 1|PRIVACY-1 (DATA MINIMIZATION)]] on the application of limitations to, and
    5 KB (583 words) - 04:03, 28 June 2018
  • Privacy Profile
    A profile of a possible Privacy configuration as communicated from a [[Relying Party]] to a [[User]]. ...idelinesontheprotectionofprivacyandtransborderflowsofpersonaldata.htm OECD privacy guidelines] have some good defintions and principles.
    7 KB (1,037 words) - 04:58, 22 April 2020
  • Privacy Enhancing Technologies
    Privacy enhancing technology generic use case. In some ways this is similar to the Privacy, Trust/Assurance, Interoperability
    14 KB (2,167 words) - 01:45, 15 May 2021
  • ISO/IEC 27018 Privacy in the Cloud
    '''Privacy''': ...ation, risk monitoring and risk review. ISO/IEC 29134 provides guidance on privacy impact assessment.
    4 KB (531 words) - 04:00, 28 June 2018
  • ISO/IEC 29100 Privacy Framework
    ...le''': ISO/IEC 29100:2011 Information technology -- Security techniques -- Privacy framework ...and places organizational, technical, and procedural aspects in an overall privacy framework.
    1,022 bytes (130 words) - 04:00, 28 June 2018
  • Identity Ecosystem Framework enables individuals to protect their privacy through clear FIPPS rules
    ...cosystem Framework must offer individuals better means of protecting their privacy by establishing clear rules and guidelines based upon the FIPPs.] [[Category:Privacy Use Cases]]
    1 KB (158 words) - 04:00, 28 June 2018
  • Kantara Federal Privacy Criteria
    Privacy Criteria '''Privacy''':
    848 bytes (97 words) - 00:51, 31 May 2020
  • OASIS SAML Security and Privacy 2.0
    '''Title''': Security and Privacy Considerations for the OASIS Security Assertion Markup Language (SAML) V2.0 '''Description''': Provides security and privacy considerations for users of SAML 2.0, including some specific implementatio
    1 KB (171 words) - 04:02, 28 June 2018
  • Other Privacy Resources
    == OTHER PRIVACY RESOURCES == ...s informative, but not normative, guidance on the matters discussed in the Privacy Requirements.
    572 bytes (71 words) - 04:02, 28 June 2018
  • Privacy-Preserving Accessibility Support
    '''Title''': Privacy-Preserving Accessibility Support ...preferences and to control the release of subsets of that information in a privacy-preserving way to enable online services to tailor their presentation and u
    3 KB (367 words) - 04:02, 28 June 2018
  • Privacy Best Practice A
    == PRIVACY-BP-A. RECOMMENDED QUALITY CONTROLS == ...). Some of those choices may be less invasive, or create less risk of USER privacy loss, than
    3 KB (340 words) - 04:02, 28 June 2018
  • Privacy Best Practice B
    == PRIVACY-BP-B. RECOMMENDED TECHNOLOGY ENFORCEMENT == ...licies SHOULD be implemented through technical mechanisms. Those technical privacy controls SHOULD be situated as low in the technology stack as possible.
    2 KB (191 words) - 04:02, 28 June 2018
  • Privacy Best Practice C
    == PRIVACY-BP-C. RECOMMENDED CONSEQUENCES OF DECLINING == ...ndation builds on and improves the mandate in Requirement [[Privacy Req 11|PRIVACY-11 (OPTIONAL
    2 KB (304 words) - 04:02, 28 June 2018
  • Privacy Enhanced by User Agent
    Privacy enhancing technology provided by an agent under the user's control. Privacy, Trust/Assurance, Interoperability
    12 KB (2,056 words) - 20:35, 27 November 2019
  • FICAM Privacy Guidance for Assessors
    '''Title''': Federal Identity, Credentialing, and Access Management Privacy Guidance for Trust Framework Assessors participants are complying with FICAM privacy requirements.
    1 KB (123 words) - 00:49, 31 May 2020
  • Privacy Evaluations
    ...ted in accordance with the [https://www.idecosystem.org/filedepot?fid=1090 Privacy Evaluation Methodology]. | OpenID Connect || [[Standards]] || 8 October 2015 || Privacy issues; no objection || 5 January 2016
    4 KB (409 words) - 04:02, 28 June 2018
  • Privacy References and Guides
    ...organizations understand how to evaluate their system for alignment to the privacy requirements. References should be considered informative guides only.''' New documents can be suggested for inclusion by emailing the Privacy Committee listserv.
    5 KB (571 words) - 00:54, 31 May 2020
  • Privacy Req 1
    == PRIVACY-1. DATA MINIMIZATION == ...tity (for example from signin to signout of the user.) See [[Privacy Req 2|PRIVACY-2 (PURPOSE LIMITATION)]].
    3 KB (425 words) - 04:02, 28 June 2018
  • Privacy Req 10
    == PRIVACY-10. USER OPTION TO DECLINE == ...rmation", see [[APPENDIX_A-Defined_Terms|Appendix A]], and [[Privacy Req 1|PRIVACY-1 (DATA MINIMIZATION)]].
    2 KB (253 words) - 04:02, 28 June 2018
  • Privacy Req 11
    == PRIVACY-11. OPTIONAL INFORMATION == ...rmation", see [[APPENDIX_A-Defined_Terms|Appendix A]], and [[Privacy Req 1|PRIVACY-1 (DATA MINIMIZATION)]].
    3 KB (383 words) - 04:02, 28 June 2018
  • Privacy Req 12
    == PRIVACY-12. ANONYMITY == ...e [[Privacy Req 4|PRIVACY-4 (CREDENTIAL LIMITATION)]] and [[Privacy Req 15|PRIVACY-15 (ATTRIBUTE SEGREGATION)]].
    3 KB (409 words) - 04:02, 28 June 2018
  • Privacy Req 13
    == PRIVACY-13. CONTROLS PROPORTIONATE TO RISK == ...gement functions]], to establish what risks those functions pose to users' privacy.
    2 KB (284 words) - 04:02, 28 June 2018
  • Privacy Req 14
    == PRIVACY-14. DATA RETENTION AND DISPOSAL== ...rmation", see [[APPENDIX_A-Defined_Terms|Appendix A]], and [[Privacy Req 1|PRIVACY-1 (DATA MINIMIZATION)]].
    2 KB (282 words) - 04:02, 28 June 2018
  • Privacy Req 15
    == PRIVACY-15. ATTRIBUTE SEGREGATION == ...ved at https://workspace.idesg.org/kws/public/download.php/56/Supplemental-Privacy-Guidance.docx
    2 KB (283 words) - 04:02, 28 June 2018
  • Privacy Req 15ng
    == PRIVACY-15. ATTRIBUTE SEGREGATION == ...ved at https://workspace.idesg.org/kws/public/download.php/56/Supplemental-Privacy-Guidance.docx
    2 KB (290 words) - 04:02, 28 June 2018
  • Privacy Req 1 Supplemental Guidance
    ''<< Back to [[Privacy_Req_1|Privacy Requirement 1]]'' ...ntity stakeholders) when applying and evaluating IDEF Baseline Requirement PRIVACY-1.
    1 KB (131 words) - 04:02, 28 June 2018

Page text matches

  • Main Page
    ...ough self-assessment with a set of common standards for reliable security, privacy, ease of use, cost savings, and user choice and declare their commitment to
    3 KB (506 words) - 00:00, 24 January 2020
  • ABADSG
    '''Privacy''':
    433 bytes (45 words) - 19:46, 21 October 2019
  • Best Practices and Example for RP System
    ...re Identity Providers (IdPs). The example does not consider the case where privacy enhancing technology is used to prevent linkage between different instances ...nd intent. For example in the need to capture the user's acceptance of the privacy policy and the terms of use, a design pattern could just let the user read
    24 KB (3,980 words) - 19:57, 13 November 2020
  • Best Practices and Example for Tagging Data
    ...that information. In the simplest case, the [[Digital Entity]] will have a privacy policy that specifies what information is collected and for what reason. So
    3 KB (502 words) - 19:57, 13 November 2020
  • Consent Receipt
    ...ees to the sharing of personal information.  Its purpose is to capture the privacy policy and its purpose for sharing personal information so it can be easily '''Privacy''': The primary purpose of the consent receipt is compliance with the [[Gen
    3 KB (380 words) - 17:28, 25 July 2020
  • Data Controller
    [[Category:Privacy]]
    3 KB (416 words) - 00:25, 15 February 2020
  • Device Integrity supporting User Authentication
    Integrity, Privacy, Compliance, Interoperability ...y provides the foundation for strong authentication and protection of user privacy.
    12 KB (1,835 words) - 20:44, 5 November 2020
  • FBCA CP 2.25
    '''Privacy''': The FPKI management authority is required to conduct a Privacy Impact Assessment. PII shall be protected ...k]], [[PKI Sponsor]], [[Policy Management Authority]], [[Principal CA]], [[Privacy]], [[Private Key]], [[Public Key]], [[Public Key Infrastructure]], [[Regist
    4 KB (377 words) - 22:59, 18 February 2021
  • FBCA Cross-certification Methodology 3.0
    '''Privacy''': None.
    2 KB (230 words) - 23:00, 18 February 2021
  • FICAM Privacy Guidance for Assessors
    '''Title''': Federal Identity, Credentialing, and Access Management Privacy Guidance for Trust Framework Assessors participants are complying with FICAM privacy requirements.
    1 KB (123 words) - 00:49, 31 May 2020
  • FICAM TFPAP 1.0.1
    ...the TFPs privacy policy and requirements. Those are evaluated against the privacy criteria in Section 3.3. The criteria are (1) opt-in for positive confirmat
    3 KB (373 words) - 23:01, 18 February 2021
  • FIDO Universal 2nd Factor (U2F) 1.x
    '''Privacy''':
    345 bytes (34 words) - 03:58, 28 June 2018
  • FIDO Universal Authentication Framework (UAF) 1.x
    '''Privacy''':
    374 bytes (34 words) - 20:10, 15 October 2019
  • FIPS 140-2
    '''Privacy''': No stipulations.
    3 KB (379 words) - 03:58, 28 June 2018
  • FIPS 186-3
    '''Privacy''':
    440 bytes (44 words) - 03:58, 28 June 2018
  • FIPS 201-1
    '''Privacy''':
    1 KB (173 words) - 03:58, 28 June 2018
  • FIPS 201-2
    '''Privacy''': Protection of personal privacy is an explicit objective of the PIV system, directly from HSPD-12. Agencies ...ments issuing PIV cards are required to assign a privacy official, conduct Privacy Impact
    3 KB (374 words) - 00:25, 24 August 2020
  • February 14, 2017 UXC Meeting Page
    *Next Tuesday after we review comments, we'll send this along to the Privacy and Security committees for their comments.
    1 KB (228 words) - 03:58, 28 June 2018
  • February 16, 2016 UXC Meeting Page
    ...lth care. Bev Corwin is the contact for International. Jim Zok contact for Privacy. Suzanne Lightman is the contact for the Security Committee. Mary is cont
    3 KB (532 words) - 03:58, 28 June 2018
  • February 2, 2016 UXC Meeting Page
    ...sary. She’ll send it to the UXC and then Mary will forward along to TFTM, Privacy and Management Council stating it is a draft.
    4 KB (682 words) - 03:58, 28 June 2018
  • February 21, 2017 UXC Meeting Page
    **Ellen Nadeau commented that in column H what the user experience is - a privacy report that a few people authored at NIST included a potential problem for ...e came up and Tom Jones will contact him to see if he has any input from a privacy committee perspective. Tom will take a look at the links Ellen sent and wil
    1 KB (169 words) - 03:58, 28 June 2018
  • February 23, 2016 UXC Meeting Page
    ...s. And Under Error Conditions, she adjusted USABLE-3 and added some of the privacy requirements. ...ea. By end of week they will send it out to those who they want to review (Privacy, TFTM and to the Board). The Management Council is no more and the governin
    5 KB (835 words) - 03:58, 28 June 2018
  • February 24, 2015 Meeting Page
    ...a requirement for transparency about what the SP’s are doing? Yes, in the Privacy requirements and UXC requirements it was believed. ...nsparency and this is out of scope, but would like to see it covered under Privacy or UXC.
    3 KB (392 words) - 03:58, 28 June 2018
  • February 27, 2014 Meeting Page
    #**Ann - policy is an important element on privacy perspective
    5 KB (753 words) - 03:58, 28 June 2018
  • February 28, 2017 UXC Meeting Page
    ...hat was discussed last week. NIST Internal Report 8062 An Introduction to Privacy Engineering and Risk Management in Federal Systems issued in January 2017.
    3 KB (447 words) - 03:58, 28 June 2018
  • February 6, 2014 Meeting page
    | 8 || Privacy Enhanced by User Agent || TBD
    3 KB (408 words) - 03:58, 28 June 2018
  • February 6, 2015 UXC Meeting Page
    Mary added three requirements from the Privacy Committee into the UXC requirements spreadsheet. These are the three requi ...s definition? What if we created a graph and called out UXC issues around privacy and security around organizations vs individuals.
    7 KB (1,070 words) - 03:58, 28 June 2018
  • February 7, 2017 UXC Meeting Page
    ...items, Tom Jones created a list on the wiki for users to show the level of privacy they were working at. He shared the information during the meeting and a di
    2 KB (320 words) - 03:58, 28 June 2018
  • February 9, 2016 UXC Meeting Page
    ...pattern would be following the requirements of the IDEF, in particular the Privacy and Security requirements.”
    5 KB (760 words) - 03:58, 28 June 2018
  • Federated Strong Employee ID
    * [http://www.tscp.org/privacy-employer-ids/ Privacy using Employer issued Identifiers] from http://tscp.org
    3 KB (429 words) - 23:13, 20 May 2020
  • Four Party Authentication and Authorization Use Case
    ===Privacy Considerations===
    7 KB (1,007 words) - 03:58, 28 June 2018
  • Functional Requirements
    *Legal and regulatory (HIPPA) privacy requirements for the users of the healthcare system.
    8 KB (1,315 words) - 19:29, 30 July 2020
  • GGG
    <center>'''Smedinghoff: Federated Identity Management: Balancing Privacy Rights, Liability Risks and the Duty to Authenticate'''</center> <center>'''Liberty Alliance Privacy and Security Best Practices'''</center>
    845 KB (86,833 words) - 04:00, 28 June 2018
  • GGG-R-Z
    <center>'''Smedinghoff: Federated Identity Management: Balancing Privacy Rights, Liability Risks and the Duty to Authenticate'''</center> <center>'''Liberty Alliance Privacy and Security Best Practices'''</center>
    135 KB (15,051 words) - 04:00, 28 June 2018
  • GGG-Sources
    Open Privacy.Org: Definitions Open Privacy Initiative
    13 KB (1,562 words) - 04:00, 28 June 2018
  • Game Avatar as Pseudonymous Identity Use Case
    ...pseudonymous identity, match names between systems, verify attributes with privacy protection] [[Category:Privacy Use Cases]]
    925 bytes (109 words) - 04:00, 28 June 2018
  • General Data Protection Regulation
    With links to all of the parts: https://www.privacy-regulation.eu/en/ [[Category:Privacy]]
    977 bytes (137 words) - 04:00, 28 June 2018
  • General IDESG Use Case
    Trust, Assurance, Authentication, Interoperability, Privacy ...(RP) role. This case is specifically designed to include general security, privacy and user experience criteria that will apply by default to all other user c
    5 KB (810 words) - 04:00, 28 June 2018
  • Generalized Presumptive Authentication
    ...a human being who wants to access services on a web site and still retain privacy by requesting that the site not link the user's attributes to any other sit ...ser experience and obtains responses from the user in order to satisfy the privacy concerns of the user and the need for identity and attribute claims by the
    10 KB (1,596 words) - 20:11, 15 October 2019
  • Health IT Record Location Service (Data Aggregation)
    ...rs using multiple personas within the system and/or verify attributes with privacy protection. (RLS has also been used to indicate a record locator service on :: * Provider name (may be encoded to protect Provider's privacy)
    8 KB (1,018 words) - 23:54, 23 March 2020
  • ICAM IMI Profile 1.0.1
    '''Privacy''':
    470 bytes (43 words) - 04:00, 28 June 2018
  • ICAM OpenID 2.0 Profile 1.0.1
    '''Privacy''':
    471 bytes (43 words) - 04:00, 28 June 2018
  • ICAM SAML 2.0 WB SSO Profile 1.0.2
    ...ers are referred to FICAM TFPAP Section 3.3 and advised that many of those privacy principles
    2 KB (214 words) - 04:00, 28 June 2018
  • IDEF Glossary
    ==== PRIVACY CONTROL ==== ...ntity to ensure compliance with applicable privacy requirements and manage privacy risks.
    11 KB (1,496 words) - 23:48, 5 September 2020
  • IDESG Baseline Process Use Case
    <p>Privacy Coordination</p>
    23 KB (3,525 words) - 04:00, 28 June 2018
  • IDESG Code of Conduct
    ...iples is prohibited. Members should also show proper consideration for the privacy of others and for topics that may be considered inflammatory.
    6 KB (946 words) - 04:00, 28 June 2018
  • IDESG Deliverables Dashboard
    === Privacy Coordination Committee === Maintenance of IDEF Reqts - Privacy
    5 KB (599 words) - 04:00, 28 June 2018
  • IETF ID SCIM 1.0
    '''Privacy''':
    417 bytes (41 words) - 04:00, 28 June 2018
  • IETF ID SWD
    '''Privacy''':
    452 bytes (42 words) - 04:00, 28 June 2018
  • IETF RFC 2026
    '''Privacy''':
    502 bytes (53 words) - 04:00, 28 June 2018
  • IETF RFC 2510
    '''Privacy''':
    407 bytes (40 words) - 04:00, 28 June 2018
  • IETF RFC 2560
    '''Privacy''':
    458 bytes (48 words) - 04:00, 28 June 2018
  • IETF RFC 3647
    '''Privacy''': The framework specifies where issuers document their privacy policy, what information is considered private
    2 KB (297 words) - 04:00, 28 June 2018
  • IETF RFC 4122
    '''Privacy''':
    424 bytes (44 words) - 04:00, 28 June 2018
  • IETF RFC 5280
    '''Privacy''':
    481 bytes (49 words) - 04:00, 28 June 2018
  • IETF RFC 6750 - OAuth 2.0 Bearer Token Usage
    '''Privacy''':
    1 KB (172 words) - 04:00, 28 June 2018
  • IETF RFC 7009 - OAuth 2.0 Token Revocation
    '''Privacy''':
    804 bytes (99 words) - 04:00, 28 June 2018
  • IETF RFC 7591
    '''Privacy''':
    2 KB (216 words) - 04:00, 28 June 2018
  • ISO-IEC Directives Part 2
    '''Privacy''':
    2 KB (217 words) - 04:00, 28 June 2018
  • ISO/IEC 27018 Privacy in the Cloud
    '''Privacy''': ...ation, risk monitoring and risk review. ISO/IEC 29134 provides guidance on privacy impact assessment.
    4 KB (531 words) - 04:00, 28 June 2018
  • ISO/IEC 29100 Privacy Framework
    ...le''': ISO/IEC 29100:2011 Information technology -- Security techniques -- Privacy framework ...and places organizational, technical, and procedural aspects in an overall privacy framework.
    1,022 bytes (130 words) - 04:00, 28 June 2018
  • ISO 27001
    '''Privacy''': If ISO 27001 is used to implement the ISMS, the ISMS would satisfy the
    2 KB (270 words) - 04:00, 28 June 2018
  • ISO 27002
    ...mplemented, protect the confidentiality of data. While not specifically a “privacy” standard, the controls address access and encryption of sensitive inform
    2 KB (199 words) - 04:00, 28 June 2018
  • ISO 9241-210 Ergonomics of human–system interaction
    '''Privacy''':
    968 bytes (122 words) - 04:00, 28 June 2018
  • ISO 98-1: Uncertainty of measurement — Part 1
    '''Privacy''':
    617 bytes (71 words) - 04:00, 28 June 2018
  • Identity
    The term identity is used in many contexts with many meanings, and the privacy implications of an attribute being part of an identity should be unders
    2 KB (255 words) - 04:00, 28 June 2018
  • Identity Design Patterns
    ...ser until that user voluntarily allows the site to identify that user. The privacy implications of any general web sites knowing so much about a user's compet ...can be collected including consideration of the community of users, their privacy and safety.
    12 KB (1,958 words) - 17:45, 25 May 2019
  • Identity Ecosystem
    ...l not mandate, stronger identification and authentication while protecting privacy by limiting the amount of information that individuals must disclose. [[NS
    1 KB (171 words) - 04:00, 28 June 2018
  • Identity Ecosystem Framework enables individuals to protect their privacy through clear FIPPS rules
    ...cosystem Framework must offer individuals better means of protecting their privacy by establishing clear rules and guidelines based upon the FIPPs.] [[Category:Privacy Use Cases]]
    1 KB (158 words) - 04:00, 28 June 2018
  • Identity Ecosystem Framework protects individuals from unbounded liability in particular for losses that they were powerless to prevent.
    [[Category:Privacy Use Cases]]
    2 KB (253 words) - 04:00, 28 June 2018
  • Identity Model
    ...the US contracts can be used to force employees and others to "opt-out" of privacy regulation. With the GDPR no "opt-out" is permitted. ...definition, public. The PKI continues to provide good functionality where privacy is not permitted by law or necessity.
    56 KB (9,154 words) - 00:16, 30 October 2020
  • Identity Model Overview
    *Creating a [[Community and Privacy Pattern Language]] has been a challenge ever since communities grew beyond ...e following are some of the concerns that are not addressed in the BFR. ([[Privacy Req 15]]).
    5 KB (842 words) - 04:01, 28 June 2018
  • Identity Modeling Introduction
    ...After all the greatest hassle for users is created when their security or privacy are breached. While interoperability is seldom raised as a user expectation Given all of the challenges of security and privacy what can the IDESG do to help create a good user experience on authenticati
    8 KB (1,351 words) - 21:37, 27 March 2020
  • Identity Proofing Use Case
    ===Privacy Considerations===
    3 KB (328 words) - 21:41, 10 January 2020
  • InCommon Glossary
    '''Privacy''': ...ipant]], [[Participant Agreement]], [[Participant Operating Practices]], [[Privacy Policy]], [[Profile]], [[Public Key Cryptography]], [[Public Key Infrastruc
    2 KB (205 words) - 04:01, 28 June 2018
  • InCommon IAAF 1.1
    '''Privacy''': Some discussion of the subject trusting the IDP to protect privacy, and real-time versus pre-approved
    2 KB (203 words) - 21:48, 10 January 2020
  • InCommon IAP 1.1
    '''Privacy''': No stipulations. For Silver profiles, there are requirements to store P
    1 KB (156 words) - 04:01, 28 June 2018
  • Inform User of Disclosure of PII Use Case
    [[Category:Privacy Use Cases]]
    676 bytes (77 words) - 04:01, 28 June 2018
  • Information Ethics and Human Capability
    ...solutions to access online services in a manner that promotes confidence, privacy, choice, and innovation.'' *#"Consider the following list: PAPA (privacy, accuracy, intellectual property and access); ‘the triple A’ (availabil
    13 KB (1,906 words) - 19:16, 2 July 2021
  • Interaction Model Working Group Collaboration Space
    ...ween different entities/roles (IdP, RP, User, etc.) that require different privacy, security, UX and other considerations. ...r deriving requirements – like security requirements, UX requirements, and privacy requirements, so on.
    6 KB (888 words) - 04:01, 28 June 2018
  • Interop Best Practice A
    ...Y-PROVIDERS SHOULD provide USERS with a mechanism for portability of their privacy and other USER preferences.
    2 KB (283 words) - 22:49, 12 October 2018
  • Interop Best Practice G
    * Children's Online Privacy Protection Act (COPPA) for entities whose transactions are governed by its
    2 KB (291 words) - 04:01, 28 June 2018
  • Interop Req 5
    * HIPAA Security and Privacy Regulations regarding development and maintenance of policies and procedure
    3 KB (313 words) - 04:01, 28 June 2018
  • Interop Req 6
    ...comments about "data storage companies" in the Modifications to the HIPAA Privacy, Security, Enforcement, and Breach Notification Rules Under the HITECH Act ...th various requirements: see "Business Associate" regulations in the HIPAA Privacy Regulations: 45 CFR Parts 160 and 164, §§ 160.103, 164.502(a)(3), (a)(
    3 KB (451 words) - 04:01, 28 June 2018
  • Interop Req 8
    Reference for “accountability” requirements: ISO/IEC 29100 (2011) Privacy Framework, Section 5.10 Accountability, http://standards.iso.org/ittf/Publi
    2 KB (190 words) - 04:01, 28 June 2018
  • January 13, 2017 VPWG Meeting Page
    ...gain education and have a health record. How do these populations get some privacy and control?
    5 KB (748 words) - 04:01, 28 June 2018
  • January 14, 2016 UXC Meeting Page
    *FTC had a privacy conference recently. Google in now on 97 percent of the top 1,000 sites an *Jim Zok also offered to take this to the Privacy Committee for their review.
    4 KB (702 words) - 04:01, 28 June 2018
  • January 19, 2016 UXC Meeting Page
    *Design Pattern work – discussed sending to TFTM, Privacy and Management Council for review.
    3 KB (460 words) - 04:01, 28 June 2018
  • January 23, 2018 Agile Advisory Team
    ...involvement was with the Privacy Committee. He is the fourth Chair of the Privacy Committee since it was originally formed. His background is in sales and m
    3 KB (428 words) - 04:01, 28 June 2018
  • January 24, 2017 UXC Meeting Page
    **Tom Jones asked to include a discussion about how to explain to a user what privacy state they are in. * How do we tell the user what their privacy state is? Mary noted that this is a critical piece for a RP – and it is
    7 KB (1,229 words) - 04:01, 28 June 2018
  • January 30, 2018 Agile Advisory Team
    *2) Tom and Jeff Brennan have devoted time to reviewing Noreen’s finding for Privacy and will be providing their recommendations – what is not reviewed during ** Tom reviewed the text for Privacy Requirements modified from IDEF version 1. This document was attached to t
    2 KB (355 words) - 04:01, 28 June 2018
  • January 31, 2017 UXC Meeting Page
    **Tom discussed the User Identity Privacy Risk Levels he put together. They are Anonyous, Pseudonymous, Weakly Authe **For an indication to the user of the current privacy status
    3 KB (474 words) - 04:01, 28 June 2018
  • July 16, 2015 Meeting Page
    ...mmittee should come up with a Security Evaluation Methology similar to the Privacy Evaluation mythology as a new work item? Steve recommended we add the next
    5 KB (845 words) - 04:02, 28 June 2018
  • July 17, 2014 Meeting Page
    ...rin about inclusion of privacy concerns in the model. Ryan suggested that privacy should be dealt with as part of the requirements.
    3 KB (448 words) - 04:02, 28 June 2018
  • July 19, 2016 UXC Meeting Page
    *Are we ready to send Ellen’s document to TFTM, Privacy or IDESG as a whole? Tom will reach out to a few contacts for feedback. *The Trustmark evolving pattern will be sent to TFTM for their feedback. Privacy Committee did not have any comments.
    3 KB (487 words) - 04:02, 28 June 2018
  • July 26, 2016 UXC Meeting Page
    ...2016. She is almost done. It was suggested that she send the document to Privacy, FMO, TFTM and the Chairs for an informal review now before officially sen * Send to TFTM, Privacy and Chairs with little feedback. Next?
    3 KB (378 words) - 04:02, 28 June 2018
  • July 31, 2014 Meeting Page
    #** To that end, Adam reached out to the Privacy Committee who’s approval is a necessary prerequisite for submission of th
    4 KB (608 words) - 04:02, 28 June 2018
  • June 14, 2016 UXC Meeting Page
    **Privacy Committee – the two design pattern documents sent to Privacy have not had any feedback.
    5 KB (790 words) - 04:02, 28 June 2018
  • June 18, 2015 Meeting Page
    *HIMSS recommendation discussed at Chairs meeting; policy has been sent to Privacy, Security and Standards Committees chairs. Chat from Paul Knight: “The
    3 KB (479 words) - 04:02, 28 June 2018
  • June 2, 2015 Meeting Page
    *Liaison reports from Jim Zok on Privacy, Standards, Noreen on International.
    2 KB (333 words) - 04:02, 28 June 2018
  • June 21, 2016 UXC Meeting Page
    ...m created this design pattern. He asked the team to look especially at the privacy concerns and the specific use case at the bottom of the page. *https://wiki
    2 KB (318 words) - 04:02, 28 June 2018
  • June 27, 2017 UXC Meeting Page
    ...has sent various documents for people to comment on. Tom went to a recent Privacy Committee meeting to provide details on this work. They talked about takin ...the user attributes that are selected on first signin. Also the terms and privacy statement are dense legalese which are written to protect the site owner. T
    5 KB (876 words) - 04:02, 28 June 2018
  • Kantara Federal Privacy Criteria
    Privacy Criteria '''Privacy''':
    848 bytes (97 words) - 00:51, 31 May 2020
  • Kantara IAF 1000
    '''Privacy''':
    1 KB (128 words) - 04:02, 28 June 2018
  • Kantara IAF 1100
    '''Privacy''': No stipulation.
    2 KB (217 words) - 04:02, 28 June 2018
  • Kantara IAF 1200
    '''Privacy''': No stipulation.
    785 bytes (85 words) - 04:02, 28 June 2018
  • Kantara IAF 1300
    '''Privacy''':
    1 KB (119 words) - 04:02, 28 June 2018
  • Kantara IAF 1400
    '''Privacy''':
    653 bytes (65 words) - 04:02, 28 June 2018
  • Kantara IAF 1600
    '''Privacy''':
    681 bytes (65 words) - 04:02, 28 June 2018
  • Kantara SAML 2.0 Profile
    '''Privacy''':
    871 bytes (95 words) - 04:02, 28 June 2018
  • March 1, 2016 UXC Meeting Page
    *Privacy group is still working on usability. They will look at UXC disclaimer lang
    3 KB (548 words) - 04:02, 28 June 2018
  • March 10, 2017 VPWG Meeting Page
    ...ling against the DoD for releasing information that is protected under the privacy act to companies like ID.me. The lawsuit is supposed to be filed within the
    6 KB (1,061 words) - 04:02, 28 June 2018
  • March 15, 2016 UXC Meeting Page
    ...40500:2012. The other standards that UXC submitted are in review with the Privacy Committee. **Privacy Committee has been discussing what to do with the reference material on the
    3 KB (514 words) - 04:02, 28 June 2018
  • March 24, 2013 Meeting Page
    ...dispose of comments and append additional comments to Use Case containing privacy considerations
    1 KB (162 words) - 04:02, 28 June 2018
  • March 26, 2015 Meeting Page
    ...ommittee could be doing related to overall requirements. For example, the Privacy Committee independently did a review of security and interoperability requi
    5 KB (880 words) - 04:02, 28 June 2018
  • March 29, 2016 UXC Meeting Page
    **Privacy Coordination Committee is working on supplemental guidance and a new refere
    3 KB (522 words) - 04:02, 28 June 2018
  • Match Names between Identity Systems Use Case
    ...pseudonymous identity, match names between systems, verify attributes with privacy protection]
    881 bytes (102 words) - 04:02, 28 June 2018
  • May 10, 2016 UXC Meeting Page
    ...ctors section, Design Patterns Common to any Internet Identity Ecosystem – Privacy Considerations. https://wiki.idesg.org/wiki/index.php?title=Design_Pattern% ...ade to send out the Design Pattern pages to other committees for feedback (Privacy, Board of Directors, Chairs Committee and TFTM).
    4 KB (658 words) - 04:02, 28 June 2018
  • May 24, 2016 UXC Meeting Page
    ...The section titled “What is the baseline?” says: “Improving the security, privacy, usability, and interoperability of everyday online transactions” and tha **Privacy Evaluation Subcommittee meeting for today is cancelled.
    6 KB (932 words) - 04:02, 28 June 2018
  • May 29, 2014 Meeting Page
    ...rting). Adam proposed we request a joint committee meeting with Use Case, Privacy and Trust Framework around functional model - committee has no objections.
    4 KB (620 words) - 04:02, 28 June 2018
  • May 3, 2016 UXC Meeting Page
    ...GRITY was changed to a simpler definition. There are no concerns from the Privacy Evaluation Committee as their recommended changes were approved. Completio **Privacy Committee meets today. They just completed their elections and Jeff Brenna
    3 KB (523 words) - 04:02, 28 June 2018
  • May 30, 2017 UXC Meeting Page
    ...g so we can gather input from them. Tom Jones will present same at June 6 Privacy Coordination Committee meeting.
    843 bytes (130 words) - 04:02, 28 June 2018
  • May 8, 2014 Meeting Page
    ...and next steps. To document uses cases and them to see where (governance, privacy, security, etc.) fit in.
    1 KB (196 words) - 04:02, 28 June 2018
  • May 9, 2017 UXC Meeting Page
    ...ed UX members to review and provide feedback before it is presented to the Privacy Committee on June 4.
    764 bytes (116 words) - 04:02, 28 June 2018
  • Meeting notes from April 28, 2014
    '''Meeting Notes from the [[Privacy Requirements]] Working Group Meeting on 4/28/14.'''
    1 KB (148 words) - 04:02, 28 June 2018
  • Meeting notes from July 28, 2014
    '''7/287/14 [[Privacy Requirements]] Working Group Meeting Notes''' ...tions shall maximize use of architectural and technical point controls for privacy.
    2 KB (215 words) - 04:02, 28 June 2018
  • Meeting notes from July 7, 2014
    '''7/7/14 [[Privacy Requirements]] Working Group Meeting Notes'''
    3 KB (469 words) - 04:02, 28 June 2018
  • Meeting notes from June 16, 2014
    '''[[Privacy Requirements]] Working Group Meeting notes from June 16, 2014''' * Privacy-enhancing technology is how, not what. too much influence on implementation
    1 KB (205 words) - 04:02, 28 June 2018
  • Meeting notes from June 2, 2014
    '''Notes from June 2, 2014 [[Privacy Requirements]] Working Group Meeting''' * Privacy, Security, Standards, User Experience, met to discuss requirements coordina
    1 KB (190 words) - 04:02, 28 June 2018
  • Meeting notes from June 23, 2014
    '''6/23/14 [[Privacy Requirements]] Working Group Meeting Notes'''
    2 KB (218 words) - 04:02, 28 June 2018
  • Meeting notes from June 30, 2014
    '''6/30/14 [[Privacy Requirements]] Working Group Meeting Notes''' * Proactive Privacy Subcommittee work provided language to clarify: "When terminating business
    3 KB (380 words) - 04:02, 28 June 2018
  • Meeting notes from June 9, 2014
    '''Notes from June 9, 2014 [[Privacy Requirements]] Working Group Meeting''' * Notice: Creating privacy policies is very difficult to do appropriately without turning into legales
    1 KB (187 words) - 04:02, 28 June 2018
  • Meeting notes from May 12, 2014
    Notes from May 12, 2014 [[Privacy Requirements]] Working Group Meeting ** "construct trees" in order to view privacy chains of action/events
    1 KB (178 words) - 04:02, 28 June 2018
  • Meeting notes from November 10, 2014
    '''11/10/14 [[Privacy Requirements]] Working Group Meeting Notes''' ...n: Organizations must provide a technical mechanism to bundle individuals' privacy choices along with attributes, and have mechanisms to ensure other parties
    4 KB (568 words) - 04:02, 28 June 2018
  • Meeting notes from November 24, 2014
    '''11/24/14 [[Privacy Requirements]] Working Group Meeting Notes''' ** You mitigate privacy risks if you keep info that could be used to identify someone separate from
    6 KB (796 words) - 04:02, 28 June 2018
  • Meeting notes from November 3, 2014
    '''11/3/14 [[Privacy Requirements]] Working Group Meeting Notes''' ** Ann suggested editing to say “maintaining the security and privacy…”
    3 KB (377 words) - 04:02, 28 June 2018
  • Meeting notes from October 20, 2014
    '''10/20/14 [[Privacy Requirements]] Working Group Meeting Notes''' ...aining the security and privacy…” Ann will write up why we want to include privacy here, and discussion will continue via email.
    2 KB (240 words) - 04:02, 28 June 2018
  • Meeting notes from October 27, 2014
    '''10/27/14 [[Privacy Requirements]] Working Group Meeting Notes'''
    2 KB (305 words) - 04:02, 28 June 2018
  • Meeting notes from October 6, 2014
    '''10/6/14 [[Privacy Requirements]] Working Group Meeting Notes''' ** Risk to privacy factor in determining an organization’s practices when assessing how comp
    2 KB (278 words) - 04:02, 28 June 2018
  • Meeting notes from September 22, 2014
    '''9/22/14 [[Privacy Requirements]] Working Group Meeting Notes'''
    2 KB (279 words) - 04:02, 28 June 2018
  • Meeting notes from September 8, 2014
    '''9/8/14 [[Privacy Requirements]] Working Group Meeting Notes''' ** Do people have a better understanding of, or control over, their privacy with an opt-in option?
    2 KB (341 words) - 04:02, 28 June 2018
  • NIST IR 7693
    '''Privacy''': There may be PII among the attributes that make up a person's identity.
    2 KB (204 words) - 04:02, 28 June 2018
  • NIST IR 7870
    '''Privacy''': No privacy stipulations.
    810 bytes (97 words) - 04:02, 28 June 2018
  • NIST SP 800-130
    '''Privacy''': Contains functional requirements related to privacy, requiring the CKMS design to specify the support for the ...ment]], [[Mode Of Operation]], [[Parameters]], [[Pre-activation State]], [[Privacy]], [[Profile]], [[Qubit]], [[Recover (key/metadata)]], [[Registration]], [[
    3 KB (390 words) - 04:02, 28 June 2018
  • NIST SP 800-152
    '''Privacy''': Lists anonymity and protection of personal privacy as stretch goals for section 4.4 Accountability. It also
    1 KB (170 words) - 04:02, 28 June 2018
  • NIST SP 800-37 Rev 1
    '''Privacy''':
    2 KB (208 words) - 04:02, 28 June 2018
  • NIST SP 800-53 Rev 4
    '''Title''': Security and Privacy Controls for Federal Information Systems and Organizations '''Description''': NIST SP 800-543 Rev 4 provides a catalog of security and privacy controls for federal information systems and organizations and a process fo
    2 KB (249 words) - 04:02, 28 June 2018
  • NIST SP 800-63-2
    ...rivacy''': Advises agencies to reference OMB Guidance for Implementing the Privacy Provisions of the E-Government .... Subscribers are assumed to trust relying parties to follow "all relevant privacy
    4 KB (459 words) - 23:02, 18 February 2021
  • NIST SP 800-73-3 Part 1
    '''Privacy''':
    1,002 bytes (102 words) - 04:02, 28 June 2018
  • NIST SP 800-73-3 Part 2
    '''Privacy''':
    1 KB (120 words) - 04:02, 28 June 2018
  • NIST SP 800-73-3 Part 3
    '''Privacy''':
    1 KB (109 words) - 04:02, 28 June 2018
  • NIST SP 800-73-3 Part 4
    '''Privacy''':
    864 bytes (94 words) - 04:02, 28 June 2018
  • NIST SP 800-76-2
    '''Privacy''':
    774 bytes (87 words) - 04:02, 28 June 2018
  • NIST SP 800-79-1
    ...agement and data protection accreditation topic includes confirmation that privacy requirements from FIPS 201 are satisfied. This document does not add privacy requirements but provides
    2 KB (198 words) - 04:02, 28 June 2018
  • NIST SP 800-85A-2
    '''Privacy''':
    566 bytes (67 words) - 04:02, 28 June 2018
  • NIST SP 800-85B
    '''Privacy''':
    765 bytes (94 words) - 04:02, 28 June 2018
  • NSTIC Strategy
    Efficiency, Security, and Privacy ...v/blog/2011/04/26/national-strategy-trusted-identities-cyberspace-and-your-privacy
    2 KB (148 words) - 04:02, 28 June 2018
  • No one service provider can gain a complete picture of an individual’s life in cyberspace
    ...iple of the envisioned Identity Ecosystem. The Identity Ecosystem will use privacy-enhancing technology and policies to inhibit the ability of service provide [[Category:Privacy Use Cases]]
    954 bytes (117 words) - 04:02, 28 June 2018
  • OASIS IMI 1.0
    '''Privacy''':
    1 KB (112 words) - 04:02, 28 June 2018
  • OASIS Interop
    '''Privacy''': No specific privacy relevance.
    933 bytes (104 words) - 04:02, 28 June 2018
  • OASIS SAML 2.0
    ...asis-open.org/security/saml/v2.0/saml-sec-consider-2.0-os.pdf Security and Privacy Considerations]
    2 KB (258 words) - 04:02, 28 June 2018
  • OASIS SAML Authentication Context 2.0
    '''Privacy''':
    489 bytes (48 words) - 20:12, 15 October 2019
  • OASIS SAML Bindings 2.0
    '''Privacy''':
    493 bytes (49 words) - 04:02, 28 June 2018
  • OASIS SAML Conformance 2.0
    '''Privacy''':
    654 bytes (69 words) - 16:30, 27 May 2020
  • OASIS SAML Glossary 2.0
    ...vacy''': Defines both transient and persistent pseudonym as mechanisms for privacy-preserving name identifiers.
    2 KB (226 words) - 04:02, 28 June 2018
  • OASIS SAML Metadata 2.0
    '''Privacy''':
    721 bytes (81 words) - 04:02, 28 June 2018
  • OASIS SAML Profiles 2.0
    '''Privacy''':
    691 bytes (77 words) - 04:02, 28 June 2018
  • OASIS SAML Protocol 2.0
    '''Privacy''':
    670 bytes (72 words) - 04:02, 28 June 2018
  • OASIS SAML Security and Privacy 2.0
    '''Title''': Security and Privacy Considerations for the OASIS Security Assertion Markup Language (SAML) V2.0 '''Description''': Provides security and privacy considerations for users of SAML 2.0, including some specific implementatio
    1 KB (171 words) - 04:02, 28 June 2018
  • OASIS TC-Process Sec 2.18
    '''Privacy''':
    478 bytes (45 words) - 04:02, 28 June 2018
  • OASIS XACML v3.0
    ...(3) enabling consistent and detailed compliance with policies on access to privacy-sensitive data of relying parties.
    2 KB (256 words) - 04:02, 28 June 2018
  • OASIS XACML v3.0 (Selected Profiles)
    '''Privacy''':
    2 KB (241 words) - 04:02, 28 June 2018
  • OASIS xNL 2.0
    '''Privacy''': Privacy is explicitly out of scope of the specification (q.v. section 4.4).
    1 KB (142 words) - 04:02, 28 June 2018
  • OAuth 1.0 Protocol
    '''Privacy''':
    869 bytes (102 words) - 04:02, 28 June 2018
  • OAuth 2.0
    '''Privacy''':
    2 KB (193 words) - 21:30, 24 July 2020
  • OAuth 2.0 Threat Model
    '''Privacy''':
    576 bytes (63 words) - 04:02, 28 June 2018
  • October 1, 2015 Meeting Page
    ...ortant that there is a clear set of operational checks, includes Security, Privacy, Standards and User Experience. What has been a baseline against what we m
    7 KB (1,031 words) - 04:02, 28 June 2018
  • October 11, 2016 UXC Meeting Page
    Example is the Common Design pattern Privacy Section: https://wiki.idesg.org/wiki/index.php?title=Design_Pattern%3A_Comm ...ocation in the document is under NSTIC Guiding Principles Considerations – Privacy Considerations.
    6 KB (955 words) - 04:02, 28 June 2018
  • October 13, 2015 UXC Meeting Page
    ...Zok brought up an issue we had discussed in a smaller group last week: the privacy committee thought it best to adjust the title of the Usable-7 requirement t
    3 KB (404 words) - 04:02, 28 June 2018
  • October 17, 2017 UXC Meeting Page
    ...rategy AND THE idesg PRINCIPLES. Besides those items related to security, privacy ad interoperability, these UX items are included:
    3 KB (454 words) - 04:02, 28 June 2018
  • October 23, 2014 Meeting Page
    #* Andrew introduced the collect, use, disclose nomenclature used in privacy circles
    1 KB (154 words) - 04:02, 28 June 2018
  • October 24, 2017 UXC Meeting Page
    ...ategy]] and the IDESG principles. Besides those items related to security, privacy and interoperability, these UX items are included:
    4 KB (639 words) - 04:02, 28 June 2018
  • October 31, 2017 UXC Meeting Page
    *Please note that the IDESG Privacy Requirements apply to these interactions and the data they generate. ...Track: https://www.ftc.gov/news-events/media-resources/protectingconsumer-privacy/do-not-track Do Not Track standard work at the W3C: http://www.w3.org/2011/
    5 KB (745 words) - 04:02, 28 June 2018
  • Online Safety for Democracy Activists Use Case
    [[Category:Privacy Use Cases]]
    2 KB (258 words) - 04:02, 28 June 2018
  • OpenID Attribute 1.0
    '''Privacy''':
    458 bytes (41 words) - 04:02, 28 June 2018
  • OpenID Auth 1.1
    '''Privacy''':
    434 bytes (37 words) - 04:02, 28 June 2018
  • OpenID Authentication 2.0
    '''Privacy''':
    809 bytes (83 words) - 04:02, 28 June 2018
  • OpenID Connect 1.0
    '''Privacy''':
    701 bytes (75 words) - 21:32, 24 July 2020
  • OpenID Connect Basic 1.0
    '''Privacy''':
    447 bytes (40 words) - 04:02, 28 June 2018
  • OpenID Connect Discovery 1.0
    '''Privacy''':
    450 bytes (40 words) - 04:02, 28 June 2018
  • OpenID Connect Dynamic Registration 1.0
    '''Privacy''':
    461 bytes (40 words) - 04:02, 28 June 2018
  • OpenID Connect Implicit 1.0
    '''Privacy''':
    453 bytes (40 words) - 04:02, 28 June 2018
  • OpenID Connect Messages 1.0
    '''Privacy''':
    438 bytes (38 words) - 04:02, 28 June 2018
  • OpenID Connect Session 1.0
    '''Privacy''':
    757 bytes (88 words) - 04:02, 28 June 2018
  • OpenID OAuth 2.0 Responses
    '''Privacy''':
    471 bytes (42 words) - 04:02, 28 June 2018
  • OpenID Policy 1.0
    '''Privacy''':
    493 bytes (41 words) - 04:02, 28 June 2018
  • OpenID SRE 1.0
    '''Privacy''':
    464 bytes (39 words) - 04:02, 28 June 2018
  • Option Not to Track Use Case
    ...pseudonymous identity, match names between systems, verify attributes with privacy protection] [[Category:Privacy Use Cases]]
    868 bytes (101 words) - 04:02, 28 June 2018
  • Other Privacy Resources
    == OTHER PRIVACY RESOURCES == ...s informative, but not normative, guidance on the matters discussed in the Privacy Requirements.
    572 bytes (71 words) - 04:02, 28 June 2018
  • PACS IG
    '''Privacy''': Agencies are recommended not to use Social Security Number as the Perso
    1,008 bytes (125 words) - 04:02, 28 June 2018
  • PIV-I Certificate and CRL Profile
    '''Privacy''':
    709 bytes (80 words) - 21:24, 25 March 2021
  • PIV-I Enrollment for Educational Institutions Use Case
    '''Use Case Category''': Trust/Assurance, Authentication, Interoperability, Privacy '''Category:''' Trust/Assurance, Authentication, Interoperability, Privacy
    9 KB (1,241 words) - 04:02, 28 June 2018
  • PIV-I Enrollment for Financial Institutions Use Case
    '''Use Case Category''': Trust/Assurance, Authentication, Interoperability, Privacy ...cant wishes to apply for and obtain an electronic credential that provides privacy, strong authentication and is trusted for high assurance transactions/inter
    6 KB (830 words) - 04:02, 28 June 2018
  • PIV-I for Non-Federal Issuers
    '''Privacy''': No stipulations.
    1,023 bytes (117 words) - 23:30, 12 January 2021
  • Patient pull of information
    ...pseudonymous identity, match names between systems, verify attributes with privacy protection] ...data is made available and follow certain interoperability, security, and privacy (HIPAAHIPPA) standards Both the patient EHR and data holder application wi
    6 KB (949 words) - 18:39, 27 April 2019
  • Persona Attributes
    ...ssary to establish a trusted persona should need to be disclosed. This is privacy-enhancing, and minimizes opportunity for aggregation of information of iden
    4 KB (531 words) - 04:02, 28 June 2018
  • Phase II IDEF Registry
    * Privacy [[file:Privacy_Requirements_Update.docx]] ...d that helps to describe how a site with no user connectivity can meet any privacy or security guideline.
    2 KB (284 words) - 18:45, 7 January 2019
  • PlayaNym as Pseudonymous Identity Use Case
    ...pseudonymous identity, match names between systems, verify attributes with privacy protection] [[Category:Privacy Use Cases]]
    1 KB (127 words) - 05:22, 31 March 2021
  • Principal
    ...ciple is persisted in a [[Digital Entity]], then that data is subject to [[Privacy]] and [[Security]] requirements of the IDESG. ...tes. (Depending on the jurisdiction and the particular data protection and privacy legislation, the synonym “data subject” can also be used instead of the
    4 KB (560 words) - 04:02, 28 June 2018
  • Privacy-Preserving Accessibility Support
    '''Title''': Privacy-Preserving Accessibility Support ...preferences and to control the release of subsets of that information in a privacy-preserving way to enable online services to tailor their presentation and u
    3 KB (367 words) - 04:02, 28 June 2018
  • Privacy Enhanced by User Agent
    Privacy enhancing technology provided by an agent under the user's control. Privacy, Trust/Assurance, Interoperability
    12 KB (2,056 words) - 20:35, 27 November 2019
  • Privacy Enhancing Technologies
    Privacy enhancing technology generic use case. In some ways this is similar to the Privacy, Trust/Assurance, Interoperability
    14 KB (2,167 words) - 01:45, 15 May 2021
  • Privacy Evaluations
    ...ted in accordance with the [https://www.idecosystem.org/filedepot?fid=1090 Privacy Evaluation Methodology]. | OpenID Connect || [[Standards]] || 8 October 2015 || Privacy issues; no objection || 5 January 2016
    4 KB (409 words) - 04:02, 28 June 2018
  • Privacy References and Guides
    ...organizations understand how to evaluate their system for alignment to the privacy requirements. References should be considered informative guides only.''' New documents can be suggested for inclusion by emailing the Privacy Committee listserv.
    5 KB (571 words) - 00:54, 31 May 2020
  • Privacy Req 1
    == PRIVACY-1. DATA MINIMIZATION == ...tity (for example from signin to signout of the user.) See [[Privacy Req 2|PRIVACY-2 (PURPOSE LIMITATION)]].
    3 KB (425 words) - 04:02, 28 June 2018
  • Privacy Req 15
    == PRIVACY-15. ATTRIBUTE SEGREGATION == ...ved at https://workspace.idesg.org/kws/public/download.php/56/Supplemental-Privacy-Guidance.docx
    2 KB (283 words) - 04:02, 28 June 2018
  • Privacy Req 1 Supplemental Guidance
    ''<< Back to [[Privacy_Req_1|Privacy Requirement 1]]'' ...ntity stakeholders) when applying and evaluating IDEF Baseline Requirement PRIVACY-1.
    1 KB (131 words) - 04:02, 28 June 2018
  • Privacy Req 2
    == PRIVACY-2. PURPOSE LIMITATION == See also Requirement [[Privacy Req 1|PRIVACY-1 (DATA MINIMIZATION)]] on the application of limitations to, and
    5 KB (583 words) - 04:03, 28 June 2018
  • Privacy Req 2 Supplemental Guidance
    ''<< Back to [[Privacy_Req_2|Privacy Requirement 2]]'' ...ntity stakeholders) when applying and evaluating IDEF Baseline Requirement PRIVACY-2.
    2 KB (257 words) - 04:03, 28 June 2018
  • Privacy Req 3
    == PRIVACY-3. ATTRIBUTE MINIMIZATION == ...eleased as claims as well as detailed attributes; see also [[Privacy Req 1|PRIVACY-1
    3 KB (438 words) - 04:03, 28 June 2018
  • Privacy Req 3 Supplemental Guidance
    ''<< Back to [[Privacy_Req_3|Privacy Requirement 3]]'' ...ntity stakeholders) when applying and evaluating IDEF Baseline Requirement PRIVACY-3.
    1 KB (143 words) - 04:03, 28 June 2018
  • Privacy Req 4
    == PRIVACY-4. CREDENTIAL LIMITATION == ...ements [[Privacy Req 1|PRIVACY-1 (DATA MINIMIZATION)]] and [[Privacy Req 2|PRIVACY-2 (PURPOSE LIMITATION)]] on the application of limitations to, and scope of
    3 KB (356 words) - 04:03, 28 June 2018
  • Privacy Req 4 Supplemental Guidance
    ''<< Back to [[Privacy_Req_4|Privacy Requirement 4]]'' ...ntity stakeholders) when applying and evaluating IDEF Baseline Requirement PRIVACY-4.
    789 bytes (93 words) - 04:03, 28 June 2018
  • Privacy Req 5 Supplemental Guidance
    ''<< Back to [[Privacy_Req_5|Privacy Requirement 5]]'' ...ntity stakeholders) when applying and evaluating IDEF Baseline Requirement PRIVACY-5.
    1 KB (147 words) - 04:03, 28 June 2018
  • Privacy Requirements
    The Privacy Requirements Work Group is drafting privacy requirements to support the development of the [[Identity Ecosystem Framewo ...ns understand the guidance for Version 1 of the IDEF can be found in the [[Privacy References and Guides]] page.
    9 KB (1,100 words) - 04:03, 28 June 2018
  • Trust Federation Membership Validation
    ...int. Also any site that provides access to resources that are protected by privacy, health, age-restrictions or other regulations. ...multiple functions, or as one that is not otherwise covered, for example a Privacy Enhancing Technology Provider, Trusted Third Party or a federation server.
    21 KB (3,285 words) - 23:37, 15 January 2020
  • Trust Frameworks
    ...issues that may arise in the areas of interoperability, cross-recognition, privacy, audit, and enforceability. As called out by the National Strategy for Trus | 2014-05-14 || GTRI: GTRI discussion on FICAM and Fair Information Privacy Practices integration into GTRI model
    5 KB (731 words) - 18:01, 21 May 2019
  • Trusted Third Party
    ...s the data are bound by legal statutes or agreements to protect the user's privacy to a high level of assurance. *Real-world users wish to maintain their privacy and still have access to protected data on the internet.
    4 KB (626 words) - 21:21, 14 May 2020
  • Trustmark Evolving Design Pattern
    ...ser experience and obtains responses from the user in order to satisfy the privacy concerns of the user and the need for identity and attribute claims by the # This request for information is intercepted by the user agent, or any privacy-enhancing technology intermediary—complex step where user drop-out is lik
    24 KB (3,856 words) - 16:05, 16 December 2021
  • UXC Dictionary
    ...ice providers, and they often must calculate the tradeoffs among security, privacy, and gaining access to a service they desire." Page 12 ...ric nature of the Identity Ecosystem, which provides greater transparency, privacy protection, flexibility,and choice to the individual." Page 21
    8 KB (1,190 words) - 16:21, 27 May 2020
  • UXC Requirements and Guidelines for TFTM
    * review by Privacy committee
    2 KB (219 words) - 20:43, 8 December 2014
  • UXC liaisons
    | Privacy Committee || Jim Zok || ...
    533 bytes (59 words) - 16:14, 25 February 2016
  • UXC resources
    * [http://www.nyu.edu/projects/nissenbaum/main_bio.html Helen Nissenbaum's Privacy By Design work] === Usability Studies in Privacy, Security, Identity, etc. ===
    7 KB (944 words) - 20:05, 11 April 2018
  • UXC worklist
    ##Design Pattern and Anti-Pattern work (First two to be submitted to TFTM, Privacy and MC for information review, February 2016) # Ken Klingenstein pilot review of Privacy Lens <br>
    3 KB (417 words) - 23:15, 13 April 2016
  • UX Usability Requirements and Guidelines Working Document
    ...nhancing technology" is widely in use in industry, research suggests that "privacy protection" is more readily understood and used by real users.... ...d be presented with pathways to the identity service they desire, such as: privacy options, identity caching, etc. <br>
    16 KB (2,145 words) - 16:18, 27 May 2020
  • Un and Underserved People Use Case
    ...d to encourage comments from the community regarding technical, standards, privacy, and usability issues that appear to be relevant.</small> ...o participate in the secure and resilient, cost effective and easy to use, privacy enhancing and voluntary interoperable online Identity Ecosystem envisioned
    13 KB (1,990 words) - 21:48, 5 December 2020
  • Usable Req 3
    ...nhancing technology" is widely in use in industry, research suggests that "privacy protection" is more readily understood and used by real users.
    3 KB (411 words) - 22:50, 12 October 2018
  • Usable Req 4
    ...be presented with pathways to the identity services they desire, such as: privacy options,
    3 KB (500 words) - 22:51, 12 October 2018
  • Usable Req 7
    Please note that the [[Baseline_Functional_Requirements_v1.0#Privacy|IDESG Privacy Requirements]] apply to these interactions and the data they ...ck]]'': https://www.ftc.gov/news-events/media-resources/protectingconsumer-privacy/do-not-track
    3 KB (401 words) - 22:53, 12 October 2018

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

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