- Wg-pemc - mailman.kantarainitiative.org

AI user agent wallets
by Tom Jones 24 Jul '24

24 Jul '24

At the request of today's meeting I create this addendum and would like feedback from the team on it prior to use. ..tom Effect of AI on User Agent Wallets Most user agents, like browsers and wallets, are already offering users assistance is setting preferences and saving passwords or pass keys. As AIs grow in capabilities on the user mobile devices, they will be more involved in user convenience, privacy and safety. This section focuses on the means to ensure that privacy enhancing choices are made for the benefit of the user. Both the existing practice with the Driver’s license card as well as the early example of mobile verification apps enable the verifier to acquire more of the user’s data than is needed for the purposes of the transaction. In order for the user, or the user’s agent to make informed decisions about the data needed the purpose and the verifiable identifier of the organization requesting the data must be supplied. This will allow a real-time evaluation of the request against the typical request for such a transaction beyond what the user would normally understand. Similarly, dark patterns from verifiers could be detected and the user warned. As new dark patterns are discovered in attacks against user privacy and security, these can be presented to any AI agent to improve the user’s experience. Here we focus on a request made to an unknown user by the verifier as well as the issuer since they also verify the user before issuing any credential to them. The Verifier may make any number of different requests in their query to the user’s agent that will help the agent make good decision for the user. Some of those requests will be to understand what wallet is used and the level of protection provided by the wallet, including proof of presence and proof of continued liveness of the certificate holder or the holder’s delegated representative. In these circumstances the agent is not permitted to act for the holder but must honor the request of the verifier. Where the agent does act on behalf of the holder, it is important for the wallet or other agent code to be identified to the verifier. Any agent instance identification can itself be personally identifiable information about the user and must be treated as such by the verifier. The information on Purpose and the Identity of the Verifier is critical to the user or the user’s agent when acting on their behalf. It is to be expected that strong trust ecosystems for these as well as other data supplied by the verification are in place. The adoption of AI agents, wallets and other mobile applications depends on such a trust relationship. One other use case where an AI user agent could help is where the user wishes to select a credential to provide to the verifier before the verifier sends any information to the user. This type of transaction is high risk as the user can only rely on the physical context and has no other control over who actually acquires the presented credentials. The AI agent can try to understand the context by any means available and help to guide the user into a safe choice.

1 0

Next meeting will be July 10
by John Wunderlich 25 Jun '24

25 Jun '24

Apologies for the delay, but vacation, travel, and backlog have caught up with me. The next PEMC meeting will be on July 10, to review the soon to be updated report, incorporating our work to date. For my Americal friends, please enjoy the 4th next week. Have a better than expected day, John Wunderlich LinkedIn: https://www.linkedin.com/in/privacycdn/ Twitter: https://twitter.com/PrivacyCDN -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

1 0

FW: [privacyframework] Concept Paper Release and More Updates for the Privacy Framework 1.1 + Data Governance and Management Profile Workshop!
by Salvatore D'Agostino 18 Jun '24

18 Jun '24

From: privacyframework <privacyframework(a)list.nist.gov> Sent: Tuesday, June 18, 2024 12:28 PM To: privacyframework <privacyframework(a)list.nist.gov> Subject: [privacyframework] Concept Paper Release and More Updates for the Privacy Framework 1.1 + Data Governance and Management Profile Workshop! Dear Colleagues,    We have released concept papers for the NIST Privacy Framework (PF) Version 1.1 update as well as the Data Governance and Management (DGM) Profile. These concept papers will support discussion sessions at next week’s hybrid workshop. We encourage you to familiarize yourself with the material prior to participating in the workshop. If you would like to provide informal feedback on this material in addition to or in lieu of participating in the workshop, please send it to privacyframework(a)nist.gov<mailto:privacyframework@nist.gov> by July 31, 2024. We have also extended the deadline for in-person registration only to 11:59 PM EDT on Thursday, June 20. Please be aware that breakout sessions are filling up quickly for in-person participants, so please register as soon as possible, if you have not already. Registration is free and required for this event. Event registration, agenda, speakers, and other workshop information is available here<https://www.nist.gov/news-events/events/2024/06/ready-set-update-privacy-fr…>. If you have any questions, please email us at privacyframework(a)nist.gov<mailto:privacyframework@nist.gov>. We look forward to seeing you next week! Best, NIST Privacy Framework Team -- To unsubscribe, email privacyframework+unsubscribe(a)list.nist.gov<mailto:privacyframework+unsubscribe@list.nist.gov> Visit this group at https://list.nist.gov/privacyframework To unsubscribe from this group and stop receiving emails from it, send an email to privacyframework+unsubscribe(a)list.nist.gov<mailto:privacyframework+unsubscribe@list.nist.gov>.

