Question 260
Original unofficial Palo Alto Networks NetSec-Architect scenario: An industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: An industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter. Governing principle: Private directories may require a trusted in-network synchronization component rather than inbound public directory exposure. The most defensible design response is: Choose a supported on-premises Cloud Identity Engine directory synchronization agent model and limit outbound connectivity appropriately. Validation: Group membership updates from the isolated directory reach the cloud mapping through the approved agent path. Sustained assurance: Monitor agent freshness, certificates and least-privileged directory service permissions
Incorrect Answers
“Alert on stalled synchronization rather than inferring health from successful sign-ins.” concerns the separate design topic: recommend cloud identity engine on-prem agent and cloud-directory sync choices. It would not fix the described weakness: an industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter. Private directories may require a trusted in-network synchronization component rather than inbound public directory exposure.
The suggested “Recertify external identity group scope at contract expiration.” tests a different architectural concern: evaluate cloud identity engine across ngfw, prisma access and prisma sd-wan. Here, an industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter. Private directories may require a trusted in-network synchronization component rather than inbound public directory exposure.
The proposed design “Rotate service credentials and test failover before expiration windows.” addresses this related architecture topic: evaluate cloud identity engine across ngfw, prisma access and prisma sd-wan. The actual security gap is that an industrial enterprise’s user directory is isolated from the internet, but its design assumes a cloud connector can query LDAP directly through the inbound perimeter. Private directories may require a trusted in-network synchronization component rather than inbound public directory exposure.