Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Behind Closed Doors: Managing Passwords in a Da...

Behind Closed Doors: Managing Passwords in a Dangerous World

Noah Kantrowitz

April 27, 2016
Tweet

More Decks by Noah Kantrowitz

Other Decks in Technology

Transcript

  1. – Jerome Saltzer, Communications of the ACM “Every program and every

    privileged user of the system should operate using the least amount of privilege necessary to complete the job.”
  2. $ echo "P@s5wd" > secret.txt $ git commit -a -m

    "yolo!" $ git push origin master To [email protected]:me/myapp.git f35a8c0..c2f0adf master -> master
  3. Surfaces • Brute force • Code leak • Backup leak

    • Traversal
 • Code exec • Root exec • Laptop theft • Higher power
  4. Identity • Who are you? • Who am I? •

    Why are we in this
 hand basket?
  5. HVAC # local_settings.py import hvac c = hvac.Client( url='https://vaultserver:8200') DATABASES

    = { 'default': { # Other settings ... 'PASSWORD': c.read('secret/dbpass') } }
  6. Chef # recipes/myapp.rb execute 'sneaker unpack ...' template 'local_settings.py' do

    # Other properties ... variables pw: citadel['pw'] end
  7. In Summary • Check your privilege and audit trail •

    Pick types and temperatures • Think about attack surfaces • Have a disaster plan