Refer to the exhibits. The exhibits show the SSL and authentication policy (Exhibit A) and the security policy (Exhibit B) tor Facebook. Users are given access to the Facebook web application. They…

Many web application functionalities, such as posting reactions or interacting with dynamic content, rely on specific API calls or encrypted traffic that can only be fully inspected and controlled when SSL inspection is set to deep content inspection. Without deep inspection, the firewall might not be able to fully understand and allow all necessary encrypted components for interactive features, even if basic content like video streaming is permitted.

Forcing HTTP service for Facebook is insecure and impractical, as modern web applications predominantly use HTTPS for security, and forcing HTTP would likely break the application or expose user data.

While application signatures are used for granular control, if basic access and video playback work, the issue likely lies with the inability to inspect deeper into encrypted traffic rather than missing signatures for specific interactive elements, which deep inspection helps with.

Adding Facebook to a URL category in the security policy primarily controls access based on the URL itself and doesn't inherently resolve issues with encrypted interactive application features when deep SSL inspection is lacking.