| SecureView |
|
| |
| Provide Users With View of File System Without Granting File System Access |
| Studios are increasingly demanding their service providers physically separate “production networks” from the general “Information Technology network,” due to piracy concerns. The requirement introduces additional constraints for the service provider’s personnel not directly involved in the creative aspects of the project. For example, Customer Service Representatives (CSRs) need the ability to effectively communicate project status to customers, but don’t necessarily need physically access to actual image data. A mechanism is needed to provide the service provider’s personnel with the information required to perform job function, without necessarily increasing piracy risks or exposure points. |
| |
"DataFrameworks separates authorization and access. This allows our Customer Service Representatives (CSRs) to have visibility of file system data without the ability (or privilege) to actually access the file systems."
|
| |
| SecureView provides individuals with the ability to see file names and sizes without the ability to actually read or write data. CSRs can be provided visibility as to where a particular client job may be (i.e. data loaded onto system) without the ability to copy or access actual files. The ability to prevent access is critical as the entire industry is very sensitive to piracy of actual image files. |
| |
| SecureView Proxies a View of File System Without Granting Access to the File Systems |
| |
|
| |
| click here to enlarge |
| |
|
|
|
|
|
|
