Securing GitHub doesn't have to be hard

It was the early morning of October 23rd. Tracy Kelpman, lead security engineer at her company, was starting her day like any other. She opened her laptop and went to check her email. But something was different. Her inbox was filled with messages from concerned users.

Someone had hacked into their corporate GitHub organization and taken control of several popular repositories at the company. They had deleted all of the code and replaced it with a message that said "Hello, world!".

Tracy quickly realized that this was a serious security incident. She immediately started investigating. She checked the activity logs and saw that the hacker had gained access to their codebases due to a lack of configured access controls.

Tracy used ThreatKey to perform a root cause analysis. She was able to quickly identify the vulnerable repositories and the exact configuration setting that the hacker had exploited. She also found that the hacker had gained access to other repositories that were configured with the same vulnerable setting.

With this information, Tracy was able to quickly fix the security hole and restore the deleted code. She also alerted the others at her company that were using the vulnerable repositories, so that they could fix the security hole on their repositories as well using ThreatKey.

Thanks to Tracy's quick thinking and thorough usage of ThreatKey, a major incident was avoided.