Skip to main content
Version: Next

Email Plugin

The Email plugin is by default shipped with your CrowdSec installation. The following guide shows how to enable it.

Enabling the plugin:#

In your profile file (by default /etc/crowdsec/profiles.yaml) , uncomment the section

#notifications:# - email_default 

Every alert which would pass the profile's filter would be dispatched to email_default plugin.

Configuring the plugin:#

By default the configuration for email plugin is located at /etc/crowdsec/notifications/email.yaml. You'll need to fill the credentials for the SMTP server here.

Example configuration for Gmail#

Example config which mail's the alerts to

# Don't change thistype: email
name: email_default # this must match with the registered plugin in the profilelog_level: info # Options include: trace, debug, info, warn, error, off
format: |  # This template receives list of models.Alert objects  {{range . -}}    {{$alert := . -}}    {{range .Decisions -}}      <a href={{.Value}}>{{.Value}}</a> will get <b>{{.Type}}</b> for next <b>{{.Duration}}</b> for triggering <b>{{.Scenario}}</b>. <a href={{.Value}}>Shodan</a>      {{end -}}  {{end -}}
smtp_host: myemail@gmail.comsmtp_password: mypassword smtp_port: 587sender_email: myemail@gmail.comreceiver_emails: - receiver@gmail.comencryption_type: ssltls # Requiredauth_type: login # "plain" also worksemail_subject: CrowdSec Notification
# group_wait: # duration to wait collecting alerts before sending to this plugin, eg "30s"
# group_threshold: # if alerts exceed this, then the plugin will be sent the message. eg "10"
# max_retry: # number of tries to attempt to send message to plugins in case of error.
timeout: 20s # duration to wait for response from plugin before considering this attempt a failure. eg "10s"

The configuration directive format is a go template, which is fed a list of Alert objects.

The configuration directive encryption_type is either none, starttls and ssltls which are self-explanatory and the configuration directive auth_type is either none, crammd5, login or plain.

Final Steps:#

Let's restart crowdsec

sudo systemctl restart crowdsec

You can verify whether the plugin is properly working by triggering scenarios using tools like wapiti, nikto etc.