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 CrowdSec Hub.

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:

  1. Set the container_runtime value to “containerd”.

  2. 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
  3. 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"
  4. 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"

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.

For further details on this please consult the CrowdSec documentation available here:

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:

pageCrowdSec Bouncer Support

Last updated