UTD CNSP 2.0 Security Track
UTD CNSP 2.0 Security Track
ULTIMATE
TEST DRIVE
Cloud Native Security
Platform
with Prisma Cloud
Workshop Guide
UTD-CNSP-2.0 | Security Track
UTD-CNSP-2.0 ©2023 Palo Alto Networks, Inc. | Confidential and Proprietary Last Update: 20230831
Table of Content
Note: Unless specified, the Google Chrome web browser will be used to perform any tasks outlined in the
following activities.
Before beginning this workshop, make sure your laptop is installed with a modern browser that supports HTML
5.0. We recommend using the latest version of Firefox®, Chrome, or Internet Explorer. We also recommend you
install the latest Java® client for your browser.
Step 1. Open a browser window and navigate to the class URL. If you have an invitation email, you will find
the class URL and passphrase there. Otherwise, your instructor will provide them.
Step 2. Complete the registration form and click Register and Login at the bottom.
Step 3. Depending on your browser, you may be asked to install a plugin. Please click yes to allow the plugin
to be installed, then continue the login process.
Step 4. Once you log in, the environment will be created automatically for you. The upper left-hand corner will
show you the progress of the preparation. You will see the lab availability time when it is ready for use.
Note: You can leverage the keyboard > send text feature inside of CloudShare when the guide instructs you to
copy/paste linux commands. Also note that when copying/pasting commands, make sure to remove the line
breaks if any before commands are executed.
The Docker workstation provided in this workshop has multiple applications running on it in the form of Docker
containers such as:
All of the above applications are accessible via the Application Portal tab from your CloudShare environment.
Note: You can also SSH to Docker Workstation from your laptop terminal (MAC) or Putty (Windows) using the
external address and login credentials as highlighted in the screenshot.
1. Credentials: kasm_user/p@lo@lto
2. Homepage: http://homepage:3000 (henceforth referred to as Homepage).
3. The Application Portal, upon startup, opens the webpage: If Homepage is not loaded, please refresh the
browser tab or open a new browser tab and navigate to aforementioned URL
4. Homepage provides you access to the various applications used within this workshop.
5. These applications are all running as Docker containers and they are accessible via their internal IPs only
via the Application portal.
6. This ensures that the traffic doesn’t go out the internet, making the setup a bit more secure and reduces
latency.
Below are the list of applications that are accessible via Application Portal and the respective tracks where these
are used in the lab:
1. Prisma Cloud Compute Edition: Click this tab to login on Prisma Cloud Compute Edition (PCCE)
console (Common for all the Tracks)
➢ Credentials: admin/p@lo@lto
2. Prometheus: Monitoring and Alerting Toolkit (Common for all the Tracks)
3. Grafana: Analytics and interactive visualization web application (Common for all the Tracks)
➢ Credentials: admin/admin
4. Splunk: Log aggregation (Common for all the Tracks)
➢ Credentials: admin/password
5. Webhook Receiver: Webhook container to receive incoming webhooks (Common for all the Tracks)
6. Mail Server: Locally hosted mail server (Common for all the Tracks)
7. Visual Studio Code: IDE (Cloud Operations and Developer Tracks)
➢ Credentials: admin/password
8. Jenkins: CICD (Development Track)
➢ Credentials: admin/p@lo@lto
9. DVWA: Damn Vulnerable Web Application docker container is a PHP/MySQL web application
Step 5. Important: This is a browser in browser setup running as a Docker container. DO NOT open more
than 3-4 browser tabs at the same time as it may cause resource exhaustion on the Docker
workstation VM.
If you prefer to use your own terminal from your laptop, you can ssh to this VM using the External Address and
the user name and password under Connection Details in the Connectivity section.
Note: You can also SSH to Docker Workstation from your laptop terminal (MAC) or Putty (Windows) using the
external address and login credentials as highlighted in the screenshot.
Complexity: Easy
Key Takeaways:
● Logging into Prisma Cloud
● View onboarded Cloud Accounts
Step 1. Click on the Prisma Cloud Enterprise Edition tab to open the demo tenant login.
NOTE: If you see a page expired message then refresh the web page by clicking on the Home
button as highlighted in below screen capture.
Step 3. Use the icons from the Action panel virtual keyboard to go back, forward and home screen while using
the Prisma Cloud console.
Step 4. To check the on-boarded public cloud accounts click on the Settings on the left-hand side and select
Account Groups. Click on the 4 Cloud Account(s) under Default Account Group. You can see the
public cloud accounts connected to this Prisma Cloud demo account.
NOTE: The screenshots captured in this workshop guide might vary slightly from the actual lab account.
Step 5. If you click on Add Cloud Account, you will get an access denied message.
NOTE: The Prisma Cloud Enterprise Edition account used in this lab is a read-only account, it does
not have full access to the Prisma Cloud Service and access to some functions is denied. This
account cannot make changes to the configuration of the associated Prisma Cloud Services.
Complexity: Easy
Key Takeaways:
● View SecOps dashboard
● View Policies
● Compliance Dashboard
When you Access Prisma Cloud, you first see the Alerts. You can then use the following tabs to interact with the
data and visualize the traffic flow and connection details to and from the different resources in your cloud
deployment; review the default policy rules and compliance standards; and explore how the web interface is
organized to help you and DevSecOps teams to monitor cloud resources.
● Dashboard
● Inventory
● Investigate
● Policies
● Compliance
● Alerts
● Compute
● Settings
Step 1. Click on the Dashboard > SecOps to review the Dashboard. The Dashboard provides a graphical
view of all assets deployed across multiple public cloud environments. You can use the predefined or
custom Time Range to view current trends or historical data. Or use the Cloud Accounts to focus on
specific public cloud accounts.
Step 3. The Investigate tab helps in identifying security threats and vulnerabilities, creating and saving
investigative queries, and analyzing impacted resources. To conduct investigations, Prisma Cloud
provides a proprietary query language called Resource Query Language (RQL) that is similar to SQL.
Step 4. The Policies tab shows the Prisma Cloud policy which is a set of one or more constraints or
conditions that must be adhered to. Any new or existing resources that violate these policies are
automatically detected.
Step 5. The Compliance > Overview dashboard enables you to view, access, report, monitor and review their
cloud infrastructure health compliance posture. You can also create compliance reports and run them
immediately, or schedule them on a recurring basis to measure your compliance over time.
Step 6. Click on the Compute tab to open up the Compute module in Prisma Cloud. Prisma Cloud offers a
rich set of cloud workload protection (CWPP) capabilities. Collectively, these features are called
Compute.
The Compute tab enables cloud native assets anywhere they operate - regardless of whether running
as containers, serverless functions, non-container hosts, or any combination of them.
Prisma Cloud Compute is also available to install as a self hosted deployment known as Prisma
Cloud Compute Edition. We have provided access to Prisma Cloud Compute Edition for the cloud
workload protection lab activities in Part 2 of this lab.
For more information on Prisma Cloud Compute (in Enterprise Edition) vs Compute Edition, please
visit here for a detailed comparison.
Step 7. The Alerts > Overview allows the admin to view the list of discovered violations and anomalies, drill
into the details and look up remediation options, and create alert rules and notification templates.
When you access Prisma Cloud, you first see the Alerts.
Complexity: Easy
Key Takeaways:
● SecOps dashboard
● Assets exposed to the internet and traffic that they are taking.
The Dashboard SecOps provides a graphical view of the performance of resources that are connected to the
internet, the risk rating for all accounts that Prisma Cloud is monitoring, the policy violations over time and a list of
the policies that have generated the maximum number of alerts across your cloud resources. It makes the
security challenges visible to you as a quick summary, so you can dig in.
Step 1. Click the Dashboard > SecOps, set the Time Range to All Time.
Step 2. Scroll down and click on one of the Top Internet Trafficked Assets by Traffic Type, such as the RDP.
Click on one of the resources, such as PANW-WindowsBastionServer-awsjamconfig to open an
investigation pane for the workload to see what traffic is coming from the internet. Expand the time range
to the last 6 months and you’ll see details about the workloads that are taking traffic directly from the
Internet.
Question: Did the workload take traffic from the Suspicious IP?
Step 4. Now go to the Dashboard > SecOps and scroll down to the bottom of the page and view the connections
from the Internet Connected Assets by Source Network Traffic Behavior map.
Note that if you do not see graphical data for the pink bubble you selected, try a different one. When you
do this, your graph may look different than what’s indicated in the screenshot.
Step 6. Click on View Details to go to the Investigate tab with the subsequent network information.
Complexity: Easy
Key Takeaways:
● Prisma Cloud Asset Inventory
Public cloud environments are very dynamic environments, and a very common customer pain point is visibility
and asset inventory tracking. You can’t protect what they don’t know about, that is why a central cloud
Configuration Management Database(CMDB) is the foundation for building and implementing a solid Cloud
Security program.
The Asset Inventory dashboard (on the Inventory tab) provides a snapshot of the current state of all cloud
resources or assets that you are monitoring and securing using Prisma Cloud. From the dashboard, you gain
operational insight over all our cloud infrastructure, including assets and services such as Compute Engine
instances, Virtual machines, Cloud Storage buckets, Accounts, Subnets, Gateways, and Load Balancers.
Step 3. In the Prisma Cloud Asset Inventory dashboard, scroll down the page and search for and click on the
Google VPC line item in the table in the Service Name column. This will open up the Google VPC assets
view.
Step 4. In the Asset Inventory / GCP | Google VPC page, you can see a quick count on all the number of
unique VPC assets.
Note: Prisma Cloud allows you to easily discover all your cloud resources
across all of your cloud accounts and gives you a security posture view with
regard to those resources. It also allows you to easily drill down to get
details of each resource and whether it has passed or failed a policy. This
enables you to get quite granular at a per resource level.
End of Activity 1
Prisma Cloud Compute Edition (PCCE) - Hosted by you in your environment. Prisma Cloud Compute Edition
(PCCE) is a self-hosted offering that’s deployed and managed by you. It includes the Prisma Cloud Compute
module only. You can download the Prisma Cloud Compute Edition software from the Palo Alto Networks
Customer Support Portal. Compute Console is delivered as a container image, so you can run it on any host with
a container runtime (e.g. Docker Engine).
With Prisma Cloud Compute Edition (PCCE), Radar is the primary interface for monitoring and understanding
your environment. It is the default view when you first log into PCCE Console. It is designed to let you visualize
and navigate through all of Prisma Cloud’s data. For example, you can visualize connectivity between
Complexity: Easy
Key Takeaways:
● Different ways to access Prisma Cloud Compute Edition in the lab.
Step 1. There are a couple of ways to access the Prisma Cloud Compute Edition Console (PCCE Console) in
this lab.
c) When presented a Security exception, click on Advanced > Proceed to 10.160.154.170 (unsafe)
➢ Credentials: admin/p@lo@lto
a) Click on Docker Workstation CloudShare Tab. From the left pane, select Connectivity > Connection
Details > External Address (when you click on it, the address will be copied to clipboard)
Note: You will get a security exception, please ignore it for this lab and proceed to the login page. We
are using a self-signed certificate, which causes the exception.
Step 4. If the message Your connection is not private opens, click Advanced, and then Proceed to <IP
address> (unsafe). Non Chrome browsers might have a different behavior
Step 5. Login to the PCCE console using the following credentials, with Local/LDAP in the drop down:
➢ Credentials: admin/p@lo@lto
Complexity: Easy
Key Takeaways:
● Containers and Hosts discovered by Prisma Cloud
● Radar view
This task guides you through key elements of the Prisma Cloud Compute console to ensure that you are aware of
them. Use this time to explore these elements at your own pace to discover points of interest.
Step 2. Change the View based on different Radar view categories by clicking the dropdown on the top left
corner
Step 3. Click Radars > Hosts, then click the docker-workstation host icon to review the host dashboard.
There is only one host in this lab.
End of Activity 2
Key Takeaways:
● How to access and use lab provided AWS Account
Step 1. Click the Public Clouds icon in the lower left corner. Click Public Clouds Log to make sure all the
resources have been created and deployed successfully.
This hands-on lab lets you do the lab activities yourself in a real cloud environment, not in a simulation or demo
environment. It does so by giving you temporary AWS credentials that you use to sign in and access the AWS
console for the duration of the lab.
Step 2. Click on the Public Clouds icon. A Public Cloud pop up window will appear. Keep this window open.
You are going to use the AWS credentials from this pop up window to login on AWS console
Step 3. Right click on the value for the Account ID in the Public Clouds section in CloudShare and select
Copy link address
Step 5. [Important] Change the AWS region to N. Virginia by clicking on the region drop down arrow and
select the US East (N. Virginia) us-east-1
Step 6. In the AWS console select the search for service box and type cloudformation. Click on
Cloudformation service and select Stacks and you should be able to see 2 stacks.
Step 7. Agentless CloudFormation stack creates an IAM policy that is required for Agentless scanning
capabilities of Prisma Cloud Compute. The second CloudFormation Stack AWS-EC2 is responsible
for creating 2 EC2 instances which will be scanned by the Agentless module, which will be covered in
this lab. For the ease of lab, these prerequisites are already created for you.
Key Takeaways:
● Create AWS IAM Access Key
Step 2. In the account summary page, click on the Security Credentials tab and then scroll down to the
Access Keys section click Create access key.
Then select Command Line Interface radio button and select the I Understand the above…
checkbox and click Next and then click Create access key
Step 4. Open the accessKeys.csv file to make sure you have downloaded the key (Note that after you close
the dialog box, you can’t retrieve this secret access key again.) You can open the csv file and you
should see the Access Key ID and the Secret access key in the file. We will be using this
information later during the lab.
Key Takeaways:
● Use the AWS Credentials created in the previous task.
● Onboarding AWS Account and setting up Agentless scanning
Step 1. Head back to CloudShare Portal > Docker Workstation Tab. Select Connection Details and click
on the External Address to copy the external address
Step 3. Navigate to PCCE Console > Manage > Cloud Account. Select Add Account and select/enter the
following details and click Next:
● Cloud Provider: AWS
● Region Type: Regular Regions
● Account Name: UTD-Account
● Authentication Method: Access Key
● Access Key: Paste the Access Key created previously
● Secret Key: Paste the Access Key created previously
Step 7. Navigate to PCCE Console > Monitor > Vulnerabilities and select "Hosts" from the top menu and
select Scan Agentless.
Step 8. This will start the discovery process of Cloud Resources within the onboarded account and will also
initial Agentless scanning, which we will come back to in later sections during this workshop
End of Activity 3
Hint: As you navigate the alerts view in the Prisma Cloud console you can click the
“Add filters” button (marked with green in the below screenshot) to enable/disable the
needed filters on the left side of the console.
Scenario:
● Your organization has an Azure account and cloud resources in it. It's currently boarded into the Prisma
Cloud.
● You want to view alerts on risky Firewall Rule configurations to gain a better understanding of the
security posture of your Azure Cloud Account.
Key takeaways:
● Understand how you can leverage the Prisma Cloud data correlation to analyze the Firewall risks in
more detail.
Step 1. Navigate to Prisma Cloud Enterprise Edition console > Alerts > Overview.
Step 2. Select the Reset Filters icon on the top right corner of the screen to reset all filters and set the Time
Range to All Time.
Step 5. Click the corresponding value for the Alert ID column next to the Resource Name to see the alert
overview.
Step 6. Then click the View Details option, which shows you the current Firewall configuration for the selected
firewall rule.
Step 7. In the Resource Config Tab, You’ll now see the current Firewall configuration settings for the selected
firewall rule. You can see here that there is a security group that allows all inbound traffic to port 3389,
which should not be used as a best security practice. Close the Configuration window once ready to
move on.
Scenario:
● You have identified an alert on risky Firewall Rule configuration from the previous task
● Now, you want to investigate and understand how the Firewall Rule got to the current state.
Key takeaways:
● Understand how you can leverage the Prisma Cloud data to analyze the audit trail
Step 1. Under the Resource Name column, click the name of the firewall rule Rdp to view the Audit Trail for
the firewall rule.
Step 4. You can get further information associated with the resources including Config
Complexity: Easy
Scenario:
● You have analyzed the audit trail and have all the context and background about the alert from the
previous tasks
● You now want to remediate that security event and resolve the alert.
Key takeaways:
● Understand how you can leverage the Prisma Cloud to remediate the security event effortlessly.
Step 1. Head back to the Alerts Overview > Azure Network Security Group allows all traffic on RDP Port
3389 screen (using the Keyboard : Back controls). Make sure to set the “Time Range” filter to “All Time”.
Click on the Alert number in the Alert Count column and click the "Recommendation" tab next to the
Violating Resources column, which will show you the Prisma Cloud remediation recommendation
associated with this alert.
Step 3. Now go ahead and review a few more remediation examples of the configuration alerts.
Note: With Prisma Cloud you are able to get a JSON of your resource
configuration so that you can easily understand what are the changes that were
made over time to identify when the alert violation occurred and who made the
change. Prisma Cloud can also be used to Remediate those violating
configuration in your resources by issuing the CLI commands to correct those
misconfigurations. This can also be set to Auto Remediate.
End of Activity 4
Background: This example demonstrates how Prisma Cloud can be used to alert on suspicious network traffic,
and how to analyze networks in the Prisma Cloud console.
In this activity you will:
Hint: As you navigate the alerts view in the Prisma Cloud console you can click the
“Add filters” button to enable/disable the needed filters on the left side of the
console.
Scenario:
● Your organization is operating in a hybrid cloud environment and you have compute resources
deployed across multiple Cloud providers.
● Some of these resources are internet facing.
● View a Network Alert for suspicious activity. detected by Prisma Cloud.
Key takeaways:
● Understand how Prisma Cloud can be used to alert on suspicious network traffic.
Step 1. In the Prisma Cloud Enterprise Edition console, click the Alerts tab and then Overview.
Step 2. Select the Reset Filters icon on the top right corner of the screen to reset all filters and set the Time
Range to All Time.
Step 3. Click on Add Filter icon and select the following options:
Step 5. Search for the linux using the search bar. Click on the corresponding value in the Alert ID Column for
LinuxBastion. Then click Investigate.
Step 6. In the Investigate window, change the time range to Past 7 days in the top right corner.You’ll now see a
network map with the workloads(virtual machines) that have received traffic from public IP addresses
within the time range selected in the top right corner of the console.
Scenario:
● Your organization is operating in a hybrid cloud environment and you have compute resources
deployed across multiple Cloud providers and some of these resources are internet facing.
● Analyze the Network Visualization to trace resources that may have been impacted.
Key takeaways:
● Understand how Prisma Cloud NEtwork Visualization can be used to to trace resources that may have
been impacted
● Prisma Cloud Resource Query Language (RQL)
Prisma Cloud Resource Query Language (RQL) is a powerful and flexible tool that helps you gain security and
operational insights about your deployments in public cloud environments. You can use RQL to perform
configuration checks on resources deployed on different cloud platforms and to gain visibility and insights into
user and network events. You can use these security insights to create policy guardrails that secure your cloud
environments. We are going to take a closer look at the RQL here.
Note: Animation may take some time to load after the RQL query is executed.
Step 2. The new text in the RQL search bar should look like this. You will now see a network map of traffic coming
from suspicious IP Addresses.
Step 3. You will now see a network map of traffic coming from suspicious IP Addresses. Your diagram may look a
little different as the cloud environment is very dynamic.
Step 4. Single-click on PANW-WebServer in the network map, and explore the Instance Summary sections on
the right side to review some of the instance information such as IP addresses, VPC, Account Names,
etc.
Step 5. Click the Network Summary section on the right side of the console and see the Firewall Rules applied
to the selected workload. You can see there are no limitations on both inbound and out-bound traffic,
which is a security risk.
Scenario:
● Your organization is operating in a hybrid cloud environment and you have compute resources
deployed across multiple Cloud providers and some of these resources are internet facing.
● Analyze the Network Visualization to trace resources that may have been impacted.
Key takeaways:
● Understand how Prisma Cloud Network Visualization can be used to examine the blast radius.
Step 1. Continuing from the last task, ensure the Past 7 days is selected in the time range next to the RQL
search field.
Step 2. Double click the LinuxBastion host in the network map to analyze the East - West traffic (blast radius)
behind the LinuxBastion host.
Step 3. Review the Instance Summary of the LinuxBastion to get some idea of where this VM is hosted.
Scenario:
● Your organization is operating in a hybrid cloud environment and you have compute resources
deployed across multiple Cloud providers and some of these resources are internet facing.
● Analyze the Network Visualization to trace resources that may have been impacted.
Key takeaways:
● Understand how Prisma Cloud Network Visualization can be used to examine the blast radius.
Step 1. In the network map, click on the communication links from the Suspicious IPs to the LinuxBastion VM.
Step 3. Click the View Details option to open a more detailed view of the inbound traffic to the LinuxBastion VM.
Step 4. Review the Threat Feed Source column that indicates the services that identify those IPs as suspicious. If
you see AutoFocus, that is the threat intelligence service provided by Palo Alto Networks, see here for
more details. You can download the list of suspicious IP addresses and access the LinuxBastion VM for
further analysis or action. Click ESC to close the details window.
Scenario:
● Your organization is operating in a hybrid cloud environment and you have compute resources
deployed across multiple Cloud providers and some of these resources are internet facing
● Examine Vulnerabilities that have been detected on your Cloud Workload to understand the risk
posture
Key takeaways:
● Understand how Prisma Cloud Network Visualization can be used to examine the blast radius.
Step 1. Click on the LinuxBastion VM, and under the Instance Summary, click the Resource ID to investigate
further on the VM.
Step 2. Go to the Findings tab at the top of the page to get details on 3rd Party Vulnerability findings. Notice the
findings by AWS GuardDuty.
Step 3. In this case the host has vulnerabilities and is taking traffic directly from a suspicious Internet IP and
should be investigated further.
Step 4. Click on the Vulnerabilities tab to look at host vulnerabilities for that resource.
End of Activity 5
Scenario:
● Your team has a Github source code repository and you want to assess the security posture by
scanning the repo to see if there are any misconfigurations and vulnerabilities before it’s deployed.
Key Takeaways:
● Explore Prisma Cloud Application Security module.
● Examine secrets hardcoded that’s detected by Prisma Cloud.
Step 1. Navigate to Prisma Cloud > Application Security > Projects. Below are a few examples of filters
that you can use. Make sure that there’s nothing selected for the Severities filter.
Step 2. Select the Secrets tab and set the repository filter to UltimateTestDrive/utd-vuln-code
Step 4. Click on cnf.yaml and on the right pane, select issues and scroll down to see the details.
Scenario:
● Your team has a Github source code repository and you want to assess the security posture by
scanning the repo to see if there are any misconfigurations and vulnerabilities before it’s deployed.
Key Takeaways:
● Explore Prisma Cloud Application Security module.
● Explore detected misconfigurations in code such as Terraform, Kubernetes manifests etc.
Step 1. Select the IaC Misconfiguration tab and set the below filters:
Repository: UltimateTestDrive/utd-vuln-code
Issue Status: Errors
Severities: Critical, High
Note: Once you apply the filter, you may need to scroll down the page to find the highlighted result.
Step 3. Select AWS S3 bucket ACL grants READ permission to everyone and click on one of the entries
that has the label Has Fix. See the screenshot above.
Step 4. Optionally, click on the overview tab. Here you can add an additional filter by clicking on the filter icon
on the left and selecting IaC Categories and selecting Kubernetes to filter only Kubernetes related
code. Once you apply the filter, explore the filtered results before proceeding to the next step.
Scenario:
● Your team has a Github source code repository and you want to assess the security posture by
scanning the repo to see if there are any misconfigurations and vulnerabilities before it’s deployed.
Key Takeaways:
● Explore Prisma Cloud Application Security module.
● Explore detected vulnerabilities in Docker code.
Step 1. Navigate to Prisma Cloud > Application Security > Projects and select the Vulnerabilities tab and set
the below filters:
Repository: UltimateTestDrive/utd-vuln-code
Issue Status: Errors
Code Categories: Vulnerabilities
Severities: Critical, High
Step 2. The above filter lists all the resource definitions (Dockerfiles) vulnerable base-image, package or code is
detected. Explore the different code blocks that are matched by this filter.
Scenario:
● Your team has a Github source code repository which is onboarded into Prisma Cloud.
● Whenever your team creates a PR (pull request), you would like automated scans to be performed on
the changes and you’d like the PR to automatically be received by Prisma Cloud and have it comment
it’s findings on the PR
Key Takeaways:
● Prisma Cloud Pull request review feature.
Step 1. Head over to utd-vuln-code Github repository. This repo contains intentionally vulnerable code and this
repo has already been onboarded within Prisma Cloud, which we will review in a bit.
Step 3. Here, you can see various comments by Prisma Cloud that occur automatically when a pull request is
created for an onboarded source code repository.
Step 4. Looking closely at one of the findings and comments, you can see the violation title and description
and also information on how to fix it. You can also see the code snippet which triggered this violation.
Step 7. You can also view these findings in Prisma Cloud as well. Head over to Prisma Cloud > Application
Security > Projects > VCS Pull Requests and select the following filters:
● Repositories: UltimateTestDrive/utd-vuln-code
● Pull Request: #1 - Second Commit
Scenario:
● Your team has a Github source code repository and you want to assess the security posture by
scanning the repo to see if there are any misconfigurations and vulnerabilities before it’s deployed.
Key Takeaways:
● Explore Prisma Cloud Application Security module.
● Prisma Cloud’s automated fix feature.
Step 1. Navigate to Prisma Cloud > Application Security > Projects > Overview tab and select the below
filters. Make sure to unselect the filters selected in the previous task(s) first.
Repository: UltimateTestDrive/utd-vuln-code
Step 2. From your left pane, select the filter icon to add a filter: IaC Labels and select Has Fix
Step 3. Clicking on any of the results will display Details section that contains information on what the fix is and is
highlighted in green
Step 5. Please note that you will not be able to see “Fix” and “Submit” (grayed out) options as we are using a
user with Read-Only permissions for the purpose of the lab. “Fix” and “Submit” options will apply the
Prisma Cloud suggested fix and commit the changes to the source control repository. The “Fix” and
“Submit” options are included in the screenshots to demonstrate the capabilities of the Application
Security module.
End of Activity 6
Scenario:
● Your team/organization wants more visibility on Compliance in your environment.
Key Takeaways:
● Prisma Cloud Compliance Explorer.
● Compliance Explorer gives you a picture of the overall compliance of the entities in your environment.
Step 2. Here you can see the compliance overview. You can also understand the Compliance Trend over a
period of time. You can also explore Compliance Coverage
Step 4. In the breadcrumbs on the top, click on Overview to get back to the previous screen.
Step 5. Clicking on View Requirements of a specific Compliance Standard will show the requirements of that
standard. You can also see the total number of Policies for that standard and the number of passing and
Step 7. Click on Add Filter and select Cloud Account and then select AWS UTD Account. Here you can see the
Compliance reports for the selected AWS Cloud Account.
Step 8. Clicking on the Download icon, you will be able to download the report. However, you will not be able to
do that in this lab environment.
Step 9. Navigate to Prisma Cloud Enterprise > Compliance > Standards. Here you will be able to see all the
available Compliance Standards. You can explore different compliance standards and the applicable
Clouds as well.
Scenario:
● Your team/organization wants more visibility on Compliance in your Compute environment.
Key Takeaways:
● Prisma Cloud Compliance Explorer.
● Compliance Explorer gives you a picture of the overall compliance of the entities in your environment.
Step 1. Compute Section is available both in Prisma Cloud Enterprise Edition as well as Prisma Cloud Compute
Edition. Both offer the same capabilities. For this task, we will be looking at Prisma Cloud Compute
Edition compliance explorer
Step 2. Go to PCCE Console > Monitor > Compliance > Compliance Explorer. Here you can get an overview
of Compliance for your compute environment.
Step 4. Clicking on Images tab, will bring up the list of images in the environment and provide the compliance
status of those images.
End of Activity 7
● Get an overview of Data Security via Prisma Cloud dashboard and inventory
● Examine Sensitive Objects discovered by Data Security
Scenario:
● You have AWS S3 bucket(s) in your organization, where you store certain data.
● You want to discover and classify data stored in AWS S3 buckets and protect against accidental
exposure, misuse, or sharing of sensitive data.
Key takeaways:
● Explore Prisma Cloud Data Security Dashboard to get an overview of the assets discovered by it.
Step 1. Navigate to Prisma Cloud > Dashboard > Data and select the following filters:
Step 2. This dashboard provides a good overview and representation of detections by the Data Security module.
Step 4. This provides an overview of the Data inventory of the connected Cloud Account and a specific S3 bucket
based on the selected filters.
Scenario:
● You have AWS S3 bucket(s) in your organization, where you store certain data.
● You want to discover and classify data stored in AWS S3 buckets and protect against accidental
exposure, misuse, or sharing of sensitive data.
Key takeaways:
● To identify and detect confidential and sensitive data, Prisma Cloud Data Security integrates with Palo
Alto Network's Enterprise DLP service and provides built-in data profiles, which include data patterns
that match sensitive information such as PII, health care, financial information and Intellectual Property.
● Protect data against threats - known and unknown (zero-day) malware—using the Palo Alto Networks
WildFire service.
Step 1. Click on the number in the Sensitive Objects column. In this page, for the Data Profiles filter, make
sure that the following options are selected: Financial information, Healthcare, Intellectual Property,
PII
Step 3. In the results, search for and select 26_all_patterns_test.txt. This displays all the sensitive information
detected by the Data Security module in that specific file/object Now, under the Snippets column, if
there's a snippet available, “available” keyword should be highlighted which can be selected to display
the snippet which triggered the alert. There are multiple snippets that are detected based on selected
data profiles and feel free to check out different snippets that are generated.
Step 4. Navigate to Prisma Cloud > Inventory > Data and select the following filters:
Step 5. Click on the number in the Malware column and in the search bar and click on any of the files to find
details about the detected malware.
Scenario:
● You have an AWS Account for your team and you have many IAM roles and profiles.
● You want to get visibility into all the IAM policies and make sure that they aren’t over permissive and
maintain good security posture.
Key takeaways:
● Prisma Cloud IAM Security capabilities.
● Out of the box Prisma Cloud IAM governance policies.
Step 1. Navigate to Prisma Cloud > Policies. Select the filter button and apply the following filters:
Step 2. The dashboard should display all the default Prisma Cloud Policies that come out of the box
Complexity: Easy
Scenario:
● You have an AWS Account for your team and you have many IAM roles and profiles.
● You want to get visibility into all the IAM policies and make sure that they aren’t over permissive and
maintain good security posture.
Key takeaways:
● Investigate over-privileged AWS IAM Permissions.
Step 1. Navigate to Prisma Cloud > Alerts > Overview. Select the filter button and apply the following filters:
Step 2. In the search bar, type in the following to filter the alert: AWS EC2 with IAM wildcard resource access
Step 4. Click on the Alert ID in the Alert ID column for any resource from the list and select investigate.
Step 5. Click on the "<>" icon in the Actions column to view the resource config.
Scenario:
● You have an AWS Account for your team and you have many IAM roles and profiles.
● You want to get visibility into all the IAM policies and make sure that they aren’t over permissive and
maintain good security posture.
Key takeaways:
● Prisma Cloud RQL(Resource Query Language)
Step 1. In this task, we will find out, with a simple RQL query, the net effective permissions of an IAM user to
demonstrate the effectiveness of IAM RQL queries in Prisma Cloud
Step 2. Navigate to Prisma Cloud > Investigate and paste the below query in the search (CTRL+V on your
keyboard should work for pasting into Prisma Cloud VM).
Step 5. Within the destination column of the graph, select “codecommit” (or run the query below) and select the
expand icon to see the granular permissions.
Step 6. From the screenshot, you can see that there’s a “*” (wildcard) permission assigned, which is not a best
practice implementation in a production environment.
Step 7. From the top right corner of the Investigate page, select “clear all” to clear the previous query and run the
following query to determine which roles and users have access to a specific S3 bucket
Step 8. After you run the above RQL query, select the “Graph” button. In the “Source” column, select “IAM” and
Step 9. After you run the above RQL query, select the “Graph” button. In the “Source” column, select “IAM” and
expand the tile to see the full permission.
End of Activity 9
In this activity you will explore Prisma Cloud Compute Agentless scanning capabilities
Scenario:
● You have AWS EC2 instances where you cannot install Prisma Cloud Defenders but you want to have
complete coverage of all the resources.
Key takeaways:
● Prisma Cloud Agentless capabilities.
Step 1. Navigate to PCCE Console > Monitor > Vulnerabilities and select "Hosts".
Note: If you do not see more than 1 host listed under hosts, head to PCCE Console > Monitor > Hosts and click
on Scan Agentless and wait for a few minutes for the agentless scanning to be complete.
Step 2. The Agentless column in the table indicates whether or not the Agentless module was used to scan that
particular host.
Step 4. Click on the identified host from the previous step to see the Host details gathered by the Agentless
module.
Step 5. Click on any of the identified vulnerabilities to see details, CVE and the risk factor score
Step 7. Navigate from the "Hosts" tab at the top of the screen to "Vulnerability Explorer"
Step 8. On the same page, scrolling down further, you will see "Top critical vulnerabilities (CVEs)". Click on any
of the vulnerabilities. For example, selecting CVE-2021-3177 row and clicking on the corresponding entry
on the "Impacted Packages" column will show more information about the CVE and the hosts impacted
by this vulnerability.
End of Activity 10
It’s recommended that you pick 1 or 2 tasks in this activity that are most relevant to you depending on
your interest.
Complexity: Easy
Scenario:
● In your organization, you have an existing monitoring setup that consists of Prometheus and Grafana.
● You want to integrate Prisma Cloud with Prometheus and Grafana
Key takeaways:
● Prisma Cloud Prometheus and Grafana integration.
Step 1. We’ve already configured Prisma Cloud Compute and Prometheus instrumentation. Navigate to PCCE
Console > Manage > Alerts > Logging and you can see that Prometheus Instrumentation is
enabled.
cat /home/sysadmin/setup/volumes/prometheus/prometheus.yml
Step 2. From the Application Portal, click on Prometheus to ensure that it’s up and running.
Step 3. Navigate to Prometheus > Status > Targets and notice that targets are Up. If not, wait for a few
seconds.
Step 5. Within Grafana, head over to Home > Connections > Data Sources
Step 6. The Grafana setup is already configured with Prometheus as its Data Source.
Step 11. Let’s repeat the process for the other Prisma-Cloud-Dashboards from step 7 . Head over to Grafana
> Home > Dashboards > Compute Prometheus Counters
Step 12. Navigate to Docker Workstation and in the terminal run the below commands to stop Prometheus and
Grafana containers in preparation for the next set of tasks as they aren’t needed anymore:
Complexity: Easy
Scenario:
● In your organization, you have a custom setup that consumes incoming webhook data from multiple
sources and runs custom data processing and/or manipulation.
● You would like to configure Prisma Cloud alerting via webhooks feature.
Key takeaways:
● Prisma Cloud webhook integration.
Step 1. Navigate to PCCE Console > Manage > Alerts > Manage and click on Add Profile to add a provider
Step 3. For the Triggers, enable the following and click next:
● Vulnerabilities: All
● Compliance: Container and Image compliance
● Runtime: Container runtime and Incidents
● Access: All
Step 5. Select Copy Webhook URL and head back to the Prisma Cloud Compute screen.
Step 6. Paste the copied URL into the Incoming webhook URL field and click Next
Step 8. Head back to the webhook application page and you should see the test webhook data come in from
Prisma Cloud.
Step 10. Head back to the Webhook page to see the alert come in (the alert might differ in your case if a
different alert is triggered that was covered in previous tasks/activities):
Step 11. Navigate to Docker Workstation and in the terminal run the below commands to stop webhook and
redis containers in preparation for the next set of tasks as they aren’t needed anymore:
Complexity: Medium
Scenario:
● In your organization, you have an existing log aggregator such as Splunk setup.
● You would like to configure Prisma Cloud to ship alerts to Splunk
Key takeaways:
● Prisma Cloud Splunk integration.
Step 1. Navigate to Application Portal and select Splunk and login to Splunk (Credentials: admin/password).
Once done, click on Settings drop down from the Splunk landing page and select Data Inputs
Step 2. Click on +Add New corresponding to HTTP Event Collector row from the Data Inputs page
Step 4. In the Input Settings page, click on main under Select Allowed Indexes . Once you do this, you
should see the selected main item get copied over to the Selected item(s) box. Then click review
Step 10. Navigate to PCCE Console > Manage > Alerts > Manage and click on Add Profile to add a provider
Step 12. For the Triggers, enable the following and click next:
Vulnerabilities: All
Compliance: Container and Image compliance
Runtime: Container runtime and Incidents
Access: All
Auth Token: Paste the one that you have copied or made note of in Step 6.
Step 14. Click Next. At the summary screen, click Send test Alert and click save.
Step 16. Within the Search bar, enter the following search string: index=main and hit return or click the search
icon
Step 18. Head back to the previous Splunk page and within the Search bar, enter the following search string:
index=main and hit return or click the search. Click the first result and expand the message [+].
Step 19. Navigate to Docker Workstation and in the terminal run the below commands to stop splunk container
in preparation for the next set of tasks as they aren’t needed anymore:
Complexity: Easy
Scenario:
● You would like to configure Prisma Cloud to send you emails when there’s an alert/incident.
Key takeaways:
● Prisma Cloud mail integration.
Step 1. Navigate to PCCE Console > Manage > Alerts > Manage and click on Add Profile to add a provider
Step 2. Set the Profile name as “Email” and select “Email” in the Provider dropdown and click Next
Step 3. For the Triggers, enable the following and click next:
Step 4. Head over to the Application Portal and click on Mail and copy the IP address from the URL bar (IP
may be different in your case)
Step 5. Head back to the Prisma Cloud Compute screen and input the following information on the
configuration screen:
● SMTP Address: The IP that you copied (without the http:// )
● Port: 1025
● From: alerts@prismacloud.local
● Recipients - Static list of emails: admin@prismacloud.local
Step 7. Click Next. At the summary screen, click Send test Alert and click save.
Step 8. Head over to the mail server and you should see the Prisma Cloud test alert.
UTD-CNSP-2.0 ©2023 Palo Alto Networks, Inc. | Confidential and Proprietary 100
Step 9. You have now successfully configured Prisma Cloud and Email integration. Let’s test it in real time.
Head back to the Docker Workstation and run the below command to trigger an incident:
Step 10. Navigate to Docker Workstation and in the terminal run the below commands to stop mail container as
they it isn’t needed anymore:
End of Activity 11
UTD-CNSP-2.0 ©2023 Palo Alto Networks, Inc. | Confidential and Proprietary 101
Activity 12: Feedback on Ultimate Test Drive
Thank you for attending the Ultimate Test Drive workshop. We hope you have enjoyed the presentation
and lab activities that we have prepared for you. Please take a few minutes to complete the online survey
form to tell us what you think.
Step 2. Please complete the survey and let us know what you think about this workshop.
Congratulations! You have now successfully completed the Prisma Cloud Native Security Ultimate Test Drive
workshop.
End of Lab
UTD-CNSP-2.0 ©2023 Palo Alto Networks, Inc. | Confidential and Proprietary 102
Appendix 1: On-board a AWS Account
Prisma Cloud trial provisioning will take a few hours to complete. It’s very likely your free trial version tenant will
not be ready during this workshop. You can refer to the steps here to connect your existing AWS account to the
Prisma Cloud trail when it is ready. To connect other public cloud services to your Prisma Cloud trial account, visit
here for more details.
To connect your AWS Organizations (only supported on public AWS) or AWS accounts on the public AWS, AWS
China, AWS GovCloud account to Prisma™ Cloud, you must complete some tasks on the AWS management
console and some on Prisma Cloud. You will need sufficient access rights on the AWS account in order to
complete the onboarding process. The onboarding workflow enables you to create a Prisma Cloud role with either
read-only access to your traffic flow logs or with limited read-write access to remediate incidents. With the correct
permissions, Prisma Cloud can successfully connect to and access your AWS account(s).
Step 1: Create a CloudWatch log group and enable flow logs on your AWS account.
Step 2: Download the CFT template to set up the Prisma Cloud role on AWS.
https://s3.amazonaws.com/redlock-public/cft/rl-read-only.template
(2) CFT to setup a role to Monitor & Protect the AWS account:
https://s3.amazonaws.com/redlock-public/cft/rl-read-and-write.template
Step 3: Create CloudFormation stack to deploy one of the CFT downloaded in the previous step to setup the
Prisma Cloud role on AWS.
Step 4: Once CFT deployment is successful, copy the value of the Prisma CloudARN from stack Outputs.
Step 5: With your Prima Cloud trial account ready, login to the Prisma Cloud tenant console and select
Settings > Cloud Accounts > Add New.
NOTE: Access denied is expected if you do this step on a Prisma Cloud tenant used in this lab. The
demo account used in this lab is a read-only account, it does not have full access to the Prisma Cloud
Service and access to some functions is denied.
A cloud account name is auto-populated for you. You can replace it with a cloud account name that
uniquely identifies your AWS account on Prisma Cloud.
Step 8: Select either the Monitor or Monitor & Protect Mode and click Next.
UTD-CNSP-2.0 ©2023 Palo Alto Networks, Inc. | Confidential and Proprietary 103
Mode selection decides whether to enable permissions to only monitor (read-only access) or to
monitor and protect (read-write access) the resources in your AWS cloud account.
Step 9: Paste the Prisma CloudARN (refer step 4) and click Next.
The Prisma Cloud ARN has the External ID and permissions required for enabling authentication
between Prisma Cloud and your AWS account.
Step 11: Review the onboarding Status of your AWS account and click Done and then click Close.
The status check verifies the services that are enabled and disabled on your AWS account.
https://docs.paloaltonetworks.com/prisma/prisma-cloud/prisma-cloud-admin/connect-your-cloud-platfor
m-to-prisma-cloud/onboard-your-aws-account/add-aws-cloud-account-to-prisma-cloud.html#id8cd842
21-0914-4a29-a7db-cc4d64312e56
End of Appendix-1
UTD-CNSP-2.0 ©2023 Palo Alto Networks, Inc. | Confidential and Proprietary 104