SecurityTeam
Differences between revisions 17 and 20 (spanning 3 versions)
|
Size: 1055
Comment: converted to 1.6 markup
|
Size: 1245
Comment: link to SecurityTeam/BugTriage
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| ||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;">'''Contents'''<<BR>><<TableOfContents>>|| | ||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;"><<TableOfContents>>|| |
| 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: |
| * Network access * [[UbuntuFirewall]] |
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 /GettingInvolved page to found out how to contribute to the SecurityTeam.
Sub-pages :
SecurityTeam (last edited 2025-06-02 10:36:53 by 0xdsousa)