Which User Credential Detection method should be applied within a URL Filtering Security profile to check for the submission of a valid corporate username and the associated password?

Question

Options

• AGroup Mapping
• BDomain Credential
• CValid Username Detected Log Severity
• DIP User

• A
  6% (1)
• B
  88% (15)
• D
  6% (1)

Explanation

Domain Credential detection is the correct method because it specifically inspects HTTP/HTTPS traffic for submitted credentials and checks whether both a valid corporate username and its matching password are being submitted - catching actual credential phishing, not just username exposure.

• Group Mapping (A) is used to map IP addresses to usernames via directory services (like Active Directory); it identifies who is using an IP, not whether credentials are being submitted to a site.
• Valid Username Detected Log Severity (C) is a logging setting that controls the severity level when only a username (without a matching password) is detected - it's a response action, not a detection method.
• IP User (D) is a user identification mechanism that associates traffic with users by IP address, unrelated to detecting credential submissions in URL filtering.

Memory tip: Think "Domain Credential" = full credential pair (username + password). The word "credential" itself implies both halves of the login, which is exactly what this method checks for - making it the only option that covers the complete corporate credential submission scenario.

No community discussion yet for this question.