SecurityTeam
Differences between revisions 18 and 22 (spanning 4 versions)
|
Size: 1035
Comment:
|
Size: 1297
Comment: clean up GettingInvolved link
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 16: | Line 16: |
| * [[SecurityTeam/BugTriage|Bug triage]] | |
| Line 18: | Line 19: |
| * [[AppArmor]] | * [[AppArmor]] (see [[SecurityTeam/KnowledgeBase/AppArmorProfiles | AppArmorProfiles]] for existing default enforcing profiles in Ubuntu) |
| Line 23: | Line 24: |
| * Auditing and Penetration Testing | * Network access * [[UbuntuFirewall]] * [[SecurityTeam/Auditing|Auditing]] and Penetration Testing |
| Line 26: | Line 29: |
| Seem like fun? Head to the [[/GettingInvolved]] page to found out how to contribute to the SecurityTeam. | Seem like fun? Head to the [[ServerTeam/GettingInvolved GettingInvolved]] page to found out how to contribute to the SecurityTeam. |
Contents |
Introduction
The Ubuntu Security Team represents multiple teams of people dedicated to keeping Ubuntu secure, and contributing to its proactive hardening.
Projects
To discuss any Security Team projects, send email to the ubuntu-hardened mailing list.
- CVE handling
- tracking: Ubuntu CVE Tracker
- fixing: main and universe
- Hardening
- Mandatory Access Control
AppArmor (see AppArmorProfiles for existing default enforcing profiles in Ubuntu)
Compiler flags (HardeningWrapper)
- pbuilder integration
- sbuild integration
- Network access
- Mandatory Access Control
Auditing and Penetration Testing
Seem like fun? Head to the ServerTeam/GettingInvolved GettingInvolved page to found out how to contribute to the SecurityTeam.
Sub-pages :
SecurityTeam (last edited 2025-06-02 10:36:53 by 0xdsousa)