Author Archives: admin

Disaster Recovery Site vs Cyber Recovery Site

While the ultimate goal of both Disaster Recovery (DR) and Cyber Recovery(CR) is the same, to bring your IT services back online after an event, DR and CR differ in many ways. DR protects against physical disasters (such as flooding, earthquake, fire, terrorist attacks), user errors, and hardware malfunctions, while CR protects against cyber attacks.

Because of these differences, a DR site may not be able to provide the necessary function for restoring systems after a cyber attack. A Cyber Recovery site is needed to recover your systems from a cyber attack. A CR site is a vaulted site, containing replicated data of critical systems. It is isolated from the network and only connects during replication. A CR site doesn’t have to be in a geographically separate location (unlike a DR site), but it should be physically secured. In fact, it will be beneficial if it’s close to the primary Data Center to take advantage of a fast network connection.

DR usually supports most of the business operations (since disasters are usually bigger in magnitude), whereas CR supports only the most critical systems for operational recovery.

While IT admins have access to a DR site, a CR site should be restricted to a few select security folks.

Usually a DR site is also dormant, but a CR site will always have monitoring and analytics tool – checking for security breaches.

Many companies with mature IT infrastructure typically have a DR site. They also conduct regular DR tests. But most do not have a Cyber Recovery site yet. With the prevalence of cyber security attacks, it is high time for companies to install Cyber Recovery sites and conduct regular cyber recovery tests.

Checklist for a Secure Backup Infrastructure

Ramsomware attacks are running rampant these days. The ability to restore your servers, data and applications after an attack is critical to minimize costly disruption and bring your business back in service.

A secure backup infrastructure is key to this. Here’s a checklist on how to keep your backup systems robust and secure:

  1. Backup and retain data for several weeks. For critical systems, you will know right away if they have been compromised. But some may take days or weeks before you know you have been attacked or get a demand for payment from attackers. It’s better to have retained good copies of backup to restore.
  2. Replicate backup to an offsite location.
  3. Conduct regular file recovery and bare metal recovery tests.
  4. Perform regular patching and upgrade of backup devices. You also need to work with your device vendor to discuss vulnerabilities, monitor security advisories and apply critical security patches as soon as possible.
  5. Harden your backup infrastructure, for instance by replacing default passwords and turning off unneeded services.
  6. Implement data-at-rest and data-in-flight encryption.
  7. Monitor and send alerts for unusual activities such as privileged user multiple login attempts as well as backup deletion attempts. You can integrate with Splunk, CyberSense or other security analytics applications that have advance AI technology to easily monitor, detect, and analyze security breaches.
  8. Recertify user accounts on your backup devices periodically.
  9. Use security tool to store and encrypt local and service accounts passwords on the devices.
  10. Use two factor authentication.
  11. Implement Retention Lock.
  12. Implement backup vault by isolating the second copies of the backup. This can be done by using tapes or air gapping the backup storage.

Safeguarding Against Ransomware

The latest ransomware attack on Colonial Pipeline that resulted in the company shutting down its gas pipeline and causing fuel shortages throughout the southeastern United States underscored the importance of securing and protecting your IT infrastructure. Hackers are increasingly attacking critical infrastructure, hospitals, local government, school systems, industrial companies, etc. and and these attacks are becoming a national security, public, and safety threat. Most of these companies are ill prepared for cyber attacks. Last month, the Massachusetts vehicle inspection system was down for a couple of weeks due to ransomware attack.

Ransomware infects your system by encrypting your important files, and the attackers then ask for ransom to decrypt your data in order to become operational again. Sometimes they also threaten to release hacked documents to the public unless the ransom is paid.

Ransomware has been around for the past several years, but the explosion of cryptocurrencies, in which transactions are difficult to trace, is the main reason for the increasing ransomware attacks. Moreover, these cyber extortionists are usually from other countries which is hard for governments to prosecute.

To protect your systems, you must have a comprehensive cyber security program. You should always employ a defense-in-depth approach in which defensive mechanisms are layered to protect your systems, data and applications. If one mechanism fails, another protection layer may thwart the attack. The following basic security measures should also be in place:

  1. Requiring multifactor authentication (MFA) for employees logging onto systems. Users are usually the weakest link as they are easily tricked or socially engineered to give information or click on a malware site enabling the ransomware to penetrate the system. MFA may thwart attackers who got a hold of your credentials by using a second method of authentication.
  2. Patching vulnerabilities promptly on your network devices, servers, appliances, databases and applications, especially the critical ones. You should also work closely with your IT vendor or service provider in regularly reviewing vulnerabilities on their software or services.
  3. Hardening your devices, operating systems and software such as replacing default passwords and turning off unneeded services. If your company also develops programs in-house, you should also enable secure software development.
  4. Segmenting networks by erecting firewalls between them and only allowing traffic that are really necessary.
  5. Keeping backups of your servers and data, and sending a second backup copy off line (using tapes), or via air-gapped second copy (see my blog on data backup security)
  6. Testing your disaster recovery or cybersecurity plan periodically to that ensure they work.

Having a comprehensive cybersecurity plan is necessary for your business to withstand attack in order to stay in business.

