-
Notifications
You must be signed in to change notification settings - Fork 426
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
24 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
# Presentation Proposal: DevSecOps takeaways from Hacking into Google's Network for $133,337 | ||
|
||
## Members | ||
Ayub Atif (aatif@kth.se) | ||
GitHub: [ayubatif](https://github.com/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. | ||
The source is [Hacking into Google's Network for $133,337](https://www.ezequiel.tech/2020/05/rce-in-cloud-dm.html) by Ezequiel Pereira, which I followed up on from a comment | ||
by @monperrus on the Devops and Security issue. | ||
|
||
See outline for more detail. | ||
|
||
## Outline | ||
* What is Google Cloud Deployment Manager? | ||
* Short reminder of the DevSecOps concept. | ||
* What sort of approach is taken to find the vulnerabilties? (multiple options via audience interaction) | ||
* Where were the actual vulnerabilities? | ||
* Relating the vulnerabilities to other DevOps platforms you may work on. | ||
* Challenges and compromises in your DevSecOps solutions. | ||
* Takeaway introduction to bug bounty programs. | ||
|
||
The contents may be altered to fit the strict presentation timeframe, but the core content should remain. |