Building an OpenStack Security Group.pdf

24
Bryan D. Payne, Nebula Robert Clark, HP Building an OpenStack Security Group

description

true

Transcript of Building an OpenStack Security Group.pdf

Page 1: Building an OpenStack Security Group.pdf

Bryan  D.  Payne,  Nebula  Robert  Clark,  HP  

Building  an  OpenStack  Security  Group  

Page 2: Building an OpenStack Security Group.pdf

10/17/12  2  

Page 3: Building an OpenStack Security Group.pdf

10/17/12  3  

Page 4: Building an OpenStack Security Group.pdf

•  Alarm  system?  •  Bars  on  the  windows?  •  Dog?  •  Security  Cameras?  •  Move?  

10/17/12  4  

Page 5: Building an OpenStack Security Group.pdf

•  Alarm  system?  •  Bars  on  the  windows?  •  Dog?  •  Security  Cameras?  •  Move?  

10/17/12  5  

Page 6: Building an OpenStack Security Group.pdf

•  Alarm  system?  •  Bars  on  the  windows?  •  Dog?  •  Security  Cameras?  •  Move?  

10/17/12  6  

Page 7: Building an OpenStack Security Group.pdf

•  Alarm  system?  •  Bars  on  the  windows?  •  Dog?  •  Security  Cameras?  •  Move?  

10/17/12  7  

Page 8: Building an OpenStack Security Group.pdf

•  Alarm  system?  •  Bars  on  the  windows?  •  Dog?  •  Security  Cameras?  •  Move?  

10/17/12  8  

Page 9: Building an OpenStack Security Group.pdf

This  Is  Hard  

10/17/12  9  

Page 10: Building an OpenStack Security Group.pdf

SoSware  Must  Be  Easier,  Right?  

10/17/12  10  

Page 11: Building an OpenStack Security Group.pdf

But  Who  Wants  to  Hack  OpenStack?  

10/17/12  11  

Page 12: Building an OpenStack Security Group.pdf

10/17/12  12  

Page 13: Building an OpenStack Security Group.pdf

Computer  Security:  What  We  Know  Be#er   Worse  

Design  for  security  from  the  start   Retrofit  security  when  it’s  important  

Understand  your  threats   Just  make  it  secure  

Understand  your  goals   Seriously,  just  add  some  security  

Pervasive  security  culture   That  paranoid  guy  has  it  under  control  

10/17/12  13  

Page 14: Building an OpenStack Security Group.pdf

Current  Approach  •  Vulnerability  Management  Team  

 •  People  star_ng  to  think  about  security  

 

10/17/12  14  

Page 15: Building an OpenStack Security Group.pdf

OpenStack  Security  Challenges  

•  Security  as  an  aSerthought  •  Security  as  silos  •  Security  by  non-­‐experts    

10/17/12  15  

Page 16: Building an OpenStack Security Group.pdf

OpenStack  Security  Group  (OSSG)  

•  Security  expert  resource  for  OS  •  Build  security  culture  within  OS  community  

10/17/12  16  

Page 17: Building an OpenStack Security Group.pdf

10/17/12  17  

OSSG  Game  Plan  

Page 18: Building an OpenStack Security Group.pdf

OSSG  Details  •  Place  at  least  one  security  engineer  on  each  core  project  

–  Code  review  –  Implement  blueprints  –  Design  blueprints  

•  Have  at  least  one  person  working  cross  project  –  Write  technical  documenta_on  –  Integra_ng  security  into  con_nuous  integra_on  –  Iden_fy  cross  project  security  concerns  

•  Mailing  list  to  have  security  discussions  

10/17/12  18  

Page 19: Building an OpenStack Security Group.pdf

Case  Study:  HTTPS  Support  

10/17/12  19  

Page 20: Building an OpenStack Security Group.pdf

© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

Observations from Summit 2012

Page 21: Building an OpenStack Security Group.pdf

Crypt

Enthusiastic Developer + Hash Algorithm + Async Crypt != Secure Design

Page 22: Building an OpenStack Security Group.pdf

Common Mistakes

Let us help

Page 23: Building an OpenStack Security Group.pdf

OSSG  Next  Steps  •  Will  require  community-­‐level  involvement  •  Now  “hiring”  for  OSSG!!  

– Security  Engineers  – Technical  Writers  – OpenStack  Deployment  Exper_se  

10/17/12  23  

Page 24: Building an OpenStack Security Group.pdf

hhps://launchpad.net/~openstack-­‐ossg  

10/17/12  24  

Please  Join  Us!  

Bryan  D.  Payne  [email protected]  

Robert  Clark  [email protected]