Initially discovered Proxifier from a SANS article. Since then, I’ve been using it to troubleshoot connection issue in corporate proxy environment. Previously Wireshark was used for troubleshooting, but it captures the whole operating system (OS) making it challenging to discern a specific app. Similar issue with Burp Suite when using OS-wide proxy configuration, app-specific proxy requires the app to support proxy connection. By using Proxifier, I can target a specific app only, resulting in accurate traffic analysis.
- In Burp Suite, Proxy top tab > proxy settings > import/export CA certificate.
- Export “Certificate and private key in PKCS#12 keystore”, set filename as burp.pfx with simple password.
- Open the exported PFX file using default Windows Certificate utility, set “current user”, enter password set in Step 2, “Place all certificates in the following store” > “Trusted Root Certificate Authorities”.
- In Proxifier, create a new proxy configuration:
- Address: 127.0.0.1
- Port: 8080
- Protocol: HTTPS
- When prompted,
- Use this proxy by default: no
- Edit Proxification Rules now: yes
- Profile > Proxification Rules, create a new rule:
- Applications: “application.exe”
- Action: “Proxy HTTPS 127.0.0.1”
- Ensure rule is above Default, move above Localhost rule to capture localhost traffic
- Back in Burp Suite, Proxy top tab > HTTP history tab, application traffic will show up here.