A financial institution suspects an insider threat due to unauthorized access attempts on restricted databases. However, SIEM alerts lack sufficient information to differentiate between legitimate…

Question

Options

• AUser context from HR systems
• BLocation and physical context from CPS sensors
• CThreat context from external threat intelligence feeds
• DVulnerability context

• A
  74% (26)
• B
  14% (5)
• C
  3% (1)
• D
  9% (3)

Explanation

User context from HR systems is the most relevant contextual source for insider-threat differentiation because it helps determine whether access aligns with the user’s role, employment status, and business need. HR context can include department, job title, manager, location assignment, employment status (active/terminated), and sometimes risk signals like recent role changes or offboarding timelines. For restricted database access, the key questions are “should this person have access?” and “is this behavior normal for their role?” Threat intelligence feeds primarily help with external adversaries (malicious IPs, domains, known actor infrastructure) and are less useful for insiders who operate from legitimate networks and accounts. Vulnerability context is useful for exposure management and exploit prioritization, but it doesn’t explain whether a particular employee’s access attempt is legitimate. Physical/CPS sensor context can be valuable in some environments (badge access vs. login), but the most broadly applicable and directly relevant enrichment for insider cases is HR-based identity context. In SOC operations, combining HR context with identity logs and data access telemetry improves detection logic (for example, flagging restricted access attempts by users outside the relevant business unit or after termination) and reduces false positives from legitimate administrative activity.

No community discussion yet for this question.