1 0

“Who Lacks ID in America Today?” – Papers, Please!
by John Wunderlich 09 Jun '24

09 Jun '24

FYI: https://papersplease.org/wp/2024/06/07/who-lacks-id-in-america-today/ Have a better than expected day, John Wunderlich LinkedIn: https://www.linkedin.com/in/privacycdn/ Twitter: https://twitter.com/PrivacyCDN -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

1 0

Reminder: No PEMC Call tomorrow
by John Wunderlich 04 Jun '24

04 Jun '24

Conference season Have a better than expected day, John Wunderlich LinkedIn: https://www.linkedin.com/in/privacycdn/ Twitter: https://twitter.com/PrivacyCDN -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

1 0

Update
by John Wunderlich 21 May '24

21 May '24

Hi; I’d like to propose a way to accelerate the development of requirements so that we can get to the finish line and get to a V1 version quicker. We have almost completed section 1 and have a model of what we are working towards. That being said, a number of conferences are coming up that will mean cancelling some meetings. To avoid losing momentum, I propose sending out a survey asking each of you to volunteer to contribute to one or more sections (i.e. Requirements for Collection Limitation). We can discuss this at next week’s call, and I will then send out the survey: If you accept, your commitment will be to: 1. Read the current candidate requirements in the section a. Comment on the statement, description, and applicability (see below) 2. Determine from your perspective if there are requirements that should be added to the section, and if so, then add the statement or statements that you believe are missing. If you think the current list of requirements for a section is sufficient for a V1 of the standard, that’s valuable feedback as well. 3. Provide me with your feedback so that I can add it to the draft document. I trust that if the members of the workgroup are amendable to this, we can get to a point were we will have a good sense of the content of the requiements and can set up some dedicated working sessions to finalize the sections. If you choose to respond, the key elements of the requirements are: Requirement Statement: A one or two page statement of the requirement Requirement Description: An explanation of the statement, ideally in a form that allows an organization to demonstrate that they have met the requirement Applicability: To whom does the statement apply. At least one must be chosen: Verifier, Issuer, Provider Link to the draft document: https://docs.google.com/document/d/1mACfcV4BGHClqaGXxfKCBRkgeO_AjvKv_lhPL8f… Have a better than expected day, John Wunderlich LinkedIn: https://www.linkedin.com/in/privacycdn/ Twitter: https://twitter.com/PrivacyCDN -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

3 2

Facial recognition and “identity verification” – Papers, Please!
by John Wunderlich 08 May '24

08 May '24

https://papersplease.org/wp/2024/05/06/facial-recognition-and-identity-veri… Have a better than expected day, John Wunderlich LinkedIn: https://www.linkedin.com/in/privacycdn/ Twitter: https://twitter.com/PrivacyCDN -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

2 1

Facial recognition and “identity verification” – Papers, Please!
by John Wunderlich 08 May '24

08 May '24

https://papersplease.org/wp/2024/05/06/facial-recognition-and-identity-veri… Have a better than expected day, John Wunderlich LinkedIn: https://www.linkedin.com/in/privacycdn/ Twitter: https://twitter.com/PrivacyCDN -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

1 0

The Breach of a Face Recognition Firm Reveals a Hidden Danger of Biometrics | WIRED
by John Wunderlich 06 May '24

06 May '24

FYI: https://www.wired.com/story/outabox-facial-recognition-breach/ Have a better than expected day, John Wunderlich LinkedIn: https://www.linkedin.com/in/privacycdn/ Twitter: https://twitter.com/PrivacyCDN -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

1 0

Cancelling today’s call
by John Wunderlich 01 May '24

01 May '24

Apologies for the late cancellation. Will catch up next week. Have a better than expected day, John Wunderlich LinkedIn: https://www.linkedin.com/in/privacycdn/ Twitter: https://twitter.com/PrivacyCDN -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

1 0