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
Newest First  |  Oldest First  |  Threaded View
I 'Hacked' My Accounts Using My Mobile Number: Here's What I Learned
Nicole Sette, Director in the Cyber Risk practice of Kroll, a division of Duff & Phelps,  11/19/2019
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-2079
PUBLISHED: 2019-11-22
A cross-site request forgery (CSRF) vulnerability in the Activity module 6.x-1.x for Drupal.
CVE-2019-11325
PUBLISHED: 2019-11-21
An issue was discovered in Symfony before 4.2.12 and 4.3.x before 4.3.8. The VarExport component incorrectly escapes strings, allowing some specially crafted ones to escalate to execution of arbitrary PHP code. This is related to symfony/var-exporter.
CVE-2019-18887
PUBLISHED: 2019-11-21
An issue was discovered in Symfony 2.8.0 through 2.8.50, 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7. The UriSigner was subject to timing attacks. This is related to symfony/http-kernel.
CVE-2019-18888
PUBLISHED: 2019-11-21
An issue was discovered in Symfony 2.8.0 through 2.8.50, 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7. If an application passes unvalidated user input as the file for which MIME type validation should occur, then arbitrary arguments are passed to the underlying file command. T...
CVE-2019-18889
PUBLISHED: 2019-11-21
An issue was discovered in Symfony 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7. Serializing certain cache adapter interfaces could result in remote code injection. This is related to symfony/cache.