Ownership and Responsibilities Sample Clauses

Ownership and Responsibilities. 3.1 SMWD shall be the sole owner of Project facilities. Metropolitan shall have no ownership right, title, security interest or other interest in the Project facilities.
AutoNDA by SimpleDocs
Ownership and Responsibilities. 2.1 As TU and TUSU are separate legal entities, both are individually registered as Data Controllers with the ICO as follows:
Ownership and Responsibilities. 5.1. Responsibility for this document rests with the Director of Nursing, Maternity & Allied Health Professionals.
Ownership and Responsibilities. 3.1 El Toro shall be the sole owner of Project facilities. Metropolitan shall have no ownership right, title, security interest or other interest in the Project facilities.
Ownership and Responsibilities. 3.1 EVWD shall be the sole owner of all Project facilities. Valley District shall have no ownership right, title, security interest or other interest in the Project facilities.
Ownership and Responsibilities. The Beneficiary is informed that the Recorder does not affect in any way the performance and / or driving of his vehicle which he remains responsible for control. Throughout the duration of the study, the Beneficiary will guard the Recorder.
Ownership and Responsibilities. 3.1 Except as may be provided by separate agreement of the Parties, Participant shall be the sole owner of all Project facilities. Valley District shall acquire no ownership right, title, security interest or other interest in the Project facilities as a result of the LRIP or this Agreement.
AutoNDA by SimpleDocs
Ownership and Responsibilities. 1. All facilities covered by this policy must present a University mission justification with sign-off at the Vice President level. Information Technology Security must keep the business justifications on file.
Ownership and Responsibilities. Equipment and applications within the scope of this policy must be administered by support groups approved by Information Technology Security for DMZ system, application, and/or network management. Support groups will be responsible for the following:  Equipment must be documented in the corporate wide enterprise management system. At a minimum, the following information is required: o Host contacts and location. o Hardware and operating system/version. o Main functions and applications. o Password groups for privileged passwords.  Network interfaces must have appropriate Domain Name Server records (minimum of A and PTR records).  Password groups must be maintained in accordance with the corporate wide password management system/process.  Immediate access to equipment and system logs must be granted to members of Information Technology Security upon demand, per the Audit Policy.  Changes to existing equipment and deployment of new equipment must follow and corporate governess or change management processes/procedures. To verify compliance with this policy, Information Technology Security will periodically audit DMZ equipment per the Audit Policy.
Ownership and Responsibilities. All internal servers deployed at University of Louisiana at Lafayette must be owned by an operational group that is responsible for system administration. Approved server configuration guides must be established and maintained by each operational group, based on business needs and approved by Information Technology Security. Operational groups should monitor configuration compliance and implement an exception policy tailored to their environment. Each operational group must establish a process for changing the configuration guides, which includes review and approval by Information Technology Security.  Servers must be registered within the corporate enterprise management system. At a minimum, the following information is required to positively identify the point of contact: o Server contact(s) and location, and a backup contact o Hardware and Operating System/Version o Main functions and applications, if applicable  Information in the corporate enterprise management system must be kept up-to-date.  Configuration changes for production servers must follow the appropriate change management procedures.
Time is Money Join Law Insider Premium to draft better contracts faster.