Effective Incident Response and Management

Cyber attacks are all too common these days. They are getting faster, more frequent and more sophisticated. Companies should be prepared when these inevitable attacks occur. One of the critical security controls to mitigate and lower this risk is to have an effective incident response and management program.

The goal of the incident response and management program is to successfully detect, understand, manage, investigate, and recover from the breach in the shortest amount of time possible. Not having an effective program:

  • may damage company reputation, lose money, customers, and competitive advantage, or incur hefty fines
  • may take several weeks or months to detect the breach
  • maybe too late for the company to develop procedures, data collection, legal protocols, and communications strategy when a breach occurs
  • may lead to panic mode leading to more damage, infecting more systems and losing more data.

An effective incident management plan should:

  • determine and document the scope of the breach (such as systems and data impacted, department impacted, magnitude of impact, and severity)
  • collect forensic evidence from log data, security tools, disk images, security video, etc.
  • perform root cause analysis (RCA)
  • return to secure state by remediation or mitigation
  • gather threat intelligence to improve defense, deploy security solutions, and detect malicious behaviors

There are several processes for an effective incident response: Preparation Process -> Detection Process -> Analysis Process -> Notification Process -> Remediation or Mitigation Process

What to do in the preparation process:

  1. Understand your environment and the threats to it
  2. Define roles and responsibilities and contact information
  3. Gather third-party contact information to be used to report a security incident, such as Law Enforcement, relevant government departments, vendors, etc.
  4. Plan how to respond and identify key partners, data sources and technologies
  5. Practice just like a Disaster Recovery (DR) test
  6. Continually review and refine the plan as the environment changes

What to do during detection process:

  1. Assess threats by gaining visibility to any active threats
  2. Define reporting outlet and encourage end user reporting
  3. Use technology to detect attack
  4. Contain damages by stopping the attack and recovering the affected endpoints

What to do during analysis process:

  1. Determine the impact and scope of the breach
  2. Protect and preserve the forensic evidence for investigation and root cause analysis
  3. Perform any remediation

What to do during notification process:

  1. Communicate diligently to upper management, internal stakeholders, or end users
  2. If the breach has to be communicated externally (e.g. to customers, law enforcement, etc.), involve the legal team and use your defined communication strategy.

What to do during remediation or mitigation process:

  1. Implement temporary measures
  2. Coordinate with stakeholders
  3. Document changes
  4. Secure defenses

An effective incident response program is a well documented plan (consisting of people, processes, and technologies) that is up to date and highly tailored to the need of the company.

IoT Security

The Internet of Things, or IoT, refers to the billions of physical devices around the world that are now connected to the Internet. These include surveillance cameras, lightbulbs, medical devices, pacemakers, smartphones, home routers, thermostats, printers, control systems and pretty much any device that is connected to the Internet, all collecting and sharing data. They have sensors that detect states or movement of equipment or materials and the data acquired by the sensors are transmitted over the network to a server. Location information can be derived as well.

The explosion of IoT devices has also increased cyberattacks on them. Hackers probe and access them via http, ftp or telnet ports to check what kind of devices they are. They also check for backdoor ports. Then they gain access by logging in via telnet (the common one, although they may also use other vulnerable ports) using default or weak username and password, and sometimes using dictionary attack. Once they gain access, they will install malware. Once malware is installed, the device will be under control of the hacker’s server, and is then used for further cyberattacks.

Hackers usually control hundreds of thousands of IoT devices all around the world that are used for DDoS (Distributed Denial-of-Service) attacks. These DDoS attacks can cause significant impact to companies being targeted.

IoT devices are specially vulnerable because they are usually online 24/7, they don’t have security or anti-virus protection, they have weak/default login password and they have global IP addresses. Security is an afterthought of the manufacturers of these devices.

To mitigate IoT security vulnerabilities, there should be an active monitoring and alerting system that notify users when their IoT devices are vulnerable, so they can take appropriate action. Technology solutions must be established to remotely detoxify IoT malware while the original IoT functions can continue to operate. There should also be a way to remotely disable IoT device.

Companies should have a strict security controls for connecting IoT devices in their network.

Finally, the industry should develop IoT security guidelines for IoT device maker/developer, IoT service provider, and IoT device user, as well as promote international standardization.

The Need for Using MFA in IT Infrastructure Devices

Multi Factor Authentication or MFA should be understood by now (hopefully) and should be widely used and implemented.

What is MFA? MFA is a simple best practice that adds an extra layer of protection on top of your user name and password. With MFA, when you sign in to a website or device, you will be prompted for your user name and password (the first factor — what you know), as well as for an authentication response from your MFA device (the second factor — what you have) such as a text message to your mobile device, or a string of numbers from an authenticator app (such as Google Authenticator). Taken together, these multiple factors provide increased security for your account settings and resources.

Most financial sites and apps, for instance, have been using MFA for years to protect your money.

In corporate settings, many breaches and cyberattacks are due to hackers gaining unauthorized access using accounts that are not properly protected. These accounts use simple and guessable passwords (Pasword123), factory default passwords, passwords written on sticky notes, passwords derived from social media profile (such as birthday or pet name), and passwords derived from social engineering and phishing attacks. Using multi factor authentication will lessen the risk of hackers gaining access to your corporate network.

