- WG-RIUP - mailman.kantarainitiative.org

Fwd: 2024.02.16
by Noreen Whysel 18 Feb '24

18 Feb '24

3 2

formated DII doc
by Tom Jones 16 Feb '24

16 Feb '24

I could not get the level two headers to work as advertised If anyone knows how to make the Kantara template work, please help. ..tom

1 0

Validating Factual Personal Information | February 2024 | Communications of the ACM
by Noreen Whysel 12 Feb '24

12 Feb '24

Vint Cerf seems to be hinting toward the process we are working on in PEMC, MAAS and RIUP, only he doesn’t mention “mobile” or “wallet”. It seems like what he is describing for the most part already exists. But duplicates the problem of storing data in a browser or at the verifier. He does mention a registry several times. Vint sits on one of my boards and I can see if he’s interested in joining a call sometime. https://m-cacm.acm.org/magazines/2024/2/279540-validating-factual-personal-… Noreen

1 0

the current working document
by Tom Jones 06 Feb '24

06 Feb '24

https://docs.google.com/document/d/1-amM1fVtVKEILrXFbLBnVZ9S_BfpZW3s/edit?u…

1 0

RIUP WG meets tomorrow at 1 PM ET, February 6, 2024
by jim kragh 06 Feb '24

06 Feb '24

*RIUP's 1st/3rd Tuesday Meeting Link:* https://us06web.zoom.us/j/87499194761?pwd=cmhDTHBXV2VTbFBMZzllMlZVbnFoZz09 Meeting ID: 874 9919 4761 *Passcode: 837815* Dial by your location +1 346 248 7799 US (Houston) +1 646 558 8656 US (New York) +1 669 900 9128 US (San Jose) +1 253 215 8782 US (Tacoma) +1 301 715 8592 US (Washington DC) +1 312 626 6799 US (Chicago) Meeting ID: 874 9919 4761 Passcode: 837815 Good evening! Below is a use case outline that RIUP WG members cultivated 2+ months ago that we can use as a starting point for our work group meeting tomorrow. Sample Use Cases include the farm workers below, indian reservations and corrections for starters Owned by Noreen Whysel <https://kantara.atlassian.net/wiki/people/5d5f436f17bc890d28ef6291?ref=conf…> Last updated: Nov 21, 2023 <https://kantara.atlassian.net/wiki/pages/diffpagesbyversion.action?pageId=2…> 1 min read *Farm Worker Use Case* - Tend to move as family - Tend to be more than one worker per family - Only one phone per family - Phone can be lost or lent to someone else - Organization providing services: - United Farmworkers - Cirrus (spelling) - Low assurance since it is used for more than one person. - Credentials themselves could have high assurance How it works - Assign a DID - User gets the wallet and user attaches the credentials they want to it - High quality credentials associated with the DID - Enables lightweight identity structure - Can’t do heavy weight without enrollment system *Successful Use Cases*: - Louisiana allows people to place in a digital wallet for $6 - Red Cross and Farm Workers' Union have “Circle of Trust/Identity” that allows individuals within one's social group to attest to a person’s identity - Ukraine: online bank accounts are attached to mobile devices used to verify identity *Other Possible Use Cases:* Services in other countries (Simone) - Going on foreign travel soon - Interested to see how 3rd world countries handle ID for various purposes. United Way (TomJ) - Concerned about deduplication to avoid fraud. Deduplication is contracted out to another entity. 2 methods: avoid killing patients, avoid fraud. Carmen at ONC working on patient matching. *Issues*: - Bev: Classification needs to be dynamic, multidimensional to address multitude of complex situations - Tom: Identity and identifier (association with the identity) needs to be separate - Bev: Self-asserted identity

1 1

Fwd: W3C Workshop Report: Secure the Web Forward
by Tom Jones 01 Feb '24

01 Feb '24

