Box 'Abnormal user activity' rule (1139230c) can never raise an alert

Abierto Apto para principiantes
#15,664 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
70/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
yaml
Área
security

Línea de trabajo

Lee el bloque query: en Solutions/Box/Analytic Rules/BoxAbnormalUserActivity.yaml (id 1139230c) y compáralo con los cuatro defectos enumerados; el KQL sugerido en el issue es un reemplazo directo basado en SrcUserUpn con una línea base de 14 días. Vuelve a ejecutar el fragmento sintético de BoxEvents del informe para confirmar que se devuelve el usuario del burst y que los usuarios con actividad intensa constante no se devuelven. Hecho significa que la regla actualizada supera localmente la validación de KQL y las comprobaciones de esquema de detección del repositorio. Ten en cuenta que quien reportó ha ofrecido abrir un PR, así que consúltalo con esa persona antes de empezar.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Describe the bug

The analytic rule Solutions/Box/Analytic Rules/BoxAbnormalUserActivity.yaml (id 1139230c-cf10-45db-b616-fed0d1415c05) can't raise an alert on any data:

  • The baseline counts rows after the union (1 or 2 per user) instead of adding up events, then divides by 29 using whole numbers. The daily average is always 0, so where EventsPerDay > TotalEventsH is never true.
  • The "last hour" parts have no time filter, so they count all 14 days. Both use SourceName, which is the file or folder acted on, not the user.
  • join ... on k with k = 1 on every row keeps only one user from the left side.
  • The comparison points the wrong way. With the counting fixed, it would alert on users who are quieter than usual, not on spikes.

To Reproduce

Paste this in front of the rule query in Log Analytics. It's one user with one event an hour for two weeks, then 500 events in the last hour. The rule returns nothing.

let BoxEvents = union
    (range h from 2 to 335 step 1
     | project EventEndTime = ago(1h * h), SrcUserName = 'Alice', SrcUserUpn = '[email protected]', SourceName = 'Roadmap.docx'),
    (range i from 1 to 500 step 1
     | project EventEndTime = ago(1m * (i % 50)), SrcUserName = 'Alice', SrcUserUpn = '[email protected]', SourceName = strcat('export-', i, '.csv'));

Expected behavior

An alert when a user's activity in the last hour is far above their usual level.

Suggested fix

This version compares each user's events in the last hour with their average over the previous 14 days, counting only hours in which they were active. It alerts when the last hour has at least 50 events and is more than three standard deviations above that average. It identifies the account by login rather than display name.

let lookback = 14d;
let recent = 1h;
let min_events = 50;
let baseline = BoxEvents
| where EventEndTime between (ago(lookback) .. ago(recent))
| where isnotempty(SrcUserUpn)
| summarize Events = count() by SrcUserUpn, bin(EventEndTime, 1h)
| summarize BaseAvg = avg(Events), BaseStdev = stdev(Events) by SrcUserUpn;
BoxEvents
| where EventEndTime > ago(recent)
| where isnotempty(SrcUserUpn)
| summarize EventsLastHour = count(), SrcUserName = take_any(SrcUserName) by SrcUserUpn
| join kind=leftouter baseline on SrcUserUpn
| extend BaseAvg = coalesce(BaseAvg, 0.0), BaseStdev = coalesce(BaseStdev, 0.0)
| where EventsLastHour >= min_events and EventsLastHour > BaseAvg + 3 * BaseStdev
| extend AccountName = tostring(split(SrcUserUpn, '@')[0]), UPNSuffix = tostring(split(SrcUserUpn, '@')[1])
| project SrcUserUpn, SrcUserName, AccountName, UPNSuffix, EventsLastHour, AvgEventsActiveHour = round(BaseAvg, 2)

I don't have a Sentinel workspace with Box data, so I tested it on the Kusto emulator with the solution's BoxEvents parser, using synthetic events:

  • With the snippet above, it returns the user.
  • A user with a normal baseline who downloads 500 files in an hour gets an alert.
  • Three heavy users (40 to 200 events an hour, varying between half and one and a half times their usual rate), replayed at each hourly run over a week, got no alerts, both with a full 14 days of history and with less.
  • It gives the same results whether the data is in BoxEventsV2_CL, BoxEvents_CL, or both.
  • It passes the repo's KQL validation, detection schema and non-ASCII checks locally.

Expect some alerts for legitimate bulk activity: a first Box Drive sync, migrations, integration or service accounts, and new users with no history. The thresholds are a best guess without real Box data.

Happy to open a PR with this change if that would help.

Lenguaje dominante
HTML
Estrellas
6.3k
Forks
3.9k
Merge medio
2 d 10 h
PR fusionados (30 d)
190

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Azure/Azure-Sentinel

Todos los issues de Azure/Azure-Sentinel

Issues similares

Más issues de Security

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.