Presentation Proposal: DevSecOps takeaways from Hacking into Google's Network for $133,337 #1053
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Members
Ayub Atif (aatif@kth.se)
GitHub: ayubatif
Topic
I want to use the report for a potential Remote Code Execution attack in Google Cloud Deployment Manager in May 2020 to give an overview of Google Cloud Deployment, the security vulnerabilities observed, and the approach to finding such a bug. I follow this up with key takeaways relevant to the DevSecOps concept. The source is Hacking into Google's Network for $133,337 by Ezequiel Pereira, which I followed up on from a comment by @monperrus on the Devops and Security issue #18.
See outline for more detail.
Outline
The contents may be altered to fit the strict presentation timeframe, but the core content should remain.