ROX-35762: Add CISA KEV UI display and policy criteria - #22103
Conversation
|
Skipping CI for Draft Pull Request. |
🚀 Build Images ReadyImages are ready for commit 491e43a. To use with deploy scripts: export MAIN_IMAGE_TAG=5.0.x-23-g491e43af31 |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #22103 +/- ##
==========================================
- Coverage 51.31% 51.27% -0.05%
==========================================
Files 2858 2858
Lines 179015 179047 +32
==========================================
- Hits 91865 91801 -64
- Misses 79082 79156 +74
- Partials 8068 8090 +22
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
c483358 to
c40876c
Compare
63cbf94 to
4844ef6
Compare
Add exploit { knownRansomwareCampaignUse } to all WorkloadCves GraphQL
fragments so the existing KnownExploitLabel and
KnownRansomwareCampaignLabel display components receive data.
Partially generated by AI.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Register CisaKev field name, query builder, and field metadata following the Fixable pattern. Enables policies that fire on CVEs in the CISA KEV catalog. Partially generated by AI.
Add radioGroup descriptor for CISA KEV in the policy wizard under Image Scanning. Users can create policies that fire when a CVE is (or is not) in the CISA KEV catalog. Gated behind ROX_CISA_KEV. Partially generated by AI.
4844ef6 to
491e43a
Compare
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Central YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (10)
Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review. 📝 WalkthroughSummary by CodeRabbit
WalkthroughChangesCISA KEV policy
CVE exploit metadata
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to This change adds CISA KEV vulnerability display and feature-gated policy criteria without any supplied evidence of a current correctness or production issue; no actionable merge-blocking risk remains beyond normal checks and review. Suggested reviewers: Sequence Diagram(s)sequenceDiagram
participant PolicyWizard
participant BooleanPolicy
participant ForCisaKev
participant Search
PolicyWizard->>BooleanPolicy: Submit CISA KEV criterion
BooleanPolicy->>ForCisaKev: Build vulnerability query
ForCisaKev->>Search: Map value to search.CisaKev
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@ajheflin: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Description
Wire CISA KEV data through the UI and add policy criteria support. PR 4/4 in a stack.
exploit { knownRansomwareCampaignUse }into all WorkloadCves GraphQL fragments so the existingKnownExploitLabelandKnownRansomwareCampaignLabelcomponents (merged in ROX-31903: Add ROX_CISA_KEV in WorkloadCves #17901) receive dataCISA KEV) following the Fixable pattern: field name, query builder, field metadata, violation message printerradioGrouptype) under Image Scanning, gated behindROX_CISA_KEVStack: [Proto changes] → [Converter wiring] → [Reporting] → 4/4 — UI + Policy
Depends on: #21752
User-facing documentation
Testing and quality
Automated testing
How I validated my change
go test ./pkg/booleanpolicy/... -count=1