[w3ctag/design-reviews] [ig/security] Security Interest Group Charter (Issue #1289)

w3cbot created an issue (w3ctag/design-reviews#1289)

This issue was created because the 'horizontal review requested' label was added to
§ https://github.com/w3c/strategy/issues/568

This review is requested prior to the [Advisory Committee Review](https://www.w3.org/guide/process/charter.html#ac-review).

New charter proposal, reviewers please take note.

# Charter Review

[Charter](https://w3c.github.io/charter-drafts/2026/ig-security.html)

[Diff from the charter template](https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fw3c.github.io%2Fcharter-drafts%2Fcharter-template.html&doc2=https%3A%2F%2Fw3c.github.io%2Fcharter-drafts%2F2026%2Fig-security.html)

Expected end of charter refinement phase: unknown

[Diff from the previous charter](https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2F2024%2F11%2Fsecurity-ig-charter.html&doc2=https%3A%2F%2Fw3c.github.io%2Fcharter-drafts%2F2026%2Fig-security.html)

[Chair dashboard](https://www.w3.org/PM/Groups/chairboard.html?gid=ig/security)

What kind of charter is this?

- [x] Existing IG recharter

Horizontal Reviews: apply the GitHub label "Horizontal review requested" to request reviews for accessibility (a11y), internationalization (i18n), privacy, security, and TAG. **Also add a "card" for this issue to the [Strategy Funnel](https://github.com/orgs/w3c/projects/97/views/2).**

## Substantive changes

- The mission, scope, and [Success Criteria](https://w3c.github.io/charter-drafts/2026/ig-security.html#success-criteria) are retained from the previous charter.
- The [Deliverables](https://w3c.github.io/charter-drafts/2026/ig-security.html#deliverables) now link and describe the current W3C drafts for the [Threat Model for the Web](https://www.w3.org/TR/threat-model-web/) and the [Threat Modeling Guide](https://www.w3.org/TR/threat-modeling-guide/).
- [Coordination](https://w3c.github.io/charter-drafts/2026/ig-security.html#coordination) replaces PING with the [Privacy Working Group](https://www.w3.org/groups/wg/privacy/) and updates the relevant collaboration language.
- Administrative and process language has been aligned with the current charter template.

## Communities suggested for outreach

- [Security Interest Group](https://www.w3.org/groups/ig/security/)
- [Technical Architecture Group](https://www.w3.org/groups/other/tag/)
- [Privacy Working Group](https://www.w3.org/groups/wg/privacy/)
- [Web Application Security Working Group](https://www.w3.org/groups/wg/webappsec/)
- [Accessible Platform Architectures Working Group](https://www.w3.org/groups/wg/apa/)
- [Internationalization Working Group](https://www.w3.org/groups/wg/i18n-core/)
- [Threat Modeling Community Group](https://www.w3.org/groups/cg/tmcg/)
- [Security Web Application Guidelines Community Group](https://www.w3.org/groups/cg/swag/)

## Known or potential areas of concern

Where would charter proponents like to see issues raised?

Please raise charter-refinement comments in this Strategy Funnel issue. Concrete document changes may also be proposed in the [w3c/charter-drafts repository](https://github.com/w3c/charter-drafts), while security-specific technical discussion may use [public-security@w3.org](mailto:public-security@w3.org).

## Anything else we should think about as we review?

Proposed chairs: [@jaromil](https://github.com/jaromil), [@patsc](https://github.com/patsc), and [@innotommy](https://github.com/innotommy).


## Charter facilitator(s)

cc @simoneonofri

<!-- Content below this is maintained by @w3c-tag-bot -->
---

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1289


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1289
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1289@github.com>