You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: "Becoming a Framework Steward | Security Alliance"
3
-
description: "Become a SEAL Framework Steward: champion and caretake a security framework. Rally collaborators, manage contributions, advocate for adoption, and shape Web3 security standards."
A framework steward is the champion and caretaker for an individual security framework (most frameworks
15
-
here -> [https://frameworks.securityalliance.org](https://frameworks.securityalliance.org) are currently
16
-
available for adoption). This role goes beyond casual contribution.
17
-
It's about taking ownership and helping guide the framework's development through community engagement.
18
-
19
-
## The Steward's Role
20
-
21
-
A framework steward is a project management role, responsible for:
22
-
23
-
-**Rallying collaborators**: Recruit contributors who share your passion for specific security challenges
24
-
-**Managing contributions**: Help triage [GitHub issues](https://github.com/security-alliance/frameworks/issues) and
25
-
coordinate improvements
26
-
-**Advocating for adoption**: Work with SEAL to promote your framework within your networks and the broader Web3
27
-
community
28
-
-**Creating content**: Work with SEAL to write blog posts, host workshops, or share best practices related to your
29
-
framework
30
-
-**Representing the community**: Be a voice for practitioners who use and rely on these standards
31
-
32
-
The core SEAL team will support you throughout this journey, helping you focus on specific challenges rather than
33
-
drowning in administrative tasks.
34
-
35
-
## Why Become a Steward?
36
-
37
-
### Recognition and Growth
38
-
39
-
-**Earn achievement badges**: Receive public recognition with roles like Security Framework Ambassador or DAO
40
-
Safeguards Steward
41
-
-**Build your reputation**: Establish yourself as a thought leader in Web3 security
42
-
-**Develop new skills**: Gain experience in open-source governance, technical writing, and community building
43
-
44
-
### Tangible Benefits
45
-
46
-
-**Access exclusive events**: Receive tickets to security conferences and invite-only Security Alliance gatherings
47
-
-**Showcase your expertise**: Get featured through SEAL's official channels, including our
48
-
[blog](https://www.securityalliance.org/news) and [social media](https://twitter.com/_SEAL_Org)
49
-
-**Connect with peers**: Build relationships with other security professionals who share your interests
50
-
51
-
### Lasting Impact
52
-
53
-
-**Shape industry standards**: Help develop frameworks that could become foundational to Web3 security
54
-
-**Prevent security incidents**: Your work will directly contribute to a safer ecosystem
55
-
-**Leave a legacy**: Carve your name into the DNA of Web3 security practices for years to come
56
-
57
-
## Stewardship in Action: What It Looks Like
58
-
59
-
### Time Commitment
60
-
61
-
Being a steward doesn't mean giving up your day job. We're looking for contributors who can dedicate approximately 3
62
-
hours per week to their framework. This might include:
63
-
64
-
- Reviewing [pull requests](https://github.com/security-alliance/frameworks/pulls) and GitHub issues
65
-
- Participating in sporadic steward meetings
66
-
- Creating occasional content or presentations
67
-
- Engaging with the community on [Discord](https://discord.gg/securityalliance)
68
-
69
-
### Support Structure
70
-
71
-
You won't be working alone. You will have:
72
-
73
-
- Access to a dedicated channel on our [Discord server](https://discord.gg/securityalliance)
74
-
- Coordination calls with the SEAL team as needed
75
-
- Documentation templates and contribution guidelines
76
-
- Access to technical advisors when needed
77
-
78
-
## How to Apply
79
-
80
-
Ready to become a framework steward? Here's how to get started:
81
-
82
-
1. Review the proposed frameworks at [frameworks.securityalliance.org](https://frameworks.securityalliance.org) and
83
-
identify which one aligns with your expertise and interests.
84
-
2. Join our [steward candidates Telegram channel](https://t.me/+Yd9OpSt1UvcyMjU5) and introduce yourself to let us know
85
-
which Framework you want to adopt.
86
-
87
-
We're looking for diverse perspectives and experiences, and you don't need to have decades of experience. Passion,
88
-
dedication, and a willingness to learn are just as important.
89
-
90
-
## Join Us in Building a Safer Web3
91
-
92
-
The "Adopt a Framework" campaign isn't just about improving documentation. You'll be part of a movement where security
93
-
becomes a shared responsibility across the Web3 ecosystem.
94
-
95
-
By becoming a steward, you're taking an active role in preventing the next major hack, protecting user funds, and
96
-
ensuring that innovation can continue without compromising safety.
97
-
98
-
We're just getting started, and we need your expertise.
99
-
100
-
Have questions about the stewardship program or ideas for improving it? You can use the [potential stewards Telegram
101
-
channel](https://t.me/+Yd9OpSt1UvcyMjU5) for that too! 🙂
14
+
A framework steward is the resident expert for one (or more) of the security domains covered by the
15
+
[Security Frameworks](https://frameworks.securityalliance.org). The role is a natural extension
16
+
of contribution: stewards are people who have demonstrated genuine depth in a specific area,
17
+
through the content they've written or reviewed, and who SEAL trusts to maintain the quality and
18
+
direction of that domain going forward.
19
+
20
+
It is a technical role, but also a community one. Stewards bring a sense of ownership to their
21
+
domain, and being embedded in the contributor community often leads to finding and connecting
22
+
with people who care deeply about the same problems.
23
+
24
+
## Why become a steward?
25
+
26
+
Because what gets written here is what practitioners across Web3 will actually read and rely on.
27
+
When you become a steward, your approval is required before anything merges into your framework.
28
+
That is real influence over what the community considers best practice, not in a symbolic way, but
29
+
in a direct, technical one.
30
+
31
+
Beyond that: the people you will meet are worth it. The stewards community is small and
32
+
deliberately kept that way. These are security professionals who care enough about the ecosystem
33
+
to put time into building something that matters.
34
+
35
+
And finally, your work here compounds. The Security Frameworks are a living resource that
36
+
practitioners, teams, and organizations will keep coming back to. The depth you bring to your
37
+
framework keeps getting read long after the initial contribution.
38
+
39
+
## How the role is earned
40
+
41
+
Most stewards got here because they genuinely cared about a topic and wrote something useful.
42
+
The role is a recognition of that, not a prerequisite for it.
43
+
44
+
There is no application form. The typical path looks like this:
45
+
46
+
1. A contributor writes or reviews content for a specific framework, either independently or
47
+
as part of a broader effort.
48
+
2. We notice the quality and depth of that work, or the contributor reaches out expressing
49
+
interest in a more active role.
50
+
3. If there is mutual trust and the fit is clear, we designate them as steward: they are
51
+
added to the [contributors database](https://github.com/security-alliance/frameworks/blob/develop/docs/pages/config/contributors.json) with the `Framework-Steward` badge, and they get their
52
+
own entry in the [Spotlight Zone](/contribute/spotlight-zone), the public-facing recognition
53
+
page where stewards are listed alongside the frameworks they own.
54
+
55
+
If you are interested, the most direct path is to start contributing to the framework you care
56
+
about. You can also reach out on [Discord](https://discord.gg/securityalliance) if you want to
57
+
discuss it first.
58
+
59
+
## Responsibilities
60
+
61
+
Once designated as steward for a framework, your responsibilities are focused:
62
+
63
+
-**Review incoming contributions**: When a pull request touches your framework, you will be
64
+
tagged as a required reviewer. The PR will not be merged without your approval. You become the
65
+
quality and accuracy gate for your domain.
66
+
-**Help grow the framework**: The Security Frameworks are a work in progress, and many domains
67
+
still have room to grow. If you know people with the right expertise, bring them in, whether as
68
+
contributors to your framework or to the project more broadly. The goal is to make these
69
+
frameworks as broad and battle-tested as possible, and stewards are well-positioned to make
70
+
that happen.
71
+
-**Advise on structural decisions**: When changes that affect the organization or direction of
72
+
the repo are being considered, stewards are consulted as domain experts. Your input carries
73
+
weight on decisions that touch your framework.
74
+
75
+
## What this looks like in practice
76
+
77
+
**On GitHub**: You are tagged as a required reviewer on any PR that touches your framework.
78
+
Nothing merges without your sign-off.
79
+
80
+
**On Discord**: Our [Discord server](https://discord.gg/securityalliance) has a dedicated
81
+
stewards channel. You will be added to it and pinged when a relevant PR comes in, when we
82
+
want your perspective on something, or when you want to share something more privately before
83
+
it goes to the broader community. It is also where you will meet the other stewards, a small
84
+
group of people who are genuinely invested in Web3 security and often worth knowing.
85
+
86
+
**On the Spotlight Zone**: Your stewardship is publicly recognized on the
87
+
[Spotlight Zone](/contribute/spotlight-zone) page, where your profile appears alongside
88
+
the framework you own.
89
+
90
+
## Open frameworks
91
+
92
+
The following frameworks are currently looking for a steward. If any of these match your
93
+
expertise, this is a good place to start:
94
+
95
+
- Awareness
96
+
- DevSecOps
97
+
- DPRK IT Workers
98
+
- Encryption
99
+
- External Security Reviews
100
+
- Front-End & Web App Security
101
+
- Governance
102
+
- IAM
103
+
- Infrastructure
104
+
- Multisig for Protocols
105
+
- Privacy
106
+
- Secure Software Development
107
+
- Security Automation
108
+
- Supply Chain
109
+
- Threat Modeling
110
+
- Treasury Operations
111
+
- User & Team Security
112
+
- Vulnerability Disclosure
113
+
114
+
If none of these match your expertise but you see a gap that isn't covered anywhere on the site,
115
+
that is worth something too. A new framework can start small, a single page or a rough outline,
116
+
and grow from there through iteration. If you have a topic in mind, reach out on
117
+
[Discord](https://discord.gg/securityalliance) and we can figure out together whether it makes
118
+
sense to build it out.
119
+
120
+
Otherwise, start contributing to whichever framework fits your background. Either way works.
0 commit comments