The PCSAE certification validates the knowledge and skills required to develop, analyze and administer our Cortex XSOAR security orchestration, automation and response platform with native threat intelligence management.
Cortex XSOAR is a single platform that orchestrates actions across your entire security product stack for faster and more scalable incident response. The PCSAE validates that engineers can correctly understand the utility of out-of-the-box and custom playbooks and integrations. They are also able to identify customer processes that can be automated through XSOAR, and know how to customize XSOAR to reduce the Mean Time to Resolution leveraging the rest of their security products.
Anyone who wants to demonstrate knowledge, skills and abilities using Palo Alto Networks Cortex XSOAR functionality, including customers, partners, system engineers, analysts, and administrators.
Palo Alto PCSAE Exam Overview:
|Exam Name||Security Automation Engineer|
|Exam Price||$175 USD|
|Number of Questions||85|
|Passing Score||Variable (70-80 / 100 Approx.)|
|Recommended Training||Cortex XSOAR IT Administrator
Cortex XSOAR Engineer- Building the Next Generation SOC
Cortex XSOAR SOC Analyst
|Sample Questions||Palo Alto PCSAE Sample Questions|
|Practice Exam||Palo Alto Networks Certified Security Automation Engineer Practice Test|
Palo Alto PCSAE Exam Topics:
|Playbook Development||25%||Conceptualize context data.
– Query and use context data.
– Differentiate between public and private contexts.
Summarize the difference between inputs, outputs and results for playbook tasks.
– Describe inputs and outputs for playbook tasks.
– Describe inputs and outputs sub-playbooks.
– Configure playbooks using the UI (e.g., box of text that you fill in).
– Read, troubleshoot, and respond to error conditions.
Outline how to use Loop sub-playbooks
– Differentiate between the three different loop types of playbooks.
Differentiate between playbook task types.
– Differentiate between manual, automatic, and conditional playbook tasks.
– Gather, analyze, and evaluate data to make decisions about specific playbook task types.
Use Filters and transformers to manipulate data.
– Explain the difference between filters and transformers.
– Identify when filtering and transforming data is required.
– Specify and explain different options of filters and transformers.
|Incident Types, Indicator Types, Layouts, and Fields||20%||Compare and contrast the different incident types.
– Outline the capabilities, functions, and features related to each incident type.
– Summarize the relationship between external data and the XSOAR incident type.
– Assess the consequences of miscategorized incident types.
– Describe how to leverage machine learning in XSOAR.
– Schedule a job to create a new incident to run a playbook.
Outline the different layout types.
– Summarize the purpose of each layout type.
– Specify the different incident layout special sections.
– Summarize the main layout options.
Compare and contrast the different indicator types.
– Outline the capabilities, functions, and features related to each indicator type.
– Explain how data is mapped to an indicator.
– Define criteria for exclusion list entries.
Summarize field types, associated capabilities, and purpose.
– Outline the different field types.
– Align appropriate field types to data types.
– Summarize how fields are created and used.
– Outline advanced field capabilities.
|Automations and Integration and Related Concepts||20%||Use automations to respond to incidents
– Outline the different types of automation.
– Differentiate between inputs and outputs.
– Apply script helper.
– Apply permission access.
– Differentiate automation objects.
– Apply appropriate automation commands.
– Identify how to build and test automations.
– Use automations for Incidents and Playbook tasks.
Outline integration concepts.
– Differentiate between parameters and arguments.
– Implement role-based access and controls (RBAC).
– Define integration types.
– Describe capabilities related to custom integrations.
– Describe the process of contributing integrations to the marketplace.
Configure integration instances.
– Apply basic troubleshooting if the integration is not performing.
– Apply the appropriate classification and mapping technique.
– Classify and map a set of data to different types of fields.
|Solution Architecture||15%||Describe the components of the XSOAR System Architecture.
– Describe the relationship between servers, live backup, Devprod, and other available components.
– Summarize how XSOAR uses the Docker component.
– Specify the benefits and differences between back-up types.
– Differentiate between a stand-alone tenant and multi-tenant.
– Describe threat intelligence management capabilities.
Assess system architecture and outline scalability opportunities.
– Review the system diagram and summarize the flow of data.
– Export log bundle and send for investigation.
– Identify common errors and refer for troubleshooting.
– Identify usage of engines.
Create incidents using XSOAR.
– Describe the three ways incidents are created.
– Understand the logic and order of incident creation.
|Content Updates and Content Management||10%||Outline marketplace concepts.
– Identify challenges and benefits related to marketplace concepts.
– Describe marketplace content.
– Outline the product development lifecycle.
– Identify how content can be searched.
– Describe the relationship between the marketplace and Docker.
Apply custom content and manage content updates
– Describe the purpose of content updates.
– Outline the process of how content is updated and why.
– Summarize the relationship between customer content and existing content updates.
– Outline recommendations for content updates and when custom content would be appropriate.
– Identify the benefits of custom content.
– Describe how new content gets implemented.
– Explain when imports or exports are appropriate and how it would be done.
|UI Workflow, Dashboards, and Reports||10%||Navigate the UI and query system data.
– Navigate between the different options in the system.
– Write a structured query using the appropriate syntax.
Summarize the workflow elements used during an investigation.
– Outline the purpose of the workflow elements.
– Differentiate the workflow elements and the impact on an investigation.
Create dashboards and reports.
– Outline the difference between dashboards and reports.
– Select the appropriate dashboard or report.
– Summarize what information can be added, edited or shared within dashboards and reports.
Apply the appropriate widget type.
– Describe the purpose of widgets.
– Define when custom widgets are necessary.