Question 50
Original unofficial Palo Alto Networks NetSec-Architect scenario: A custom internal service is being identified as generic SSL and is over-permitted because engineers never characterize its normal transactions. Which test result best demonstrates that the design meets its requirement?
Explanation
Correct Answer
Original fictional security architecture situation: A custom internal service is being identified as generic SSL and is over-permitted because engineers never characterize its normal transactions. Governing principle: Encrypted transport visibility without application classification can lead to coarse network exceptions. The most defensible design response is: Characterize the application and adopt suitable custom application identification with tightly scoped allowed services. Validation: Traffic logs identify the intended custom service, and the generic-SSL allowance is no longer necessary. Sustained assurance: Maintain identification signatures and dependency inventories when the custom service changes
Incorrect Answers
The suggested “A controlled workflow works without a blanket allow rule for unrelated code repositories.” tests a different architectural concern: differentiate authorization to specific applications. Here, a custom internal service is being identified as generic SSL and is over-permitted because engineers never characterize its normal transactions. Encrypted transport visibility without application classification can lead to coarse network exceptions.
“Approved test flows are decrypted and inspected, while documented exempt workflows follow the exception policy.” concerns the separate design topic: design continuous inspection of allowed traffic for malware and exploits. It would not fix the described weakness: a custom internal service is being identified as generic SSL and is over-permitted because engineers never characterize its normal transactions. Encrypted transport visibility without application classification can lead to coarse network exceptions.
This alternative is linked to the architecture category: architect identity, device posture and least-privilege controls using user-id, hip and device-id. The actual problem is that a custom internal service is being identified as generic SSL and is over-permitted because engineers never characterize its normal transactions; the controlling distinction is: encrypted transport visibility without application classification can lead to coarse network exceptions.