Question 380
Original unofficial Palo Alto Networks NetSec-Architect scenario: A finance institution needs contractor access to one private API but its design enables broad access to an entire corporate CIDR. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: A finance institution needs contractor access to one private API but its design enables broad access to an entire corporate CIDR. Governing principle: Network-level connectivity can expose far more services than a contractor’s business requirement. The most defensible design response is: Design an application-specific private-access path with verified identity policy and narrow destination selection. Validation: An approved contractor reaches the API but cannot scan unrelated private hosts in the same network. Sustained assurance: Use negative destination tests before expanding remote contractor groups
Incorrect Answers
“Review latency and residency after expanding to new regions.” concerns the separate design topic: architect regional and global prisma access private application designs. It would not fix the described weakness: a finance institution needs contractor access to one private API but its design enables broad access to an entire corporate CIDR. Network-level connectivity can expose far more services than a contractor’s business requirement.
This alternative is linked to the architecture category: differentiate service connections, ztna connectors, colo-connect and ncc. The actual problem is that a finance institution needs contractor access to one private API but its design enables broad access to an entire corporate CIDR; the controlling distinction is: network-level connectivity can expose far more services than a contractor’s business requirement.
The proposed design “Require overlap analysis for external partner integration.” addresses this related architecture topic: differentiate service connections, ztna connectors, colo-connect and ncc. The actual security gap is that a finance institution needs contractor access to one private API but its design enables broad access to an entire corporate CIDR. Network-level connectivity can expose far more services than a contractor’s business requirement.