However a lot of IT infrastructure devices do not use MFA. Privileged accounts on network routers, switches, application servers, database servers, hypervisors, storage and backup devices, etc. should use MFA to strengthen their security. Manufacturers should make it easy to configure MFA on these devices.

Creating a Cybersecurity Culture for your Organization

As more and more organizations are becoming digital, accelerated by the Covid-19 pandemic, it is imperative for businesses to build a culture of cybersecurity. This enables them to be more resilient in the face of growing cyber attacks.

Many of these organizations, especially in the manufacturing sectors, have developed a robust safety culture where every employee is trained, knowledgable, and constantly reminded of ways to stay safe and decrease the chance of accidents. But when it comes to cybersecurity, most organizations do not have a similar culture of security.

Just like building a safety culture, building a cybersecurity culture is a big undertaking and usually takes time. It involves transforming processes, changing mindset, getting support from leadership all the way to the top, and changing the way every employee works.

Many companies think that technology alone will solve cybersecurity problems. They rely on the IT department and in some cases on the security office – if one exists – to mitigate security issues. But the goal of every orgainization should be that everyone must feel personally responsible for keeping the company secure.

Building a culture of cybersecurity involves everyone’s attitudes, beliefs and values that will drive behaviors that will lead to better actions such as not clicking a link on a phishing email or not visiting an unknown website. At the heart of a culture of cybersecurity is getting every employee to execute their day-to-day activities in ways that keep the organization as secure as possible.

For more information on this topic and to gain insights on how to build a culture of cybersecurity, visit the MIT CAMS website at https://cams.mit.edu/research/

The Importance of Securing Your Company’s Intellectual Property

In the wake of the massive Solarwinds attack affecting major government institutions and public/private companies, the importance of securing your company’s Intellectual Property (IP) has never been more critical.

Companies should be worried that their valuable data, trade secrets, and IP are being stolen by cyber thieves, foreign hackers, and company insiders (current or former employees, partners, trusted customers, distributors, or vendors).  Stolen IP poses a significant threat to a company’s competitive advantage.  A bio-pharmaceutical company, for example, generates a ton of research/clinical data and manufacturing processes that are stored on premise and increasingly on the cloud.

Companies should protect their data.  They should learn the best practices in implementing operational and cyber security measures, instituting policies and processes, and educating end users. They should continually tweak and and re-evaluate their security practices.  They should deploy technologies that are effective in securing their data.

Attacks will only get more sophisticated and their frequency will only increase in the future. It’s better to be prepared than caught off guard.

The Five Stages of Crisis Management: COVID-19 in the US

I recently attended the virtual ISC2 Security Congress 2020. One of the keynote addresses was regarding crisis management by Harvard Kennedy School Professor Juliette Kayyem. She used to be Assistant Secretary at the Department of Homeland Security.

Crisis management is central to cybersecurity. When there is a breach or security incident, crisis management is invoked to minimize damage. A well executed crisis management program leads to a successful resolution in a short period of time.

I’d like to share this chart presented by Ms Kayyem on the five stages on how the COVID-19 was managed in the US, which is similar to the five stages of cybersecurity crisis management: Protection > Prevention > Response > Recovery > Resiliency

The keynote address can be viewed here: https://securitycongress.brighttalk.live/keynote-november-18/

Building and Operating a Private Cloud

The future of computing is both public and private cloud. It may seem that public cloud – dominated by AWS, Microsoft Azure and Google – is now the norm, but companies will continue to run workloads that are best suited to be on premises. There are three main reasons for this. First, with large volume of data generated on-prem, storage and compute power need to be close since latency and distance are major issues. Second, there are studies which prove that consumption-based services offered by public cloud can be quite expensive after a certain threshold. Thus we hear some companies pulling back their storage and compute on premises to save money. Third, compliance and data sovereignty requirement by organization and governments are better controlled on-prem.

The challenge for most companies is how to build and operate on premises private cloud. Most companies have traditional data centers which are not suited any longer for delivering and maintaining reliable compute, storage, and network services to the rapidly changing business requirements. They should build and operate a private cloud that have the same characteristics of a public cloud – including on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service (read my blog on the Characteristics of a True Private Cloud).

Fortunately, companies such as VMware now offer a single integrated solution that enable companies to build and operate private cloud. For instance, the VMware Cloud Foundation based on underlying hyperconverged hardware (e.g. DellEMC VxRail), provides software-defined services for compute, storage, networking, security and cloud management to run enterprise traditional or containerized applications. It extended its VMware vSphere server virtualization platform with integrated software-defined storage (vSAN), networking (NSX), cloud management (vRealize suite), and security capabilities that can be consumed flexibly on premises. In addition, VMware Cloud Foundation delivers IT automation based on blueprints (templates), which embeds both automation and policy, and when executed will automatically orchestrate the provisioning and lifecycle of all the components in the blueprint.

Although some features are still not at par with the public cloud (such as the ease of self-service provisioning) , private cloud will continue to improve as more technologies are integrated or built on top of this private cloud foundation.