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

9/2/2020
11:30 AM
Jai Vijayan
Jai Vijayan
Slideshows
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

5 Tips for Triaging Risk from Exposed Credentials

Not all exposed usernames and passwords present a threat. Here's how to quickly identify the ones that do.
Previous
1 of 6
Next

With more than 15 billion exposed credentials currently available online, security teams need a formal process for quickly identifying the ones that might pose a threat to their organizations.

A study that Digital Shadows conducted earlier this year found that two-thirds of the credentials available on Dark and Clear Web markets are duplicates, and 80% of them are in cleartext format. Many are employee credentials that pose a significant risk to organizations in the hands of cybercriminals.

It's the security team's role to assess all of their exposed employee credentials to ascertain whether those credentials could enable attackers to take over accounts and gain access to internal systems, says Michael Marriott, manager of product marketing at Digital Shadows.

Security admins need to determine whether an exposed credential poses a risk to the business or whether it is no longer a threat because it is associated with a user who has left the organization, has expired, or another reason. Given that billions of credentials are exposed every year, this can be time-consuming, he says.

"This is a real challenge, and a practical solution requires a methodical approach that is less whack-a-mole," Marriott says. "Security teams spend a lot of time reassessing the same credential pair and wasting their time. If the security team has reset the password of a user who has had their credential breached, there is no need to do so every time that password resurfaces."

The following are five tips for triaging the risk associated with breached credentials.

 

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio
 

Recommended Reading:

Previous
1 of 6
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
vantinc
50%
50%
vantinc,
User Rank: Apprentice
9/5/2020 | 5:00:11 AM
Tips for Triaging Risk from Exposed Credentials
In my experience, breaches are often the result of lack of cybersecurity readiness, early detection, or timely response. You need to take a holistic approach to cybersecurity – that means addressing the before, during, and after stages of a potential compromise to prevent it from becoming a breach.
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
WannaCry Has IoT in Its Crosshairs
Ed Koehler, Distinguished Principal Security Engineer, Office of CTO, at Extreme Network,  9/25/2020
Safeguarding Schools Against RDP-Based Ransomware
James Lui, Ericom Group CTO, Americas,  9/28/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-26120
PUBLISHED: 2020-09-27
XSS exists in the MobileFrontend extension for MediaWiki before 1.34.4 because section.line is mishandled during regex section line replacement from PageGateway. Using crafted HTML, an attacker can elicit an XSS attack via jQuery's parseHTML method, which can cause image callbacks to fire even witho...
CVE-2020-26121
PUBLISHED: 2020-09-27
An issue was discovered in the FileImporter extension for MediaWiki before 1.34.4. An attacker can import a file even when the target page is protected against "page creation" and the attacker should not be able to create it. This occurs because of a mishandled distinction between an uploa...
CVE-2020-25812
PUBLISHED: 2020-09-27
An issue was discovered in MediaWiki 1.34.x before 1.34.4. On Special:Contributions, the NS filter uses unescaped messages as keys in the option key for an HTMLForm specifier. This is vulnerable to a mild XSS if one of those messages is changed to include raw HTML.
CVE-2020-25813
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, Special:UserRights exposes the existence of hidden users.
CVE-2020-25814
PUBLISHED: 2020-09-27
In MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4, XSS related to jQuery can occur. The attacker creates a message with [javascript:payload xss] and turns it into a jQuery object with mw.message().parse(). The expected result is that the jQuery object does not contain an <a> ...