lock

x509 SSL Certificate Monitoring Template

Template built by

Telegraf Plugins used:

Included Resources:

  • 1 Telegraf Configuration
  • 1 Dashboards: x509.yml
  • 1 bucket: 'x509'
  • 1 label: 'x509'

Quick Install

If you have your InfluxDB credentials configured in the CLI, you can install this template with:

https://raw.githubusercontent.com/influxdata/community-templates/master/x509/x509.yml

X.509 certificate monitoring dashboard

X.509 is a format of public key certificates and is used in many Internet protocols, including TLS/SSL. These certificates are also used in offline applications, like electronic signatures. An X.509 certificate contains a public key and an identity and is either signed by a certificate authority or self-signed.

When a certificate is signed by a trusted certificate authority, or validated by other means, someone holding that certificate can rely on the public key it contains to establish secure communications with another party, or validate documents digitally signed by the corresponding private key.

Why monitor your x509 certificates?

X.509 certificates have an expiration date that can prevent your website or applications from working properly and presenting your users with an alarming warning that the site’s security certificate has expired. To avoid this, it is a best practice to check the expiration dates on a regular basis. This X.509 SSL Certificate Monitoring Template does just that – monitors SSL certificates expiration.

How to use X.509 SSL Certificate Monitoring Template

Once your InfluxDB credentials have been properly configured in the CLI, you can install the X.509 certificate Monitoring template using the Quick Install command. Once installed, the data for the dashboard will be populated by the included Telegraf configuration, which includes the relevant X509 Cert Telegraf Input Plugin Input. Note that you might need to customize the input configuration to better serve your needs, including by specifying a new input value.

To find out more information about environmental variables within the Telegraf configuration, consult the following link.

Telegraf Configuration requires the following environment variables:

  • INFLUX_TOKEN - The token with the permissions to read Telegraf configs and write data to the telegraf bucket. You can just use your operator token to get started.
  • INFLUX_ORG - The name of your Organization.
  • INFLUX_HOST - The address of your InfluxDB.
  • INFLUX_BUCKET - The name of the Bucket. If you are going to use the bucket included, you need to export the variable. Ex: export INFLUX_BUCKET=x509

In order to use this template, before import, you need to specify the certificates you want to monitor in the x509.yml file.

Key x509 SSL Certificate metrics to monitor

Some of the most important x509 SSL Certificate metrics that you should proactively monitor include:

  • Number of certificates
  • Expiration countdown

Related Resources

Endpoint Security State Template

Monitoring the security state of endpoints helps you to understand the effectiveness of the endpoint detection and response.

Fail2ban Monitoring Template

Fail2Ban blocks IP addresses that might be trying to breach your system’s security. Use it with this system monitoring template.

X509 Cert Telegraf Plugin

This plugin provides information about X509 certificates accessible via local file or network connection.

Scroll to Top