Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

2/25/2021
10:00 AM
Joseph Cortese
Joseph Cortese
Commentary
Connect Directly
LinkedIn
RSS
E-Mail vvv
50%
50%

How to Avoid Falling Victim to a SolarWinds-Style Attack

A multilayered, zero-trust security posture provides a better chance of fending off sophisticated supply chain attackers before it's too late.

2020 ended with shocking cybersecurity news: a massive supply chain attack involving SolarWinds, Microsoft, VMware, and others. The hackers went undetected for nearly a year, impacting many sensitive targets, from US federal departments to private sector companies, including security firms.

This is the most sophisticated supply chain attack we've ever seen. Experts will be uncovering the damage for months, perhaps even years, to come. And while we may never know its full scope, I'm sure of one thing: It won't be the last time we witness this style of attack.

Are We Entering a Zero-Trust Era?
As new information emerges, many organizations are renewing focus on their cybersecurity practices. They're asking: What controls can we put in place to protect against the next supply chain attack?

Related Content:

SolarWinds Attack Reinforces Importance of Principle of Least Privilege

Special Report: Understanding Your Cyber Attackers

New From The Edge: Fighting Fileless Malware, Part 3: Mitigations

The SolarWinds hackers started with small gaps, infiltrated ever more sensitive environments, and finally reached a broad point of access to deploy malware: the official software updates that organizations rely on for security. As a result, we may be entering into a zero-trust era where nothing — not even well-known programs — can be implicitly trusted. Even the US National Counterintelligence and Security Center's director is discussing zero trust.

In practice, a zero-trust approach may be challenging for organizations. That said, there are two ways to make real progress towards zero trust: implementing fundamental security measures and layering defenses.

Organizations can enact several controls immediately to do this. Here's what that could look like.

1. Audit Active Directories and Changes
Many organizations have implemented processes around Active Directory (AD), continuously monitoring, logging, and auditing everything that happens in their systems. These safeguards can help spot bad behavior, prepare for audits, and investigate future incidents. By ensuring a governing group reviews major changes, organizations stay aware of who makes changes — or requests changes — in their systems. The net effect is that it's easier to spot and stop a hacker.

2. Implement SIEM and Log Management
The system information mentioned above should feed into a security information and event management (SIEM) platform for logging and alerting. SIEM programs are vital for detecting incidents. While logging seems like basic advice, the truth is not all organizations keep logs, or if they do, monitor them closely. But when monitored regularly for anomalies — such as changes in network activity, payload size, or data movement — logs can expose unsafe behavior, unauthorized users, or other risks.

A single log may not mean anything. But multiple suspicious signs flagged by a SIEM can indicate that something malicious (or accidental but dangerous) is happening.

3. Fine-Tune Your DLP
Data loss prevention (DLP) tools are well known, but many organizations aren't using them fully. DLPs are sensitive and can send false positives, leading to alert fatigue. And because DLPs can be expensive and labor-intensive to manage, some organizations don't use them at all.

However, if it's configured and managed properly, a DLP can audit even trusted software or agents by monitoring activity such as how many files are written or what is created in memory. The key is to focus your DLP around a core set of tasks rather than a broad scope.

Of course, a DLP may not always catch hackers. But when layered with other cybersecurity measures, it's one of the best tools for providing visibility and limiting the impact of a breach.

4. Conduct Regular Penetration Testing
The SolarWinds hackers got their toehold via a developer environment. Now, imagine if penetration testing had identified that environment as vulnerable. The attack could've been prevented at the login stage.

Organizations should conduct regular penetration testing to understand their vulnerabilities from the perspective of a threat. This is not a "one and done" endeavor; I recommend quarterly testing. Continuously monitoring for threats, understanding your weaknesses, and remediating vulnerabilities are some of the best ways to prevent any kind of cyberattack, not just supply chain attacks. (Full disclosure: My employer offers penetration testing services. But my firm conviction in regular testing and assessments as a best practice is based on 20+ years of experience in cybersecurity.)

SolarWinds 2.0 — Only a Matter of Time
The SolarWinds hack was one of the worst of all time. Organizations and governments around the world should now understand that, like the proverbial call coming from inside the house, attacks can be perpetrated via trusted software and vendors.

While the steps above are critical areas of defense, any one of them alone won't stop an attacker. While another SolarWinds-style supply chain attack will happen in the future, prepared organizations stand a better chance of fending off attackers before things escalate. Hackers grow more sophisticated every day, and it's a constant battle to keep up. That's why organizations should take a multilayered approach inspired by a zero-trust security posture.

Joseph Cortese is an accomplished cybersecurity leader with a unique and extensive background in DevOps, cybersecurity, and zero-day exploration. He is a Certified Ethical Hacker of mobile, embedded, wireless, and web-enabled devices and has over 12 years of specialized cyber ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-20733
PUBLISHED: 2021-06-22
Improper authorization in handler for custom URL scheme vulnerability in ????????? (asken diet) for Android versions from v.3.0.0 to v.4.2.x allows a remote attacker to lead a user to access an arbitrary website via the vulnerable App.
CVE-2021-20734
PUBLISHED: 2021-06-22
Cross-site scripting vulnerability in Welcart e-Commerce versions prior to 2.2.4 allows remote attackers to inject arbitrary script or HTML via unspecified vectors.
CVE-2021-20735
PUBLISHED: 2021-06-22
Cross-site scripting vulnerability in ETUNA EC-CUBE plugins (Delivery slip number plugin (3.0 series) 1.0.10 and earlier, Delivery slip number csv bulk registration plugin (3.0 series) 1.0.8 and earlier, and Delivery slip number mail plugin (3.0 series) 1.0.8 and earlier) allows remote attackers to ...
CVE-2021-20736
PUBLISHED: 2021-06-22
NoSQL injection vulnerability in GROWI versions prior to v4.2.20 allows a remote attacker to obtain and/or alter the information stored in the database via unspecified vectors.
CVE-2021-20737
PUBLISHED: 2021-06-22
Improper authentication vulnerability in GROWI versions prior to v4.2.20 allows a remote attacker to view the unauthorized pages without access privileges via unspecified vectors.