One Article Review
| Source |  NoticeBored |
|---|---|
| Identifiant | 1501881 |
| Date de publication | 2020-01-18 09:00:04 (vue: 2020-01-19 17:42:46) |
| Titre | NBlog Jan 18 - business discontinuity |
| Texte |  As if following a cunning plan (by sheer conicidence, in fact) and leading directly on from my last two bloggings about business continuity exercises, Belgian manufacturing company Picanol suffered a ransomware infection this week, disabling its IT and halting production of high-tech weaving machines at its facilities in Ypres, Romania and China.Fortunately, Picanol's corporate website is still up and running thanks to Webhosting.be, hence management was able to publish this matter-of-fact press release about the incident: Unsurprisingly, just a few short days after it struck, technical details about the "massive ransomware attack" are sparse at this point. The commercial effects, though, are deemed serious enough for trading in its shares to have been suspended on the Brussels bourse. There's already plenty of information here for a case study in February's awareness module. Through a brief scenario and a few rhetorical questions, we'll prompt workers to consider the implications both for Picanol and for their own organizations. If a similar malware incident occurred here, knocking out IT and production for at lea |
| Envoyé | Oui |
| Condensat | belgian technical there able about advanced after already always appeals apt are attack audience audiences awareness because been bloggings both bourse brief brussels business but can case changes china choose commercial company conicidence consider continuity corporate cunning customers danger days deemed designed details directly disabling discontinuity discuss discussion done effects emphasis enough espionage exercises facilities fact february find following fortunately from general halting have hence here high how however implications incident incident:unsurprisingly incidents industrial infection information insider involving its jan just a kept knocking largely last leading learning least machines malware malware: managed management manufacturing massive minor module nblog newsworthy normally not now occurred one only organizations other out own particular persistent picanol plan plenty point present press production prompt publish purposes questions quiet quite ransomware rarely real recent reduce regardless release relevant respond rhetorical right risks romania running sad say scenario security serious shares sheer short should similar so easy somehow sparse specific staff stakeholders struck struggle studies study such suffered suspended tech tech/specialist thanks this matter though threats through too topical topics trading travelex two victims weaving webhosting website week what workers would ypres |
| Tags | Ransomware Malware Studies Guideline |
| 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.