Sweet Security Launches Virtual Patching for Cloud Workloads
The new feature lets teams block exploits instantly while engineering teams develop permanent fixes for vulnerable applications.
Key points
- Sweet Security released Virtual Patching to protect cloud and AI apps immediately upon vulnerability identification.
- The tool blocks malicious requests during the remediation window without affecting normal application traffic.
- Sweet Attack, an AI agent, suggests policies that security teams can enforce with a single click.
Sweet Security announced the availability of Virtual Patching, a new capability designed to shield running cloud and artificial intelligence applications from specific vulnerabilities. According to Help Net Security, this feature allows security teams to enforce protection instantly while engineering groups work on permanent fixes.
The company states that traditional vulnerability remediation often takes days or weeks. During this period, engineering teams must develop fixes, test changes, obtain necessary approvals, and deploy updated applications. Consequently, the running application remains exposed to potential threats throughout this extended window.
Context and Background
Sweet Security’s new feature addresses the gap between vulnerability identification and permanent remediation. From the company’s Vulnerabilities Catalog, a security team can select a specific issue and deploy a policy to every node running that workload. The sensor applies this policy to the active application, blocking requests that attempt exploitation while leaving legitimate traffic unaffected.
James Berthoty, CEO of Latio Tech, noted that artificial intelligence is accelerating both the discovery of vulnerabilities and their exploitation. He stated that exploits are now emerging days before official patches become available, meaning faster patching alone is insufficient. Virtual Patching provides a layer of defense against known and unknown exploits during this critical interim period.
Dror Kashti, CEO of Sweet Security, emphasized that waiting for a permanent fix is not a viable option when an application is known to be exploitable. He argued that this capability changes the economics of cloud security by significantly reducing the time and effort required between identifying a risk and mitigating it.
Affected Workloads and Integration
The protection mechanism follows the workload as it scales or restarts, ensuring continuous coverage. When a permanent fix is eventually deployed, removing the virtual patch is described as equally simple. This dynamic approach ensures that security measures adapt to the changing state of cloud environments without manual reconfiguration.
Virtual Patching operates alongside Sweet Attack, which Sweet Security describes as an autonomous AI red-team agent. This agent continuously validates exploitable attack paths using runtime context. When Sweet Attack identifies a vulnerability, it suggests a corresponding virtual patching policy that the security team can enforce immediately, streamlining the response process.
What should you do?
Security professionals should review their current vulnerability remediation timelines to identify gaps where applications remain exposed. Assessing how quickly threats can be mitigated without code changes is essential for reducing risk during engineering cycles.
What to do and how to stay safe: Sweet Security
- Identify critical cloud workloads that require immediate protection while permanent fixes are being developed and tested.
- Evaluate existing tools to determine if they can block malicious requests without disrupting normal application traffic or user experience.
- Monitor vendor announcements for features that allow rapid policy enforcement across multiple nodes without manual intervention per server.
- Review the integration capabilities of security agents to ensure they can automatically suggest and deploy protective policies based on runtime data.
Step-by-step guide: Cloud Misconfiguration Response: Containment, Recovery and Prevention Steps
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
How does Sweet Security's Virtual Patching work?
It allows security teams to deploy policies to nodes running a vulnerable workload, blocking exploitation attempts while normal traffic continues.
Why is this feature considered necessary now?
AI is accelerating exploit emergence, often appearing days before patches, leaving applications exposed during lengthy remediation cycles.
Can the protection be removed easily?
Yes, the company states that removing protection is simple once a permanent fix is deployed to the application.
