Security

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Add mention about new 'SetUserGroupIDExecutables' page, dedicated to list SUID / SGID binaries within F-14 and newer versions)
(Security Response: Adding communicating links)
(10 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Fedora Security Response Procedures ==
+
== Mission ==
 +
The Security SIG has three missions that contributors can assist with:
 +
 
 +
# Secure Coding
 +
# Code Auditing
 +
# Security Response
 +
 
 +
Contributors can work on any or all of these missions.
 +
 
 +
== Secure Coding ==
 +
 
 +
Secure coding is writing code with security in mind from the beginning.  By not making security mistakes the code is more secure and time won't be wasted down the road having to rewrite or redesign features and functionality.
 +
 
 +
=== Communicating ===
 +
==== E-Mail List ====
 +
* [https://lists.fedorahosted.org/mailman/listinfo/secure-coding-announce Secure Coding Announce list]
 +
* [https://lists.fedorahosted.org/mailman/listinfo/secure-coding-dev Secure Coding Development list]
 +
 
 +
==== IRC ====
 +
* '''{{fpchat|#fedora-security}}''' - Fedora's Security SIG channel on Freenode.
 +
 
 +
=== Projects ===
 +
 
 +
==== Defensive Coding book ====
 +
 
 +
The [https://docs.fedoraproject.org/en-US/Fedora_Security_Team//html/Defensive_Coding/index.html Defensive Coding book] is published on the [https://docs.fedoraproject.org Fedora Docs website] and is [https://fedorahosted.org/secure-coding/ under development].  The purpose of the book is to document common mistakes developers make and help educate developers on how to better their code from the beginning.
 +
 
 +
==== Training and Articles ====
 +
 
 +
In addition to the Defensive Coding book the Security SIG is charged with creating training resources.  Videos and smaller articles on secure development can also be created to concentrate specific topics.  These resources should be stored in the [https://fedorahosted.org/secure-coding/ secure coding] git repository.
 +
 
 +
== Code Auditing ==
 +
=== Communicating ===
 +
==== IRC ====
 +
* '''{{fpchat|#fedora-security}}''' - Fedora's Security SIG channel on Freenode.
 +
 
 +
== Security Response ==
 +
=== Communicating ===
 +
==== E-mail list ====
 +
 
 +
Fedora {{fplist|security}} list: For discussion about improvement of Fedora security.
 +
 
 +
==== IRC ====
 +
* '''{{fpchat|#fedora-security}}''' - Fedora's Security SIG channel on Freenode.
 +
 
 +
=== Fedora Security Response Procedures ===
  
 
If you would like to report any potential security issues with Fedora follow the procedures in [[Security/Bugs|Security Bugs]] page for escalated attention to it.
 
If you would like to report any potential security issues with Fedora follow the procedures in [[Security/Bugs|Security Bugs]] page for escalated attention to it.
  
== Security Issues Classification ==
+
=== Security Issues Classification ===
  
 
So what counts a security issue in Fedora? Find answers in the [[Security/Classifications|Security Classifications]] page.
 
So what counts a security issue in Fedora? Find answers in the [[Security/Classifications|Security Classifications]] page.
  
== Security Status ==
+
=== Security Status ===
  
 
The current security status of Fedora is available from [[Security/Status|Security Status]] page.
 
The current security status of Fedora is available from [[Security/Status|Security Status]] page.
  
== Security Features ==
+
=== Security Features ===
  
 
Security features available in Fedora is explained on [[Security/Features|Security Features]] page.
 
Security features available in Fedora is explained on [[Security/Features|Security Features]] page.
  
== Security Mailing list ==
+
=== Fedora Security Response ===
 
+
[https://www.redhat.com/mailman/listinfo/fedora-security-list Fedora security list]: For discussion about improvement of Fedora security. Other mailing lists are available at the [[Communicating_and_getting_help#Mailing_Lists|Communicate]] page
+
 
+
== Fedora Security Response ==
+
  
 
The Fedora [[Security/ResponseTeam|Security Response Team]] handles security issues within Fedora. The Red Hat security team can be reached by mailing secalert AT SPAMFREE redhat DOT com. Information regarding known public issues can be found on the [[Security/Status|Security Status]] page.
 
The Fedora [[Security/ResponseTeam|Security Response Team]] handles security issues within Fedora. The Red Hat security team can be reached by mailing secalert AT SPAMFREE redhat DOT com. Information regarding known public issues can be found on the [[Security/Status|Security Status]] page.
  
== Endemic Security Risks  ==
+
=== Endemic Security Risks  ===
  
 
Due to the Fedora Project's use of resources not directly under our control, such as mirrors, Fedora and its users have exposure to [[Mirror_manager_security_risks|additional endemic risks]], and takes as many steps as possible mitigate these risks.
 
Due to the Fedora Project's use of resources not directly under our control, such as mirrors, Fedora and its users have exposure to [[Mirror_manager_security_risks|additional endemic risks]], and takes as many steps as possible mitigate these risks.
  
== References ==
+
=== References ===
  
 
* http://people.redhat.com/drepper/nonselsec.pdf
 
* http://people.redhat.com/drepper/nonselsec.pdf
 
* http://docs.fedoraproject.org/selinux-faq/
 
* http://docs.fedoraproject.org/selinux-faq/
 +
* [[Updates_Policy|Fedora Updates Policy]]
  
== Presentations ==
+
=== Presentations ===
  
 
* http://fedoraproject.org/wiki/Presentations
 
* http://fedoraproject.org/wiki/Presentations
  
== Fedora Security Advisories ==
+
=== Fedora Security Advisories ===
  
 
* http://fedoraproject.org/wiki/FSA
 
* http://fedoraproject.org/wiki/FSA
  
== Fedora Security Tracking Bugs ==
+
=== Fedora Security Tracking Bugs ===
  
 
* To track security vulnerabilities in packages, [[Security/TrackingBugs|tracking bugs]] are used.
 
* To track security vulnerabilities in packages, [[Security/TrackingBugs|tracking bugs]] are used.
  
== List of Embedded Software ==
+
=== List of Embedded Software ===
  
 
* We are maintaining a list of embedded software within various packages.  This will help us to quickly identify if a problem in library X can be corrected with updating library X, or if it also requires updating other packages that may contain their own private copies of library X.  The [[Security/EmbeddedSoftware|embedded software list]] is used for this purpose.
 
* We are maintaining a list of embedded software within various packages.  This will help us to quickly identify if a problem in library X can be corrected with updating library X, or if it also requires updating other packages that may contain their own private copies of library X.  The [[Security/EmbeddedSoftware|embedded software list]] is used for this purpose.
  
== List of SUID / SGID executables ==
+
=== List of SUID / SGID executables ===
  
 
* We are maintaining a list of SUID / SGID bit equipped executables
 
* We are maintaining a list of SUID / SGID bit equipped executables
Line 55: Line 97:
 
for Fedora release of 14 and it will be enhanced later to include
 
for Fedora release of 14 and it will be enhanced later to include
 
list of privileged binaries in also in newer versions of Fedora.
 
list of privileged binaries in also in newer versions of Fedora.
The [[Security/SetUserGroupIDExecutables| list of SUID / SGID executables]]
+
The [[Security/SetUserGroupIDExecutables| list of SUID SGID executables]]
 
is used for this purpose.
 
is used for this purpose.
 +
  
 
[[Category:Documentation]]
 
[[Category:Documentation]]
 
[[Category:Security]]
 
[[Category:Security]]

Revision as of 16:09, 26 March 2013

Contents

Mission

The Security SIG has three missions that contributors can assist with:

  1. Secure Coding
  2. Code Auditing
  3. Security Response

Contributors can work on any or all of these missions.

Secure Coding

Secure coding is writing code with security in mind from the beginning. By not making security mistakes the code is more secure and time won't be wasted down the road having to rewrite or redesign features and functionality.

Communicating

E-Mail List

IRC

Projects

Defensive Coding book

The Defensive Coding book is published on the Fedora Docs website and is under development. The purpose of the book is to document common mistakes developers make and help educate developers on how to better their code from the beginning.

Training and Articles

In addition to the Defensive Coding book the Security SIG is charged with creating training resources. Videos and smaller articles on secure development can also be created to concentrate specific topics. These resources should be stored in the secure coding git repository.

Code Auditing

Communicating

IRC

Security Response

Communicating

E-mail list

Fedora security list: For discussion about improvement of Fedora security.

IRC

Fedora Security Response Procedures

If you would like to report any potential security issues with Fedora follow the procedures in Security Bugs page for escalated attention to it.

Security Issues Classification

So what counts a security issue in Fedora? Find answers in the Security Classifications page.

Security Status

The current security status of Fedora is available from Security Status page.

Security Features

Security features available in Fedora is explained on Security Features page.

Fedora Security Response

The Fedora Security Response Team handles security issues within Fedora. The Red Hat security team can be reached by mailing secalert AT SPAMFREE redhat DOT com. Information regarding known public issues can be found on the Security Status page.

Endemic Security Risks

Due to the Fedora Project's use of resources not directly under our control, such as mirrors, Fedora and its users have exposure to additional endemic risks, and takes as many steps as possible mitigate these risks.

References

Presentations

Fedora Security Advisories

Fedora Security Tracking Bugs

  • To track security vulnerabilities in packages, tracking bugs are used.

List of Embedded Software

  • We are maintaining a list of embedded software within various packages. This will help us to quickly identify if a problem in library X can be corrected with updating library X, or if it also requires updating other packages that may contain their own private copies of library X. The embedded software list is used for this purpose.

List of SUID / SGID executables

  • We are maintaining a list of SUID / SGID bit equipped executables

within various packages. This will help us to quickly identify privileged binaries. This list is preliminary planned to be prepared for Fedora release of 14 and it will be enhanced later to include list of privileged binaries in also in newer versions of Fedora. The list of SUID SGID executables is used for this purpose.