Automate Global Secure Access With Prisma Access and Cortex XSOAR
Automate Global Secure Access With Prisma Access and Cortex XSOAR
Palo Alto Networks | Automate Global Secure Access with Prisma Access and Cortex XSOAR | Brief 1
Integration Features Automate Source IP-Based
As organizations newly depend on largely remote w orkforces, Whitelisting
Prisma™ Access provides cloud-delivered security and a ccess
for employees anywhere in the world. It rapidly enables Challenge
remote workers without the need for additional hardware
When you deploy workloads in a public cloud, it is a security
or infrastructure deployment, and it automatically scales as best practice to enforce source IP-based restrictions by setting
the workforce grows. At Palo Alto Networks, our own global up appropriate security groups or firewall rules—for instance,
workforce of more than 7,000 employees across 39 office a rule to only allow SSH access to a cloud instance from a spe-
locations is now entirely remote, leveraging our own solu- cific set of IP addresses. To allow your users to access this
tions. Moreover, we’ve successfully transitioned our inter- instance via Prisma Access, you need to whitelist Prisma Access
nal SOC to a fully operational remote model, which continues egress IPs.
to monitor for threats, protecting our user population with
Prisma Access and Cortex™ XSOAR. Prisma Access can auto-scale in response to surge in remote
workers. Whenever there is an auto-scale event, or when new
Cortex XSOAR consumes feeds from Prisma Access and Cortex Prisma Access locations are provisioned, these new egress IPs
Data Lake. These feeds can include alerts (e.g., egress IP need to be whitelisted to ensure continuous user c
onnectivity
notifications) or indicators of compromise (e.g., malicious or to those workloads. Using legacy security, administrators
anomalous user behavior) that are relevant to a SOC analyst or have to manually update all their security groups and fire-
network administrator. Upon receiving these triggers, Cortex wall rules when such events happen, making it hard to scale
XSOAR can automatically correlate data from other sources, quickly or respond in real time to any changes.
enrich the data, and take the right actions, such as whitelisting
egress IPs, logging out a user, or disabling a user account. All Solution
these actions are performed by way of automated playbooks for
With Prisma Access and Cortex XSOAR, when an auto-scaling
quick and consistent incident response.
or new provisioning event comes in, the related Cortex XSOAR
Cortex XSOAR enables organizations to: playbook immediately picks up the new list of Prisma Access
• Automate triage of remote connectivity and user activity egress IPs and automatically updates the relevant security
alerts. groups or firewall rules on the cloud platform. This ensures
• Manage indicator blocklists (add, access, delete) auto- business continuity with no loss or interruption for your users
matically in real time. who need access to these workloads or software-as-a-service
(SaaS) applications.
• Leverage hundreds of third-party product integrations to
coordinate response across security functions based on
insights from Prisma Access and Cortex Data Lake.
• Run hundreds of commands (including for Prisma Access)
interactively via a ChatOps interface while collaborating
with other analysts and the Cortex XSOAR chatbot.
PN
Manage Logs
Alerts
Indicators of
Cortex XSOAR compromise
Automated response
Enriched data
Palo Alto Networks | Automate Global Secure Access with Prisma Access and Cortex XSOAR | Brief 2
Automate Multi-Factor Automate M alicious User
Authentication Enforcement Activity Response
Challenge Challenge
Your remote access policy probably includes multi-factor Many modern organizations allow users to connect from
authentication (MFA) for users connecting from untrusted or corporate-managed devices as well as their personal devices.
unknown IPs. This is configured in your identity and access When the security posture of an endpoint cannot be trusted,
management (IAM) solution, such as Okta, where you define or when your users visit phishing sites or malicious domains,
trusted IPs. For example, when a user connects from head- you want to track those endpoints and users so that you can
quarters, from a branch office, or through Prisma Access—all take corrective actions. Manually tracking user logins and
considered trusted networks—MFA is not required. However, triaging malicious logins is repetitive and time-consuming,
when that same user connects from a public Wi-Fi hotspot, and high volumes of threat logs and alerts are difficult to
MFA is required. parse and address in a timely manner, presenting attackers
With auto-scaling or provisioning of new locations, the list of with a window of opportunity.
Prisma Access IPs assigned for your organization will change.
Solution
Whitelisting these new egress IPs is done manually (and thus
often slowly), so a user connected to these new Prisma Access Alerts such as threat logs or compromised endpoints talking
instances may still be required to do MFA even if accessing to command-and-control servers can trigger Cortex XSOAR
their SaaS applications via a trusted network. This results in playbooks to automatically pull user details from a directory
poor user experience and less-than-seamless connectivity. such as Active Directory, log the user out, and enforce MFA
and/or disable the user’s account. This playbook can moni-
Solution tor active users and take actions—such as logging users out
A Cortex XSOAR playbook triggered by an incoming if there is unauthorized activity, or updating user tags on the
auto-scaling or new provisioning event immediately picks firewall—all from the Cortex XSOAR interface.
up the new list of Prisma Access egress IPs and a
utomatically
updates your IAM. So, when users connected to these new Panorama Prisma Access Cortex Data Lake
SaaS 3
Disable user account
Egress IPs
IP1 IP2 IP3
Palo Alto Networks | Automate Global Secure Access with Prisma Access and Cortex XSOAR | Brief 3
onitor and Alert on Broken
M Solution
Tunnels Between Branches Enter Jobs, a Cortex XSOAR feature that runs playbooks and
helps SOCs automate proactive security operations. An auto-
mated VPN tunnel monitoring playbook can be scheduled to
Challenge poll Prisma Access connection statuses on a regular basis and
In a security team’s busy day, there is no time to proactively send a Slack® alert for remediation actions if a tunnel is down.
monitor for potential connectivity downtime as staff is usually
busy firefighting and triaging critical incidents. Among other
things, this makes it difficult to keep track of the health status
of all VPN tunnels to ensure 100% uptime for users.
3000 Tannery Way © 2020 Palo Alto Networks, Inc. Palo Alto Networks is a registered
Santa Clara, CA 95054 trademark of Palo Alto Networks. A list of our trademarks can be found at
https://www.paloaltonetworks.com/company/trademarks.html. All other
Main: +1.408.753.4000 marks mentioned herein may be trademarks of their respective companies.
Sales: +1.866.320.4788 automate-global-secure-access-with-prisma-access-and-cortex-
Support: +1.866.898.9087 xsoar-b-060820
www.paloaltonetworks.com