How to manage a multi-cloud environment with multi-workload components that include, among other things, a local domain and providing Security to Cloud-Native Platform with Azure, AWS, and others.
Recently I tested several security platform solutions that require to address the following environments:

• Few cloud provider
• Different and many workloads
• Multi-workload
• Other models (PaaS, IaaS, SaaS)
• Existing local environment

One of the essential requirements is to provide Security for all enterprise requirements, whether for DevOps or Automation, including Infrastructure as Code, and to ensure cloud-native mode support.
From here, it took me to do a comprehensive and in-depth investigation into choosing the proper protection without getting lost and staying in a sane area.
It is unique and complicated when it comes to protecting multiple cloud providers with an accent on the cloud-native scenario and adopting the Cloud Native Security Platform model while preserving the local environment.
Traditional security control and methodologies are no longer suitable to protect cloud native’s developer-driven and infrastructure-agnostic multi-cloud models.
It’s now time to enter the ERA of the hybrid and Multi-Cloud Native Security Platform.
Infrastructure as a service (IaaS) took existing infrastructure and operational models and moved them to environments that could be more easily scaled.
The underlying business model was mainly consumption-based because the base models and technology stack mostly didn’t change. The modern security tools of the age could easily ride along for this transition and be lift and shift to run on those IaaS platforms.
However, over the past years, we’ve entered the cloud-native age, defined by shifting focus to higher-value outcomes rather than simply faster deployments and a shift from Capex costs.

Cloud-Native Approach

Cloud-native is all about changing the way we think about constructing critical business systems.
Cloud-native systems are designed to embrace rapid change, large scale, and resilience.
The Cloud Native Computing Foundation provides an official definition.

Cloud-native technologies empower organizations to build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds. Containers, service meshes, microservices, immutable infrastructure, and declarative APIs exemplify this approach.

These techniques enable loosely coupled systems that are resilient, manageable, and observable. Combined with robust automation, they allow engineers toprotection make high-impact changes frequently and predictably with minimal toil.

Applications have become more complex, with users demanding more and more. The users expect rapid responsiveness, innovative features, and zero downtime.
Performance problems, recurring errors, and the inability to move fast are no longer acceptable. They’ll quickly transfer to your competitor.
Cloud-native is much about speed and agility. Business systems are evolving from enabling business capabilities to strategic transformation weapons, accelerating business velocity and growth.
It’s important to get ideas to market immediately.
CNSPs are optimized for this app-centric, infrastructure agnostic nature. They integrate with the development lifecycle, are programmatically accessible via APIs, and run everywhere they do.
The speed and agility of cloud-native come about from several factors. Foremost is cloud infrastructure with five additional foundational pillars.

New Cloud Security Approach

The Cloud Native Computing Foundation (in short, “CNCF”) is one piece of the puzzle.
After all, it brings a remixing of existing technologies behind a new set of buzzwords and optimized for the present and future cloud-native architectures and operational practices.
Alongside moving to the cloud in different configurations and technologies, we need to protect the cloud infrastructure and ensure we are at the front with the proper security controls, which means that the current protection tools are not appropriate.
We need to “re-prepare” for the new environment and new configuration.
In Security, the benefit is to apply Security early in the life cycle because earlier problems can be identified and corrected, the less risk they expose, and the lower protection of the cost to resolve them.
However, IaaS computing wasn’t helpful in actually making this vision a reality.
When development and security operations are separate teams and entirely separate disciplines with different tools, it’s impossible to consistently monitor and enforce Security from developer to deployment to process.
Cloud-native changes this equation by highlighting a more integrated approach to building and running apps, enabled by modern tools such as microservices, containers, and serverless, making this integration a possible reality.
When discussing moving to the cloud and protecting and defending our assets, including preserving the cloud-native situations, we are entering digital security transformation with new options such as Cloud Workload Protection Platform and Cloud Security Posture Management Cloud-Native Security Platform.
A CNSP provides security visibility and control from a security perspective from the first time an app is built throughout its operational life, wrapped in APIs and tooling that emphasize automation and developer experience.
What is all about all those security protection and the specific one of the Cloud-Native Security Platform?
The security approach for the Cloud Workload Protection Platform, Cloud Security Posture Management, and the Cloud Native Security Platform is a new age of security perspective that provides a better way and security tools to work with the latest cloud requirements.

