SecurityTeam

Differences between revisions 2 and 40 (spanning 38 versions)
Revision 2 as of 2008-01-30 20:03:26
Size: 1402
Editor: c-76-105-157-155
Comment:
Revision 40 as of 2017-01-25 23:50:10
Size: 4670
Editor: emilyr
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
[[Include(SecurityTeam/Header)]] <<Include(SecurityTeam/Header)>>
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 6: Line 6:
= Introduction =
## Describe:
## the teams's purpose and community role
## the team tasks and work
## who might be interested in joining/getting involved with the team
== Introduction ==
Line 12: Line 8:
= Contact =
## List the contact information of the team: Mailing-list, IRC channel and Web Forum as they may apply. Provide a link to the Launchpad page as a Team Member list if applicable. Consider how people will get in touch with you based on the contact information you supply.
The Ubuntu Security Team represents multiple teams of people dedicated to keeping Ubuntu and its users secure through fixing vulnerabilities and contributing to its security development. The primary teams are:
 * [[https://launchpad.net/~ubuntu-security|Ubuntu Security]]: team responsible for [[https://wiki.ubuntu.com/SecurityTeam/FAQ#Official%20Support|officially supported packages]] in Ubuntu
 * [[https://launchpad.net/~motu-swat|MOTU Swat]]: team responsible for helping to coordinate community supported updates in Ubuntu
Line 15: Line 12:
= How to Contribute =
## Describe easy ways to contribute to the team. These should look a lot like the bulleted points on the ContributeToUbuntu wiki page. Link to more detailed subpages as necessary.
== Vulnerabilities ==
A security vulnerability can be defined as ''"a mistake in software that can be directly used by a hacker to gain access to a system or network" -- [[http://cve.mitre.org/about/terminology.html|Mitre]].'' There are many different types of vulnerabilities, some of which are denial of service, gaining user or root privileges, data loss, and information disclosure. The Ubuntu Security Team and Ubuntu community work together to find and correct these mistakes through various activities.
Line 18: Line 15:
= Projects =
## List the team's current projects and tasks as well as status and contact persons for each one. Make it easy for new people to know who to ask and where to go to get involved with a specific project.
=== Auditing ===
Searching for security vulnerabilities is usually referred to as auditing. The Ubuntu Security Team often performs audits on software before it is to be [[MainInclusionProcess|officially supported]]. Once vulnerabilities are found, the Security Team uses [[https://wiki.ubuntu.com/SecurityTeam/BugTriage#Private%20Bugs|responsible disclosure]] to let others know about the issue. The [[SecurityTeam/Auditing|Auditing]] page has more information.
Line 21: Line 18:
= Launchpad Membership Policy =
## Describe your Launchpad team membership policy here.
=== Tracking ===
Most flaws in software are found by security researchers and users of the software. These flaws are tracked globally in the [[http://cve.mitre.org|MITRE CVE database]], and the Security Team will track issues that affect Ubuntu in the [[http://people.canonical.com/~ubuntu-security/cve/|Ubuntu CVE Tracker]]. As new issues come in, they are evaluated, or [[SecurityTeam/BugTriage|triaged]], then added to the CVE Tracker. As issues are fixed the CVEs are updated and retired.
Line 24: Line 21:
= Meetings =
## Link to Meeting Agendas and old meeting summaries here.
For security vulnerabilities that do not have a CVE yet, a [[https://wiki.ubuntu.com/DebuggingSecurity#How%20to%20File|new bug is filed]]. The bug is [[SecurityTeam/BugTriage|triaged]] and if appropriate, a CVE requested by a member of the Security Team.

=== Reporting ===
If you would like to report a security bug in Ubuntu, please see [[https://wiki.ubuntu.com/DebuggingSecurity#How%20to%20File|How to File]].

=== Fixing ===
After a flaw is found and assigned a CVE, it should be [[https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase#Announcements|fixed]]. Oftentimes the author of the software will provide a patch, or a patch will be created by other developers, including the Ubuntu Security Team. Details for providing security updates to Ubuntu can be found in SecurityTeam/UpdateProcedures.

=== Testing ===
Before making the security update available, the update needs to be tested to see if it fixes the flaw and also doesn't introduce any regressions. The Security Team uses the [[https://code.launchpad.net/~ubuntu-bugcontrol/qa-regression-testing/master|QA Regression Testing]] suite when performing testing. QA Regression Testing has information on performing tests, checklists, scripts and various other information to help with testing.

=== Debian ===
Debian and Ubuntu share a lot of the same software and collaboration with each other is beneficial to both distributions. If you are a Debian Developer or member of the Debian security team, please see [[SecurityTeam/ForDebianDevelopers]] for how you can collaborate with Ubuntu and use Ubuntu resources for your updates.

== Development ==
The Security Team also actively develops protections to help keep Ubuntu users safe from new vulnerabilities. Some projects that the Ubuntu Security Team actively develops are:
 * [[AppArmor]] (see [[SecurityTeam/KnowledgeBase/AppArmorProfiles | AppArmorProfiles]] for existing default enforcing profiles in Ubuntu)
 * [[CompilerFlags|CompilerFlags]]
 * [[UncomplicatedFirewall]]
 * [[SecurityTeam/Specifications|Specifications]] and [[SecurityTeam/ReleaseStatus|ReleaseStatus]] for current and past development
 
== What You Can Do ==
Seem like fun? Head to the [[SecurityTeam/GettingInvolved|GettingInvolved]] page to found out how to contribute to the Security Team.
Line 28: Line 46:
'''Sub-pages :''' [[Navigation(children,1)]] '''Sub-pages :''' <<Navigation(children,1)>>

Introduction

The Ubuntu Security Team represents multiple teams of people dedicated to keeping Ubuntu and its users secure through fixing vulnerabilities and contributing to its security development. The primary teams are:

Vulnerabilities

A security vulnerability can be defined as "a mistake in software that can be directly used by a hacker to gain access to a system or network" -- Mitre. There are many different types of vulnerabilities, some of which are denial of service, gaining user or root privileges, data loss, and information disclosure. The Ubuntu Security Team and Ubuntu community work together to find and correct these mistakes through various activities.

Auditing

Searching for security vulnerabilities is usually referred to as auditing. The Ubuntu Security Team often performs audits on software before it is to be officially supported. Once vulnerabilities are found, the Security Team uses responsible disclosure to let others know about the issue. The Auditing page has more information.

Tracking

Most flaws in software are found by security researchers and users of the software. These flaws are tracked globally in the MITRE CVE database, and the Security Team will track issues that affect Ubuntu in the Ubuntu CVE Tracker. As new issues come in, they are evaluated, or triaged, then added to the CVE Tracker. As issues are fixed the CVEs are updated and retired.

For security vulnerabilities that do not have a CVE yet, a new bug is filed. The bug is triaged and if appropriate, a CVE requested by a member of the Security Team.

Reporting

If you would like to report a security bug in Ubuntu, please see How to File.

Fixing

After a flaw is found and assigned a CVE, it should be fixed. Oftentimes the author of the software will provide a patch, or a patch will be created by other developers, including the Ubuntu Security Team. Details for providing security updates to Ubuntu can be found in SecurityTeam/UpdateProcedures.

Testing

Before making the security update available, the update needs to be tested to see if it fixes the flaw and also doesn't introduce any regressions. The Security Team uses the QA Regression Testing suite when performing testing. QA Regression Testing has information on performing tests, checklists, scripts and various other information to help with testing.

Debian

Debian and Ubuntu share a lot of the same software and collaboration with each other is beneficial to both distributions. If you are a Debian Developer or member of the Debian security team, please see SecurityTeam/ForDebianDevelopers for how you can collaborate with Ubuntu and use Ubuntu resources for your updates.

Development

The Security Team also actively develops protections to help keep Ubuntu users safe from new vulnerabilities. Some projects that the Ubuntu Security Team actively develops are:

What You Can Do

Seem like fun? Head to the GettingInvolved page to found out how to contribute to the Security Team.


Sub-pages :



CategoryUbuntuTeams

SecurityTeam (last edited 2017-01-25 23:50:10 by emilyr)