The use of video continues to grow across the enterprise—from large-scale, all-hands meetings to customer service to research and analysis—with some estimates show- ing the market growth of enterprise video products and services at more than 11%
per year for the next 6 years, for a total anticipated market of almost $37 billion by the year 2020.
Given this uptick in enterprise video, there’s
a corresponding and ever-increasing need to
analyze which security approaches to implement. Some video content, whether it is intended for consumption inside or outside the firewall, needs to be embargoed to avoid leaking
information prior to a product launch. Other
content may need to be even more highly protected, such as video that contains competition-sensitive information.
This article explores content security on three
levels: encryption (whether for content that’s being transported or stored), rights management,
and content management. Along the way, we will
also briefly touch on customized enterprise video platforms (EVPs) versus more generic EVPs.
This distinction of generic EVPs, customized
EVPs, and even generic media asset management
(MAM) solutions is key, since the majority of video
solutions used within companies have their origins in online video platforms (OVP).
While OVPs and EVPs are not created equal,
the expertise in content encryption tends to fall
into the more mature OVP solutions. This isn’t to
say that secure EVPs are lacking in encryption
options, but the expertise of handling encrypted
video content appears to reside within OVP support teams a bit more than EVP support teams.
Brightcove, a large OVP service provider, offers a few tips for encrypting Apple HTTP Live
Streaming (HLS) for delivery to a variety of iOS
devices. This flavor of HLS, called HLSe (for encrypted), utilizes the Advanced Encryption Standard (AES) as well as other technologies. Brightcove claims that there is “no detectable difference
to video playback” when compared to standard
The encryption for HLSe works at the segment
level (an HTTP-based video is divided into multiple segments or chunks). At the point of ingestion and packaging for standard HLS segments,
often 2–10 seconds in length, each segment file
From pipes to pixels,
enterprise video security
is becoming big business.
By Tim Siglin