DX Unified Infrastructure Management

 View Only

 Probe to monitor a Server- client authentication certificate

Abhimanue Bhaskaran's profile image
Abhimanue Bhaskaran posted Jan 28, 2023 12:17 PM
Hello,

We have a need to monitor Server- client authentication certificate which does not have a URL and cannot be monitored by url_response

Is there a probe which we can use to monitor such a certificate?

Thanks
AB
Luc Christiaens's profile image
Luc Christiaens
How do you verify this certificate for the moment?
If there is a command line (openssl?) to verify this you can do the verification via the logmon probe
Abhimanue Bhaskaran's profile image
Abhimanue Bhaskaran
Hello,

This was a new monitoring request from the users. We do not have any monitoring in place for Server certificates.

I found that there is a script for logmon is linux, I was wondering if there was one for windows machines? Maybe a PowerShell which everyone use?

link to Linux .sh script: https://community.broadcom.com/communities/community-home/digestviewer/viewthread?MID=764981

Thanks,
AB
Luc Christiaens's profile image
Luc Christiaens
You can launch your powershell via logmon command as: powershell -command "your command or script" and add watchers to create dynamic alarms
Or you can use a direct command, like: "openssl x509 -enddate -noout -in c:\temp\server-cert.pem"
This will return: notAfter=Feb 2 06:52:18 2024 GMT
Thomas Linder's profile image
Thomas Linder
Hi.

We're using the attached script wrapped around logmon Rules to identify certificates that are about to expire.
It allows for Warning and Critical thresholds, lists all certificates (one per line) except those outside of -IgnoreDaysPast (default -15) and -IgnoreDaysFuture (default 1500). Indication via OK, WARNING or CRITICAL string, fingerprint, days and CN,OU, ... included to be used in variables.

Logmon setup is a bit complex, see screenshots below for examples. I had to set up alerts via Advanced tab to get consistent alerts/clears. Can't remember why unfortunately.
Suppression key uses the fingerprint from the reported entry.

Basic syntax for execution from cmd / logmon: powershell.exe Check-Cert.ps1 -CertStore <Cert Store Path> -WarningDays <Warning Days> -CriticalDays <Critical Days>


Maybe this helps.

Regards,
Thomas.