User Access Control. We have implemented and maintain appropriate access controls and the concept of least privilege designed to ensure only authorized users have access to Customer Data within PureCloud. User access is logged for audit purposes.
a. Customer User Access
b. Our User Access
i. User accounts are requested and authorized by our management.
ii. User accounts follow the concept of least privilege.
iii. Access to the PureCloud Production environment requires multifactor authentication.
iv. SSH keys are utilized instead of passwords within PureCloud.
v. Dormant or unused accounts are disabled after 90 days of non-use.
vi. Session time-outs are systematically enforced.
vii. User accounts are promptly disabled upon employee termination or role transfer, eliminating a valid business need for access.
User Access Control. Genesys will implement appropriate access controls to ensure only authorized users have access to Customer Data.
User Access Control. We have implemented and maintain appropriate access controls and the concept of least privilege designed to ensure only authorized users have access to Customer Data within Altocloud. User access is logged for audit purposes.
a. Customer User Access
b. Our User Access
i. User accounts are requested and authorized by our management.
ii. User accounts follow the concept of least privilege.
iii. Access to the Altocloud Production environment requires multifactor authentication.
iv. SSH keys are utilized instead of passwords within the Altocloud server environment.
v. User accounts are promptly disabled upon employee termination or role transfer, eliminating a valid business need for access.
User Access Control. We have implemented and maintain appropriate access controls and the concept of least privilege designed to ensure only authorized users have access to Customer Data within Genesys Hub. User access is logged for audit purposes.
a. Customer User Access
b. Our User Access
i. User accounts are requested and authorized by our management.
ii. User accounts follow the concept of least privilege.
iii. User accounts are promptly disabled upon employee termination or role transfer, eliminating a valid business need for access.
User Access Control. 7.1. In connection with all GoodData Workspaces, only designated GoodData personnel, Your administrators, or partner administrators can manage Customer access and remove from or manage Customer data on the Platform. GoodData personnel can obtain user-level access to Customer data only when explicitly invited by You or a partner administrator for the purposes of technical support or when contractually authorized to provide professional services. The Platform supports role- based access control and user groups to define objects and capabilities within the Platform to which a Customer will have access.
7.2. There are additional measures that You should use to implement Customer-specific access control policies.
7.2.1. IP whitelisting allows You to define trusted IP address ranges from which Customers can access Your domains.
7.2.2. Custom session expiration allows You to specify a period of inactivity after which sessions are terminated and Customers are automatically logged out of the Platform.
User Access Control. Zugriffskontrolle")
User Access Control. 5.1.1 The DATA CONTROLLER will use means that are commercially viable so that REVIEW PRO can only access the confidential Data of the DATA CONTROLLER that are necessary for REVIEW RANK to fulfill its obligations under the Agreement. X
User Access Control. Vendor shall allow Customers, Users, and Vendor staff to Access the CRM System based on security and information Access requirements through a web browser. Notwithstanding anything to the contrary in this Contract, Vendor shall:
a. Provide FHKC with a minimum of 12 User licenses that will provide read/write Access to the CRM System Graphical User Interface (GUI);
b. Provide a minimum of four FHKC employees with CRM System technical network account and read-only database Access, as well as Access to third-party vendor customer support sites;
c. Provide read/write Access to a minimum of 100 CEC staff;
d. Provide read-only Access to a minimum of 300 grantees, partners, other Users, as determined by FHKC;
e. Create unique Customer and User accounts based on FHKC criteria;
f. Establish role-based Access with differing levels of privilege;
g. Maintain internal security controls to record the security ID of any User who Accesses an account, as well as a recorded date and time stamp for each transaction;
h. Require account authentication or "identity validation;"
i. Limit each User to one account with a unique username and password;
j. Allow password modification only in the event of a password breach;
k. Make electronic signature authority available for electronic transactions with proper security;
l. Provide credentialing using two-factor authentication;
m. Log and retain all User actions for security auditing;
n. Allow for and fully support single sign-on capability with other secure websites (e.g., Insurer member websites) as agreed upon by the Parties and as determined by FHKC. Vendor shall be responsible for hosting and maintaining the single sign-on database and engine;
o. Support the current and previous two versions of the following browsers: Internet Explorer, Firefox-Mozilla, Safari, Chrome, and Microsoft Edge. Browser updates will be reviewed by Vendor for compatibility with the CRM System and certified if compatible within 30 Calendar Days of release. If a newly released version cannot be supported within 30 Calendar Days, Vendor shall notify FHKC within 10 Calendar Days of the release, identifying: (i) when the update will be fully supported, (ii) what activities must occur to become fully supported, and (iii) what barriers prevent Vendor from fully supporting the new version within that timeframe. The intent is for the CRM System to be browser agnostic; and
p. At no additional cost to FHKC, purchase and/or renew and apply Secure Socket Layer (SSL) C...
User Access Control
