Meridian Electric Cooperative wants to restrict which video categories back-office staff can watch on a major video-sharing site. That site is served entirely over HTTPS. What does the video filter profile require in order to make category- or channel-level decisions on that traffic?

Video filtering operates at a finer grain than a simple domain block: it needs visibility into which video or channel is actually being requested on a site, and on an HTTPS-only platform that information travels inside the encrypted session. SSL deep inspection is what exposes that content to FortiGate's inspection engines, which is why it's a prerequisite for meaningful video- or channel-level enforcement on such a site — without it, FortiGate can see that the domain was reached but not enough about the specific video request to apply a category or channel rule. The claim that video filtering works identically without any extra configuration ignores that HTTPS traffic is encrypted by default and simply isn't inspectable at that level without decryption. A DNS filter profile can block or allow the whole domain, but that's an all-or-nothing decision at the domain level — it can't substitute for channel- or category-specific enforcement within a site that stays reachable. Application control identifies the application in use, not the specific video content being requested, so it isn't the mechanism responsible for video-level decisions either. A caveat: enabling deep inspection has broader implications for every session in that policy, not just video traffic, so it's worth scoping which policies actually need it. Confirm enforcement is working by checking the video filter log for entries showing the specific category or channel action taken.