'Reactivity's patent-pending "content+envelope" security checking allows security decisions to be made based on both header and message content'

BELMONT, Calif., July 22, 2002 - Reactivity, Inc., a provider of products for distributed application security, today debuted the Reactivity Service Firewall(TM), a unique, drop-in solution that makes secure XML and Web services-based application integration fast and affordable. The Reactivity Service Firewall can be deployed at a fraction of the time and cost of custom-coded solutions. It is easy to use and maintain and scales effortlessly as the number of applications increase and environments become more complex. The Service Firewall supports both XML-based message integration and the latest Web Service standards and tools.

The first practical solution for securing and controlling XML applications and Web services usage, the Reactivity Service Firewall sits at the edge of the corporate network to secure message flow between distributed applications. The Run-Time Engine normalizes messages from multiple transport protocols and performs authentication, authorization, validation and routing to secure bi-directional message flow. The Management Console centralizes policy configuration, monitors messages and exceptions in real-time and enables comprehensive audit logging and reporting of all messages and transactions.

"With today's announcement Reactivity is filling a critical gap for products that secure and control distributed applications, providing a high degree of application-level security and increasing the speed and ease of application deployment," said Glenn Osaka, President and CEO of Reactivity. "As applications become more distributed, security must be enforced and managed outside of the application for maximum safety, ease of maintenance, high message throughput and cost efficiency."

The Reactivity Service Firewall reduces redundant code that would otherwise be hard-wired into each application in a distributed environment or built into a series of integration points. Without abstracting application-level security, every time a new application or partner is added, all other applications would need to be modified to incorporate the necessary security requirements before they can interact.

Full Article: WebServices.Org