Hugo P.Brito b49e49f543 fix(m365): require active PIM stale alert before flagging accounts ...

The PIM alert object exposes an is_active flag that goes False once the
alert condition stops firing, even though the previous number_of_affected_items
count can stick around in the API response. The check was ignoring that
flag, so a tenant whose alert was already resolved or dismissed could
still receive a FAIL based on stale counters.

Gate the FAIL branch on alert.is_active so only currently-firing alerts
produce findings; everything else (resolved alert, inactive with leftover
counts) is reported as PASS. A regression test covers the inactive-with-
counts case to lock the behavior in.

2026-05-11 11:48:46 +01:00

..

config

feat(sdk): integrate universal compliance into CLI pipeline (#10301)

2026-04-30 13:49:00 +02:00

contrib/wazuh

fix(wazuh): patch command injection vulnerability in prowler-wrapper.py (#8331)

2025-07-23 16:06:55 +02:00

lib

chore: route vulnerability references to canonical URLs (#10853)

2026-05-07 15:28:50 +01:00

providers

fix(m365): require active PIM stale alert before flagging accounts

2026-05-11 11:48:46 +01:00

__init__.py

feat(pip): Prepare for PyPI (#1531)

2022-12-13 09:07:55 +01:00