Ransomware is continuing to grow not only in the manufacturing automation sector, but in just about every other industry and more organizations need to step up in their protection efforts.
Along those lines, the Cybersecurity and Infrastructure Security Agency (CISA) released its first CISA Insights product that talks about steps companies can take to protect themselves.
Ransomware emerged as the most visible cybersecurity risk playing out across our nation’s networks, locking up private sector organizations and government agencies alike.
As it is with most security issues, that is only the tip of the iceberg as organizations suffer from attacks and they end up going unreported, ransoms are being paid, and attacks continue.
CISA is attempting to build an understanding of how ransomware attacks unfold, and what potential steps you can take to better defend systems.
CISA listed some moves a company can take to become for resilient in case there is an attack:
1. Backup your data, system images, and configurations and keep the backups offline
2. Update and patch systems
3. Make sure your security solutions are up to date
4. Review and exercise your incident response plan
5. Pay attention to ransomware events and apply lessons learned
If there is an attack here are more moves a company can take:
• Ask for help. Contact CISA, the FBI, or the Secret Service
• Work with an experienced advisor to help recover from a cyber attack
• Isolate the infected systems and phase your return to operations
• Review the connections of any business relationships (customers, partners, vendors) that touch your network
• Apply business impact assessment findings to prioritize recovery
CISA also listed some moves a company can take to possibly ward off a ransomware attack:
1. Practice good cyber hygiene; backup, update, whitelist apps, limit privilege, and use multifactor authentication
2. Segment your networks; make it hard for the bad guy to move around and infect multiple systems
3. Develop containment strategies; if bad guys get in, make it hard for them to get stuff out
4. Know your system’s baseline for recovery
5. Review disaster recovery procedures and validate goals with executives