Well, I sustain my words: the only EFFECTIVE way is to prevent.
All other ways are recipes what to do after failure happens, to minimize
the impact.
This resembles data loss scenario. What to do when you lost your data?
The answer is AVOID it. Use RAID arrays, remote copies, backups, archive
copies, transaction logs... every mentioned thing will not help you when
you lost your data, it is to help you avoiding data loss.
BTW: The only method for rabies is to immunization (by vaccination).
There is no cure.
--
Radoslaw Skorupka
Lodz, Poland
W dniu 08.09.2020 o 01:31, Tom Brennan pisze:
While I really like your new term, "ransomwared", I have to disagree
with the conclusion. Of course we need to try to prevent the attack,
but we also need to have some kind of backup to get things at least
somewhat back to normal. And that doesn't mean a single backup method
for all kinds of data. For example, operating system changes don't
happen every day, so as long as you get a system back up, it probably
doesn't matter too much if all the PTF's are applied. DB2 is another
story if you want something reasonably up-to-date.
Hmm... maybe make a deal with the hacker at half price and only get
the DB2 datasets back. Just kidding of course. It should be a moral
decision to *never* pay any ransom, no matter what the cost to the
business. Of course that will never fly in reality.
On 9/7/2020 4:34 AM, R.S. wrote:
Conclusion: the only effective way is to do not allow ransomware
attack to happen. Yes, we have to prevent it. All other ideas are
like good advices to a guy after his house was already robbed. Too
late. You already lost a lot.
======================================================================
Jeśli nie jesteś adresatem tej wiadomości:
- powiadom nas o tym w mailu zwrotnym (dziękujemy!),
- usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś
na dysku).
Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać
tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza)
tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać
karze.
mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950
Warszawa,www.mBank.pl, e-mail: [email protected]. Sąd Rejonowy dla m. st.
Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 0000025237,
NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na
01.01.2020 r. wynosi 169.401.468 złotych.
If you are not the addressee of this message:
- let us know by replying to this e-mail (thank you!),
- delete this message permanently (including all the copies which you have
printed out or saved).
This message may contain legally protected information, which may be used
exclusively by the addressee.Please be reminded that anyone who disseminates
(copies, distributes) this message or takes any similar action, violates the
law and may be penalised.
mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950
Warszawa,www.mBank.pl, e-mail: [email protected]. District Court for the Capital
City of Warsaw, 12th Commercial Division of the National Court Register, KRS
0000025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN
169.401.468 as at 1 January 2020.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
