iboss allowed malware activity detected

This rule is part of a beta feature. To learn more, contact Support.
iboss

Classification:

attack

Tactic:

TA0002-execution

Technique:

T1204-user-execution

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

Goal

Detects instances where malware was detected but allowed through the iboss security gateway, potentially exposing endpoints to infection.

Strategy

Monitor security events with iboss to identify risky traffic and exposed users or devices where malicious content is allowed.

Triage and Response

  1. Identify the user {{@usr.name}} and the device {{@computerName}} involved in the malware-allowed event.
  2. Review the client IP address {{@network.client.ip}} for any signs of suspicious or malicious activity.
  3. Isolate the endpoint if necessary, perform a malware scan, and apply remediation steps.
  4. Investigate potential policy gaps or misconfigurations that allowed the threat.