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.

Threat Intelligence

7/11/2019
08:00 AM
Connect Directly
Twitter
RSS
E-Mail
100%
0%

Persistent Threats Can Last Inside SMB Networks for Years

The average dwell time for riskware can be as much as 869 days.

Dwell time — the amount of time a threat spends inside of a network before an organization discovers and removes it — has become a significant problem for small and midsize businesses (SMBs), according to a report released today by Infocyte.

The report, based on more than 339,000 accounts and behavioral logs for malicious activity, focuses on companies that have between 99 and 5,000 employees and annual revenue of up to $1 billion.

Dwell time for attacks with ransomware averaged 43 days, the report points out. On the other hand, average dwell time for all other persistent threats (non-ransomware) averaged 798 days, while dwell time for riskware – defined as unwanted applications, Web trackers, and adware – averaged a whopping 869 days.

According to Chris Gerritz, co-founder and chief product officer at Infocyte, 72% of SMBs had riskware and unwanted applications in their networks that took longer than 90 days to remove. While they were generally lower risk issues, the bigger takeaway is networks that fail to control riskware typically have a lower readiness to respond to high-priority threats when they are uncovered.

"We found that 60% of malware is identified by [antivirus] vendors using a generic signature – it doesn't specify what the issue is – so that's also why SMBs can't always understand the difference between high-priority and low-priority risks," Gerritz says.

The Infocyte report also explains why the dwell times of some of the persistent threats and riskware are well more than two years. For example, some of the active infections residing on the inspected systems are configured to sinkholed domains and pose no immediate threat, it says.

That said, one family of infections that researchers found traced back as long as a decade ago. While they didn’t pose a threat after a series of botnet operators were arrested in subsequent years, "it’s still surprising to find the malware still active on what appear to be protected endpoints so many years later," Gerritz says.

If continuous monitoring is not an option, Gerritz recommends that SMBs once a year bring in a third party to perform a "compromise assessment" at the same time they conduct a vulnerability assessment and pen tests.

"If companies can't afford threat analysis, they should at least get these tests done once a year," he says, so security pros can check for active malware with long dwell times that may have been sitting active in the network for many years.

Aaron Sherrill, a senior analyst at 451 Research, says Infocyte's research brings to light how most small companies lack standard security controls.

"They may not have updated technology, the signatures are not updated, the alerts and events are often ignored, or maybe they just don't have the bandwidth to do it all," Sherrill says. If companies can afford them, compromise assessments should be more than once-a-year events.

"Too often companies do these assessments as a checkbox item and they forget about it," Sherrill says. "Many of these threats are very sophisticated and are engineered not to be detected. Companies are at risk every minute of every day. What they really need is to have their networks continuously monitored."

Related Content:

 

Black Hat USA returns to Las Vegas with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions, and service providers in the Business Hall. Click for information on the conference and to register.

Steve Zurier has more than 30 years of journalism and publishing experience, most of the last 24 of which were spent covering networking and security technology. Steve is based in Columbia, Md. View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/1/2020
Ripple20 Threatens Increasingly Connected Medical Devices
Kelly Sheridan, Staff Editor, Dark Reading,  6/30/2020
DDoS Attacks Jump 542% from Q4 2019 to Q1 2020
Dark Reading Staff 6/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The Threat from the Internet--and What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15478
PUBLISHED: 2020-07-01
The Journal theme before 3.1.0 for OpenCart allows exposure of sensitive data via SQL errors.
CVE-2020-6261
PUBLISHED: 2020-07-01
SAP Solution Manager (Trace Analysis), version 7.20, allows an attacker to perform a log injection into the trace file, due to Incomplete XML Validation. The readability of the trace file is impaired.
CVE-2020-15471
PUBLISHED: 2020-07-01
In nDPI through 3.2, the packet parsing code is vulnerable to a heap-based buffer over-read in ndpi_parse_packet_line_info in lib/ndpi_main.c.
CVE-2020-15472
PUBLISHED: 2020-07-01
In nDPI through 3.2, the H.323 dissector is vulnerable to a heap-based buffer over-read in ndpi_search_h323 in lib/protocols/h323.c, as demonstrated by a payload packet length that is too short.
CVE-2020-15473
PUBLISHED: 2020-07-01
In nDPI through 3.2, the OpenVPN dissector is vulnerable to a heap-based buffer over-read in ndpi_search_openvpn in lib/protocols/openvpn.c.