Privilege Management Sample Clauses
The Privilege Management clause defines how confidential or sensitive information, such as communications between parties or legal advice, is protected from disclosure in legal or business contexts. It typically outlines the procedures for identifying, handling, and maintaining privileged information, and may specify who is authorized to access such materials or how inadvertent disclosures are to be addressed. This clause serves to safeguard privileged communications, ensuring that sensitive information remains protected and is not used improperly or disclosed to unauthorized parties, thereby reducing legal risks and maintaining trust between parties.
Privilege Management. Supplier shall restrict and control the allocation and use of privileges to information systems and services through a formal authorization process. Privileges shall be allocated to users on a need-to-use basis and on least privileges in line with the access control policy.
Privilege Management. Airship personnel with access to the Airship customer account or technical management systems are required to authenticate themselves via logical access controls with multi-factor authentication in order to administer the Service. Any access to customer data by an Airship representative is logged and tracked in real time, with oversight from the security team. In addition, Airship has implemented these additional privilege management measures:
Privilege Management. Subscriber’s administrators must authenticate themselves via a central authentication system or via a single sign on system in order to administer the Services.
Privilege Management. Maximl Labs Pvt Ltd’s and Customer’s administrators and end users must authenticate themselves via a Multi-Factor authentication system or via a single sign on system in order to use the Services
Privilege Management. 4.3.3.1.1. The computer and communications system privileges of all users, systems, and programs must be restricted based on the need to know.
4.3.3.1.2. System administrators managing multi-user computer systems must have at least two user IDs, one that provides privileged access, and the other to perform her or his normal day-to-day work.
4.3.3.1.3. Current records reflecting all the system privileges the users have on all the computer systems must be maintained.
4.3.3.1.4. The system privileges granted to every user must be reevaluated by the user’s immediate manager every year to determine whether currently-enabled system privileges are needed to perform the user’s current job duties.
4.3.3.1.5. The number of privileged user IDs must be strictly limited to those individuals who absolutely must have such privileges for authorized purposes.
4.3.3.1.6. Attribution of system privileges must be approved by the IS/IT management.
4.3.3.1.7. Special system privileges, such as the ability to examine the files of other users or to change the security state of the system, must be restricted to those directly responsible for system management or security, and granted only to those who have attended an approved system administrator training class.
Privilege Management. Customer’s Administrators and End Users must authenticate themselves via a central authentication system or via a single sign on system in order to use the Services. Internal Data Access Processes and Policies – Access Policy. Google’s internal data access processes and policies are designed to prevent unauthorized persons and/or systems from gaining access to systems used to process Customer Data. Google designs its systems to (i) only allow authorized persons to access data they are authorized to access; and (ii) ensure that Customer Data cannot be read, copied, altered or removed without authorization during processing, use and after recording. The systems are designed to detect any inappropriate access. Google employs a centralized access management system to control personnel access to production servers, and only provides access to a limited number of authorized personnel. Google’s
Privilege Management. Customer’s administrators and Customer End Users must authenticate themselves via a central authentication system or via a single sign on system in order to use the Services.