Paloalto Networks PSE-Cortex Palo Alto Networks System Engineer - Cortex Professional Exam Practice Test

Premium Customer Success is an important part of any Cortex bill of materials because it offers expert-led configuration guidance. This ensures that customers can effectively set up and optimize the Cortex platform according to their specific needs and security requirements, helping them achieve the best results and reduce time to value.

Cortex Xpanse uses continuous internet scanning to identify previously unknown assets. This feature allows the platform to continuously monitor the internet for new or unregistered assets that could be associated with an organization's network, providing real-time visibility into potential exposure or vulnerabilities.

The ASM for Remote Workers module in Cortex Xpanse focuses on analyzing global scan data, identifying risky issues on remote networks, and providing internal insights. This helps organizations maintain visibility and control over the security of their remote workforce, ensuring that potential risks and vulnerabilities in remote network configurations are addressed proactively.

Cortex XSOAR automation helps save time during a phishing incident by purging unopened phishing emails from user mailboxes. This automated response reduces the need for manual intervention, allowing security teams to quickly contain the threat and prevent further exposure, while also enabling them to focus on more complex tasks.

The integration of Attack Surface Management (ASM) in Cortex XSIAM enriches incidents with ASM data for all internet-facing assets, providing a unified approach to security event management. This integration helps identify and address vulnerabilities related to external assets, offering more context and enhancing the overall security incident response. Traditional SIEMs typically lack this level of integration with external asset visibility.

Adding processing resources for heavily used integrations, ensuring that the workload is distributed effectively across multiple engines via load-balancing groups.

Integrating with tools in network locations that the main Cortex XSOAR server cannot reach directly, ensuring proper communication and functionality between the server and isolated systems.

A clear understanding of a customer’s technical expertise helps post-sales teams customize their support and training efforts to match the customer's knowledge level. This ensures that the customer receives the appropriate guidance, training, and resources needed to effectively use the product or solution after the sale.

Audit users in Cortex XSOAR have limited, read-only access to the system, which allows them to view information without making any changes. Full users, on the other hand, have read-write access, meaning they can both view and modify incidents, configurations, and other system components.

The primary purpose of Cortex XSIAM's machine learning-led design is to automate the handling of the bulk of incidents. By leveraging machine learning, it can automatically classify, group, and respond to incidents, reducing the need for manual intervention and increasing efficiency in incident management.

When integrating Cortex XSIAM or Cortex XDR with other Palo Alto Networks products, a XDR/XSIAM Broker VM is required. This Broker VM facilitates secure communication between the Cortex platform and other products, enabling proper integration and data exchange.

Cortex Data Lake (often referred to as Strata Logging Service in some contexts) is Palo Alto Networks’ cloud-based storage solution that centralizes security data for products like Cortex XDR, Prisma Access, and NGFWs. The question involves a customer who has activated a TMS (Tenant Management Service) tenant but has not purchased a Cortex Data Lake instance. TMS is part of the Palo Alto Networks ecosystem for managing tenants and services, typically associated with Cortex or Prisma deployments. Let’s break this down to determine the size of the free Cortex Data Lake instance provided in this scenario.

Understanding TMS and Cortex Data Lake:

TMS Tenant: The Tenant Management Service is a framework used to manage multiple tenants or instances within Palo Alto Networks’ cloud services (e.g., Cortex XDR, Prisma Access). Activating a TMS tenant implies the customer has initialized a management structure but hasn’t committed to a full Cortex Data Lake purchase.

Free Cortex Data Lake Instance: Palo Alto Networks provides a limited, free tier of Cortex Data Lake storage to customers who activate certain services or products, allowing them to evaluate functionality or store minimal data before committing to a paid license.

Free Storage Allocation:

When a customer activates a TMS tenant without purchasing a Cortex Data Lake instance, Palo Alto Networks allocates a default free storage capacity to enable basic functionality. According to official documentation and standard practices:

The free Cortex Data Lake instance provides 100 GB of storage.

This amount is intended for initial use cases, such as storing logs from a small number of endpoints (e.g., Cortex Xテゴ XDR Prevent agents), firewall logs, or trial data during evaluation periods.

Option Analysis:

A. 10 GB:

