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.

Comments
Uber's Security Slip-ups: What Went Wrong
Newest First  |  Oldest First  |  Threaded View
ebyjeeby
ebyjeeby,
User Rank: Strategist
12/14/2017 | 5:20:42 PM
scramble data
Uber should have scrambled the data before it went into the test environment.
jdub161
jdub161,
User Rank: Apprentice
11/30/2017 | 11:14:16 PM
What went wrong 'after the incident'
Great article Kelly, but what went wrong after the incident?

Understand that it's critical to understand what went wrong to cause the incident, but I feel it would be very insightful to understand who made the decision not to disclose the incident.  

Where did that decision occur?  At Uber's Board, CEO, Legal team.  Even if that decision was left to the CISO then that's actually a damning indictment on their delegation of authority. 

I understand that Uber want to offer up the CISO as the official 'scapegoat' but wow if the standard response to a major data breach is 'sack the CISO' then in not to long we will be faced with an understaffed industry having to fill strategic leadership positions potentially with highly skilled cyber security people that may not have had the training and experience to work at the strategic C suite level.

Jason 


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
Building the SOC of the Future
While an attacker just needs to find one vulnerability to get in to the network, the defender has to look everywhere. Defenders have to identify, disrupt, and stop attacks in the short period of time between when an attacker gets in and causes damage. One way is a security operations center to get that "all the time" coverage. What's Inside: --AI and cybersecurity response --Automation --Proctive threat hunting --Next-gen SIEM
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-22493
PUBLISHED: 2022-10-07
IBM WebSphere Automation for Cloud Pak for Watson AIOps 1.4.2 is vulnerable to cross-site request forgery, caused by improper cookie attribute setting. IBM X-Force ID: 226449.
CVE-2022-30613
PUBLISHED: 2022-10-07
IBM QRadar SIEM 7.4 and 7.5 could disclose sensitive information via a local service to a privileged user. IBM X-Force ID: 227366.
CVE-2022-34308
PUBLISHED: 2022-10-07
IBM CICS TX 11.1 could allow a local user to cause a denial of service due to improper load handling. IBM X-Force ID: 229437.
CVE-2022-36772
PUBLISHED: 2022-10-07
IBM InfoSphere Information Server 11.7 could allow an authenticated user to obtain sensitive information that should only be available to a privileged user.
CVE-2022-41291
PUBLISHED: 2022-10-07
IBM InfoSphere Information Server 11.7 does not invalidate session after logout which could allow an authenticated user to impersonate another user on the system. IBM X-Force ID: 236699.