One Article Review
| Source |  AlienVault Blog |
|---|---|
| Identifiant | 2575099 |
| Date de publication | 2021-04-02 10:00:00 (vue: 2021-04-02 11:05:41) |
| Titre | 5 steps to respond to a data breach |
| Texte | This blog was written by an independent guest blogger. You’ve just been breached. What do you do next? Depending on personality, preparation, and ability under crisis, there are a variety of responses to choose from, some effective and some not. Hopefully, you’re the rare breed who plans in advance how to respond. Even better if this planning includes how to prevent them. But to execute a logical, effective response, keep reading. In this guide, I’ll take you through a methodical process of handling a data breach and how to stop it from happening again. Let’s get to it. 1. Stop the breach At the risk of resembling Captain Obvious, before anything else you need to stop the data leak. But to do that you have to recognize a data breach exists. For some organizations the problem with data breaches isn’t responding to them – it’s knowing they are happening at all. Research indicates that breach detection can take half a year or longer on average. That should be a mind-boggling statistic and testament to the general widespread lack of effective cybersecurity. By the time the problem is spotted, potentially private data has been leaking into the wrong hands for a long time. So... contain it quickly. Isolate the systems that have been compromised and immediately take them offline. Late though it might be, it’s critical to stop the problem from spreading to other parts of your network. Shut down any user accounts that you believe have been used to steal data – it’s better to be safe than sorry. You can restore them later. 2. Assess the damage Next, get ready to undertake some forensics. These should be focused not just on tracing how your data was accessed, but the likely impact of it being released to the general public, in the unfortunate event that happens. While determining whether it’s a data breach, leak, or compromise, you should also ask yourself (and your team) a number of questions: What was the attack vector? Was the attack based on social-engineering tactics or through user accounts? How sensitive is the breached data? What is the type of data affected? Does the data contain high-risk information? Was the data encrypted and can it be restored (did the company backup their data)? It’s crucial that you perform this analysis before going on to the next step. Otherwise, your response to the breach could look uninformed and casual to an outsider. Get the facts straight, in other words, before customers start asking awkward questions. 3. Notify those affected Then it’s time to come clean. Inform everyone who is likely to be affected by the breach at the earliest possible opportunity. While it’s not a terrible idea to make sure your systems are safe before breaking the news, that doesn’t give you a license to wait months “just in case.” It’s tempting to play down the breach. Maybe omit some damaging details in hopes of preserving your brand integrity. Unthink those thoughts! If you are not totally honest and it’s discovered later - which it almost certainly will be - brand damage could be much, much worse. There is also the possibility of legal action. Any nasty, negative online comments the breach gen |
| Envoyé | Oui |
| Condensat | “just 100 ability able above accessed accordingly accounts action actually adequately advance affected after again against all almost already also analysis any anything approach appropriate are ask asking assess attack attacks audit average avoidable awkward backup based because becoming been before being believe better big birth blocks blog blogger boggling both brand breach breached breaches breaking breed bring brute but calm can captain careful case casual caused certainly choose clean come comments common commonly companies company compromise compromised contain coordination correctly could crisis critical crucial customer customers cyberattack cyberattacks cybersecurity damage damaging data dates dealt depending designate details detection determining develop devote did discover discovered does doesn’t done down earliest effective effectively effort else eminently encrypted ended engineering error even event everyone examine execute executed exists facts fall feasible feed finally find finding first focus focused follow force forensics forms from future general generates get give going guest guide hack hackers half handling hands happening happens has have here high honest hopefully hopes how human i’ll idea immediately impact important improve includes independent indicates inform information integrity isn’t isolate issue issues it’s just keep kind know knowing knowledge lack late later leak leaked leaking learn learning legal let’s license like likely limit limiting logical logs long longer look make maybe methodical might mind months more most much nasty need negative network new news next not notify number obvious offline omit on once one online open openness opportunity order organization organizations other otherwise out outsider overwhelming particularly parts party passwords penetrate perfect perform personality phishing place plan planning plans play policies ports possibility possible post potentially preparation preserving prevent private proactive problem process processes program protect provide public questions questions: quickly rare rdns reading ready realm recent recognize records recovery regularly released reports research resembling respond responded responding response responses restore restored review rising risk risks safe second security sensitive server set should shut simply skills smart social some sorry speed spotted spreading staff start statistic steal step steps stop straight successful suggest suppliers sure surprise system systems tactics take takeaway target team tempting terrible testament than that’s them then therefore these things third those though thoughts threats through time today’s totally tracing training trickier turn two type under understand undertake unfortunate unfortunately uninformed unthink update used user variety vector wait what what’s whether which who widespread will words work worse would written wrong year years you’ll you’re you’ve your yourself |
| Tags | Data Breach Hack |
| Stories | |
| Notes | |
| Move | 
|
L'article ne semble pas avoir été repris aprés sa publication.
L'article ne semble pas avoir été repris sur un précédent.