+ All Categories
Home > Technology > Open Source Security

Open Source Security

Date post: 30-Oct-2014
Category:
Upload: sander-temme
View: 878 times
Download: 1 times
Share this document with a friend
Description:
Slide deck on the security aspects of using Open Source Software. Focused on the Apache HTTP Server project, this deck discusses general topics like what Open Source software is, what the prevailing myths surrounding it are and how the open development process works to ensure the result is secure.
Popular Tags:
38
Security and Open Source Software Sander Temme sander @ temme.net @keysinthecloud
Transcript
Page 1: Open Source Security

Security and Open Source

SoftwareSander Temme [email protected]@keysinthecloud

Page 2: Open Source Security

Your Presenter

Member, Apache Software Foundation

Contributor, Apache HTTP Server

Sales Engineer & Consultant

Open Source Integration Expert

Page 3: Open Source Security

Agenda

Open Source Software

Security Process

Security Implications

Development Model

Page 4: Open Source Security

Three Questions

How does open source respond when security problems occur?

How does the open source development process affect software quality?

Is open source software more susceptible to security problems?

Page 5: Open Source Security

Open Source Software

Page 6: Open Source Security

About Open Source Closed Source

Microsoft, Adobe, Oracle, Symantec, Check Point, …

Open Source Apache, Debian, FreeBSD, Mozilla, Python, FSF, …

Hybrid Red Hat, Hippo, Apple, SugarCRM, …

Inclusion Oracle, IBM, Apple, Autodesk, Cisco, NetApp, …

Page 7: Open Source Security

Open Source Is Not…

Freeware

Trialware

Shareware

Abandonware (hopefully)

Public Domain

Page 8: Open Source Security

Who Develops Open Source

Users

Consultants

Vendors

Hobbyists

Page 9: Open Source Security

Why Develop Open Source

Resume

User to contributor

Work

Page 10: Open Source Security

Where is Open Source Used

Server side

Operating Systems

Application Stack

Web Facing In the line of fire

Page 11: Open Source Security

Open Source Security Myths

Given enough eyeballs, all bugs are shallow

Page 12: Open Source Security

Open Source Security Myths

Given enough eyeballs, all bugs are shallow

Open Source is Communist!

Page 13: Open Source Security

Open Source Security Myths

Given enough eyeballs, all bugs are shallow

Open Source is Communist!

Bad guys have the code, too!

Page 14: Open Source Security

Open Source Security Myths

Given enough eyeballs, all bugs are shallow

Open Source is Communist!

Bad guys have the code, too!

Open Source is more secure than Closed Source

Page 15: Open Source Security

28%

26%19%

11%

4%

4%2%

6%

Attack GoalsDefacement/Planting Malware

Information Leakage/Stealing Sensitive Data

Disinformation

Monetary Loss

Downtime

Link Spam

Phishing

Other

Source: The Web Hacking Incidents Database, 2009 Report

Page 16: Open Source Security

19%

11%

11%

10%10%

8%

8%

5%

5%

3% 10%

Attack VectorsSQL Injection

Unknown

Insufficient Authentication

Content Spoofing

Insufficient Anti-Automation (DoS/Brute Force)

Configuration/Admin Error

Cross-site Scripting (XSS)

Cross-site Request Forgery (CSRF)

DNS Hijacking

Worm

Other

Source: The Web Hacking Incidents Database, 2009 Report

Page 17: Open Source Security

Exploits of a Mom

http://xkcd.com/327/

Page 18: Open Source Security

Case Study

Apache HTTP Server Security

Page 19: Open Source Security

The httpd Project #1 Web Server

Non-profit Foundation

Contributors Oracle, IBM, Novell, VMWare, Red Hat, Google Many individual contributors

http://httpd.apache.org

Many packagers and distributors

http://people.apache.org/~coar/mlists.html

Page 20: Open Source Security

Apache Security

Very few vulnerabilities reported

No critical vulnerabilities in 2.2.x

Upgrade to any new release [email protected]

Default installation locked down But it doesn’t do a whole lot

http://httpd.apache.org/security/vulnerabilities-oval.xmlhttp://www.apache.org/security/

Page 21: Open Source Security

Apache Security Process

Report security problems to [email protected]

Real vulnerabilities are assigned CVE number

Vulnerabilities are classified, fixed

New httpd version released

http://httpd.apache.org/security_report.htmlhttp://cve.mitre.org/http://httpd.apache.org/security/[email protected]://www.apache.org/security/committers.html

Page 22: Open Source Security

ImplicationsSecurity Implications of Open

Source Software

Page 23: Open Source Security

Application

App Server

Operating System

Network

Page 24: Open Source Security

Security Implications

Developed by programmers

Provenance?

Warranty?

Support?

Page 25: Open Source Security

Developed by Programmers

Not security experts

Get it running

Page 26: Open Source Security

Database Privileges

Wordpress: GRANT ALL PRIVILEGES ON databasename.* TO "wordpressusername"@"hostname” IDENTIFIED BY "password";

Joomla 1.5: GRANT ALL PRIVILEGES ON Joomla.* TO nobody@localhost IDENTIFIED BY 'password';

Drupal: SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER, CREATE TEMPORARY TABLES, LOCK TABLES

Gallery 2: mysql gallery2 -uroot -e"GRANT ALL ON gallery2.* TO username@localhost IDENTIFIED BY 'password'”;

Bugzilla: GRANT SELECT, INSERT, UPDATE, DELETE, INDEX, ALTER, CREATE, LOCK TABLES, CREATE TEMPORARY TABLES, DROP, REFERENCES ON bugs.* TO bugs@localhost IDENTIFIED BY '$db_pass';

Page 27: Open Source Security

Getting it Right: Bugzilla

Install script Creates database Executed as root

Application privileges Limited Only as needed

This is not always practical

GRANT SELECT, INSERT, UPDATE, DELETE, INDEX, ALTER, CREATE, LOCK TABLES, CREATE TEMPORARY TABLES, DROP, REFERENCES ON bugs.* TO bugs@localhost IDENTIFIED BY '$db_pass';

Page 28: Open Source Security

Provenance

Source Integrity

Intellectual Property

Apache: Digital signatures Committer License Agreement Patent Grant

http://www.apache.org/licenses/icla.txthttp://www.apache.org/licenses/cla-corporate.txt

Page 29: Open Source Security

Warranty

Open Source No warranty

Closed Source No warranty

Page 30: Open Source Security

Support

Often community based You can be part of it

Visible to the world Don’t post confidential information!

Support contracts available From third party companies

[email protected]

Page 31: Open Source Security

Development Model

Open Development At Apache

Page 32: Open Source Security

Open Development

Mailing lists

Source code changes

Releases

Bus Factor

Page 33: Open Source Security

Mailing Lists

All communication by e-mail

Several lists announce@<project>.apache.org users@<project>.apache.org dev@<project>.apache.org cvs@<project>.apache.org

Page 34: Open Source Security

Code Changes: Transparency

Source history available

Every modification posted

Instant code review

Etiquette

Page 35: Open Source Security

Bus Factor

Development Community

Project Survival

Closed Source Equivalent Vendor out of business Product end-of-life

Page 36: Open Source Security

Tips for Open Source Users

Get on announce mailinglist

Investigate community

Get involved

Page 37: Open Source Security

Conclusion

Open Source responds proactively to security issues

Open Development encourages clean and secure code

Security Issues are universal and not specific to Open or Closed Source Software

Page 38: Open Source Security

Questions?

Sander [email protected]@keysinthecloud


Recommended