Dockhand vulnerability scans: warn about critical findings, with a setting to turn it off
Reads what Dockhand's scans have already stored (never starts one) every 15 minutes and raises a warning per Docker host with critical findings. Unknown counts and stale readings are held, not treated as clean. Settings -> Notifications has a switch (on by default); the Docker page shows counts, scan coverage and the critical findings; /metrics and docs updated. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
65214f6f0f
commit
5a2b320175
25 files changed
+8527
-12
No files matched your search
@@ -0,0 +1,15 @@
|
||||
CREATE TABLE `dockhand_vulnerabilities` (
|
||||
`integration_id` integer NOT NULL,
|
||||
`environment_id` integer NOT NULL,
|
||||
`environment_name` text NOT NULL,
|
||||
`critical` integer,
|
||||
`high` integer,
|
||||
`medium` integer,
|
||||
`low` integer,
|
||||
`images_scanned` integer,
|
||||
`total_images` integer,
|
||||
`findings` text DEFAULT '[]' NOT NULL,
|
||||
`updated_at` text NOT NULL,
|
||||
PRIMARY KEY(`integration_id`, `environment_id`),
|
||||
FOREIGN KEY (`integration_id`) REFERENCES `integrations`(`id`) ON UPDATE no action ON DELETE cascade
|
||||
);
|
||||
Reference in new issue
Block a user