open-appsec (openappsec.io) builds on machine learning to provide preemptive web app & API threat protection against OWASP-Top-10 and zero-day attacks. It can be deployed as an add-on to Kubernetes Ingress, NGINX, Envoy (soon), and API Gateways.
The open-appsec engine learns how users normally interact with your web application. It then uses this information to automatically detect requests that fall outside of normal operations, and conducts further analysis to decide whether the request is malicious or not.
Upon every HTTP request, all parts are decoded, JSON and XML sections are extracted, and any IP-level access control is applied.
Every request to the application goes through two phases:
-
Multiple variables are fed to the machine-learning engine. These variables, which are either directly extracted from the HTTP request or decoded from different parts of the payload, include attack indicators, IP addresses, user agents, fingerprints, and many other considerations. The supervised model of the machine learning engine uses these variables to compare the request with many common attack patterns found across the globe.
-
If the request is identified as a valid and legitimate request the request is allowed, and forwarded to your application. If, however, the request is considered suspicious or high risk, it then gets evaluated by the unsupervised model, which was trained in your specific environment. This model uses information such as the URL and the users involved to create a final confidence score that determines whether the request should be allowed or blocked.
open-appsec uses two machine learning models:
-
A supervised model that was trained offline based on millions of requests, both malicious and benign.
- A basic model is provided as part of this repository. It is recommended for use in Monitor-Only and Test environments.
- An advanced model which is more accurate and recommended for Production use can be downloaded from the open-appsec portal->User Menu->Download advanced ML model. This model updates from time to time and you will get an email when these updates happen.
-
An unsupervised model that is being built in real time in the protected environment. This model uses traffic patterns specific to the environment.
open-appsec can be managed using multiple methods:
open-appsec Web UI:
You can experiment with open-appsec using Playgrounds
For Kubernetes (NGINX Ingress) using the installer:
$ wget https://downloads.openappsec.io/open-appsec-k8s-install && chmod +x open-appsec-k8s-install
$ ./open-appsec-k8s-installFor Kubernetes (NGINX or Kong) using Helm: follow documentation – use this method if you’ve built your own containers.
For Linux (NGINX or Kong) using the installer (list of supported/pre-compiled NGINX attachments is available here):
$ wget https://downloads.openappsec.io/open-appsec-install && chmod +x open-appsec-install
$ ./open-appsec-install --autoFor Linux, if you’ve built your own package use the following commands:
$ install-cp-nano-agent.sh --install --hybrid_mode
$ install-cp-nano-service-http-transaction-handler.sh --install
$ install-cp-nano-attachment-registration-manager.sh --installYou can add the --token <token> and --email <email address> options to the first command, to get a token follow documentation.
For Docker: follow documentation
For more information read the documentation or follow the video tutorials.
open-appsec GitHub includes four main repositories:
- openappsec/openappsec the main code and logic of open-appsec. Developed in C++.
- openappsec/attachment connects between processes that provide HTTP data (e.g NGINX) and the open-appsec Agent security logic. Developed in C.
- openappsec/smartsync in charge of correlating learning data from multiple agent instances and delivering a unified learning model for each asset. Developed in Golang.
- openappsec/smartsync-shared-files interface to physical storage used by smartsync service for storing learning data. Developed in Golang.
Before compiling the services, you'll need to ensure the latest development versions of the following libraries and tools:
- Boost
- OpenSSL
- PCRE2
- libxml2
- GTest
- GMock
- cURL
- Redis
- Hiredis
- MaxmindDB
- yq
An example of installing the packages on Alpine:
$ apk update
$ apk add boost-dev openssl-dev pcre2-dev libxml2-dev gtest-dev curl-dev hiredis-dev redis libmaxminddb-dev yq- Clone this repository
- Run CMake command
- Run make install command
$ git clone https://github.com/openappsec/openappsec.git
$ cd openappsec/
$ cmake -DCMAKE_INSTALL_PREFIX=build_out .
$ make install
$ make packageOnce the agent code has been compiled and packaged, an Alpine image running it can be created. This requires permissions to execute the docker command.
$ make dockerThis will create a local image for your docker called agent-docker.
To run a Nano-Agent as a container the following steps are required:
- If you are using a container management system / plan on deploying the container using your CI, add the agent docker image to an accessible registry.
- If you are planning to manage the agent using the open-appsec UI, then make sure to obtain an agent token from the Management Portal and Enforce.
- Run the agent with the following command (where -e https_proxy parameter is optional):
docker run -d --name=agent-container --ipc=host -v=<path to persistent location for agent config>:/etc/cp/conf -v=<path to persistent location for agent data files>:/etc/cp/data -v=<path to persistent location for agent debugs and logs>:/var/log/nano_agent -e https_proxy=<user:password@Proxy address:port> -it <agent-image> /cp-nano-agent [--token <token> | --standalone]
Example:
$ docker run -d --name=agent-container --ipc=host -v=/home/admin/agent/conf:/etc/cp/conf -v=/home/admin/agent/data:/etc/cp/data -v=/home/admin/agent/logs:/var/log/nano_agent –e https_proxy=user:[email protected]:8080 -it agent-docker /cp-nano-agent --standalone
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
1e67f2abbfd4 agent-docker "/cp-nano-agent --hybrid-mode" 1 minute ago Up 1 minute agent-containerNote that you are not required to use a token from the Management Portal if you are managing your security policy locally. However, you are required to use the --standalone flag in such cases. In addition, the volumes in the command are mandatory only if you wish to have persistency upon restart/upgrade/crash of the agent and its re-execution. Lastly, --ipc=host argument is mandatory in order for the agent to have access to shared memory with a protected attachment (NGINX server).
- Create or replace the NGINX container using the Attachment Repository.
This will run a docker container using the agent docker image.
We welcome everyone that wishes to share their knowledge and expertise to enhance and expand the project.
Please see the Contributing Guidelines.
open-appsec code was audited by an independent third party in September-October 2022. See the full report.
If you've found a vulnerability or a potential vulnerability in open-appsec please let us know at [email protected]. We'll send a confirmation email to acknowledge your report within 24 hours, and we'll send an additional email when we've identified the issue positively or negatively.
open-appsec is open source and available under Apache 2.0 license.
The basic ML model is open source and available under Apache 2.0 license.
The advanced ML model is open source and available under Machine Learning Model license, available upon download in the tar file.