What you are evaluating
The platform documents several deployment and workload patterns, but coverage must be confirmed for the chosen environment. Image scanning, pipeline controls and runtime enforcement require different integrations; product assurances or authorization claims should not replace a scoped technical evaluation.
A useful evaluation context
A Kubernetes or workload-security team can evaluate predeployment checks and runtime controls within the same application lifecycle.
Documented capabilities
The vendor describes these capabilities in the linked sources. Availability depends on the product edition and supported environment.
- Repository and image scanning identify documented software and configuration issues before deployment.
- Agentless posture assesses supported cloud resources separately from runtime workload controls.
- Runtime capabilities describe process, file, network and memory visibility or enforcement on supported containers, hosts and related environments.
Where it fits in the work
- Select a lab image, pipeline and cluster or host that reflect the deployment pattern being evaluated.
- Introduce a harmless policy violation into the image or configuration, then verify how the pipeline reports or rejects it under the approved rule.
- Deploy an acceptable image and exercise one benign documented runtime event, distinguishing assessment findings from enforcement outcomes.
APPLY THE IDEA / ILLUSTRATIVE EXERCISE
Make the outcome observable.
Run a synthetic container through a lab pipeline, verify a deliberately failed configuration rule, then test a permitted container with a harmless runtime event.
Evidence to look for
The pipeline result identifies the failed rule, and the later runtime record identifies the deployed workload and configured action without requiring exploit execution.
Use synthetic data and an authorized test environment. Agree the scope and recovery steps before enabling enforcement.
Questions for your evaluation
- Which supported component enforces the pipeline rule and which supplies runtime evidence?
- What privileges and compatibility constraints apply in the selected cluster or disconnected environment?
- How are exceptions approved so a false detection does not silently block an essential application release?