Earlier quoted context omitted.
Author here :) Endgame exploits/abuses features. If it was a bug, I'd work with AWS to solve the problem, but with abusing features - that would result in years of unsatisfied feature requests. This should push the issue along. >...and it's not even a hacking tool! It can be used to backdoor resources to rogue accounts, so I'd say it's a hacking tool and can/should be used on penetration tests. I'd certainly use it o…
So did you just put this out there or did you give AWS Security peeps a week or two notice?
Show HN: Endgame – An AWS Pentesting tool to backdoor or expose AWS resources
41–50 of 101 posts
Re: Show HN: Endgame – An AWS Pentesting tool to backdoor or expose AWS resources
#42Earlier quoted context omitted.
Author here :) Endgame exploits/abuses features. If it was a bug, I'd work with AWS to solve the problem, but with abusing features - that would result in years of unsatisfied feature requests. This should push the issue along. >...and it's not even a hacking tool! It can be used to backdoor resources to rogue accounts, so I'd say it's a hacking tool and can/should be used on penetration tests. I'd certainly use it o…
I'm impressed you were able to get your employer (Salesforce) to actually let you publish this under their organization. Kudos to that.
Not to mention companies such as Google, Netflix and Mozilla all release security tools just like this.
Re: Show HN: Endgame – An AWS Pentesting tool to backdoor or expose AWS resources
#43Can someone explain why you'd ever want to run this in the non-dryrun mode? I understand that if you have these problems you've already effectively granted those permissions anyway but actually executing them before someone finds them lowers the bar quite a bit for other baddies to attack.
Re: Show HN: Endgame – An AWS Pentesting tool to backdoor or expose AWS resources
#44Make sure you check AWS' pentesting policy [0]. [0]: https://aws.amazon.com/security/penetration-testing/
Also the pentesting policy explicitly states that customers can pentest without approval.
Re: Show HN: Endgame – An AWS Pentesting tool to backdoor or expose AWS resources
#45Can someone explain why you'd ever want to run this in the non-dryrun mode? I understand that if you have these problems you've already effectively granted those permissions anyway but actually executing them before someone finds them lowers the bar quite a bit for other baddies to attack.
Re: Show HN: Endgame – An AWS Pentesting tool to backdoor or expose AWS resources
#46Re: Show HN: Endgame – An AWS Pentesting tool to backdoor or expose AWS resources
#47Also I guess it might have been a not so nice from an almost direct competitor of AWS - salesforce - to publish something like that. Salesforce owns heroku.
Re: Show HN: Endgame – An AWS Pentesting tool to backdoor or expose AWS resources
#48Earlier quoted context omitted.
dry run should be the default, and for you to actually do damage, you should explicitly run with a flag like `--commit` or `--deploy-evil-payload "yes I am certain of this"`
Dry run as default is a good idea. I'll open a GitHub issue for that. FWIW, if you run `endgame smash` with `--service all`, then it spits out a huge "WARNING" in ASCII art with an explanation and a confirmation prompt. But I agree, we should have dry-run on by default.
Re: Show HN: Endgame – An AWS Pentesting tool to backdoor or expose AWS resources
#49Re: Show HN: Endgame – An AWS Pentesting tool to backdoor or expose AWS resources
#50Can someone explain why you'd ever want to run this in the non-dryrun mode? I understand that if you have these problems you've already effectively granted those permissions anyway but actually executing them before someone finds them lowers the bar quite a bit for other baddies to attack.