The core features of a WAF do require SSL offload, which of course means that the data needs to be unencrypted with your certificate on their edge nodes, then re-encrypted with your origin certificates. There is no other way in a WAF to protect from these exploits if the encryption is not broken, and WAF vendors can respond much faster than developers can to put protections in place for emerging threats.

I had never considered that Akamai or Cloudflare would be doing any deeper analytics on our data, as it would open them up to significant liability, same as I know for certain that AWS employees cannot see the data within our buckets.

As for the captcha prompts, I can’t speak to how those work in Cloudflare, though I do know that the AWS WAF does leave the sensitivity of the captcha prompts entirely up to the website owner. For free versions of CF there might be fewer configurable options.

Can you educate me on the negatives of Cloudflare?

My company is on Akamai, who has a pretty solid combined offering of WAF, DNS, and CDN, and yet I still feel like their platform is antiquated and well overdue for a refresh.

Thinking back to log4j, it was cloudflare who had the automatic protections in place well ahead of Akamai, who we had to ask for custom filters. Cloudflare also puts out many articles on Internet events and increase adoption of emerging best practices, sometimes through heavy shaming.

Eyyy yes! I just picked up an MZ-N505 a few months ago! It’s been great at work to quickly start music without staring at my phone for 5 minutes first.

Plex, as a company, definitely is aware of what items are in your library but streams don’t go through the Plex servers unless you use the Plex proxy service which is enabled by default but only used when the client connection speed is too slow to use the desired streaming setting.

Everyone who accesses their Plex externally should use app.plex.tv rather than NAT/port forwarding unless you’re also doing IP whitelisting on the NAT (not feasible for most remote access scenarios, as IPs are dynamic in most cases). Jellyfin should never be exposed externally.

I work in a highly regulated sector of IT and have learned that even the most robust software will have serious exploits at some point.

I have not looked into it for a while but I believe their servers broker a direct connection between the client and server.

I always wonder why some people are so dedicated to Jellyfin. Even if JF had full feature and experience parity, it would still not have secure remote access the way Plex does. There is no need to port forward or NAT Plex for external access if you use app.plex.tv to access. With the threat landscape the way it is today, that is worth a lot.

You don’t think it’s possible that the accusations were mostly unfounded and the LTT crew are just decent people? They did bring up some issues with onboarding which are completely expected on smaller companies.

At my work we pay auditors to assess our security controls and I would chose a different company if I thought they were being anything less than honest with us on their findings. The agreements and SOW are set up at the beginning of the engagement, so the investigators get paid regardless of their findings. It’s not like the bond rating agencies on Wall Street.