Analysis: 10 GB is too small to be a meaningful free tier for a product like Cortex Data Lake, which is designed to handle security telemetry from endpoints, networks, or cloud services. Even basic log storage for a few devices over a short period would exceed this quickly.

Conclusion: Incorrect.

B. 1 TB:

Analysis: 1 TB (1,000 GB) is a substantial amount of storage, typically associated with paid Cortex Data Lake subscriptions rather than a free tier. Offering this much for free would undermine the paid licensing model.

Conclusion: Incorrect.

C. 10 TB:

Analysis: 10 TB is even larger and aligns with enterprise-scale paid deployments, not a free instance. This size is far beyond what’s provided without a purchase.

Conclusion: Incorrect.

D. 100 GB:

Analysis: 100 GB is the documented size of the free Cortex Data Lake instance provided to customers who activate a tenant (e.g., via TMS) without purchasing additional storage. It’s sufficient for small-scale testing, such as storing logs from a handful of Cortex XDR agents or firewall data for a limited retention period (e.g., 30 days).

Conclusion: Correct.

Supporting Context:

Cortex XDR Example: For Cortex XDR Prevent customers, activating a tenant includes 100 GB of free Cortex Data Lake storage for 30 days of alert data (not full telemetry, which requires XDR Pro). This aligns with the TMS scenario, where basic tenant activation triggers the same free tier.

Prisma Access: Similarly, Prisma Access customers activating a tenant without a purchased Data Lake instance receive 100 GB for initial log storage.

Documentation: While exact wording may vary, Palo Alto Networks consistently references 100 GB as the free tier across product activation guides.

https://docs.paloaltonetworks.com/cortex/cortex-xdr/cortex-xdr-pro-admin/cortex-xdr-overview/cortex-xdr-concepts

The Cortex XSOAR Starter Edition has a more limited capacity compared to Cortex XSOAR (SOAR + TIM). It includes up to 5 active threat intelligence feeds and a maximum of 100 indicators per fetch. In contrast, the SOAR + TIM version typically provides more extensive threat intelligence capabilities.

Before deploying Cortex XSOAR, it’s important to consider whether communication with internal or external applications is required. This ensures that integrations and data flows between Cortex XSOAR and other tools or systems in the environment can be properly configured, enabling seamless automation and orchestration of security operations.

In the malware protection flow of the endpoint agent in Cortex XSIAM, hash comparisons are performed after local static analysis. This ensures that files are first analyzed locally to determine whether they are suspicious or potentially harmful, and then their hash is compared against known threat intelligence to check for any known malicious files.

If a prospective customer is unable to run a product evaluation, Tech Rehearsal can be used to showcase Cortex XDR. A Tech Rehearsal provides a guided demonstration of the product's capabilities and features, allowing the customer to gain a deeper understanding of how it works in their environment without a formal evaluation.

To automate the response to certain alerts in Cortex XSIAM, playbook triggers should be configured. Playbooks allow automated workflows to be executed based on specific conditions or alerts, enabling faster and more consistent responses to security events.

Confirm the integration credentials or API keys are valid, as incorrect or expired credentials are a common cause of connection issues.

Check the integration logs and enable a higher logging level if needed, to view more detailed error information. This can help identify the root cause of the failure and guide further troubleshooting.

The function of reputation scoring in the Threat Intelligence Module of Cortex XSIAM is to resolve conflicting scores from different vendors for the same indicator. This helps standardize threat intelligence, allowing the platform to provide a more accurate and reliable assessment of the risk associated with a given indicator, even when different sources may provide conflicting information.

The Data Ingestion Dashboard in Cortex XSIAM is used to onboard data sources. It provides a centralized view for configuring and monitoring the ingestion of various data sources into the platform, making it easier to integrate and manage security data from different systems.

Cortex Xpanse ingests public IP addresses from XDR endpoints. This allows the platform to monitor and track internet-facing assets, providing visibility into exposed assets and potential attack surfaces across the network.

The primary mechanism for the attribution of attack surface data in Cortex Xpanse is scanning from public internet data sources. Cortex Xpanse continuously scans the internet to identify assets that are potentially exposed or vulnerable, providing a comprehensive view of an organization's attack surface based on public-facing data.