Paloalto Networks Practitioner Online Access

An Intrusion Prevention System (IPS) includes automated security actions, such as blocking malicious traffic, resetting connections, or alerting administrators when it detects suspicious activity, helping to stop attacks in real time.

Attack Surface Management (ASM) platforms focus on continuous discovery and monitoring of all internet-facing assets, both internal and external, to identify attack vectors, vulnerabilities, and exposures that could be exploited by threat actors.

Multitenancy is a key characteristic of the public cloud, and an important risk. Although public cloud providers strive to ensure isolation between their various customers, the infrastructure and resources in the public cloud are shared. Inherent risks in a shared environment include misconfigurations, inadequate or ineffective processes and controls, and the “noisy neighbor” problem (excessive network traffic, disk I/O, or processor use can negatively impact other customers sharing the same resource). In hybrid and multicloud environments that connect numerous public and/or private clouds, the delineation becomes blurred, complexity increases, and security risks become more challenging to address.

Cloud-native security is the integration of security strategies into applications and systems designed to be deployed and to run in cloud environments. It involves a layered approach that considers security at every level of the cloud-native application architecture. The four C’s of cloud-native security are123:

Code: This layer refers to the application code and its dependencies. Security at this layer involves ensuring the code is free of vulnerabilities, using secure coding practices, and implementing encryption, authentication, and authorization mechanisms.

Container: This layer refers to the lightweight, isolated units that encapsulate the application and its dependencies. Security at this layer involves scanning and verifying the container images, enforcing policies and rules for container deployment and runtime, and isolating and protecting the containers from unauthorized access.

Cluster: This layer refers to the group of nodes that host the containers and provide orchestration and management capabilities. Security at this layer involves securing the communication between the nodes and the containers, monitoring and auditing the cluster activity, and applying security patches and updates to the cluster components.

Cloud: This layer refers to the underlying infrastructure and services that support the cloud-native applications. Security at this layer involves configuring and hardening the cloud resources, implementing identity and access management, and complying with the cloud provider’s security standards and best practices.

The correct order of the four C’s from the top (surface) layer to the bottom (base) layer is code, container, cluster, cloud, as each layer depends on the security of the next outermost layer. References: What Is Cloud-Native Security? - Palo Alto Networks, What is Cloud-Native Security? An Introduction | Splunk, The 4C’s of Cloud Native Kubernetes security - Medium