Security Interest Group - Activity
No matches.
Past meetings
GitHub
w3c/securityig
-
1 issue closed.
-
Agenda: 2026-11-10 w3c/securityig#56.
-
-
1 issue received 4 new comments.
w3c/threat-modeling-guide
-
5 pull requests opened.
-
Add note on trust boundaries w3c/threat-modeling-guide#40, by @simoneonofri.
-
Introduction: restore canonical Four Question Framework wording w3c/threat-modeling-guide#39, by @simoneonofri.
-
Update “Where to Publish the Threat Model” w3c/threat-modeling-guide#38, by @simoneonofri.
-
Expand practical Security Considerations writing guidance w3c/threat-modeling-guide#37, by @simoneonofri.
-
Add practical ERTA decision flow to Consider Responses w3c/threat-modeling-guide#36, by @simoneonofri.
-
Past meetings
Participants
-
4 participants joined.
-
Raju Ghimire (Global Cybersecurity Community Forum) joined.
-
Raju Ghimire (Global Cybersecurity Community Forum) joined.
-
Ari Chivukula (Google LLC) joined.
-
Kumar Pudashine (Global Cybersecurity Community Forum) joined.
-
-
1 participant left.
-
Raju Ghimire (Global Cybersecurity Community Forum) left.
-
-
1 organization joined.
-
Global Cybersecurity Community Forum joined.
-
GitHub
w3c/securityig
-
1 issue opened.
-
Agenda: 2026-11-10 w3c/securityig#56, by @simoneonofri.
-
-
1 issue closed.
-
Agenda: TPAC 2026 @ Dublin (F2F) w3c/securityig#49.
-
-
1 issue received 1 new comment.
TR publications
-
4 documents published.
-
Threat Model for the Web published twice as a Draft Note. History of Threat Model for the Web
-
Threat Model for Decentralized Credentials published twice as a Draft Note. History of Threat Model for Decentralized Credentials
-
Past meetings
GitHub
w3c/securityig
-
1 issue opened.
-
Agenda: 2026-09-29 w3c/securityig#55, by @simoneonofri.
-
-
2 issues closed.
-
Agenda: 2026-09-29 w3c/securityig#55.
-
Agenda: 2026-09-15 w3c/securityig#54.
-
-
2 issues received 11 new comments.
w3c/threat-model-web
-
4 issues opened.
-
Missing process w3c/threat-model-web#25, by @bkardell.
-
The System Model w3c/threat-model-web#24, by @bkardell.
-
Are we dating this by saying "modern" w3c/threat-model-web#23, by @bkardell.
-
Application Capability Threat Model w3c/threat-model-web#22, by @csarven.
-
-
1 issue closed.
-
Application Capability Threat Model w3c/threat-model-web#22.
-
-
4 issues received 8 new comments.
-
1 pull request opened.
-
Clarify references to the threat models w3c/threat-model-web#26, by @simoneonofri.
-
-
2 pull requests merged.
-
Replace the High-Level Web Threat Model with the Generic Web API L0 w3c/threat-model-web#21.
-
Add identifiers and mark concepts w3c/threat-model-web#20.
-
-
1 pull request received 2 new comments.
-
Add identifiers and mark concepts w3c/threat-model-web#20 (2 comments by @BDADAD-stack, @elf-pavlik)
-
w3c/threat-modeling-guide
-
1 pull request opened.
-
Clarify the definition of threat and its distinction from threat source w3c/threat-modeling-guide#35, by @simoneonofri.
-
-
1 pull request received 1 new comment.
-
Clarify the definition of threat and its distinction from threat source w3c/threat-modeling-guide#35 (1 comment by @jandrieu)
-
w3c/threat-model-decentralized-credentials
-
2 pull requests opened.
-
Fix default code owners w3c/threat-model-decentralized-credentials#8, by @simoneonofri.
-
Trace harm pathways to their sources and refine workshop-derived scenarios w3c/threat-model-decentralized-credentials#7, by @simoneonofri.
-
-
2 pull requests merged.
-
Trace harm pathways to their sources and refine workshop-derived scenarios w3c/threat-model-decentralized-credentials#7.
-
Fix default code owners w3c/threat-model-decentralized-credentials#8.
-
-
1 pull request received 3 new comments.
-
Trace harm pathways to their sources and refine workshop-derived scenarios w3c/threat-model-decentralized-credentials#7 (3 comments by @Sh-Amir, @simoneonofri)
-