14.1 C
London
Saturday, September 23, 2017
Home Tags Incident

Tag: Incident

Since deleted, post gave public and private key for Adobe incident response team.
The SEC alerted the financial world that its public filing system had been hacked in 2016, an incident that may have resulted in insider trades based on the stolen information.
Container security startup delivers new release adding an incident explorer feature to help detect threats.
Months after acquiring automated incident response specialist Hexadite, the company has integrated the former startup's technology into Windows Defender ATP.
After plea deal, DOJ says: “this appears to be a one-time lapse in judgment.”
Sigh.

Admins of free AWS instances just didn't tick the right boxes. Lazily-configured software has again created a security incident, this time resulting in 4,000 instances of open source analytics and search tool Elasticsearch inadvertently running PoS-stealing malware.…
Game company wants to take down YouTube starrsquo;s livestream after n-word incident.
Visiting Equifax website to see if you're a victim requires you to waive lawsuit rights.
Customers' e-mail address, mobile number, and date of birth are compromised in the cybersecurity incident that targeted the insurance company's health portal.
Google Fiber turned her Internet back on after bizarre sales tax discrepancy.
Google allegedly told Forbes "the article was problematic and had to come down."
Itrsquo;s never good news when your workloads, data, or both get hacked in a public cloud.

Fortunately, itrsquo;s something that rarely occurs.

But as workloads and data sets on the public clouds become more numerous, such a hack could occur.The best way to recover from an attack, aka a hack, is to remain calm and follow these simple rules.[ What is cloud computing? Everything you need to know now. | Also: InfoWorldrsquo;s David Linthicum explains how to move into a cloud career from traditional IT. ]What do if your public cloud is hacked Do shut down the machine instances as quickly as you can. Irsquo;m often taken aback by the number of admins who keep compromised systems up and running.

Chances are that the hackers have not yet culled all your data, so you can stop further damage by taking those systems down quickly. Do contact your provider right away. It typically has automated procedures to lock things down for you, and even locate the source of the attack. Do review your security policies and security tools, at your first opportunity. Something fell through the cracks, and most breaches that I see are due to human error. While itrsquo;s fresh in your mind, itrsquo;s time to do some self-discovery to ensure something like this does not happen again.

Even if this specific breach was the cloud providerrsquo;s fault, the next time it could be your faultmdash;so use the incident to review what you control. Do contact those whose information may have been compromised. The days of keeping breaches to yourself are long over.
If Social Security numbers or credit card data has been compromised, the owners need to be contacted so they can watch for fraud.
If itrsquo;s personally identifiable information (PII) or other protected data, you need to contact your regulatory authority as well. What not to do if your public cloud is hacked Donrsquo;t try to combat the hackers with a counterattack. Shut the systems down first, remove the IP addresses, and then figure out what happened. Retaliation is a macho thing that Irsquo;ve seen occur in the last few yearsmdash;donrsquo;t go there.
Itrsquo;s not a street fight.
Irsquo;ve even seen companies that were attacked launch counter-DDOS attacks at the offending IP addresses. Not smart.
In the long run, yoursquo;ll just waste more time and money, and possibly open yourself to a full-on vendetta attack. Donrsquo;t make rash decisions about rehosting. These days, many companies move to the cloud because their on-premises systems got hacked.
If cloud-based systems are hacked, I suspect wersquo;ll hear a lot of people say, “Wersquo;re heading back to the enterprise data center.” The grass is always greener, and you need to thoroughly think through such a move. Huge and expensive rehosting decisions could turn into huge and expensive mistakes.  Donrsquo;t play the blame game. Although itrsquo;s tempting to call people out who you view as responsible, that almost never delivers the outcome yoursquo;re seeking. Donrsquo;t overexplain. Among the great many mistakes Irsquo;ve seen included a company sending out press releases, where one would have done the trick.

The public will view such overexplaining as a weakness, and many will assume yoursquo;re hiding something in the deluge of explanationsmdash;that yoursquo;re fast-talking. Make your points and be done with it. To read this article in full or to leave a comment, please click here