[go: up one dir, main page]

Skip to content
This repository has been archived by the owner on Apr 3, 2019. It is now read-only.
/ ChaoSlingr Public archive

ChaoSlingr: Introducing Security into Chaos Testing

License

Notifications You must be signed in to change notification settings

Optum/ChaoSlingr

Repository files navigation

FileImage

Thanks for your interest in Optum’s ChaoSlingr project! Unfortunately, we have moved on and this project is no longer actively maintained or monitored by our Open Source Program Office. This copy is provided for reference only. Please fork the code if you are interested in further development. The project and all artifacts including code and documentation remain subject to use and reference under the terms and conditions of the open source license indicated. All copyrights reserved.

ChaoSlingrLogo

ChaoSlingr: Introducing Security into Chaos Testing

ChaoSlingr is a Security Chaos Engineering Tool focused primarily on the experimentation on AWS Infrastructure to bring system security weaknesses to the forefront.

Security is chaotic and the industry has traditionally put emphasis on the importance of preventative security control measures and defense-in-depth where-as our mission is to drive new knowledge and perspective into the attack surface by delivering proactively through detective experimentation.

With so much focus on the preventative mechanisms we never attempt beyond one-time or annual pen testing requirements to actually validate whether or not those controls actually are performing as designed.

Our mission is to address security weaknesses proactively, going beyond the reactive processes that currently dominate traditional security models.

ChaoSlingr Diagram

Contributing to the Project

The ChaoSlingr team is open to contributions to our project. For more details, see our Contribution Guide and join the discussion on Slack.

Original Contributors

  • Aaron Rinehart (@AARonSTeneo)
  • Grayson Brewer (@egb2016)
  • Josh Gorton (@Jgorton612928)
  • Amy L Schoen (@amyschoen)
  • Mehul Shah (@mehul0sejal)
  • Shawn Ertel (@SHA34)
  • Samuel W Roden (@sbroden)
  • Joseph P Niquette (@Joeyn414)
  • Stephen M Klugherz (@Smklugherz)
  • Alex R Nielsen (@anielse2)
  • Arun K Singh (@Oarusoft)
  • Rajitha Ramasayam (@rajitha-ramasayam)
  • David W Cloninger (@dcloninger)
  • Mike Zhou (@MichaelLiZhou)
  • Dan Brock (@Bluephish)

Special Thanks

  • John Garner
  • Sean O'Neil
  • Patrick E Bergstrom (@IAmPatrickB)
  • Scott Maciej (@sgm44)
  • Magnus J Hedemark (@magnus919)
  • Kevin Nelson (@pkn4645)
  • Sridhar R
  • Michael R Baker
  • Randy Olinger
  • David S Hanauer
  • Ryan Wencl
  • Bryce Ashey
  • RJ Seibert (@alephnot0)
  • Angela Mulcahy
  • Joseph C Kollasch
  • Andrew R Brennan
  • Kyle J Erickson
  • Daniel Henry
  • Brandon Jeup
  • Robert J Dufek
  • Heather Mickman
  • Barbara J Doenges
  • Hugh Smith
  • Tomo Lennox
  • Norman O'Neal
  • Henry B Kono
  • Zachary S Brown (@ZacharySBrown)
  • Nicholas S Kerling
  • Jeff Sivori
  • Marcus Maday
  • Joel E Carlson (@joelelmercarlson)
  • Shelby R Erickson

About

ChaoSlingr: Introducing Security into Chaos Testing

Topics

Resources

License

Code of conduct

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published