Overview of k2 security features – Grass Valley K2 System Guide v.7.2 User Manual
Page 159
07 April 2010
K2 System Guide
159
Overview of K2 security features
Overview of K2 security features
K2 security features reference Windows operating system user accounts and groups
on the local K2 system to determine permission levels. Depending on the account
used to log on to the Windows operating system, to log on to K2 applications, or to
otherwise authenticate system access, permission is granted for various levels of
operational and media access.
K2 systems offer security features as follows:
• Windows operating system — Depending on the current Windows logon,
permission is granted to make settings in the Windows operating system. Refer to
the next section
“Security and user accounts” on page 161
• K2 applications — Depending on the user account used to log on to the application,
permission is granted to control and configure the application. These K2
applications include AppCenter, Storage Utility, and the K2 System Configuration
application. Refer to the next section
“Security and user accounts” on page 161
• Media access — There are three types of media access security, as follows:
• Media access in AppCenter — You can set user permissions on the K2 bins that
store your media. Then, depending on the current AppCenter logon, permission
is granted for AppCenter operations on the media in the bins. Refer to
“AppCenter operations and media access security” on page 163
.
• Media access via FTP — The user permissions set on K2 bins in AppCenter also
determine access via FTP. Depending on the FTP session logon, permission is
granted for FTP commands accessing the media in the bins. Refer to
media access security” on page 163
• Media access via protocols — The permissions set on K2 bins in AppCenter also
determine access for channels controlled by protocols. Depending on the
channel accessing the media, permission is granted for operations on the media
in the bins. Refer to
“Protocol control of channels and media access security” on
• Channel access — You can set user permissions for each channel. Then, depending
on the current AppCenter logon or protocol operating a channel, permission is
granted or denied to operate the channel. Refer to