One Article Review
| Source |  NoticeBored |
|---|---|
| Identifiant | 1570365 |
| Date de publication | 2020-01-30 11:02:19 (vue: 2020-02-29 05:00:23) |
| Titre | NBlog Jan 30 - simplicity itself |
| Texte |  "Simplicity is the default unless there's a good business reason to do something else. What is typically lacking are the business reasons ..."That comment on CISSPforum set me pondering during this morning's caffeine fix. We've been chatting about some training webinar sessions recently promoted by (ISC)2. Some say they over-simplify information security to the point of trivialising and perhaps misleading people.If you follow NBlog, you'll know that this month I have been slaving away on an awareness module covering malware, a topic we've covered many times before - particularly the avoidance or prevention of infections but this year a customer asked us for something on publicly disclosing incidents in progress, a disarmingly simple request that turned into a fascinating foray into the post-malware-infection incident management and resolution phase for a change. I've been exploring and writing about what does, could or should happen after malware 'hits' - from that dramatic moment the ransomware demands appear on everyone's screens, for example. What follows is quite an intricate and frantic dance, in fact, involving management, IT and other staff, customers, suppliers and partners, regulators/authorities, journalists and the news + social media etc. plus the Incident Management Team, infosec and business continuity pros trying to keep everything on track, the legal team figuring out who to sue, the compliance pros wondering how not to get sued, and various hired-hands helping with forensics, disinfection and finding then retrospectively plugging whatever holes were initially exploited by the malware. All the while, the menacing hackers and cybercrims are wielding big coshes in the shape of threats to make the disruption permanent and terminal, and/or to disclose whatever juicy tidbits of corporate and personal info they've previously stolen (the CEO's emails, or browser history perhaps?). And all the while the systems, data, business processes/activities, websites and apps are being maintained, recovered or restored. Brands and relationships are under pressure, along with all the dancers. It's an intensely stressful time for them, I'm sure. The approach we've taken is to explore the timeline of an actual incident, in real time as it happens (as it happens), building a case study around the ongoing Travelex ransomware incident: the sequence forms a convenient thread to lead people through the story, thinking about what's going on at each stage and imagining how it would be if a similar incident happened 'here'. I've drawn up a simplified Travelex incident timeline in the same style as the one I drew for the Sony Pictures Entertainment fiasco 5 years back, pointing out some of the key events plus the phases of the overall process. The new Travelex version ('in press'!) is simpler |
| Envoyé | Oui |
| Condensat | as in is my the what 2 webinars able about accept accepting accounts act actual actually address after aimed alice all along already also although amber and/or animated appear approach apps are around asked aspects assurance audience audiences avoidance awareness away back barely bars bear been before being best big blind blog bothered bottom boxes brands brief briefing bright browser budget building business business” busy but caffeine can care case catchers catches catching ceo challenge change chat chatting cisspforum coaching colour colourful colours comes comment complex compliance concerns conjour contemplate content contents context continuity control convenient corporate coshes could course covered covering creativity cues customer customers cybercrims dance dancers dash data day days decks default demands depends details diagram diagrams differences different disarmingly disclose disclosing discuss discussion disinfection disruption distracted does don done down downside dramatic drawn drew during each easier educator either eloquently else emails employees: employees” end engage engineer engineering enough entertainment enthusiasm especially etc even events ever everyone everything example expanding experience expert explain explained explaining exploited explore exploring express extend extensive extensively eye face fact fairly far fascinated fascinating fiasco figures figuring finding finish first firstly fix flexible flowcharts foils follow follows foray forensics forget forms frantic freda frequent from geek generally get glance going good governance graphic graphical graphics graphics: graphs green greybeard guess hackers half hand hands happen happened happens hard has have headings headline help helping here high hired history hits holes how images imagining incident incident: incidents individuals individuals: infection infections info information infosec initially inspired instance intensely interest interesting interests internalising intricate involving isc ishikawa its itself jan john journalists juicy keen keep key know knowledge known lacking largely lead learning legal let level light like likewise listen little lobby love maintained make making malware management many maps materials maybe means media meeting menacing middle might mind minute misleading modes module moment month more morning most motivate much must naturally nblog neat need needs new news nice not notes now numbers obvious off once one ongoing online only organization oriented other others out outline over overall own pages paper particularly partners passion people perhaps permanent personal personally phase phases pick picture pictures piece pieces pigs place plain plugging plus point pointing policy pondering post powerpoint practice prefer preferably preferences preferred prepare prepared presence present presenter press pressure prevention previously pro probably process processes/activities professional professionals programs progress promoted prompts pros provided ps publicly pullquotes puzzle quite ransomware rather read real really reason reasonably reasons recently recovered red reduce regulators/authorities reject relationships relatively relevance relevant remarkably replace report request resolution restored retrospectively right risk risks room run said same say scrap scratch screen screens screenshots scribbled secondly security seem senior sequence session sessions set shape should shown side sideways similar simple simpler simplicity simplification simplified simplify simplifying simply since skim slaving slide slides social some someone something sometimes sony sort spare speak speaker speaking specifically spectra spoken stack staff stage step stolen story strategy stressful study stuff style subject such sue sued summaries supplement supplementing suppliers sure surface systems taken takes teaching team techniques terminal terms text than that them themselves then there they things thinker thinking those though thousand thread threats through tidbits tidy tim |
| Tags | Ransomware Malware 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.