How useful is a Kubernetes scanner for Java4Shell exposure?
Could a kubectl plugin help identify Java workloads exposed to Java4Shell, including pods that might become exposed after rescheduling? What would make its findings useful for remediation?
Could a kubectl plugin help identify Java workloads exposed to Java4Shell, including pods that might become exposed after rescheduling? What would make its findings useful for remediation?