Question 1020
Original unofficial Palo Alto Networks NetSec-Architect scenario: A private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: A private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. Governing principle: TLS decryption adds cryptographic and content-inspection work absent from cleartext benchmarks. The most defensible design response is: Recalculate capacity using measured decrypted session mixes, cryptographic algorithms and session churn. Validation: A representative encrypted load test remains within throughput and CPU headroom targets. Sustained assurance: Track decrypted traffic share and session rates as applications evolve
Incorrect Answers
“Review exceptional no-decrypt rules and owners on a fixed schedule.” concerns the separate design topic: evaluate ssl decryption inspection and performance tradeoffs. It would not fix the described weakness: a private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. TLS decryption adds cryptographic and content-inspection work absent from cleartext benchmarks.
The suggested “Forecast steady-state and degraded-state SSL inspection utilization separately.” tests a different architectural concern: evaluate ssl inspection sizing and deployment requirements. Here, a private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. TLS decryption adds cryptographic and content-inspection work absent from cleartext benchmarks.
The proposed design “Maintain representative encrypted traffic test profiles for refresh planning.” addresses this related architecture topic: evaluate ssl inspection sizing and deployment requirements. The actual security gap is that a private-cloud firewall is sized using cleartext traffic and its CPU saturates after TLS forward-proxy decryption is enabled. TLS decryption adds cryptographic and content-inspection work absent from cleartext benchmarks.