Attack in progressA leaked CI key of ‹ci-deploy-bot› is being used to break in: 6 accounts and machines created.Open the case
GuardDuty parity slice V-019a
Checks every GuardDuty finding against Warden's own records and names the ones its own sensors missed.
Checks
| Checks | Needs |
|---|---|
| Checks every GuardDuty finding against Warden's own records and names the ones its own sensors missed. | guardduty finding |
Coverage
Could not read anything this run
| eu-west-1 | |
|---|---|
‹sandbox› 345678901234 | Not read |
Run history
No run has recorded this rule yet.
Findings
No open findings.
What it fed
No case has used a finding of this rule in the last 30 days.
Techniques
None mapped.
How to fix
warden show for the cited GuardDuty finding, then the sensor rows the family names (the instance's flow-log rows, or the window's trail events for the counterpart check) → a sensor that should have seen it is a product gap to file; telemetry Warden does not read is a declared gap; nothing in the estate changes