CrowdSec Intelligence Sharing Using open-appsec Parser/Scenario

When using CrowdSec alongside open-appsec to consume CrowdSec Threat Intelligence you might also want to have the CrowdSec security engine parse the security logs created by open-appsec's multiple security layers to add additional security indicators to your local CrowdSec "ecosystem" and share intelligence with CrowdSec Threat Intelligence to contribute to their Community Blocklist. To achieve this you can use our open-appsec collection available from the .

Required Parsers and Collections

In order to parse open-appsec logs within CrowdSec the following parsers require installation:

The following Collections must be installed:

Required CrowdSec Configuration for Parsing open-appsec Logs

For CrowdSec and open-appsec both deployed on Kubernetes:

For information on how to deploy CrowdSec on Kubernetes with Helm see here: Make sure to add the following configuration to your helm chart's crowdsec-values.yaml file:

Set the container_runtime value to “containerd”.

Set the following docker image values in the "image" section:

repository = crowdsecurity/crowdsec
pullPolicy = IfNotPresent
tag = "v1.4.6"
# mandatory to use CrowdSec container version v1.4.6 or later

Under the "agent" section, add an entry in the "acquisition" array and configure in with the following namespace, pod name and program values:

namespace = "<namespace-of-your-open-appsec-agent>"
podName = "appsec-open-appsec-*"
# make sure this query matches the names of the deployed open-appsec pods, especially if you adjusted the name-template parameter for the open-appsec deployment
program = "openappsec"

Under the "agent" section, add 2 entries in the "env" array:

- name: PARSERS
  value: "crowdsecurity/cri-logs crowdsecurity/dateparse-enrich"
- name: COLLECTIONS
  value: "crowdsecurity/nginx openappsec/openappsec"

For CrowdSec and open-appsec both deployed on Linux:

Make sure to have a CrowdSec version >= 1.4.6 installed on your Linux machine, see
Configure the acquisition for consuming the open-appsec log-files in CrowdSec's main yaml configuration file /etc/crowdsec/config.yaml as follows:
```
source: file
filenames:
  - /var/log/nano_agent/cp-nano-http-transaction-handler.log*
labels:
  type: openappsec
```

Edit the following configuration file /etc/crowdsec/collections/linux.yaml and add the relevant parsers and collections as shown below:

parsers:
  - crowdsecurity/cri-logs
  - crowdsecurity/dateparse-enrich

collections:
  - crowdsecurity/nginx
  - openappsec/openappsec

Restart crowdsec to apply the changes by running sudo systemctl restart crowdsec Alternatively you can use CrowdSec's cscli command to apply the changes: sudo cscli capi update

For CrowdSec and open-appsec both deployed on Docker:

Configure the acquisition for consuming the open-appsec log-files in CrowdSec's main yaml configuration file /etc/crowdsec/config.yaml mounted into your crowdsec docker container as follows:
```
source: docker
container_name:
 - open-appsec-agent
labels:
  type: openappsec
```
Edit the following configuration file /etc/crowdsec/collections/linux.yaml mounted into your crowdsec docker container and add the required parsers and collections as shown below:
```
parsers:
  - crowdsecurity/cri-logs
  - crowdsecurity/dateparse-enrich

collections:
  - crowdsecurity/nginx
  - openappsec/openappsec
```
Restart your CrowdSec docker container to apply the changed configuration.

CrowdSec version needs to be above or equal to 1.4.6 for open-appsec log parsing integration to work. Note that if you use specify "latest" as tag you might still get an older version below v1.4.6.

If you didn't configure open-appsec to bounce malicious source IP addresses based on CrowdSec's Threat Intelligence using the Community Blocklist you can follow the steps explained here to configure this in couple easy steps:

PreviousCrowdSec Bouncer Support NextNGINX Proxy Manager

Last updated 12 days ago

Was this helpful?

namespace = "<namespace-of-your-open-appsec-agent>" podName = "appsec-open-appsec-*" # make sure this query matches the names of the deployed open-appsec pods, especially if you adjusted the name-template parameter for the open-appsec deployment program = "openappsec"