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.

Operational Security //

Data Leakage

4/24/2018
08:05 AM
Scott Ferguson
Scott Ferguson
News Analysis-Security Now
50%
50%

SunTrust Investigation Shows Continuing Threats Posed by Insiders

SunTrust Banks investigate a possible data theft by an employee that could have exposed the personal information of 1.5 million customers. The incident shows insider threats remain a significant security issue.

A recent security incident at SunTrust Banks shows how dangerous an insider threat is to any enterprise.

On April 20, the Atlanta-based bank notified customers the company is investigating whether a former employee gained access to customers' personal data in an effort to sell or exploit that information, which included names, addresses, phone numbers and details associated with certain account balances.

Overall, SunTrust has told about 1.5 million of its customers about the incident, which is still under investigation. The company is also offering free credit monitoring and other services.

(Source: Flickr)
(Source: Flickr)

Although fairly large in scope, the information the former employee may have collected did not include some important and sensitive personal data such as social security numbers, account numbers, PINs, user IDs, passwords or driver's license information.

Even if the former employee did not manage to fully carry out this data breach, this type of incident is a reminder to enterprises of how dangerous insider threats can be to the network and the data that is stored within that infrastructure.

In fact, a Kaspersky Labs report released earlier this year, found that of 5,000 enterprises interviewed, more than half -- 52% -- reported employees constituted the greatest risk to security. However, in 46% of cases, the breach is due to negligent or careless behavior by an employee rather than a more malicious case, such as the one SunTrust is investigating.

Still, the insider threat remains a potential security dilemma.


The fundamentals of network security are being redefined -- don't get left in the dark by a DDoS attack! Join us in Austin from May 14-16 at the fifth-annual Big Communications Event. There's still time to register and communications service providers get in free!

"Inside threats are a very real and very significant problem, especially if you're dealing with an employee who may be disgruntled or who is otherwise motivated to cause the business as much harm as possible," Nathan Wenzler, chief security strategist at AsTech, a San Francisco-based security consulting firm, wrote in an email.

"It's an even harder problem to deal with if the employee was given legitimate, authorized access to critical data at any point as part of their normal job duties, as it gives them a level of familiarity with the data and relevant systems that an outside attacker may not have," Wenzler added.

In his note, Wenzler said while attacks by nation-states and advanced persistent threats (APTs) garner the headlines and attention of security pundits, it's the threat that lingers inside an organization that usually proves to be the most dangerous. (See APTs Are Rising in the East, Kaspersky Finds.)

"Collectively speaking, we can't keep only looking outward to identify threats," Wenzelr wrote. "Sometimes, the most dangerous attackers are the ones we already know and have brought in to our organizations."

Related posts:

— Scott Ferguson is the managing editor of Light Reading and the editor of Security Now. Follow him on Twitter @sferguson_LR.

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/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
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-32598
PUBLISHED: 2021-08-05
An improper neutralization of CRLF sequences in HTTP headers ('HTTP Response Splitting') vulnerability In FortiManager and FortiAnalyzer GUI 7.0.0, 6.4.6 and below, 6.2.8 and below, 6.0.11 and below, 5.6.11 and below may allow an authenticated and remote attacker to perform an HTTP request splitting...
CVE-2021-32603
PUBLISHED: 2021-08-05
A server-side request forgery (SSRF) (CWE-918) vulnerability in FortiManager and FortiAnalyser GUI 7.0.0, 6.4.5 and below, 6.2.7 and below, 6.0.11 and below, 5.6.11 and below may allow a remote and authenticated attacker to access unauthorized files and services on the system via specifically crafte...
CVE-2021-3539
PUBLISHED: 2021-08-04
EspoCRM 6.1.6 and prior suffers from a persistent (type II) cross-site scripting (XSS) vulnerability in processing user-supplied avatar images. This issue was fixed in version 6.1.7 of the product.
CVE-2021-36801
PUBLISHED: 2021-08-04
Akaunting version 2.1.12 and earlier suffers from an authentication bypass issue in the user-controllable field, companies[0]. This issue was fixed in version 2.1.13 of the product.
CVE-2021-36802
PUBLISHED: 2021-08-04
Akaunting version 2.1.12 and earlier suffers from a denial-of-service issue that is triggered by setting a malformed 'locale' variable and sending it in an otherwise normal HTTP POST request. This issue was fixed in version 2.1.13 of the product.