Reduce Piracy Points

Many major motion picture studios have focused on the value of their content and are mandating that both vendors and internal divisions develop and implement formal security policies. Studio concerns include:
  • Sharp increase in piracy for theatrical release content and new production for DVD and Blu-ray release.
  • Existing library material destined for DVD release.
  • Evolving digital workflows put elements and finished content at risk.
  • Physical asset security procedures cannot protect electronic base content.
 
High Level Technology Challenges in Protecting Content
Changing technology has increased content security risks:
  • File based networks.
  • Assets and images are easily transported across a network or across the world.
  • Traceability is difficult.
  • Electronic file based operations can be performed faster than real time.
  • Assets are generated easily and often.
  • Ability to move content quickly across networks without formality associated with physical media.
  • Ability for others to penetrate workspaces from the outside.
  • Transportation of content across both secure and unsecured networks.
 
Detailed Technology Challenges in Protecting Content
Specific implementation details of technologies required, combined with file system permissions required by operators, increase content security risks:
  • Many of the creative applications (Lustre, Clipster, etc.) run with "administrator" privileges.
  • Many facilities set file system permissions owned by administrator with read / write access by everyone.
  • Data managers often require "administrator" (root, sudo) privileges for basic data management tasks (high speed copy, defragmentation).
  • Poor traceability with file system actions.
  • Studio service providers can often define and outline workflows and practices but lack automated mechanisms to lock down adherence.
 
Barriers Provided by DataFrameworks

 
Provides a Degree of File System Forensics   Template Based File System Management
  • History of actions (example: cut, copy, move, delete) initiated via DataFrameworks interface are logged and tracked.
 
  • Provides mechanism to automate adherence to studio policies
  • Reduces probability of content error.
     
Limits Operational Exposures   Automated Detection of "Non-Conformance"
  • Reduces need for data managers to have administrator privileges.
  • Configurable interface to enforce operational roles and functions.
  • Separates access from authorization (SecureView).
  • Enhances management of physical permissions.
 
  • Provides ability to define file system "baseline" policies, budgets, and business logic.
  • Provides automated detection of "non-conforming" file system events to policy "baseline."