You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rancher/security-scan already implements an e2e which currently creates a k8s cluster to confirm the execution of a scan (not its outcome). We want to improve this test, so that for each distribution the smoke test will test whether a given cis profile delivers the expected results.
For example, rke-cis-1.8-permissive profile will be tested as below:
RKE v1.26 would be created with microVM
MicroVM is configured with all environment requirements
Run security-scan with rke-cis-1.8-permissive
Scan should have 0 check fails (permissive and hardened)
Note: We should the define the expected results per distro's setup.
The text was updated successfully, but these errors were encountered:
Linked issue: #227
rancher/security-scan already implements an e2e which currently creates a k8s cluster to confirm the execution of a scan (not its outcome). We want to improve this test, so that for each distribution the smoke test will test whether a given cis profile delivers the expected results.
For example, rke-cis-1.8-permissive profile will be tested as below:
Note: We should the define the expected results per distro's setup.
The text was updated successfully, but these errors were encountered: