logo

Using PowerShell Empire with a Trusted Certificate

ID: e4f8af9c-2b49-5b04-87e8-e836b0c4606e

STIX ID: report--e4f8af9c-2b49-5b04-87e8-e836b0c4606e

Feed Name: Black Hills Infosec Blog

Threat Score
55/100

Date Published: 2016-11-23

Date Updated: 2026-04-27

Author: BHIS

...
...

This blog post walks through configuring PowerShell Empire to serve HTTPS command-and-control using a trusted certificate (Let's Encrypt or self-signed), including certbot installation, combining cert and key files, stopping Apache to free ports, and example Empire listener and stager settings (jitter, default profile, port 443) to increase the chance of a successful, stealthy session.

Your team is not currently subscribed to this feed. You must subscribe to it in order to see this post.