The Cloud Security Posture Management (CSPM), previously known as Cloud Infrastructure Security Posture Assessment, was defined in response to organizations’ growing need to correctly configure IaaS and PaaS and address cloud risks.
CSPM is a class of security tools, as Gartner defines, including use cases for compliance monitoring, DevOps integration, incident response, risk assessment, and risk visualization.
The Cloud Workload Protection Platforms (CWPPs) are defined by workload-centric security protection solutions, typically agent-based.
They address server workload protection’s unique requirements in modern hybrid data center architectures that span on-premises, physical and virtual machines (VMs), and multiple public cloud infrastructure as a service (IaaS) environments. Ideally, they also support container-based application architectures.
CWPPs provide host-based protections for your “workload,” which is another way to refer to your applications, databases, or functions running in instances, nodes, virtual machines, or whatever terminology the cloud provider uses.

Shared Responsibility Levels

Any cloud provider has a unique model of shared responsibility. If I am taking the most significant cloud providers Azure and AWS, you can see, each of the cloud providers builds its model differently, but in the end, those models are relatively the same.
Microsoft SRM
AWS SRMIt can be helpful to think of this shared responsibility model as having three layers. Providers are accountable for the bottom layer of infrastructure and finished services.
Customers are accountable for how they configure these services and what they run on them.
In the age of IaaS, cloud security posture management (CSPM) tools were used in an attempt to provide visibility of these service configurations, but without any insight into the accompanying compute that ran on top and alongside them.

A CWPP approach may detect these vulnerabilities and stop these attacks, but it can’t determine if the function is configured with the wrong security group in isolation.
Multiply these silos across the hundreds of services in use across tens of regions in dozens of accounts across several cloud providers, and these gaps become practically unsolvable.
Thus, a CNSP must provide monitoring, visibility, and remediation of these provider layer components while correlating data and applying policy across the compute components of cloud-native, hybrid apps.

Cloud Security Agnostic

Increasingly, organizations are becoming intentionally multi-cloud. Large organizations rarely use a single provider, whether this is for vendor management, data locality, or other reasons.
While cloud providers have added security capabilities at both layers of the stack, they focus on their services and don’t provide visibility across clouds.
A CNSP protects the time and technology dimensions across multiple clouds, such that organizations have a single platform on which to automate Security regardless of where the underlying services and compute reside.
As comprehensive platforms, CNSPs must provide a broader range of security capabilities than the point solutions of the Age of IaaS. CNSPs includes the following qualifications:

• Blueprint (including Automation)
• Identity Protection
• Infrastructure Security (IaaS)
• Compliance & Data Privacy
• Security Risk Analysis
• Shadow and Visibility
• Data Protection (data at rest and data in transit)
• Governance (including Enforcement)
• Threat Detection & Continuous Monitoring
• Audit, Logging, and log archive
• Configuration Management
• Environment Lockdown
• Vulnerability Management
• Patch Management
• Secure DevOps
• SIEM integration
• SOC Automation

While some are more relevant at some phases of the lifecycle or layers of the stack than others, all of these capabilities should work together in fundamental ways to provide more robust Security than even best-of-breed point solutions in isolation.
We need a Cloud-Native Security Platform because the Cloud-Native Security Platform (CNSP) changes are fundamental and essential to how enterprise security has traditionally been delivered.
The cloud-native ecosystem and active intellect create challenges that traditional security approaches cannot meet and provide the opportunity for delivering Security that’s more integrated, autonomous, and ultimately effective.
CNSPs protect the entire lifecycle of apps, the entirety of technology stacks they run on, and all the clouds they run in.
CNSPs are built as the right platforms, using rich APIs and open data formats. Just as cloud-native itself fundamentally changed how the cloud is used, CNSPs are fundamentally restructuring how it’s secured.
In conclusion, what are the following steps to build, create, and manage the Cloud-Native Security Platform? Isn’t it easy because using a Multi-Cloud scenario with Multi-Workload and Hybrid environment requires knowing the Cloud Security approach of each cloud provider?
After an in-depth investigation and after learning each cloud provider’s advantage, capabilities, and values with his dedicated security features, I can share that, including how each Cloud security can provide a protective layer to the other.