Download as PDF, PPTX
Uploaded byDinis Cruz
Using security to drive chaos engineering
This document discusses chaos engineering and how it relates to security testing. Some key points: - Chaos engineering involves experimenting on systems by introducing variables like server crashes or network failures to test how systems respond to turbulent conditions. This helps build confidence in systems' availability. - Security testing can be viewed as a form of chaos engineering, as security tests intentionally introduce "changes" like vulnerabilities to verify systems' security and resilience. - To test systems effectively, experiments should be run continuously in production environments and introduce real-world events while minimizing impact. This helps validate that systems can withstand attacks and changes in production. - Properties of resilient, secure systems include availability, ability to handle failures, validating all
More Related Content
Similar to Using security to drive chaos engineering
Using security to drive chaos engineering
- 1. Using Security todrive Chaos Engineering Dinis Cruz, CISO 22 Feb 2018
- 2.
- 3. Chaos Engineering Building Confidence inSystem Behaviour through experiments
- 5.
- 7.
- 8. Chaos Engineering is abouttrying controlled changes to observe system availability deviation
- 9. Chaos Engineering is specificallyabout Availability
- 10. Chaos Engineering is carefullyinjecting harm into our systems to test the system’s ability to respond to it.
- 11. Chaos Engineering is thediscipline of experimenting on a distributed system in order to build confidence in the system’s capability to withstand turbulent conditions in production.
- 12. Chaos Engineering is Limitedscope, continuous, disaster recovery
- 13.
- 14. 1. Start bydefining ‘steady state’ as some measurable output of a system that indicates normal behavior. 2. Hypothesize that this steady state will continue in both the control group and the experimental group. 3. Introduce variables that reflect real world events like servers that crash, hard drives that malfunction, network connections that are severed, etc. 4. Try to disprove the hypothesis by looking for a difference in steady state between the control group and the experimental group. Chaos in practice - 4 experiments http://principlesofchaos.org/
- 15. 1.Build a Hypothesisaround Steady State Behavior 2.Vary Real-world Events 3.Run Experiments in Production 4.Automate Experiments to Run Continuously 5.Minimize Blast Radius Advanced Principles http://principlesofchaos.org/
- 16. the idea that“Chaos engineering is not Testing” is caused by the TDD tragedy
- 17. Chaos Engineering is testing thedifferent are the test abstractions and the extra random layer
- 18.
- 19. Cyber Security isa ‘change generation factory’
- 20. Security testing arechaos creators
- 21. I have beencalled Director of chaos :)
- 22. Do you understandwhat is going on in your network?
- 23. Biggest threat isnot the issue, but is not having visibility
- 24. When do youknow about security incidents? (or changes)
- 25. You need toknow what the attackers are doing on your system
- 26. If you don’tknow what is on the pentest report, you have a big problem (your SOC team should be able to tell you)
- 27. Best Security modelis one based on the attacker making a mistake (i.e. a change)
- 28. Use risks tounderstand reality and to make the business owners responsible for their decisions
- 29. Use Threat Modelsto understand how your system works and to document it
- 30. Use tests toreplicate known behaviours and simulate changes (with and without random events)
- 31. Properties of resilient andsecure systems
- 32.
- 33. Plan for Failure Abilityto sustain failures
- 34. Validate and Sanitise allrequests
- 35. Authenticate and Authorise allrequests
- 36. Reduce capabilities and featuresgracefully
- 37.
- 38. Have error budgets (from Google SRE)
- 39. Are easy tochange
- 40. Are easy torefactor (make changes with confidence)
- 41. Pushes to production happen minutes (fully tested and 100x a day (if needed))
- 42. The bigger they getthe faster they go (it is smooth and safe to make changes)
- 43. Have 99% changecoverage
- 44.
- 45. It is notabout test code coverage
- 46. What matters is changecoverage
- 47. If you makechanges and they are not detected
- 48. you are justmaking random changes
- 49. you are an agentof chaos
- 50. Every change youmake has to have a respective test change (much better pair programming model)
- 51.
- 52. If a serveror app misbehaves when do you know about it?
- 53. If your serversstart running 30% slower what happens to your application?
- 54. If your serversfail to reboot after a patch, what happens to your system?
- 56. Malicious or apibreaking NuGet package
- 57. If a serveron your cloud is mining bitcoins would you know about it
- 58. is chaos =change?
- 59. Chaos Engineering is modernchange management
- 60. Chaos Engineering is theprogramatic introduction of changes
- 61.
- 62. should it thenbe called Digital Change Engineering?
- 63.
- 64. We are recruitingat Photobox Group Security
- 67.