+ All Categories
Home > Technology > Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

Date post: 17-Jul-2015
Category:
Upload: pete-cheslock
View: 1,044 times
Download: 2 times
Share this document with a friend
Popular Tags:
54
Why We Can’t Have Nice Things A Tale of Woe, and Hope for the Future Pete Cheslock @petecheslock
Transcript
Page 1: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

Why We Can’t Have Nice Things A Tale of Woe, and Hope for the Future

Pete Cheslock

@petecheslock

Page 2: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 3: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Wal

l of C

onfu

sion

Dev Ops Sec

Page 4: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 5: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

DevOps

Sec

@hijinksensue

Page 6: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 7: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 8: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

Pete CheslockNot an InfoSec

Twitters: @petecheslock

theshipshow.com

threatstack.com

Page 9: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

– President Josiah Bartlet

"The most costly disruptions always

happen when something we take

completely for granted stops working for a

minute."

Page 10: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 11: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 12: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 13: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 14: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 15: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 16: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 17: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 18: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 19: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

It’s time that we recognize that all these new tools which are helping to enable our teams to work so well are also introducing new attack vectors.

Page 20: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

risk = (threat) x (probability) x (business impact)

http://sysadvent.blogspot.com/2014/12/day-24-12-days-of-secdevops.html

- Jen Andre

Page 21: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

What data are you sending?

What happens if that system is compromised?

Page 22: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

WE TAKE SECURITY SERIOUSLY

http://blog.b3k.us/2012/01/24/some-rules.html

“These are not features: Security, Availability, Performance.”- Benjamin Black

Page 23: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 24: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 25: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 26: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

https://github.com/codahale/sneakerhttps://vaultproject.iohttps://github.com/square/keywhizhttps://github.com/LuminalOSS/credstashhttps://github.com/oleiade/trousseau - Storing sensitive data

https://github.com/cloudflare/redoctober - High value secrets

https://github.com/jschauma/jass - really helpful tool for sharing of secrets using SSH keys.

Page 27: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 28: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 29: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Keep It Simple

Skip the ITIL IR Plan for now

Page 30: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future
Page 31: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 32: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 33: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 34: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 35: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

“FWIW, I have most of a sub-key implementation done, but that still won’t solve your problem, as it will be years before that implementation is widely deployed…”

Page 36: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Compile your Source Build a Package Sign the Package Test the Package

Deploy the Package

You can’t hate the curl bash and be OK deploying from Github

Page 37: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

aptly deb-s3

freight/sync to s3 packagecloud.io

Page 38: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 39: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 40: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 41: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

https://www.ssllabs.com/ssltest/

Page 42: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 43: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Safe Access to Production

Page 44: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

– Mark Burgess

“Every time someone logs onto a system interactively, they compromise everyone's

knowledge of that system”

Page 45: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Trust, but Verify.

Page 46: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

auditd + OSSEC

…and SELinux

http://stopdisablingselinux.com/

Page 47: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Controlled Access Protection Profilehttp://www.commoncriteriaportal.org/files/ppfiles/capp.pdf

Labeled Security Protection Profilehttp://www.commoncriteriaportal.org/files/ppfiles/lspp.pdf

National Industrial Security Program Operating Manual (NISPOM)http://www.fas.org/sgp/library/nispom.htm

Security Technical Implementation Guideshttp://iase.disa.mil/stigs/Pages/index.aspx

Page 48: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future
Page 49: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 50: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 51: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Start Small

Identify High Risks

Page 52: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Security Culture is People

Page 53: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock

Page 54: Why We Can't Have Nice Things, A Tale of Woe and a Hope For the Future

@petecheslock


Recommended