Restrict AD entity risk panel rendering to host/user flyouts only

[Copilot]

Risk panels were being shown for all AD entity flyouts, including non-risk-eligible types. This updates attack discovery flyout rendering so risk UI appears only for hosts and users, and remains hidden for other AD entity types.

• UI logic: scope risk panel visibility by AD entity type

  • Updated EntityFlyout in src/views/attack-discovery/App.tsx to render the risk block only when state.type is host or user.
  • Non-host/user flyouts no longer render the risk panel or unscored fallback panel.

• Risk lookup correctness

  • Tightened risk selection to match on both type and name (instead of name-only), preventing cross-type risk mismatches when identifiers overlap.

• Behavioral impact

  • Hosts/users: unchanged risk panel behavior (scored or unscored state).
  • Other entity types (e.g., process/file): no risk panel rendered.

const showRiskPanel = state.type === "host" || state.type === "user";
const risk = detail?.entityRisk?.find(
  (er) => er.type === state.type && er.name === state.value
);

{showRiskPanel && (
  risk && risk.level.toLowerCase() !== "unknown"
    ? <RiskPanel ... />
    : <UnscoredRiskPanel ... />
)}

Original prompt

Currently, the app displays risk panels for all Active Directory (AD) elements, but the desired behavior is to show risk panels only for hosts and users. Please update the relevant UI logic/components so that risk panels are rendered exclusively for these two AD element types (hosts and users), and hidden for all others. Ensure test coverage is updated if needed and describe the change in the PR body.

References:

• Slack context indicates this was surfaced by multiple users and is considered a needed UI correctness improvement.

Acceptance criteria:

• Only hosts and users in AD have risk panels rendered
• No risk panel is shown for other AD element types
• Tests updated (if applicable)

This pull request was created from Copilot chat.

[opauloh]

LGTM