>_ IzzyLab

Hands-on task

This task is step 9 of the course “Investigating a server”

The attacker's certificate fingerprint

easy~3 min

Among the evidence on the server there's a certificate /srv/evidence/c2.crt — the attacker used it to front their command-and-control server. To recognise it over TLS on other machines, you need an indicator of compromise: compute the SHA-256 fingerprint of this certificate and write it to /root/ioc-fingerprint.txt.

What you'll practise:
  • certificate fingerprint
  • openssl x509
  • indicator of compromise
  • sha-256

Topic breakdown

A certificate fingerprint is a hash of its entire DER encoding. It's a short string that uniquely identifies the certificate: it's published as an indicator of compromise (IoC), compared in certificate pinning and in TLS inspection logs. openssl x509 computes it: you give it the input file, suppress printing the PEM itself and ask for the fingerprint with the algorithm you need — the default isn't SHA-256, so the algorithm is specified explicitly. The fingerprint belongs to the certificate, not the key: reissuing it with the same key changes the fingerprint.

What's checked

  1. SHA-256 fingerprint of c2.crt written

What it looks like