Question 60
Original unofficial Palo Alto Networks NetSec-Architect scenario: A retail edge firewall allows sanctioned web apps but does not attach threat-prevention profiles to those allow rules. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: A retail edge firewall allows sanctioned web apps but does not attach threat-prevention profiles to those allow rules. Governing principle: An allow decision does not imply that subsequent content inspection is enabled. The most defensible design response is: Attach the approved vulnerability, anti-malware, and relevant content security profiles to each eligible allow rule. Validation: A safe test signature is blocked and logged while ordinary sanctioned traffic remains available. Sustained assurance: Continuously audit allow policies for missing security-profile coverage
Incorrect Answers
“Review decryption exceptions and certificate trust before each policy rollout.” concerns the separate design topic: design continuous inspection of allowed traffic for malware and exploits. It would not fix the described weakness: a retail edge firewall allows sanctioned web apps but does not attach threat-prevention profiles to those allow rules. An allow decision does not imply that subsequent content inspection is enabled.
The suggested “Tie application onboarding to identity, decryption, and data policy reviews.” tests a different architectural concern: design continuous zero trust monitoring and analytics. Here, a retail edge firewall allows sanctioned web apps but does not attach threat-prevention profiles to those allow rules. An allow decision does not imply that subsequent content inspection is enabled.
The proposed design “Expire stale posture observations and test the noncompliant-device denial path.” addresses this related architecture topic: architect identity, device posture and least-privilege controls using user-id, hip and device-id. The actual security gap is that a retail edge firewall allows sanctioned web apps but does not attach threat-prevention profiles to those allow rules. An allow decision does not imply that subsequent content inspection is enabled.