January 23, 2020
I often get asked to share examples of the types of alerts we send to clients. I work on the front lines here at Digital Shadows as a Sales Engineer, and I see a wide variety of alerts being sent to our clients on a daily basis. Most, thankfully, require simple but nonetheless necessary remediation – a minor settings tweak or an email to another department informing them that the Tweet they just posted was a little too forthcoming with sensitive company information.
Others take a little more work to resolve.
In this blog series, we’ll share some tales from the front lines – keeping client names anonymous, of course. We’ll investigate some of SearchLight’s most impactful findings, and more importantly, shed light on how our customers are using the alerts we provide them to make a tangible impact on the security of their organizations.
Today’s tale is one of data leakage detection and third-party exposure. It all began in our internal analysis platform, the area where our analysts triage mentions of customer assets before they even become alerts in a customer portal. Initially, this looked like a routine commit to GitHub by a company email address – a common occurrence for which there is a simple remediation. All it takes is a simple Google search for “GitHub sensitive data” to get an idea of the scale of the problem – you’ll see a variety of frenzied StackExchange (et al) posts looking for advice and reports by security commentators on the latest large organization to be compromised after inadvertently leaving the keys to the kingdom publicly available.
Support the originator by clicking the read the rest link below.
