No. Sweet covers the 30 days of protection in full. There's no purchase commitment.
No. Virtual Patching is a protection policy applied through the sensor. Your application code stays as it is.
No. Virtual Patching protects affected workloads while your team tests and deploys the permanent fix, on its own timeline.
- Linux kernel version >= 5.10 - No support for serverless or managed container environments without host access, such as AWS Fargate, Azure Container Instances, and Google Cloud Run.
You will need to sign the Master Subscription Agreement .
The evaluation ends, unless you decide to continue with Sweet. If you do not wish to continue, the platform will not be responsive.
No. Your CS team can help you apply protection.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
