Here are all the actual test exam dumps for IT exams. Most people prepare for the actual exams with our test dumps to pass their exams. So it's critical to choose and actual test pdf to succeed.

Exam NetSec-Analyst Topic 1 Question 102 Discussion

Actual exam question for Palo Alto Networks's NetSec-Analyst exam
Question #: 102
Topic #: 1
An organization relies heavily on Palo Alto Networks firewalls for perimeter security. They want to implement a custom Threat Signature to detect a highly evasive malware strain that attempts to communicate over HTTP/S using a specific pattern in its TLS Client Hello extension (e.g., a unique, non-standard extension value or an unusual ordering of standard extensions). The challenge is that the malware changes its C2 domain frequently, and traditional URL/DNS blacklisting is ineffective. Which type of custom signature and what specific 'Location' for the pattern match would be most appropriate for this detection, assuming the pattern is 'malware_tls_signature_bytes' and is located within the 'client_hello_extensions' field?

Suggested Answer: C Vote an answer

This question targets advanced custom signature creation, specifically focusing on TLS handshake details. The key is detecting a pattern within the 'TLS Client Hello extension'. Signature Type: Custom Threat - This is the general category for detecting specific malicious patterns not covered by pre-defined signatures. While 'Vulnerability' or 'Spyware' could potentially be used for broader malware, 'Custom Threat' is designed for specific, targeted threat detection. Location: 'ssl-client-hello-extensions' - This is the crucial part. Palo Alto Networks custom signatures offer specific 'Locations' to target different parts of network protocols. To inspect details within the TLS Client Hello extensions , the 'ssl-client-hello-extensions' location is the precise target. 'ssl-client-hello' would match the entire Client Hello, but 'ssl-client-hello-extensions' provides a more granular context for patterns specifically within the extensions field, which is what the problem describes. Let's review other options: A. Signature Type: Vulnerability, Location: 'tcp-payload' : 'tcp-payload' is too broad; it inspects the entire TCP payload, which would be inefficient and prone to false positives if the pattern is specific to TLS handshake elements. 'Vulnerability' is generally for exploits. B. Signature Type: Spyware, Location: 'ssl-client-hello' : While 'ssl-client-hello' is closer, it's less specific than 'ssl-client-hello-extensions' if the goal is to target patterns within the extensions. 'Spyware' is a valid threat category, but the location precision is important here. D. Signature Type: DoS, Location: 'tls-handshakes : DoS signatures are for denial-of-service attacks. 'tls-handshake' is a valid location but 'ssl-client-hello-extensions' is even more granular and accurate for the specific problem. E. Signature Type: Protocol Anomaly, Location: 'http-request-headers' : Protocol Anomaly signatures detect deviations from RFCs. 'http-request-headers' is for HTTP headers, not TLS handshake details.

by Ida at Oct 29, 2025, 09:33 PM

Comments

Chosen Answer:
This is a voting comment (?) , you can switch to a simple comment.
Switch to a voting comment New
Nick name: Submit Cancel
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.