# Join the Python Security Response Team!

**URL:** <https://discuss.python.org/t/join-the-python-security-response-team/106253>\
**Category:** Core Workflow\
**Created:** [February 23, 2026, 2:57pm UTC](https://discuss.python.org/t/join-the-python-security-response-team/106253 "2026-02-23T14:57:19Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![sethmlarson](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/sethmlarson/32/1644_2.png) [@sethmlarson](https://discuss.python.org/u/sethmlarson)\
**Post date:** [February 23, 2026, 2:57pm UTC](https://discuss.python.org/t/join-the-python-security-response-team/106253/1 "2026-02-23T14:57:19Z")

</div>

Hello all,

I’ve published a new blog post “Join the Python Security Response Team!” now that the [publication of membership, responsibilities, and nomination process](https://devguide.python.org/developer-workflow/psrt/) described in [PEP 811](https://peps.python.org/pep-0811/) have been implemented in the Python Developer Guide. I wanted to highlight the [call-to-action](https://pyfound.blogspot.com/2026/02/join-the-python-security-response-team.html#user-content-how-can-i-join-the-python-security-response-team) of this blog post to anyone who is interested in security or believes their employer may support their time coordinating for the PSRT: I invite you to read the process and consider joining the team, your efforts will have a real positive impact on the security of Python.

Thanks for your consideration and support 🙂