In AsyncOS 7.0 for web the choice of Authentication Surrogate is?

Question

Options

• ADefined separately for each Identity
• BA global setting
• CDefined separately for each Access Policy
• DDefined separately for each malware engine

• A
  88% (37)
• B
  2% (1)
• C
  7% (3)
• D
  2% (1)

Explanation

In AsyncOS 7.0 for Web, the Authentication Surrogate (which determines how the appliance tracks authenticated users - typically via IP address or a cookie) is configured individually within each Identity policy. This makes sense architecturally because different user populations (e.g., office workers vs. guest Wi-Fi users) may need different tracking mechanisms, so granular per-Identity control is required.

Why the distractors are wrong:

• B (Global setting): A single global surrogate would be too inflexible - it couldn't accommodate mixed environments where some users need cookie-based tracking and others need IP-based.
• C (Per Access Policy): Access Policies govern what authenticated users can do (URLs, bandwidth, etc.), not how the appliance identifies them after login - that belongs to the Identity layer.
• D (Per malware engine): Malware scanning engines are completely unrelated to authentication surrogates; this is a nonsense distractor.

Memory tip: Think of it as a layered model - Identity answers "Who are you?" and the surrogate is the mechanism that remembers who you are between requests. Since Identity is where you define users, it's naturally where you configure how to track them.

No community discussion yet for this question.