Access Controls a. Authorized Access - DST shall have controls that are designed to maintain the logical separation such that access to systems hosting Fund Data and/or being used to provide services to Fund will uniquely identify each individual requiring access, grant access only to authorized personnel based on the principle of least privileges, and prevent unauthorized access to Fund Data.
Drug Testing Procedures a. The testing procedures and safeguards provided in this policy shall be adhered to by any laboratory personnel administering departmental drug tests.
Log Reviews All systems processing and/or storing PHI COUNTY discloses to 11 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY 12 must have a routine procedure in place to review system logs for unauthorized access.
Review Protocol A narrative description of how the Claims Review was conducted and what was evaluated.
Personnel File Review a. A unit member has the right upon his/her own request to review the contents of his/her personnel file. The review will be conducted in the presence of the administrator, or his/her designee, responsible for the safekeeping of such file. The employee may have a committee person assist in said review. Such review shall be conducted at a mutually agreeable time. A copy of requested material will be provided.
System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization. Measures: • Multiple authorization levels are used when granting access to sensitive systems, including those storing and processing Personal Data. Authorizations are managed via defined processes according to the SAP Security Policy • All personnel access SAP’s systems with a unique identifier (user ID). • SAP has procedures in place so that requested authorization changes are implemented only in accordance with the SAP Security Policy (for example, no rights are granted without authorization). In case personnel leaves the company, their access rights are revoked. • SAP has established a password policy that prohibits the sharing of passwords, governs responses to password disclosure, and requires passwords to be changed on a regular basis and default passwords to be altered. Personalized user IDs are assigned for authentication. All passwords must fulfill defined minimum requirements and are stored in encrypted form. In the case of domain passwords, the system forces a password change every six months in compliance with the requirements for complex passwords. Each computer has a password-protected screensaver. • The company network is protected from the public network by firewalls. • SAP uses up–to-date antivirus software at access points to the company network (for e-mail accounts), as well as on all file servers and all workstations. • Security patch management is implemented to provide regular and periodic deployment of relevant security updates. Full remote access to SAP’s corporate network and critical infrastructure is protected by strong authentication.
Random Testing Notwithstanding any provisions of the Collective Agreement or any special agreements appended thereto, section 4.6 of the Canadian Model will not be applied by agreement. If applied to a worker dispatched by the Union, it will be applied or deemed to be applied unilaterally by the Employer. The Union retains the right to grieve the legality of any imposition of random testing in accordance with the Grievance Procedure set out in this Collective Agreement.
Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.
Performance Testing 7.2.1 The Design-Builder shall direct and supervise the tests and, if necessary, the retests of the Plant using Design-Builder’s supervisory personnel and the Air Emissions Tester shall conduct the air emissions test, in each case, in accordance with the testing procedures set forth in Exhibit A (the “Performance Tests”), to demonstrate, at a minimum, compliance with the Performance Guarantee Criteria. Owner is responsible for obtaining Air Emissions Tester and for ensuring Air Emissions Tester’s timely performance. Design-Builder shall cooperate with the Air Emissions Tester to facilitate performance of all air emissions tests. Design-Builder shall not be held responsible for the actions of Owner’s employees and third parties involved in the Performance Testing, including but not limited to Air Emissions Tester.
Testing Procedures Testing will be conducted by an outside certified Agency in such a way to ensure maximum accuracy and reliability by using the techniques, chain of custody procedures, equipment and laboratory facilities which have been approved by the U.S. Department of Health and Human Services. All employees notified of a positive controlled substance or alcohol test result may request an independent test of their split sample at the employee’s expense. If the test result is negative the Employer will reimburse the employee for the cost of the split sample test.