From Fedora Project Wiki

No edit summary
(Updated apprenticeship requirements.)
Line 1: Line 1:
{{draft}}
{{draft}}
== Mission ==
To create a training program that creates competent, trusted members of the [[Security Team]] that can handle most every situation that could come their way.
== Background ==
When the [[Security Team]] was created we were forced to guess at what skills were needed and who would be right to work on potentially sensitive cases.  That was a bad way to start ''but'' I believe we're now beyond guessing.


== Requirements to be met ==
== Requirements to be met ==
=== Skills ===
=== Introduction ===
* [[Using security tracking features in Bugzilla]] and [[Security Bugs]]
Send the following information to the [https://lists.fedoraproject.org/mailman/listinfo/security-team Security Team mailing list].
* [[Understand CVEs]]
* Name (pseudonym) and FAS ID
* [[Understanding Packaging Process]] and [[Packaging Policies]]
* GPG Key Fingerprint (attach GPG public key to email)
* [[Basic Understanding of Software and System Security Principles]]
* Interests
 
* Why do you want to join the [[Security Team]]?
=== Time in Service ===
 
=== Trustworthiness ===


== Completing the requirements ==
== Required Reading ==
* [[Security Team Mission]]
* [[Security Team Goals]]
* [[Security Team Work Flow]]
* [[Policy_for_nonresponsive_package_maintainers|Non-Responsive Maintainer Policy]]


== Resources ==
== Required Training ==
'''To be determined.'''


=== Security Training ===
== Required On-the-job Training ==
* [https://fedoraproject.org/wiki/Information_Security_Training Information Security Training]
* Shadow mentor through a ticket and patch process.
=== Packaging Policies and Procedures ===
* Lead ticket and patch process with mentor shadowing.
* [https://fedoraproject.org/wiki/Join_the_package_collection_maintainers?rd=PackageMaintainers/Join Becoming a Packager]
* [http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers Non-Responsive Maintainer Policy]
=== CVE Description and Use ===
* [https://cve.mitre.org/ CVE Central]

Revision as of 20:07, 11 March 2016

Warning.png
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.

Requirements to be met

Introduction

Send the following information to the Security Team mailing list.

  • Name (pseudonym) and FAS ID
  • GPG Key Fingerprint (attach GPG public key to email)
  • Interests
  • Why do you want to join the Security Team?

Required Reading

Required Training

To be determined.

Required On-the-job Training

  • Shadow mentor through a ticket and patch process.
  • Lead ticket and patch process with mentor shadowing.