Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/Optum/ChaoSlingr
ChaoSlingr: Introducing Security into Chaos Testing
https://github.com/Optum/ChaoSlingr
deprecated-repo
Last synced: 29 days ago
JSON representation
ChaoSlingr: Introducing Security into Chaos Testing
- Host: GitHub
- URL: https://github.com/Optum/ChaoSlingr
- Owner: Optum
- License: apache-2.0
- Archived: true
- Created: 2019-03-27T13:52:02.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2019-04-03T15:41:37.000Z (over 5 years ago)
- Last Synced: 2024-08-03T21:02:00.929Z (4 months ago)
- Topics: deprecated-repo
- Language: Python
- Homepage:
- Size: 758 KB
- Stars: 66
- Watchers: 22
- Forks: 25
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
- awesome-chaos-engineering - ChaoSlingr - Introducing Security Chaos Engineering. ChaoSlingr focuses primarily on the experimentation on AWS Infrastructure to proactively instrument system security failure through experimentation. (3. Fault Injection / Security)
README
![FileImage](./docs/Files.png)
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](./docs/ChaoSlingrLogo.jpg)
# 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](./docs/ChaoSlingr_designAndArchitecture.jpg?raw=true "ChaoSlingr Diagram")
## Contributing to the Project
The ChaoSlingr team is open to contributions to our project. For more details, see our [Contribution Guide](CONTRIBUTING.md) and join the discussion on [Slack](https://chaoslingr.slack.com).
## 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