Question above Forward Proxy Decryption implementation

jsalmans — Fri, 10 May 2024 18:22:32 GMT

Greeting all,

I've tinkered with Forward Proxy Decryption a bit in the past and I want to revisit this for a limited rollout to our servers at least. My previous experimentation into the feature was for a Windows client so I understand the basics there in that you can add the certificate to the Windows cert store and most applications should use it by default (with the exception of some such as Firefox, Filezilla, etc).

What is the implementation for Linux servers? If you drop the same certificate in the system's certificate store, will all command line applications (including yum, apt-get, etc) use that or is it common to run into issues with ones that use their own certificate store?

I'm also curious about the certificate itself... using an internal PKI, is it best practice just to create a new cert signed by the internal CA for decryption? And what about cert lifetime duration?

Thanks!

Re: Question above Forward Proxy Decryption implementation

Claw4609 — Thu, 16 May 2024 13:23:54 GMT

Hello,

While Im not personally that familiar with Linux. You could need the device to trust the certificate as the firewall will dynamically sign certs so the device would need to know this cert if same.

For the cert itself, you can use an internal pki and sign it using the "subordinate" template. This templates default length is 2 years, but for actual cert length that would be what level of security the businesses decides, maybe your business whats certs rotated every year for example.

How to Implement and Test SSL Decryption - Knowledge Base - Palo Alto Networks

topic Re: Question above Forward Proxy Decryption implementation in Next-Generation Firewall Discussions

Question above Forward Proxy Decryption implementation

Re: Question above Forward Proxy Decryption implementation