OpenRASP

Unlike perimeter control solutions like WAF, OpenRASP directly integrates its protection engine into the application server by instrumentation. It can monitor various events including database queries, file operations, and network requests, etc.

When an attack happens, WAF matches the malicious request with its signatures and blocks it. OpenRASP takes a different approach by hooking sensitive functions and examines/blocks the inputs fed into them. As a result, this examination is context-aware and in-place. It brings in the following benefits:

Only successful attacks can trigger alarms, resulting in lower false-positive and higher detection rate;
A detailed stack trace is logged, which makes the forensic analysis easier;
Insusceptible to malformed protocol.

FAQ

1. List of supported web application servers

We’ve fully tested OpenRASP on the following application servers for Linux platforms:

Java
- Tomcat 6-9
- JBoss 4.X
- Jetty 7-9
- Resin 3-4
- SpringBoot 1-2
- IBM WebSphere 8.5, 9.0
- WebLogic 10.3.6, 12.2.1
PHP
- 5.3-5.6, 7.0-7.3

The support of other web application servers will also be soon included in the coming releases.

2. Performance impact on application servers

We ran multiple intense and long-lasting stress tests prior to release. Even in the worst-case scenario (where the hook point got continuously triggered), the server’s performance was only reduced by 1~4%

3. Integration with existing SIEM or SOC

OpenRASP logs alarms in JSON format, which can be easily picked up by LogStash, rsyslog or Flume.

4. How to develop a new plugin?

A plugin receives a callback when an event occurs. It then determines if the current behavior is malicious or not and blocks the associated request if necessary.

Detailed plugin development instructions can be found here

Changelog v1.3.7

Java Agent

Multiple bug fixes
Add JNDI hooks and javascript plugins
Add DNS hooks and javascript plugins

PHP Agent

Multiple bug fixes

Panel

Multiple bug fixes

Install && Use

Tags: openrasp