It does not immediately mean that. If it were AWS, there are ten thousand things PagerDuty could have done wrong: lost an access key, made an IAM role too permi

It does not immediately mean that. If it were AWS, there are ten thousand things PagerDuty could have done wrong: lost an access key, made an IAM role too permissive and lost access to the instance, turned off key-based ssh, made the ports open to the public, hard coded credentials, simply used a weak password for their console, not enabled TFA, lost the root credentials somewhere, allowed a privilege escalation by giving one key the ability to create more keys and attach permissions. The list goes on. Plug: I'm working on an open-source and hosted project called CloudSploit that can scan for these kinds of things. Check it out at https://cloudsploit.com https://cloudsploit.com