Search

Staying One Step Ahead of the Pandemic: Evolving Trends in Cybersecurity Amid a Health Crisis

Although Agile deployment practices such as Agile, Scrum, Kanban, and many others have been around for years, the digital shift driven by the COVID-19 pandemic pushed many organizations to finally take these practices more seriously. The only way to keep up with a continuous demand for new features, running workloads at scale, and ensuring applications are resilient is through DevOps.

If you were not doing DevOps yet, you’ve hopefully started during the pandemic. Organizations are forced to embrace the cloud because they must now support mostly remote workforces. And solid DevOps practices are the key to cloud success.

The move to cloud-centric DevOps isn’t all sunshine and roses, however. As developers and DevOps practitioners, we’ve had to take on additional responsibilities to ensure our systems are secure. These include secrets management, source code security, container and VM security, and more.

Accelerated Movement to the Cloud

During 2020 and 2021, organizations in the early stages of moving to the public cloud accelerated their move. Even companies who thought they could postpone this maneuver soon realized they must take action immediately.

Gartner forecasts that in the aftermath of the COVID-19 crisis, the worldwide end-user spending on public cloud services will grow 18.4 percent in 2021 to total $304.9 billion.

This migration to the cloud means DevOps will only continue to grow in importance, so we had better be prepared.

Rapidly Shifting to Remote Work

The pandemic forced organizations worldwide to shift everyone to remote work. Employees had to perform as many business activities as possible remotely. Most organizations weren’t ready for this change.

With the rapid-paced movement to public cloud environments, DevOps teams need to migrate trusted on-premise tools to the cloud without compromising security. One major challenge to collaboration and remote work is determining where to store application source code.

Yes, we have distributed source control solutions based on Git (GitHub, Bitbucket, GitLab, and the like), but not all organizations use public cloud services. Many run Git in the company’s centralized data center using tools like GitHub Enterprise Server and Azure DevOps Server.

But we can move our source to the cloud without compromising security. Major providers like GitHub offer encryption and robust access control to ensure private code remains private. And source scanning tools like Trend Micro Cloud One – Open Source Security by Snyk provide additional protection by scanning your dependencies to find vulnerabilities.

Put simply, shifting left in our DevOps processes allows us to put security first — and it works just as well in the cloud as it does on-premise.

Supporting a Geographically Dispersed Workforce

Remote working and interconnecting sites involve building out a scalable VPN network. While many organizations already used VPNs before the pandemic, access was usually only available to a limited set of users.

Almost everyone now works from home, and connecting through the VPN introduces one more layer of complexity. Developers and DevOps must now test and deploy internal corporate apps to ensure they are all fully accessible via the company’s VPN.

One significant benefit of moving to the cloud is the ease of access. All employees can access line-of-business apps in the cloud without first connecting to the corporate VPN. However, this cloud availability introduces security risks such as malware and distributed denial-of-service (DDOS) attacks. We’ll explore these risks in the next section.

Digitalization Expands Security Concerns

As organizations embrace the cloud, they face new security concerns. Security must be top of mind for developers and DevOps professionals because we’re the ones writing, deploying, and maintaining our organization’s cloud applications.

Let’s consider some specific workload scenarios on top of the movement to the cloud. When deploying virtual machines, we’re in control of (but also taking responsibility for) network security (firewall and WAF-integrated load balancers) and virtual host protection (anti-malware tools).

Although we typically can’t control much of the runtime-host environment, a source code analysis tool is still beneficial when using a platform as a service. Storage solutions, which used to run on on-premises server farms and SAN/NAS appliances, can now shift to cloud-based storage solutions like Amazon Simple Storage Service (S3), Azure Blob storage, and the like.

When using containers (Docker or Kubernetes as a service with Amazon Elastic Kubernetes Service (EKS), Azure Kubernetes Service (AKS), Google Kubernetes Engine (GKE), or RedHat OpenShift), we must integrate a container vulnerability scanning tool as part of our process. These tools are necessary to tackle common container security vulnerabilities such as public container images, often containing outdated (thus vulnerable) packages and regularly having hard-coded secrets inside the images. Trend Micro’s container image security and registry scanning can help secure our containerized workloads.

Runtime Environments and Security Observability

We have already touched on the various hybrid and multi-cloud platform scenarios available to run our workloads, ranging from virtual machines to platform-as-a-service solutions to containerized workloads. No matter what architecture we put into place, our DevOps teams should always access end-to-end workload observability metrics, dashboards, and logs.

These metrics should primarily include and represent runtime data (indicating workload health) and allow for a complete security-state-view of those workloads. Trend Micro has teamed up with New Relic to provide this integration, relying on cloud connectors to centralize data and security information, and taking the necessary actions to mitigate cybersecurity threats.

As we’ve mentioned, the “shift left” approach, which moves security considerations and protection close to the start of the DevOps process, should become a priority. Security should include vulnerability scanning tools for source control code, keeping secrets and other confidential strings away from the source code, integrating container vulnerability scanning, and more. Many tools in Trend Micro’s Cloud One suite, such as container security protection and workload security, check to ensure we haven’t accidentally introduced vulnerabilities to our apps or embedded credentials and other secrets in our code.

Summary

The pandemic has impacted the way organizations work. This shift to online solutions triggers a greater risk of cyberattacks than ever, so companies must prioritize safety.

Trend Micro security tools for your on-premises data center infrastructures and hybrid or public cloud, and solutions to secure end-to-end networks and end users’ devices all help reduce your security risks in this era of remote work. Also, Trend Micro’s cybersecurity response center tool scans all layers of your data center solutions to provide clear security risk visibility. It allows for security incident creation, follow-up, policy-based management, and complete integration with your existing security incident management, security orchestration automation, and response tools.

Explore Trend Micro’s solutions to improve your organization’s remote working cybersecurity.

If you’re interested in developing expert technical content that performs, let’s have a conversation today.

Facebook
Twitter
LinkedIn
Reddit
Email

POST INFORMATION

If you work in a tech space and aren’t sure if we cover you, hit the button below to get in touch with us. Tell us a little about your content goals or your project, and we’ll reach back within 2 business days. 

Share via
Copy link
Powered by Social Snap