pdf) before being executed, though we would need to interview the user to see if she remembers anything like this. It could have been sitting on the hard drive for weeks (looking like a. Most entries in the User's Log file were harmless, though the way this virus worked, it could have been downloaded at any time but still needed to be executed by the user. This is not an uncommon risk-a small company or organisation website that doesn't have IT funding to keep up with the security risks in today's lightspeed world. pdf file that had been compromised on a grant coordination site run by a non-profit. In the final analysis, we believe the ransomware attack originated from a 'drive-by' where a single city employee visited and opened a. Here below find the complete story shared by John with us: They continued to stumble along until they were hit with a CryptoLocker ransomware attack. Part of that underinvestment is that they continued to rely on a tape drive that was ten years old using Backup Exec. 'We are slowly recovering from a decade of underinvestment in IT and have a large backlog of software, hardware and network upgrades.' 'We are spread so thin that logs are not monitored consistently,' reports John. The city has only two IT staff dedicated to infrastructure. John's team manages all technology, from phones, networks, servers, desktops, applications and cloud services. John T, IT Manager leads a team of five employees who execute all IT initiatives co-developed with the city's IT Governance team. According to Forbes, they are the 2nd fastest growing suburb in the state of Washington. Issaquah is a small city of 30,434 people in Washington, United States.

Unitrends-an American company specialised in backup and business continuity solutions-recently shared with us a real cyber-attack incident happened with one of their customers to describe the required steps they took to recover functionality following a CryptoLocker attack against a US city.Īlso, how it cost city's Governance team days of production and hundreds of man-hours to recover. Recovery from a downtime event includes inconvenience, extra work, embarrassment and yes, real pain. We look at other people's backup and recovery issues and hope we are smarter or clever enough to keep it from happening to us. We don't really know the pain and cost of a downtime event unless we are directly touched.īe it a flood, electrical failure, ransomware attack or other broad geographic events we don't know what it is really like to have to restore IT infrastructure unless we have had to do it ourselves.

Download crypto locker