an effort is underway to secure the web https://www.w3.org/2023/03/secure-the-web-forward/report.html their first priorities are "start by documenting threat models on the web and* formulating end-user stories related to security to inform standardization groups*, developers, and policy makers." I would like to add this effort as one of the targets of the RIUP use cases that are now under development in RIUP ..tom ---------- Forwarded message --------- From: Ian Jacobs <ij(a)w3.org> Date: Thu, Feb 1, 2024 at 11:24 AM Subject: Fwd: W3C Workshop Report: Secure the Web Forward To: <public-payments-wg(a)w3.org> Dear Web Payments WG, For those interested in security, W3C published today a report from the September 2023 Workshop "Secure the Web Forward”: https://www.w3.org/2023/03/secure-the-web-forward/report.html Ian Begin forwarded message: *From: *xueyuan <xueyuan(a)w3.org> *Subject: **W3C Workshop Report: Secure the Web Forward* *Date: *February 1, 2024 at 12:59:05 AM CST *To: *chairs(a)w3.org *Resent-From: *chairs(a)w3.org Dear Chairs, The report from the W3C Secure the Web Forward Workshop [1], held online in September 2023 in coordination with OpenSSF, OWASP and OpenJS, is now available: https://www.w3.org/2023/03/secure-the-web-forward/report.html This report contains a brief summary, collects highlights from the live sessions, links to the presentation videos, and details next steps. The workshop was organized to review the state of technologies (existing, in development, or proposed), guidelines, tools, and documentation available to developers to secure applications deployed on the web, and coordinate relevant activities. About 30 people attended the live sessions to discuss the 9 selected position papers along 3 different themes: supply chain security (including Software Bills of Materials, also known as SBOMs), JavaScript security, and developer awareness. Participants acknowledged the growing complexity of web applications and of security related web technologies (e.g., CORS, Content Security Policy), which together makes it challenging for developers to secure applications. The main outcomes are that: - The use of SBOMs, which some regulations may require, could help developers keep track of security vulnerabilities. - A verification mechanism, such as the Source Code Transparency proposal, would allow browsers to validate that the application resources received match the resources advertised by the application developer in a web bundle or an SBOM and possibly analyzed by security researchers. - In parallel, JavaScript execution could be split in Compartments to isolate third party code and keep their power under control. Making this foolproof with the design of the DOM API remains a challenge. - Additionally, same origin realms can be manipulated by an attacker against the web application itself when they are not properly handled. Web applications should have the ability to control, at load time, how the potentially untrusted code they contain can create or access same origin realms. - Cookies are another source of security vulnerabilities. The deprecation of third party cookies creates a unique opportunity to revise the defaults of the cookies model for the web for increased security. - Regardless of technical solutions, a documentation effort is warranted: tutorials, how-tos, references, guides and best practices, targeted at developers as well as policy makers. On top of progressing technical topics mentioned above, one of the suggested next steps is to initiate an activity, possibly hosted within a W3C Community Group, set to take a holistic approach to security and coordinate collaborations with other organizations (OpenSSF, OWASP, OpenJS, Open Web Docs, MDN, IETF, etc.). This activity could start by documenting threat models on the web and formulating end-user stories related to security to inform standardization groups, developers, and policy makers. Progress on this proposal is tracked in a GitHub issue [2]. Interested parties can contact Francois Daoust <fd(a)w3.org>. W3C thanks those who helped with the organization and execution of the workshop, including members of the Program Committee, speakers, the MDN team, the WebDX Community Group and workshop participants. For Philippe le Hégaret, Strategy Lead; Xueyuan Jia, W3C Marketing & Communications [1] https://www.w3.org/2023/03/secure-the-web-forward/ [2] https://github.com/w3c/secure-the-web-forward-workshop/issues/42 -- Ian Jacobs <ij(a)w3.org> https://www.w3.org/People/Jacobs/ Tel: +1 917 450 8783

2 1

For anyone interested in biometric privacy issues
by Tom Jones 30 Jan '24

30 Jan '24

https://www.nextgov.com/emerging-tech/2024/01/tsa-uses-minimum-data-fine-tu… thx ..Tom (mobile)

1 0

Article
by Salvatore D'Agostino 19 Jan '24

19 Jan '24

https://www.nytimes.com/2024/01/17/nyregion/migrants-shelter-snow-nyc.html?… Free read I think Get Outlook for iOS<https://aka.ms/o0ukef>

5 6

Fwd: 2024 Webinars! We've Got A Great Lineup!
by Noreen Whysel 18 Jan '24

18 Jan '24

1 0

My need for IDs
by Salvatore D'Agostino 18 Jan '24

18 Jan '24

https://www.nytimes.com/2024/01/17/nyregion/migrants-shelter-snow-nyc.html?… I don't think this email address post to the list Can you please share Best Sal Get Outlook for iOS<https://aka.ms/o0ukef>

1 0