3 ms·
> A few years back (2015 or so) the average time from push-to-repo to AWS account compromise was 6 minutes. Surely that time has only gone down, and the number
by weinzierl 8y ago
> A few years back (2015 or so) the average time from push-to-repo to AWS account compromise was 6 minutes. Surely that time has only gone down, and the number of different credentials identified has gone up.
I don't doubt that a second and I'd like to use that as a quote. I'd like to be prepared if someone doubts it, so: Do you have a primary source for this?
- bostik 8y agoI'll need to find the talk I lifted it from. Not easy... but looks like downthread a sibling comment gives a relatively decent update about the current speed of compromise.
- bostik 8y agoAnswering myself: I think it was a BSides London talk. (Quite likely from 2017.) After doing a search, I don't think it was recorded. Hence, I can't provide a primary source. Sorry.
- kelnage 8y agoThis paper may be relevant to your interests: https://blog.acolyer.org/2019/04/08/how-bad-can-it-git-characterizing-secret-leakage-in-public-github-repositories/ https://blog.acolyer.org/2019/04/08/how-bad-can-it-git-chara...
- scraptor 8y agoBlog post summary: https://blog.acolyer.org/2019/04/08/how-bad-can-it-git-characterizing-secret-leakage-in-public-github-repositories/ https://blog.acolyer.org/2019/04/08/how-bad-can-it-git-chara... Source if blog is unavailable: https://www.ndss-symposium.org/wp-content/uploads/2019/02/ndss2019_04B-3_Meli_paper.pdf https://www.ndss-symposium.org/wp-content/uploads/2019/02/nd...
- frandroid 8y agoI thought that AWS nowadays is also feeding at the firehose and auto-disabling any of its keys it could find in a commit?