Add Kubernetes privileged workload matcher#112
Open
jadenfix wants to merge 3 commits into
Open
Conversation
|
@jadenfix is attempting to deploy a commit to the Vercel Labs Team on Vercel. A member of the Team first needs to authorize it. |
jadenfix
force-pushed
the
jaden/k8s-privileged-workload
branch
from
July 19, 2026 21:09
8b9856f to
355fd8a
Compare
jadenfix
marked this pull request as ready for review
July 19, 2026 21:10
Author
|
Ready for review at |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Adds and registers a reusable
k8s-privileged-workloadmatcher for privileged execution, host access, root UID, unmasked proc mounts, and dangerous Linux capabilities.The matcher now:
speccapabilities.addcapabilities.drop, annotations, and YAML-looking block-scalar dataWhy
DeepSec already reviews Kubernetes secret handling but had no built-in workload privilege coverage. Document and
specscoping keeps this high-value rule in theprecisenoise tier instead of flagging configuration text that only resembles a workload setting.Verification
pnpm --filter @deepsec/scanner buildpassesgit diff --checkpassesNotes for reviewer
Generated dependencies and workflow paths remain excluded; first-party
charts/**/templatesmanifests are intentionally scanned. The branch is based on the currentmain.