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

Esta página aún no está disponible en español. Estamos trabajando en su traducción.
Si tienes alguna pregunta o comentario sobre nuestro actual proyecto de traducción, no dudes en ponerte en contacto con nosotros.

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.