Law Enforcement Data “Blue Leaker”: A Danger or a Public Service?
- By Nilesh Dherange
- Sep 14, 2020
The recent release of a massive cache of sensitive Law Enforcement data has been in the news recently. The trove of roughly 270 gigabytes of data posted to the Denial of Secrets website has been referred to as “BlueLeaks.” This is just the latest in a long series of data breaches against government agencies that have revealed sensitive information to the public at large. The collection includes over ten years’ worth of sensitive data and has been verified by the National Fusion Centers Association. Data leaked includes images of people under investigation, sensitive government and law enforcement reports, banking information, and Personally Identifiable Information (PII).
An attacker’s motivation to breach a government source and reveal what he or she finds varies widely. Maybe it’s political – someone trying to further a specific party agenda. Perhaps it’s an activist trying to achieve an explicit civic goal. It could even be a group of rival state actors looking to alter the balance of power for political, diplomatic, or economic gain. There are also criminal organizations with their own goals in mind. Whatever the motive, as information security professionals our role is to try and prevent these breaches from happening in the first place, and to mitigate the damage as much as possible when they do.
The data released by Denial of Secrets was acquired during a breach of a “Fusion Center” operated by Netsential, a web development firm based in Houston, Texas. Fusion centers such as this serve as a clearing house to disseminate law enforcement and public safety information between partners. A Fusion Centers’ typical partners are law enforcement and safety organizations at the federal, state, local, county and tribal levels.
While the timing of this breach makes it especially relevant (during this period of civil tension), it is only unusual in character. Breaches in both the Public and Private sectors that reveal personal, business, medical, and financial intellectual property data result from similar ploys. Attackers rely on comparable tools and techniques to breach any network perimeter. While the details of the Netsential breach are not public, they did confirm that the leak was most likely caused by a compromised user account that allowed the attackers to upload malware. That, in turn, led to the data exfiltration.
The attack relied on common tactics. The techniques used to prevent them are also common.
User education is often the easiest and most logical first step. This is especially true with our current environment. While much of the workforce has gone remote since the early months of 2020, how many organizations have updated their policies and process to adapt to this shift in attack surface? How many users can identify the common attacker techniques used to steal credentials or compromise home systems? When was the last time the workforce was tested against the kinds of real-world attack scenarios they’re likely to confront?
What about user authentication? How many organizations are implementing multi-factor authentication for every user login? While there have been some attacks against MFA systems, they have proven to be much more effective than simple passwords while adding only a slight inconvenience. In fact, Google reported in 2018 that none of their 85 thousand users had been phished since implementing a hardware based MFA scheme in early 2017.
We can’t tell from the publicly revealed information whether Multi Factor Authentication or improved education would have prevented this particular breach. It is possible that Netsential already had multi-factor authentication in place and the users had received recent training, leading the attackers to get in through some other vector, but these are still Best Practices and worth implementing.
The organization’s Information Security team and the Security Operations Center team will play a vital role in mitigating a breach. When an attacker manages to compromise a user or system in the environment, they still need to identify their primary target, traverse laterally to it, and exfiltrate their target data from the network.
With the right tools and training, the SOC can often break the attack chain and prevent the malicious actors from completing their mission. The challenge is identifying an attack early enough in the cycle to mitigate the effect. Unfortunately, this task has been made more complex by the shift to more remote workers and the ongoing moves to third party and SaaS applications.
Even with the latest generation of tools in place, such as AI-based advanced security analytics, it can be difficult for an organization to see into the partner environments, SaaS applications, third party vendors, contractors, and more. It is hard to assure they are also up to the same security standards the organization has set for itself.
Difficult, but not impossible. By deploying the most effective tools, educating users, and requiring partner organizations follow the same best practices, it is possible to manage risk in our rapidly evolving environments. We may never reach a perfect 100% effective security solution, but we can keep raising the bar and reduce the number and severity of security incidents.