Security Interest Group - Activity in 2025
No matches.
Past meetings
Participants
-
1 participant joined.
-
Nishant Jain (W3C Invited Experts) joined.
-
GitHub
w3c/securityig
-
1 issue opened.
-
Agenda: 2026-01-06 w3c/securityig#36, by @simoneonofri.
-
-
1 issue closed.
-
Agenda: 2025-12-09 w3c/securityig#35.
-
-
4 issues received 5 new comments.
w3c/security-guidelines-cryptography
-
1 issue received 1 new comment.
-
John Preuß Mattsson review of the document w3c/security-guidelines-cryptography#15 (1 comment by @Frosne)
-
-
3 pull requests opened.
-
Changed the standards references from informative to normative w3c/security-guidelines-cryptography#18, by @Frosne.
-
Follow-up - Confidentiality links to be more robust w3c/security-guidelines-cryptography#17, by @Frosne.
-
Fix formatting error in reference list w3c/security-guidelines-cryptography#16, by @loganaden.
-
-
5 pull requests merged.
-
Follow-up - Confidentiality links to be more robust w3c/security-guidelines-cryptography#17.
-
Updates for confidentiality subsection w3c/security-guidelines-cryptography#12.
-
Correct spelling of 'recommended' w3c/security-guidelines-cryptography#13.
-
Fix formatting error in reference list w3c/security-guidelines-cryptography#16.
-
Expand on hybrid key exchanges w3c/security-guidelines-cryptography#14.
-
-
4 pull requests received 5 new comments.
-
Updates for confidentiality subsection w3c/security-guidelines-cryptography#12 (2 comments by @Frosne, @verocri)
-
Changed the standards references from informative to normative w3c/security-guidelines-cryptography#18 (1 comment by @Frosne)
-
Correct spelling of 'recommended' w3c/security-guidelines-cryptography#13 (1 comment by @simoneonofri)
-
Past meetings
Participants
-
2 participants joined.
-
Mia Therese Jamili (PayPal) joined.
-
Johann Hofmann (Google LLC) joined.
-
-
1 organization joined.
-
PayPal joined.
-
GitHub
w3c/security-guidelines-cryptography
-
2 issues opened.
-
John Preuß Mattsson review of the document w3c/security-guidelines-cryptography#15, by @emanjon.
-
Crypto Agility References w3c/security-guidelines-cryptography#8, by @seanturner.
-
-
1 issue closed.
-
7.2. Asymmetric encryption misses ECC w3c/security-guidelines-cryptography#5.
-
-
7 pull requests opened.
-
Expand on hybrid key exchanges w3c/security-guidelines-cryptography#14, by @loganaden.
-
Correct spelling of 'recommended' w3c/security-guidelines-cryptography#13, by @loganaden.
-
Updates for confidentiality subsection w3c/security-guidelines-cryptography#12, by @Frosne.
-
Updated Security Services section w3c/security-guidelines-cryptography#11, by @Frosne.
-
Fix typos and minor editorial changes w3c/security-guidelines-cryptography#10, by @iherman.
-
Prefer American English w3c/security-guidelines-cryptography#9, by @ProgramMax.
-
Fix typo -- missing space w3c/security-guidelines-cryptography#7, by @ProgramMax.
-
-
5 pull requests merged.
-
Prefer American English w3c/security-guidelines-cryptography#9.
-
Fix typo -- missing space w3c/security-guidelines-cryptography#7.
-
Fix typos and minor editorial changes w3c/security-guidelines-cryptography#10.
-
Updated Security Services section w3c/security-guidelines-cryptography#11.
-
Added draft spec link to README w3c/security-guidelines-cryptography#3.
-
-
6 pull requests received 8 new comments.
-
Fix typos and minor editorial changes w3c/security-guidelines-cryptography#10 (3 comments by @Frosne, @iherman)
-
Updates for confidentiality subsection w3c/security-guidelines-cryptography#12 (1 comment by @Frosne)
-
w3c/securityig
-
2 issues opened.
-
Agenda: 2025-12-09 w3c/securityig#35, by @simoneonofri.
-
Agenda: 2025-11-25 w3c/securityig#34, by @simoneonofri.
-
-
2 issues closed.
-
Agenda: 2025-11-25 w3c/securityig#34.
-
Agenda: 2025-11-14 (physically at TPAC) w3c/securityig#30.
-
-
1 issue received 5 new comments.
-
Agenda: 2025-11-14 (physically at TPAC) w3c/securityig#30 (5 comments by @anssiko, @simoneonofri, @TomCJones)
-
w3c/security-questionnaire
-
1 issue opened.
-
Consider replacing "meaningful user consent" with wording about user intent w3c/security-questionnaire#197, by @jyasskin.
-
-
1 pull request opened.
-
Update the design-principles#consent reference to #user-intent. w3c/security-questionnaire#196, by @jyasskin.
-
-
3 pull requests merged.
-
Update the design-principles#consent reference to #user-intent. w3c/security-questionnaire#196.
-
Embed the markdown template into the main questionnaire. w3c/security-questionnaire#191.
-
Remove the TAG from the groups responsible for this document. w3c/security-questionnaire#185.
-
-
1 pull request received 1 new comment.
-
Update the design-principles#consent reference to #user-intent. w3c/security-questionnaire#196 (1 comment by @simoneonofri)
-
w3c/threat-model-decentralized-credentials
-
1 issue opened.
-
Update links in repo to the document w3c/threat-model-decentralized-credentials#3, by @wip-abramson.
-
Past meetings
Participants
-
1 participant joined.
-
Giovanni Corti (Fondazione Bruno Kessler) joined.
-
GitHub
w3c/securityig
-
5 issues opened.
-
Agenda: 2025-10-28 w3c/securityig#31, by @simoneonofri.
-
Agenda: 2025-11-14 (physically at TPAC) w3c/securityig#30, by @simoneonofri.
-
Agenda: 2025-10-21 w3c/securityig#29, by @simoneonofri.
-
Agenda: 2025-10-14 w3c/securityig#28, by @simoneonofri.
-
5 issues closed.
-
Work Item: Cryptgraphy usage in Web Standards w3c/securityig#12.
-
Agenda: 2025-10-28 w3c/securityig#31.
-
Agenda: 2025-10-21 w3c/securityig#29.
-
Agenda: 2025-10-14 w3c/securityig#28.
-
Agenda: 2025-09-30 w3c/securityig#26.
-
-
6 issues received 13 new comments.
-
CfC: Adopt W3C Standards Vulnerability Disclosure & Handling Process and Policy as a Work Item w3c/securityig#13 (2 comments by @innotommy, @simoneonofri)
-
1 pull request opened.
-
Update agenda with security topics discussion w3c/securityig#32, by @TomCJones.
-
-
1 pull request merged.
-
Update agenda with security topics discussion w3c/securityig#32.
-
-
1 pull request received 1 new comment.
w3c/security-guidelines-cryptography
-
3 issues opened.
-
Key derivation function might benefit from talking about parameters (like, number of iterations) w3c/security-guidelines-cryptography#6, by @Frosne.
-
7.2. Asymmetric encryption misses ECC w3c/security-guidelines-cryptography#5, by @Frosne.
-
Cryptographic keys section does not distinguish asymetric private/public and symmetric keys. w3c/security-guidelines-cryptography#4, by @Frosne.
-
-
3 pull requests opened.
-
Added draft spec link to README w3c/security-guidelines-cryptography#3, by @Frosne.
-
Add .pr-preview.json configuration file w3c/security-guidelines-cryptography#2, by @verocri.
-
Add index.bs w3c/security-guidelines-cryptography#1, by @verocri.
-
-
2 pull requests merged.
-
Add index.bs w3c/security-guidelines-cryptography#1.
-
Add .pr-preview.json configuration file w3c/security-guidelines-cryptography#2.
-
w3c/security-disclosure
-
5 issues closed.
-
Legal threats can be counterproductive. Include a policy for outgoing security disclosures. w3c/security-disclosure#6.
-
Extend scope to include access service providers w3c/security-disclosure#5.
-
Cite the published version on w3.org as well w3c/security-disclosure#2.
-
Feedback from the TAG w3c/security-disclosure#4.
-
private key discloser w3c/security-disclosure#7.
-
-
5 issues received 5 new comments.
-
Legal threats can be counterproductive. Include a policy for outgoing security disclosures. w3c/security-disclosure#6 (1 comment by @simoneonofri)
-
Extend scope to include access service providers w3c/security-disclosure#5 (1 comment by @simoneonofri)
-
FIRST.ORG: Guidelines and Practices for Multi-Party Vulnerability 14 Coordination w3c/security-disclosure#1 (1 comment by @simoneonofri)
-
Past meetings
Participants
-
1 participant left.
-
Will Abramson (Legendary Requirements) left.
-
GitHub
w3c/securityig
-
1 issue opened.
-
4 issues received 7 new comments.
-
Security and Privacy Challenges in the Future Forms, Identity Binding, and Authentication Mechanisms of AI Agents w3c/securityig#27 (1 comment by @simoneonofri)
Past meetings
Participants
-
2 participants joined.
-
Michele Orru (W3C Invited Experts) joined.
-
Zahra Ebadi Ansaroudi (Fondazione Bruno Kessler) joined.
-
GitHub
w3c/securityig
-
3 issues opened.
-
Agenda: 2025-09-30 w3c/securityig#26, by @simoneonofri.
-
Agenda: 2025-08-19 w3c/securityig#25, by @simoneonofri.
-
IdP in the middle attack w3c/securityig#24, by @TomCJones.
-
-
2 issues closed.
-
Agenda: 2025-08-19 w3c/securityig#25.
-
Agenda: 2025-08-05 w3c/securityig#23.
-
-
4 issues received 9 new comments.
w3c/security-questionnaire
-
1 issue opened.
-
Pullrequest please w3c/security-questionnaire#195, by @lynn1980gooze-cpu.
-
-
1 issue closed.
-
Pullrequest please w3c/security-questionnaire#195.
-
Past meetings
-
1 meeting.
Participants
-
1 chair appointed.
-
Tommaso Innocenti became a chair.
-
-
1 chair stepped down.
-
Tommaso Innocenti stepped down as a chair.
-
-
2 participants joined.
-
Alberto Fernandez-de-Retana (W3C Invited Experts) joined.
-
Tommaso Innocenti (Amazon) joined.
-
-
1 participant left.
-
Tommaso Innocenti (Amazon) left.
-
-
1 organization joined.
-
Amazon joined.
-
GitHub
w3c/securityig
-
1 issue opened.
-
Agenda: 2025-08-05 w3c/securityig#23, by @simoneonofri.
-
-
1 issue closed.
-
Agenda: 2025-07-08 w3c/securityig#22.
-
-
3 issues received 4 new comments.
Past meetings
GitHub
w3c/securityig
-
4 issues opened.
-
Agenda: 2025-07-08 w3c/securityig#22, by @simoneonofri.
-
Agenda: 2025-06-24 w3c/securityig#21, by @simoneonofri.
-
Work Item: AI in the Browser Threat Model w3c/securityig#20, by @simoneonofri.
-
Agenda: 2025-06-10 w3c/securityig#19, by @simoneonofri.
-
-
2 issues closed.
-
Agenda: 2025-06-24 w3c/securityig#21.
-
Agenda: 2025-06-10 w3c/securityig#19.
-
-
6 issues received 9 new comments.
w3c/security-questionnaire
-
3 issues opened.
-
add question about testability w3c/security-questionnaire#194, by @npdoty.
-
possibly add question on whether different s&p decisions are testable w3c/security-questionnaire#193, by @pes10k.
-
question / guidance on background requests w3c/security-questionnaire#192, by @npdoty.
-
-
1 issue closed.
-
There are three active versions of this questionnaire w3c/security-questionnaire#175.
-
-
1 issue received 1 new comment.
-
There are three active versions of this questionnaire w3c/security-questionnaire#175 (1 comment by @ylafon)
-
w3c/threat-model-web
-
2 pull requests opened.
-
Add web fonts (again) w3c/threat-model-web#2, by @svgeesus.
-
Add web fonts as a major category of content w3c/threat-model-web#1, by @svgeesus.
-
-
2 pull requests merged.
-
Add web fonts (again) w3c/threat-model-web#2.
-
Add web fonts as a major category of content w3c/threat-model-web#1.
-
Past meetings
Participants
-
1 participant joined.
-
Yakup Efe Tuncay (Rakuten Group, Inc.) joined.
-
-
1 organization joined.
-
Rakuten Group, Inc. joined.
-
GitHub
w3c/securityig
-
4 issues opened.
-
Work Item: Threat Model for the Web (TMW) w3c/securityig#18, by @simoneonofri.
-
Work Item: Threat Modeling Guide (TMG) w3c/securityig#17, by @simoneonofri.
-
Work Item: Digital Credentials Threat Model w3c/securityig#16, by @simoneonofri.
-
Agenda 2025-05-13 w3c/securityig#14, by @simoneonofri.
-
-
2 issues closed.
-
Agenda 2025-05-13 w3c/securityig#14.
-
-
5 issues received 9 new comments.
-
CfC: Adopt W3C Standards Vulnerability Disclosure & Handling Process and Policy as a Work Item w3c/securityig#13 (3 comments by @jyasskin, @simoneonofri)
-
Work Item: Digital Credentials Threat Model w3c/securityig#16 (2 comments by @msporny, @simoneonofri)
-
CfC: Acknowledging on reviewing the protocols to be added into the Digital Credentials API Registry w3c/securityig#11 (1 comment by @simoneonofri)
-
-
1 pull request opened.
-
Fix "Intrest" in meetings/README.md w3c/securityig#15, by @jyasskin.
-
-
1 pull request merged.
-
Fix "Intrest" in meetings/README.md w3c/securityig#15.
-
w3c/threat-model-decentralized-credentials
-
2 pull requests opened.
-
Update index.bs w3c/threat-model-decentralized-credentials#2, by @simoneonofri.
-
Update index.bs w3c/threat-model-decentralized-credentials#1, by @simoneonofri.
-
-
2 pull requests merged.
-
Update index.bs w3c/threat-model-decentralized-credentials#2.
-
Update index.bs w3c/threat-model-decentralized-credentials#1.
-
w3c/security-questionnaire
-
1 pull request received 2 new comments.
-
Embed the markdown template into the main questionnaire. w3c/security-questionnaire#191 (2 comments by @jyasskin, @pes10k)
-
TR publications
-
1 document published.
Past meetings
Participants
-
4 participants joined.
-
John Wilander (Apple Inc.) joined.
-
ㅤ Pascoe (Apple Inc.) joined.
-
Matthew Finkel (Apple Inc.) joined.
-
Theresa O'Connor (Apple Inc.) joined.
-
-
1 organization joined.
-
Apple Inc. joined.
-
GitHub
w3c/securityig
-
5 issues opened.
-
Work Item: Cryptgraphy usage in Web Standards w3c/securityig#12, by @simoneonofri.
-
Agenda: 2025-04-29 w3c/securityig#10, by @simoneonofri.
-
Agenda 2025-04-15 w3c/securityig#9, by @simoneonofri.
-
2 issues closed.
-
Agenda: 2025-04-29 w3c/securityig#10.
-
Agenda 2025-04-15 w3c/securityig#9.
-
-
2 issues received 5 new comments.
w3c/security-questionnaire
-
1 issue closed.
-
"Explainer" in Markdown template is a dead link w3c/security-questionnaire#190.
-
-
1 issue received 1 new comment.
-
There are three active versions of this questionnaire w3c/security-questionnaire#175 (1 comment by @jyasskin)
-
-
1 pull request opened.
-
Embed the markdown template into the main questionnaire. w3c/security-questionnaire#191, by @jyasskin.
-
-
1 pull request merged.
-
Update links now that this repo has moved from the w3ctag org to the w3c org. w3c/security-questionnaire#184.
-
-
3 pull requests received 9 new comments.
-
Update links now that this repo has moved from the w3ctag org to the w3c org. w3c/security-questionnaire#184 (5 comments by @jyasskin, @pes10k, @simoneonofri)
-
Remove the TAG from the groups responsible for this document. w3c/security-questionnaire#185 (3 comments by @jyasskin, @pes10k, @tantek)
-
Embed the markdown template into the main questionnaire. w3c/security-questionnaire#191 (1 comment by @jyasskin)
-
Participants
-
1 participant joined.
-
Kester Quist-Aphetsi (CRITAC) joined.
-
-
1 organization joined.
-
CRITAC joined.
-
GitHub
w3c/securityig
-
1 issue opened.
-
Agenda 2025-04-01 w3c/securityig#8, by @simoneonofri.
-
-
1 issue closed.
-
Agenda 2025-04-01 w3c/securityig#8.
-
-
1 issue received 1 new comment.
w3c/security-questionnaire
-
1 issue opened.
-
"Explainer" in Markdown template is a dead link w3c/security-questionnaire#190, by @emlun.
-
TR publications
-
1 document published.
Past meetings
-
1 meeting.
Participants
-
2 participants joined.
-
Will Abramson (Legendary Requirements) joined.
-
Andrea D'Intino (Dyne.org) joined.
-
-
1 organization joined.
-
Digital Contract Design joined.
-
GitHub
w3c/securityig
-
1 issue opened.
-
Agenda for SING meeting February 18 2025 w3c/securityig#7, by @innotommy.
-
-
1 issue closed.
-
Agenda for SING meeting February 18 2025 w3c/securityig#7.
-
-
1 issue received 2 new comments.
-
1 pull request merged.
-
Ask for Sec/Priv questionnaire editors in 2025-02-04_agenda.md w3c/securityig#6.
-
-
1 pull request received 1 new comment.
-
Ask for Sec/Priv questionnaire editors in 2025-02-04_agenda.md w3c/securityig#6 (1 comment by @simoneonofri)
-
w3c/security-questionnaire
-
1 pull request opened.
-
Add Simone as an editor from SING w3c/security-questionnaire#189, by @simoneonofri.
-
-
1 pull request merged.
-
Add Simone as an editor from SING w3c/security-questionnaire#189.
-
-
1 pull request received 1 new comment.
TR publications
-
2 documents published.
-
Self-Review Questionnaire: Security and Privacy published twice as a Note. History of Self-Review Questionnaire: Security and Privacy
-
GitHub
w3c/security-questionnaire
-
1 issue opened.
-
Improving: Does this specification have both "Security Considerations" and "Privacy Considerations" sections? w3c/security-questionnaire#181, by @simoneonofri.
-
-
2 issues closed.
-
Example 10 is not supported by referenced article w3c/security-questionnaire#174.
-
Questionnaire markdown file is not actually convenient w3c/security-questionnaire#172.
-
-
2 issues received 3 new comments.
-
Improving: Does this specification have both "Security Considerations" and "Privacy Considerations" sections? w3c/security-questionnaire#181 (2 comments by @jyasskin, @simoneonofri)
-
There are three active versions of this questionnaire w3c/security-questionnaire#175 (1 comment by @jyasskin)
-
-
7 pull requests opened.
-
Minor tweaks w3c/security-questionnaire#188, by @plehegar.
-
Update w3c.json with Security w3c/security-questionnaire#186, by @simoneonofri.
-
Remove the TAG from the groups responsible for this document. w3c/security-questionnaire#185, by @jyasskin.
-
Update links now that this repo has moved from the w3ctag org to the w3c org. w3c/security-questionnaire#184, by @jyasskin.
-
Update references from PING to the Privacy WG. w3c/security-questionnaire#183, by @jyasskin.
-
Update the boilerplate to try to pass Pubrules. w3c/security-questionnaire#182, by @jyasskin.
-
Add the Security Interest Group to the list of groups jointly responsible for this document. w3c/security-questionnaire#180, by @hober.
-
-
11 pull requests merged.
-
Minor tweaks w3c/security-questionnaire#188.
-
Update w3c.json with Security w3c/security-questionnaire#186.
-
Update references from PING to the Privacy WG. w3c/security-questionnaire#183.
-
Link to Lukasz' specific analysis on visited links. w3c/security-questionnaire#178.
-
Copy-edit the AT section. w3c/security-questionnaire#168.
-
Fix uses of "effect" that should "affect" things. w3c/security-questionnaire#167.
-
Update the boilerplate to try to pass Pubrules. w3c/security-questionnaire#182.
-
Add the Security Interest Group to the list of groups jointly responsible for this document. w3c/security-questionnaire#180.
-
Add `class=question` to a header so it's included in questionnaire.markdown. w3c/security-questionnaire#176.
-
Don't describe this document as having conformance requirements, using the RFC2119 keywords, or having algorithms. w3c/security-questionnaire#170.
-
Make questionnaire.markdown convenient for copying into an explainer. w3c/security-questionnaire#177.
-
-
3 pull requests received 4 new comments.
-
Add the Security Interest Group to the list of groups jointly responsible for this document. w3c/security-questionnaire#180 (2 comments by @hober, @jyasskin)
-
Update references from PING to the Privacy WG. w3c/security-questionnaire#183 (1 comment by @npdoty)
-
Update the boilerplate to try to pass Pubrules. w3c/security-questionnaire#182 (1 comment by @jyasskin)
-
w3c/securityig
-
1 issue closed.
-
Define a good time for the group call w3c/securityig#4.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Ask for Sec/Priv questionnaire editors in 2025-02-04_agenda.md w3c/securityig#6, by @jyasskin.
-
Create 2025-02-04_agenda.md w3c/securityig#5, by @simoneonofri.
-
-
1 pull request merged.
-
Create 2025-02-04_agenda.md w3c/securityig#5.
-
-
1 pull request received 1 new comment.
-
Ask for Sec/Priv questionnaire editors in 2025-02-04_agenda.md w3c/securityig#6 (1 comment by @jyasskin)
-