1. click on compliance standard.

2. add custom compliance standard.

3. edit policies.

4. add compliance standard from drop-down menu

https://docs.prismacloudcompute.com/docs/enterprise_edition/compliance/custom_compliance_checks.html#creating-a-new-custom-check

The process of mapping a policy to a custom compliance standard in a security platform like Prisma Cloud by Palo Alto Networks involves several specific steps. Firstly, one must access the compliance standards, which is typically done by clicking on the " Compliance Standards " section within the platform ' s interface. This is where all standards, including custom and predefined ones, are listed.

Next, if the custom compliance standard does not already exist, it must be created. This step involves defining the criteria and controls that make up the standard, tailored to the organization ' s specific requirements.

Once the custom compliance standard is in place, the policy in question needs to be edited. This editing process would involve configuring the policy to align with the compliance controls outlined in the custom standard, ensuring that the policy will enforce or check for the necessary requirements as defined by the standard.

Finally, the last step is to formally associate or map the edited policy with the custom compliance standard. This is typically done by adding the policy to the standard, which may involve selecting the custom compliance standard from a drop-down menu within the policy settings, confirming that this particular policy should be enforced as part of the compliance checks for that standard.

This ordered process ensures that policies are properly aligned with the organization ' s compliance goals and can be enforced and reported on accurately within the security platform.

The activities listed (Backdoor account access, Hijacked processes, Lateral movement, Port scanning) are categorized as incidents (option B). Incidents represent security events or patterns of activity that indicate potential security breaches or malicious behavior within the environment. Prisma Cloud identifies and classifies such activities as incidents to highlight significant security concerns that require investigation and potential remediation. This categorization helps security teams prioritize their response efforts, focusing on activities that pose a real threat to the integrity and security of the cloud environment. By distinguishing incidents from other types of security findings, Prisma Cloud enables more effective incident response and threat management processes.

VM image scanning is a critical component of cloud security, allowing organizations to identify vulnerabilities within virtual machine images before deployment. The three major public cloud providers supported for VM image scanning are Google Cloud Platform (GCP), Amazon Web Services (AWS), and Microsoft Azure. These platforms offer extensive infrastructure services and are commonly used in various industries, making them primary targets for VM image scanning integration.

GCP, AWS, and Azure each provide capabilities to store, manage, and deploy VM images through their respective services such as Google Compute Engine, AWS EC2, and Azure Virtual Machines. By integrating VM image scanning with these services, organizations can ensure that their VM images are free from known vulnerabilities and comply with security best practices before being deployed in the cloud environment.

This approach to VM image scanning is consistent with Prisma Cloud ' s comprehensive security strategy, which emphasizes the importance of securing cloud workloads across the entire development lifecycle. By supporting VM image scanning across GCP, AWS, and Azure, Prisma Cloud enables organizations to maintain a consistent security posture across multiple cloud environments, mitigating the risk of deploying vulnerable or misconfigured VM images that could lead to security breaches.

When enabling Registry Scanning in Prisma Cloud for a registry that stores Windows images, it ' s important to note that Windows host defenders must be deployed in the environment to scan these images effectively. The Windows host defenders are specialized versions of the Prisma Cloud Defender that are designed to run on Windows operating systems. They provide the necessary functionality to scan Windows container images stored in registries, identifying vulnerabilities and ensuring the images comply with security policies before they are deployed. This requirement underscores the importance of having the appropriate Defender deployments that match the operating systems of the images being scanned.

https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute/access_control/rbac

https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin-compute/continuous_integration/set_policy_ci_plugins

The given admission control policy is designed to evaluate pod creation requests in a Kubernetes environment, specifically targeting the creation of privileged pods, which can pose significant security risks.

Option D: The policy will block the creation of a privileged pod is the correct answer when the effect of the policy is set to “block”. In this context, the policy ' s logic checks if a pod being created is set to run in privileged mode (a high-risk configuration that grants the pod extended system privileges). If such a configuration is detected, the policy triggers an action to block the pod ' s creation, thereby preventing the deployment of privileged pods that could undermine the security posture of the Kubernetes environment.

B -- > Anomaly Trusted List—Exclude trusted IP addresses when conducting tests for PCI compliance or penetration testing on your network. Any addresses included in this list do not generate alerts against the Prisma Cloud Anomaly Policies that detect unusual network activity such as the policies that detect internal port scan and port sweep activity, which are enabled by default. C -- > Trusted Alert IP Addresses—If you have internal networks that connect to your public cloud infrastructure, you can add these IP address ranges (or CIDR blocks) as trusted ... Prisma Cloud default network policies that look for internet exposed instances also do not generate alerts when the source IP address is included in the trusted IP address list and the account hijacking anomaly policy filters out activities from known IP addresses. Also, when you use RQL to query network traffic, you can filter out traffic from known networks that are included in the trusted IP address list.

For a customer who does not want alerts to be generated from network traffic originating from trusted internal networks, the appropriate setting is C. Trusted Alert IP Addresses. This setting allows for specifying certain IP addresses as trusted, meaning alerts will not be triggered by activities from these IPs, ensuring that internal network traffic is not flagged as potentially malicious.

The image provided showcases a filtered compliance view, which is displaying only certain checks with varying severities and descriptions related to container and image compliance. Since the compliance rule was configured to enable all checks but only a subset of entries is visible, it implies that the current view is filtered to show specific entries. To obtain a comprehensive view of all checks, including those that have passed, the rule options must be adjusted. By selecting the option to list both failed and passed checks, one can gain complete visibility over the compliance status of the container, ensuring that no aspect of the compliance has been overlooked and that all necessary information is available for review.

https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin/manage-prisma-cloud-alerts/prisma-cloud-alert-resolution-reasons

In Prisma Cloud, POLICY_UPDATED is a valid reason for the dismissal of an alert. This reason indicates that an alert can be dismissed if the policy that triggered the alert has been updated. When a policy is updated to no longer apply to certain resources or conditions, any open alerts that were generated based on the previous version of the policy may be dismissed as they are no longer relevant.

The other options, such as SNOOZED_AUTO_CLOSE, ALERT_RULE_ADDED, and USER_DELETED, are not standard reasons for the dismissal of an alert in Prisma Cloud. SNOOZED_AUTO_CLOSE refers to the temporary suspension of an alert, ALERT_RULE_ADDED is related to the creation of a new alert rule, and USER_DELETED would pertain to the removal of a user account, not directly to alert dismissal.