The Medical
University of South Carolina   About MUSC  ·  Education  ·  Medical Center  ·  Research  ·  Library   

Search


Support Desk, 792-9700
   helpdesk@musc.edu

   Getting Help
   Training
   Policies
   Description of Fees
   Account Forms
   Circuit Requests

   Software Downloads
   Software Licensing Info
   Computer Connection
   Network Systems

   E-mail
   Homeroom
   LYNX
   MNA - NetID
   Macintosh Help
   Oacis
   Off-Campus Access
   SunONE Calendar
   Web Publishing

   About IS
   Info Services Home
   OCIO Home
   More IT Groups
   MUSC Home

   Webmaster

   Disclaimer









Medical University of South Carolina
Center for Computing and Information Technology
Policy and Procedure


Subject: MUSC Third Party Connection Acceptable Use Policy

Purpose:

To ensure that a secure method of connectivity is provided between the Medical University of South Carolina (MUSC) and all third party (partner) companies, and to provide guidelines for the use of network and computing resources associated with a Third Party Network as defined below.

This policy applies to all third party companies who form a partnership with MUSC which requires a partner network. This includes the employees at said company who will be performing the work over the partner connection.

Third party network connections are to be used only for the specific business purposes defined in the Information Requirements Document for each connection. Any violation of this Acceptable Use Policy may result in immediate termination of the connection/partner agreement with said parties.

Definition: A Third Party Network is any physical or logical connection between any component of MUSC's data network, and one or more computers, terminals or other network components at a third party company. Third party companies may be MUSC Partners, Vendors and Suppliers.

Associated Documents:
MUSC Partner Connection Policy
MUSC Third Party Connection Request - Information Requirements Document

Agreement:

In the text below, "user" refers to employees of the partner company who user the resources associated with the partner network.
  1. The information provided on the Information Requirements Document is correct to the best of my knowledge.
  2. Any MUSC equipment located on partner premise will only be configured for IP and will only be used for MUSC related data transfers.
  3. Configuration changes on MUSC equipment shall only be performed after notification and approval by the appropriate MUSC personnel.
  4. The password on MUSC devices located on the partner premise will be set by an MUSC network engineer and shall not be changed unless approved by the appropriate MUSC personnel.
  5. The partner company shall notify the appropriate MUSC personnel when an employee, who has access to any MUSC network resource per the partner connection, leaves the company or is transferred to another position which no longer requires access.
  6. The partner company shall assume all responsibility for protection of their private network(s) which may be interconnected via the third party connection to MUSC.
  7. Only employees of the partner company specified in the Information Requirements Document shall use the resources associated with the partner connection.
  8. The partner company shall notify the appropriate MUSC personnel whenever there is a change in the user base for the work performed over the partner network.
  9. The partner company shall notify the appropriate MUSC personnel whenever there is a change in the functional requirements of the partner network.
  10. The partner company shall notify the appropriate MUSC personnel whenever there is a change in the access method used for the partner network.
  11. The partner company shall perform a timely review of audit reports provided by MUSC, and shall promptly notify the appropriate MUSC personnel of any suspected breach or compromise of the security of the partner network.
  12. The partner company shall provide timely and adequate assistance to MUSC personnel in the investigation and resolution of any security incidents or issues relating to the partner network.

I, the undersigned, have read and understand the MUSC Third Party Connection Acceptable Use Policy, and agree to its terms.



Partner Company:

Name:

Title:

Signature:

Date:


Effective Date: September 27, 2000
Revised Date: August 2002

Approval:  Melissa S. Forinash, Controller, OCIO-IS
Author: Richard Gadsden