Question 520
A network security architect is assigned to resolve: A company plans User-ID policy using only IP-to-user mappings while many employees share a NAT gateway. Following this examination—Review mapping collectors, NAT boundary and application-side authenticated identity data—which change is appropriate?
Explanation
Correct Answer
Given a company plans User-ID policy using only IP-to-user mappings while many employees share a NAT gateway, the selected remedy is to choose supported user identification or application authentication methods at a point where principal identity is observable. The prior inspection is review mapping collectors, NAT boundary and application-side authenticated identity data. The design is not complete until the team confirms that two users behind one address receive their distinct expected permissions in a pilot.
Incorrect Answers
The option applies in “A contractor group requires time-bounded access, but the IAM architecture has no reliable revocation mechanism”. The prior inspection is review directory group lifecycle, authentication session expiry and policy enforcement dependencies. That evidence does not directly establish “Choose supported user identification or application authentication methods at a point where principal identity is observable” for the scenario at hand.
Applying this option would direct attention to an enterprise wants to use centralized SAML authentication for security platform admins without local password duplication. In the reported design—a company plans User-ID policy using only IP-to-user mappings while many employees share a NAT gateway—the needed action statement is choose supported user identification or application authentication methods at a point where principal identity is observable.
The distinct use case for this response is “an administrator wants security gateways to enforce MFA for a high-risk internal application and uses only broad network allow rules”. The prior inspection is inspect authentication policy options, supported IdP SAML flow and application access topology. The present case instead calls for “Choose supported user identification or application authentication methods at a point where principal identity is observable”.