k8s-ci-robot
commented
6 months ago This issue is currently awaiting triage.
If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.
Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
mrueg
Following UK TSR requirement provided by the UK Department for Digital, Culture, Media and Sport in conjunction with the UK NCSC
V.D.4: Address Space Layout Randomization The vendor only ships executable code that has been compiled using modern ASLR techniques. Why it matters: Widely used to make it more difficult for an attacker to exploit any security issues. Evaluation (Security Declaration):The Security Declaration states whether the vendor’s products use ASLR throughout their product. Evaluation (Customer or third-party lab test): Verify that address space layer randomization mitigations are enabled by (automatically) inspecting the product for this mitigation.