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.

Attacks/Breaches

9/26/2016
10:00 AM
Gary Newe
Gary Newe
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
50%
50%

What The WADA Hack Proves About Today's Threat Landscape

Fancy Bear's initial release of data on four top American athletes reminds us all to reassess our risks.

The World Anti-Doping Agency (WADA) recently released the name of the hacker group that exposed sensitive and personal information on four top American athletes, Serena and Venus Williams, Simone Biles, and Elena Delle Donne, followed later by several international athletes.

As we hear more about this kind of attack, we need to take a step back and at least give credit to the names these people choose for their groups — in this case, Fancy Bear. You can't make this stuff up.

This wasn't a hack for financial gain, it wasn't for credit card numbers or Social Security details. The decision to first release information solely on U.S. athletes was simply to call into question their reputation, and that of the U.S. Olympic Committee, in direct response to the International Olympic Committee's decision to ban so many Russian athletes because of alleged "state sponsored" doping in Russia.

What's interesting about this attack is that the target isn't a group you would associate with being a likely target. WADA isn't an organization you would at first glance think would hold vast amounts of personal, health-related information on anyone, let alone some of the best athletes in the world. What's also interesting is that the organization may not have seen the risk and applied relevant safeguards.

Know What You Need to Protect
What can we learn from this event? It's clear that you have to know what you're trying to protect. In this case, it was the personal data of these athletes, their drug tests, and other medical information. Once you have identified the actual data you need to protect, you need to work out the "how," which is no easy task. In some cases, people do what they've always done and rely on the same old risk mitigations they've always used. In many cases, these safeguards haven't evolved with the times and can't protect against today's dynamic threat landscape.

Another fundamental mistake is to assume that you won't be attacked. Lots of IT security marketing centralizes on the message “you will be attacked” or "it's not if, but when," and so on. While this sounds like FUD (fear, uncertainty, and doubt), it is beginning to ring true. It seems that no one is safe anymore. From a personal security perspective, it's easy for your details and identity to be stolen. From a professional point of view, it seems that any company or organization is fair game now.

So, it really is time to reassess your risk and review your current protections. Are they ready to take on today's threats and attacks? Can they stand up to blended attacks? Can they protect data, applications, and identities, or do they still only protect your network?

We are going to continue to see more releases like Fancy Bear's until we step up our security and rethink what our security policies are and what they should be. 

Related Content:

Gary Newe joined F5 in 2007 and serves as the companies' director of systems engineering. His role includes working with channel and SI partners, as well as working directly with larger customers on a range of F5 security solutions. Gary is a certified Information Systems ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
7 Tips for Infosec Pros Considering A Lateral Career Move
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2020
For Mismanaged SOCs, The Price Is Not Right
Kelly Sheridan, Staff Editor, Dark Reading,  1/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
IT 2020: A Look Ahead
Are you ready for the critical changes that will occur in 2020? We've compiled editor insights from the best of our network (Dark Reading, Data Center Knowledge, InformationWeek, ITPro Today and Network Computing) to deliver to you a look at the trends, technologies, and threats that are emerging in the coming year. Download it today!
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-3154
PUBLISHED: 2020-01-27
CRLF injection vulnerability in Zend\Mail (Zend_Mail) in Zend Framework before 1.12.12, 2.x before 2.3.8, and 2.4.x before 2.4.1 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via CRLF sequences in the header of an email.
CVE-2019-17190
PUBLISHED: 2020-01-27
A Local Privilege Escalation issue was discovered in Avast Secure Browser 76.0.1659.101. The vulnerability is due to an insecure ACL set by the AvastBrowserUpdate.exe (which is running as NT AUTHORITY\SYSTEM) when AvastSecureBrowser.exe checks for new updates. When the update check is triggered, the...
CVE-2014-8161
PUBLISHED: 2020-01-27
PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to obtain sensitive column values by triggering constraint violation and then reading the error message.
CVE-2014-9481
PUBLISHED: 2020-01-27
The Scribunto extension for MediaWiki allows remote attackers to obtain the rollback token and possibly other sensitive information via a crafted module, related to unstripping special page HTML.
CVE-2015-0241
PUBLISHED: 2020-01-27
The to_char function in PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 allows remote authenticated users to cause a denial of service (crash) or possibly execute arbitrary code via a (1) large number of digits when processing a numeric ...