Collected Network Policies and Assessment

1. Examples of inappropriate use include sending unsolicited email to large numbers of people to promote products or services, and engaging in unauthorized peer-to-peer file sharing. policy source

2. The use of peer-to-peer file sharing applications on Campbell University computing resources is strictly prohibited. policy source

3. Use of peer-to-peer file sharing software through which files are made available to other users, are prohibited unless authorized by the IS&T Department. policy source

4. Examples of inappropriate use include engaging in unauthorized peer-to-peer file sharing, participating in bandwidth-consuming activities that are not academic or instructional in nature;or sending marketing or spam email messages that are not consistent with the University’s mission. policy source

5. Do not install or use Peer-to-Peer file sharing software; policy source

6. BitTorrent software (or other file sharing software) used to download and share movies, music, and other copyrighted media is strictly forbidden unless it is used for Rowan business or academic purposes. policy source

7. While peer-to-peer (P2P) file-sharing utilities (e.g., BitTorrent) are not illegal and are not banned by the University, it is illegal to download or share copyrighted material that has not been approved for such distribution and such downloading of copyrighted material is a violation of this and other University policies. policy source

8. Users must not tie up the University Network with game playing or personal uses, or use hardware or software that results in overloading the University Network or outside Internet resources or services, by sending numerous Internet transactions, establishing numerous Internet connections or by any other method. This includes, without limitation, any peer-to-peer system such as bit-torrent or similar programs. policy source

9. At no time is it acceptable to load or use peer-to-peer file sharing applications for the purpose of downloading music, video, or any other copyrighted media type. policy source

10. The use of campus computer resources, including ResNet, to share or distribute copyrighted material to others without the permission of the copyright holder is prohibited. This includes, but is not limited to, using peer-to-peer applications to share these files. policy source

11. Peer to peer recreational use affecting the university’s primary instructional mission or impeding office operations is unacceptable. policy source

12. P2P File sharing software such as limeware, Imesh and alike is Strictly Prohibited by Oakwood University. policy source

13. Computers found to be distributing copyrighted materials, or accessing peer-to-peer networks will result in, but not limited to, a 60-minute ban from the network. policy source

14. Violations include, but are not limited to: Use of peer-to-peer software illegally to transfer or share material. policy source

15. Use of P2P file sharing software may result in loss of network and Internet privileges. policy source

16. P2P applications are not allowed on the University of Memphis network. policy source

17. The use of P2P file sharing applications on the AUM network without the prior authorization of the CIO is strictly prohibited. policy source

18. Peer-to-Peer applications are restricted on the HMS network, the HMS wireless network and the HMS VPN. policy source

19. Peer-to-Peer (P2P) file sharing of copyrighted material is prohibited on the campus network at the University of Nevada, Reno. Use of P2P software is discouraged and may be throttled or blocked if it becomes detrimental to the proper functioning of the network. policy source

20. Peer-to-Peer (P2P) networking and file sharing is not allowed on the Saint Leo University network or systems under any circumstances. policy source

21. The following activities are strictly prohibited: Port scanning or security scanning unless these duties are within the scope of an employee’s normal job responsibilities and with proper authorization. policy source

22. CIS will take action to contain devices that exhibit the behaviors indicated below, and allow normal traffic and central services to resume: exhibiting a pattern of malicious network traffic associated with scanning or attacking others, exhibiting behavior consistent with host compromise. policy source

23. Port scanning or security scanning is prohibited without prior ITS approval. policy source

24. Examples of misuse include, but are not limited to, the following: Attempting to monitor or tamper with another entity’s electronic communications, including scans and probes of the residences and other networks. policy source

25. The unauthorized scanning of the Drexel Network is also prohibited. policy source

26. Students should not attempt to exploit, test, or probe for suspected security holes on Harvard computers or networks, but instead should report them to HUIT. policy source

27. Students may not scan the Harvard network or computers that they do not own or officially administer. policy source

28. Specific Prohibitions on Use of Information Systems: Probe by any means the security mechanisms of any resource on the Liberty network, or on any other network through a connection to the Liberty network. policy source

29. In addition to all of the requirements of this Policy, it is specifically prohibited to use Northeastern University information systems to: Probe by any means the security mechanisms of any resource on the Northeastern network, or on any other network through a connection to the Northeastern network. policy source

30. Inappropriate or malicious use of IT systems includes: Conducting any port scanning, network sniffing, packet capturing, security scanning, vulnerability scanning, or any other type of network monitoring without approval. policy source

31. Port scanning or security scanning is expressly prohibited unless prior notification to InfoSec (Information Security) is made. policy source

32. For example, SHSU users must not run password cracking programs, packet sniffers, or port scanners or any other non-approved programs on SHSU information technology services. policy source

33. Examples of unlawful acts, system or network security violations include but are not limited to the following: any attempt to probe, damage, scan or test the vulnerability of a system or network or to breach security or authentication measures without express authorization of the owner of the system or network. policy source

34. "RezNet" users are prohibited from probing or data collection on "RezNet". policy source

35. Users are not permitted to conduct unauthorized scanning of University information technology resources. policy source

36. The following activities and behaviors are prohibited: Unauthorized scanning of networks for security vulnerabilities. policy source

37. Examples of system or network security violations include, without limitation, the following: unauthorized access to or use of data, systems, or networks, including any attempt to probe, scan, or test the vulnerability of a system or network or to breach or circumvent the security or authentication measures without express authorization of the owner of the system or network. policy source

38. The following uses are prohibited: Network scanning, probing or sniffing. policy source

39. Some examples of policy violations: Probing and/or exploiting security holes in other systems either on or off campus. policy source

40. Scanning machines on the Internet and on the network for security vulnerabilities by "port scanning" and other means is not allowed. policy source

41. Scanning for computers on any network using port scanners or network probing software including packet sniffers, is prohibited. policy source

42. Unacceptable activities include, but are not limited to: Probing, scanning or other activities done to learn about devices connected to the University’s network, whether such activity is innocent or malicious in nature. policy source

43. Unacceptable uses that are prohibited include, but are not limited to the following: Unauthorized scanning of networks or computers for security vulnerabilities. policy source

44. Port scanning or security scanning is expressly prohibited unless prior notification to Information Technology Security is made. policy source

45. Unauthorized access to University networking equipment (firewalls, routers, switches, etc.) is prohibited. This includes port scanning or connection attempts using applications such as SSH/SNMP, or otherwise attempting to interact with University network equipment. policy source

46. Because port scanning creates substantial risk of interference with network operations, it goes against the CWRU Acceptable Use Policy (AUP), and is specified as a Banned Protocol. policy source

47. Using port scanners or using network probing software, including packet-sniffing software, is strictly prohibited. policy source

48. Examples of activity that is prohibited by this policy include, but are not limited to: running port scanning software, packet sniffers. policy source

49. Port scanning or sniffing, exploitation of security holes, execution of hacking tools or use of another person's user and password credentials are all grounds for termination of access and may result in disciplinary action and/or civil penalties and/or criminal charges. policy source

50. Users may not attempt to gain unauthorized access to other systems, networks and services external to the University via the University’s Internet or other network connections. policy source

51. Please note that unauthorized scanning to or from Caltech systems is not permitted. It is a violation of our acceptable use policy. policy source

52. Port scanning has legitimate uses in managing networks, but unauthorized port scanning is strictly prohibited. policy source

53. Port scanning or security scanning is expressly prohibited unless prior notification to the Queens IT Services Department is made. policy source

54. Port scanning and/or other network scanning is prohibited. policy source

55. Port scanning or security scanning is expressly prohibited unless prior approval is obtained from the Campus Information Technology Services office. policy source

56. The following activities are strictly prohibited, with no exceptions: For purposes of this section, "disruption" includes, but is not limited to, network sniffing, pinged floods, packet spoofing, denial of service, and forged routing information. policy source

57. The use of TCP or UDP port scanners to scan remote networks without the express written consent of the network administrator is prohibited. policy source

58. The user may not use the University's network and/or systems to: Perform any of the following: port scanning, security scanning, network sniffing, keystroke logging. policy source

59. Users must not: Use a port scanning tool targeting either Anderson University's network or any other external network, unless this activity is a part of the user's normal job functions. policy source

60. Port scanning or security scanning is expressly prohibited, unless this activity is a part of the employee's normal job/duty. policy source

61. The use of port scanning or network administration software by anyone other than authorized network administrators is prohibited. policy source

62. Port scanning, security scanning, or vulnerability testing is expressly prohibited unless prior notification to Linfield University ITS is made and approved. policy source

63. Running a network analysis or testing tool (e.g., port scanning software) is prohibited unless cleared in advance by IT staff. policy source

64. The following activities are strictly prohibited on university information technology facilities: Port scanning or vulnerability scanning. policy source

65. For example, users must not run password cracking programs, packet sniffers, port scanners, or any other non-approved programs on Texas Tech University Information Resources. policy source

66. The following activities are strictly prohibited, with no exceptions: Executing any form of network monitoring which will intercept data not intended for the employee's host, unless this activity is a part of the employee's normal job/duty and with proper authorization. policy source

67. The following are examples of misuse of computing resources: Tampering with the university computer network or building wiring or installing any type of electronic equipment or software that could be used to capture or change information intended for someone else. policy source

68. Executing any form of network monitoring which will intercept data not intended for the student or employee is forbidden. policy source

69. The use of packet sniffers, password capture applications, keystroke loggers and any other tools that perform such similar behavior or any form of network wiretapping on Computing Resources is prohibited. policy source

70. Attempts to monitor, analyze, or tamper with network data packets that are not explicitly addressed to your computer are prohibited. policy source

71. Examples of prohibited uses include, but are not limited to, the following: Monitoring or attempting to monitor another user's data communications. policy source

72. Don't try to intercept or otherwise monitor any network communications not explicitly intended for you. These include logins, e-mail, user-to-user dialog, and any other network traffic not explicitly intended for you. policy source

73. Users may not attempt to intercept, monitor, forge, alter or disrupt another user’s communications or information. policy source

74. The following activities are strictly prohibited: Executing any form of network monitoring which will intercept data not intended for the student or employee's host, unless this activity is a part of the employee's normal job/duty. policy source

75. Users of Pepperdine University computer and network resources must not: Hinder, monitor or intercept another user's network traffic. policy source

76. Examples of unlawful acts, system or network security violations include but are not limited to the following: Unauthorized monitoring of data or traffic on any network or system without express authorization of the owner of the system or network. policy source

77. Inappropriate Access of User Information: Intercepting or monitoring, or attempting to intercept or monitor, network communications or other communications not intended for that user's access without prior authorization. policy source

78. Uses that interfere with the proper functioning of the University's information technology resources are prohibited. Such inappropriate uses would include but are not limited to insertions of viruses into computer systems, tapping a network or running a "sniffer" program. policy source

79. Users WILL NOT Eavesdrop on or intercept other Users’ transmissions. policy source

80. Examples of violations include, but are not limited to: intercepting, monitoring, or retrieving any network communication without authorization. policy source

81. Unacceptable uses include, but are not limited to: Disruption to or performing unauthorized monitoring of electronic communications. policy source

82. The following activities and behaviors are prohibited: The interception or attempted interception of communications by parties not explicitly intended to receive them. policy source

83. Examples of system or network security violations include, without limitation, the following: Unauthorized monitoring of data or traffic on any network or system without express authorization of the owner of the system or network. policy source

84. Unacceptable uses include, but are not limited to, the following: Intercepting or altering network packets. policy source

85. The unauthorized use of IAS's information technology resources is prohibited and, in some cases, may be a violation of a local, state, federal or international laws and regulations. Inappropriate use of IAS's information technology resources includes, but is not limited to, the following: Using network sniffer applications on IAS's computer network. policy source

86. Unacceptable activities include, but are not limited to: Packet and content sniffing. policy source

87. Users may not run sniffers or any other software or hardware designed to intercept packets or to disrupt the security or operation of the campus network. policy source

88. Network administration tools are not allowed without the consent of ITS. This includes, but is not limited to: Network monitors, Sniffers. policy source

89. Some activities deemed inappropriate include, but are not limited to: Engaging in network packet sniffing or snooping. policy source

90. The following list, while not exhaustive, contains examples of what TCU deems to be improper use: Attempts to monitor, analyze, or tamper with network data packets. policy source

91. The University Network must not be deliberately used by a User for activities having, or likely to have, any of the following characteristics: denying access to the University Network and its services to other users. policy source

92. CIS will take action to contain devices that exhibit the behaviors indicated below, and allow normal traffic and central services to resume: exhibiting a pattern of network traffic that disrupts centrally provided services. policy source

93. Users must not intentionally disrupt the campus electronic communication systems or obstruct the work of other users by interfering with the accounts of others or knowingly consuming inordinately large amounts of system resources or in any other way. policy source

94. Users are prohibited from accessing or using IT Resources to: Engage in wasteful use of IT Resources or which unfairly monopolizes them to the exclusion of others. policy source

95. Any use of the GSU network that consumes so many resources as to noticeably degrade services to others will be reviewed by the administrator of the department where the problem is occurring and Information Technology Services (ITS). policy source

96. No individual or group may degrade or attempt to degrade the performance of ISU Information Technology Resources and Systems. policy source

97. Users may not use information systems irresponsibly, wastefully, or in a manner that adversely affects the work or equipment of others at Northeastern or on the Internet. policy source

98. In order to allow normal traffic and central services to resume, IT will take action to contain devices that exhibit the behaviors indicated below: exhibiting a pattern of network traffic that disrupts centrally provided services. policy source

99. Any networked devices or services that are detected and verified to degrade the quality of service on the network will result in termination of network service of that device until the cause of the problem is corrected. policy source

100. Activities that interfere with the operation of the network are prohibited. These include but are not limited to the propagation of computer worms, network sweeps, network probing, viruses or Trojan horses. policy source

101. Under no circumstances may faculty, students, staff, or others use University information technology in ways that are illegal, that threaten the University's tax-exempt or other status, or that interfere with reasonable use by other members of the University community. policy source

102. Students wishing to configure their machines as servers, have fixed IP addresses, or run other operating system software than the conventional Microsoft Windows or Macintosh network client systems must first consult with ITS staff. Incorrectly configured machines can cause serious disruptions of the campus network. policy source

103. A client machine may also be disconnected if the client's activity adversely affects the network's performance or is considered a security risk to protected data or the College. policy source

104. Residents shall not use ResNet in a manner that intentionally or negligently disrupts normal network use and service. Such disruption includes, but is not limited to, intentionally or negligently propagating computer viruses, sending offensive messages, knowingly causing system crashes, denying reasonable use of UNLV Housing and Residential Life network and computer resources to others, violating others’ personal privacy, and accessing without the proper authority protected and/or private network resources. policy source

105. "RezNet" users are prohibited from provisioning network services on their privately owned computers, including but not limited to HTTP, Peer-to-peer apps, Chat, DHCP, DNS, FTP, IRC, NNTP, POP3, SMTP, Telnet, WINS, etc. policy source

106. You are not allowed to offer alternate methods of access to UF’s IT resources, including by means such as modems and virtual private networks (VPNs) or network infrastructure services such as Domain Name System (DNS) and Dynamic Host Control Protocol (DHCP). policy source

107. Using the university network to provide any service that is visible off campus without prior UNIT approval, is prohibited. This applies to services such as, but not limited to, HTTP (Web), SSH, FTP, IRC, email, private VPN, etc. policy source

108. Using the university network to provide any service that is visible off campus is prohibited. This applies to services such as, but not limited to, HTTP (Web), FTP, IRC, peer-to-peer (p2p) multimedia sharing, game servers and email. policy source

109. Baylor University does not allow network users to run unauthorized SMTP, DHCP, DNS, or directory services on any networks. policy source

110. Establishing a server or providing a service that over-utilizes the shared bandwidth is prohibited. FTP, Web servers, e-mail servers, and Peer-to-peer are examples of server programs. policy source

111. Devices connecting to the University’s data network must use the central Dynamic Host Control Protocol server. policy source

112. Devices connecting to the University’s data network must use the central Domain Name Service (DNS). policy source

113. Also, providing server services for DHCP/BOOTP, NAT, NTP, FTP, IRC and NFS is prohibited. policy source

114. In no case shall the following types of servers (except those maintained by CIT for the express purposes delineated) be connected to the network: DNS, DHCP, BOOTP, or any other server that manages network addresses. policy source

115. To ensure network stability and security, it is prohibited for any user or IT support person to run a local DHCP server (on a computer, printer, etc.) Devices that are (mis)configured to distribute IP address will be blocked from the network. policy source

116. All machines connected to the university network must be registered with an ACCC operated or approved domain name server. Machines found connected that are not properly registered will be considered security threats and will have their network access blocked. policy source

117. UNLV Housing and Residential Life network connections are provided for client use only. Servers are not permitted. Servers include any device that offers services over the network or that allows incoming network connections. policy source

118. The following examples of types of devices would require approval: Services that answer broadcast messages, such as DHCP and BOOTP. policy source

119. Unacceptable Activities: Running unauthorized servers or daemons, i.e., SMTP, DNS, DHCP, etc., on the network. policy source

120. Non-university owned and operated FTP servers are not permitted. policy source

121. All services on the firewalls that are not needed will be disabled, including other network access, user shells and applications. policy source

122. All IllinoisNet traffic shall be identifiable as to its source and anonymous traffic is disallowed for security reasons. policy source

123. All UMSL network traffic to and from the Internet must go through the firewall. Any network traffic going around the firewall must be accounted for and explicitly allowed by the Computer Security Incident Response Team (CSIRT). policy source

124. Inbound Internet traffic will only be allowed using protocols, addresses and ports approved by DoIT. Other inbound traffic will be blocked at the network perimeter. policy source

125. Systems must be protected by a firewall which allows only those incoming connections necessary to fulfill the business requirements of that system. policy source

126. Perimeter Firewalls will allow access to the following for outbound and inbound network traffic: Outbound: Allow ALL network traffic to hosts and services outside of the perimeter. Inbound: Only secure applications and specific services which support the Georgia Southern University mission will be allowed access from the perimeter. All in-bound real-time external connections to University internal data center networks must pass through a firewall. policy source

127. The perimeter firewall permits the following outbound and inbound network traffic: Outbound – Allow all internet traffic to hosts and services outside of the campus with the exception of known security vulnerabilities, servers that generate email messages with a non-campus destination, or other exceptions. Inbound – Users may only access defined services that support the university mission. policy source

128. All external and wireless connections to University networks must pass through a network firewall. In addition, all network connections entering a high security network must pass through a network firewall. Any change to an external connection or to the configuration of the firewall must be adequately tested and documented according to the ITS Network Firewall Standard. policy source

129. The University’s perimeter firewall permits the following outbound and inbound Internet traffic: Outbound – All internet traffic to hosts and services outside of Millersville University’s networks except those specifically identified and blocked as malicious sites. Inbound – Internet traffic that supports the mission of the University and is in accordance with defined policies. policy source

130. The following type of network traffic should always be blocked: Inbound traffic from a non-authenticated source system with a destination address of the firewall system itself. Inbound or Outbound network traffic containing a source or destination address of 127.0.0.1 (localhost). Inbound or Outbound network traffic containing a source or destination address of 0.0.0.0. Inbound traffic containing IP Source Routing information. policy source

131. CIS will take action to contain devices that exhibit the behaviors indicated below, and allow normal traffic and central services to resume: imposing an exceptional load on a campus service. policy source

132. Information Services operates and maintains computers, network systems and servers, and is expected to maintain an acceptable level of performance and must assure that frivolous, excessive, or inappropriate use of the resources by one person or a few people does not degrade performance for others. policy source

133. Behaviors that inhibit or have the potential to inhibit the ability of others to utilize shared computing resources are considered policy violations. Such behaviors include but are not limited to: Exceeding limits for resource usage (e.g. disk space, bandwidth, CPU time). policy source

134. Copying or transmitting excessive amounts of data is forbidden. policy source

135. Excessive or sustained bandwidth consumption may burden the network and such usage may be restricted. policy source

136. The following activities are prohibited without the expressed written consent of Fordham IT: Using traffic-intensive applications that may cause problems within the network or diluting the level of service to other users. policy source

137. Applications that require large amounts of bandwidth, or are sensitive to changes in signal quality and strength may not be appropriate for wireless access. policy source

138. Providing services or running applications that consume excessive bandwidth or impede others' use of the Harvard network is prohibited without authorization. policy source

139. Extensive use of new applications that require very large amounts of bandwidth on the campus backbone must be discussed with Technology Services beforehand, so that appropriate planning can take place. policy source

140. Large-scale distribution of digital files can cause excessive network loading. The University reserves the right to automatically manage and restrict excessive use of network bandwidth. policy source

141. Examples of inappropriate use include participating in bandwidth-consuming activities that are not academic or instructional in nature. policy source

142. Any person operating a network-intensive application or a defective computer that overloads University networks will be notified and steps will be taken to protect the overall University network. policy source

143. Excessive or improper use of network resources that inhibits or interferes with use by others is prohibited and will be cause for action by CIT, which may include restricting, limiting, or disabling network access. policy source

144. Excessive use of network resources which inhibits or interferes with the use of the network by others is not permitted. policy source

145. In making acceptable use of resources, individuals covered by this policy must not: Waste shared computing or network resources, for example, by intentionally placing a program in an endless loop, printing excessive amounts of paper, or by sending chain letters or unsolicited mass mailings. policy source

146. Although there is no set bandwidth, disk space, CPU time, or other limit applicable to all uses of university computing resources, the university may require users of those resources to limit or refrain from specific uses in accordance with this standard. policy source

147. Prohibited Uses of University Computer Resources: Unauthorized use (for example, modifying the network) or excessive personal use (for example, use that overburdens a network, results in substantial use of system capacity, or otherwise subjects the institution to increased costs or risks). policy source

148. Examples of inappropriate uses of Seton Hall University computer facilities include, but are not limited to: Activities that damage or disrupt hardware or communications, such as irresponsible or destructive use of equipment, the use of unauthorized network equipment, including the use of wireless equipment that operates above the 900-Megahertz range, virus creation and propagation, wasting system resources and overloading networks with excessive data. policy source

149. All users of University computing resources must: Respect the limited capacity of the University's computer resources, and limit use so as not to consume an unreasonable amount of those resources or to interfere unreasonably with the activity of other users. policy source

150. You agree not to obstruct any others' work by using unnecessarily large amounts of network resources (such as bandwidth and storage space) or deliberately act in a manner that will cause harm to the network. policy source

151. Any deliberate wasteful use of resources is irresponsible; it encroaches on other’s use of facilities and deprives them of resources. Printing of large unnecessary listing and the playing of games solely for entertainment are examples of such abuse. policy source

152. Avoid excessive personal use. Some uses will be plainly excessive in all environments, but the extent to which other uses become excessive may vary. policy source

153. Examples of specific violations include, but are not limited to: Excessive use of information technology resources, especially when it impedes the mission-related activities of other users, or adversely affects system availability or performance; policy source

154. Excessive use of the network is prohibited and subject to restrictions. Excessive use is defined as using an amount of network resources that inhibits other people's computers from being able to use the network. policy source

155. Users are not permitted to: Engage in excessive use of system information technology, including but not limited to network capacity. policy source

156. Prohibited Uses of University Computer Resources: Unauthorized or excessive personal use. Use may be excessive if it overburdens a network, results in substantial use of system capacity, or otherwise subjects the institution to increased costs or risks. policy source

157. Users WILL NOT Use without authorization any device or application that consumes a disproportionate amount of network bandwidth. policy source

158. We ask that you be careful how you use computing resources, especially shared finite resources (e.g., dial-in modem time, disk space, or Internet bandwidth), where selfish behavior on the part of a few can prevent many others from doing their work. policy source

159. You will not generate excessive network traffic in so much that it interferes with another user's ability to utilize the network. policy source

160. If your bandwidth usage is excessive to the point of causing network degradation, your Internet connection may be temporarily disabled while we work with you to investigate the cause of the problem. policy source

161. Generating excessive network traffic, including spamming, certain file-sharing applications and denial-of-service, is prohibited. policy source

162. Colby College ITS policies prohibit disruptive or abusive behavior on the network, which includes but is not limited to such actions as: Interfering or tampering with network or computer operation on the network, such as misconfiguration and oversubscription of services or bandwidth policy source

163. The running of programs, services, systems, processes or servers by a single user, or group of users, that may substantially degrade network performance or accessibility will not be allowed. policy source

164. Providing services or running applications which consume excessive bandwidth on the HMS Network without authorization is prohibited. policy source

165. Computing equipment found to be generating unacceptable amounts of traffic, emitting protocol fragments with an intent to deny services to other network users, or generate substantially sequential access to a range of ports or network addresses shall be automatically disconnected from the network. policy source

166. If high bandwidth applications for recreational use of our network are identified, they will be restricted or blocked. policy source

167. Due to potential jamming and interference issues, critical systems must not be attached to the wireless network. policy source

168. In order to allow normal traffic and central services to resume, IT will take action to contain devices that exhibit the behaviors indicated below: imposing an exceptional load on a campus service. policy source

169. Activities considered to be in conflict with this policy include, but are not limited to, the following: Overloading computers or networks with excessive data. policy source

170. User should not engage in activities that consume excessive amounts of network bandwidth. policy source

171. Using a computer connected to the Student ResNet to provide services that result in large amounts of inbound/outbound traffic is prohibited. policy source

172. The following are examples of activities that do result in high bandwidth use and should be limited or eliminated: Computers that act as Web servers and distribute large data files, usually video, music and games. policy source

173. The following examples of types of devices would require approval: High bandwidth devices (averaging more than 1 GB/day for a week). policy source

174. Unacceptable Activities: Unreasonably slowing down the University Computer Systems or Computer Networks through the excessive use of system resources (network bandwidth, disk space, CPU time, and printer queues). policy source

175. Users shall not use applications that utilize an unusually high portion of the network bandwidth. policy source

176. Examples of misuse include, but are not limited to, the following: Using an unauthorized IP address or statically assigned address without approval. policy source

177. Only officially assigned Internet Protocol (IP) numbers may be used for equipment connected to the University's data network. policy source

178. Using a network address other than the one assigned by HUIT is prohibited. policy source

179. Examples of unacceptable use: Assigning of addresses not specifically granted by IT. policy source

180. Using other than the assigned IP address can disrupt normal network operation for others, so users and owners of such devices are expected to refrain from supplying some other IP address for use in any network transaction. policy source

181. The following are violations that will result in suspension of network access and disciplinary action: Any attempt to bypass the DHCP system or use any IP address that has not been assigned by the DHCP server. policy source

182. It is required that you use DHCP for IP address assignment. You will not use any IP address except that which has been automatically assigned to you via DHCP. policy source

183. The following uses are prohibited: Using unauthorized IP addresses. policy source

184. Some examples of policy violations: Using unauthorized IP addresses. policy source

185. The residential network is a shared resource. Thus, network use or applications which inhibit or interfere with the use of the network by others are not permitted. (For example, using an IP address not registered to you, or applications which use an unusually high portion of the bandwidth for extended periods of time, thus inhibiting the use of the network by others, are not permitted). policy source

186. All Network enabled devices connected to the University Network (other than Network enabled devices connected to the CUIMC Network) must use (a) the DHCP to configure Network IP addresses and (b) the DNS protocol for Server information. policy source

187. Alterations of any kind to the assigned IP address or related settings, including using an unauthorized IP address, is prohibited. policy source

188. Using a network address other than the one assigned by HMS IT is prohibited. policy source

189. Users may not, under any circumstances, arbitrarily assign a University IP address (130.68.x.x) or domain name (*.montclair.edu) to a device without prior authorization from IT. policy source

190. You may not configure your computer with any address other than one provided by Oakwood University. policy source

191. "Borrowing" an IP address (or a network connection) from one system to be used on another is prohibited. policy source

192. All IP addresses used on the University of Florida network must be registered with Infrastructure and Communication Technology (ICT). policy source

193. By default, IP addresses are automatically assigned by Dynamic Host Configuration Protocol (DHCP). The use of a hard-coded or non-approved IP address is prohibited. policy source

194. Every network interface configured with one or more IPv4 addresses, including addresses from the non-globally routable ranges, must have corresponding entries for all of these IPv4 addresses in the Assignments database. policy source

195. Network-connected devices that have static IP configurations must not use IP addresses already registered in the Assignments database for other devices. policy source

196. IP addresses registered in the Assignments database for IP address assignment via DHCP must not be used as part of a static configuration by any device. policy source

197. The following list, while not exhaustive, contains examples of what TCU deems to be improper use: Manually assigning an IP address to a network device or otherwise using an IP address that is not assigned to you. policy source

198. System users must not use any other network address (e.g., IP address) for a Computer or Network Resource than has been properly assigned by an authorized system or network administrator. policy source

199. Only authorised users of the University computer systems are entitled to use bath hostnames and IP addresses on the network. policy source

200. IP addresses shall not be assigned from within the University of Michigan IP address space for individuals or organizations who are not directly affiliated with the University of Michigan. policy source

201. The University does not support the use of personal wireless printers on the campus network. policy source

202. Any wireless device that is found to interfere with the proper operation of Chapman's wireless network is prohibited. This can include some portable telephones that operate in the 2.4 GHz or 5 GHz frequency bands. policy source

203. Examples of misuse include, but are not limited to, the following: Hosting or operating a wireless access point that is connected to the University’s network in your unit or common area of your residence. policy source

204. Due to the security risks posed to the network by these devices, students are not permitted to connect wireless printers to the Harvard network. policy source

205. Examples of prohibited uses include, but are not limited to, the following: Installing unauthorized wireless access points. policy source

206. The following uses of LLS IT Facilities are prohibited: Attaching wireless access points to the network. policy source

207. Wireless access points may not be installed by individuals in campus academic, administrative, or service buildings, including buildings rented or owned by the University off campus, without authorization from the responsible department. policy source

208. You must not use Rhodes computing and/or network resources in conjunction with the execution of programs, software, processes, or automated transaction-based commands that are intended to disrupt (or that could reasonably be expected to disrupt) other computer or network users, or damage or degrade performance, software or hardware components of a system. This includes attempts to set up wireless connectivity within research laboratories in order to avoid process of requesting and budgeting for network points. policy source

209. The following are violations that will result in suspension of network access and disciplinary action: Unapproved attachment of wireless access points in Texas A&M residence halls. policy source

210. Unauthorized Wireless Access Points (APs not installed, maintained and managed by the UIT Division) are prohibited at WWU. policy source

211. Operation and use of private networks not explicitly authorized by Information Services include, but not limited to, the use of independent wireless access points, peer-to-peer networks, use of client devices as private servers, etc. and are prohibited. policy source

212. Wireless access points which are built into purchased equipment will be disabled before such equipment may be used within range of the College’s wireless network. policy source

213. Users are not permitted to set up or operate their own wireless systems on the Oakwood University campus. policy source

214. You may not modify, extend, or bridge your network connection. Use of personal wireless routers are not permitted in residence halls. policy source

215. Do not purchase or install your own access. It is also prohibited to use "Internet Connection Sharing" software to make a computer behave like a wireless access point. policy source

216. All wireless access points must be registered and pre-approved by OTS before being placed into service. policy source

217. All wireless access points must be secured from unauthorized use. Appropriate forms of authentication and authorization will vary depending on the wireless medium. policy source

218. For example, using a wireless access point, wireless repeater, or a very long cable to provide network connectivity to an adjacent building, another floor, or another room is not acceptable. policy source

219. Use of external modems or wireless access points are not permitted to connect to the Saint Leo University network unless approved by UTS. policy source

220. The addition of new wireless access points on the University network must be coordinated and approved by ITS. policy source

221. Prohibited uses include, but are not limited to, development of programs, data processing or computations for commercial use, preparation and presentation of advertising material and the running of a Server connected to the University Network. policy source

222. The student may not set up a server without authorization of the university. policy source

223. The hosting of web servers or other Internet services which perform commercial activity is also prohibited. policy source

224. The following activities are prohibited without the expressed written consent of Fordham IT: Setting up any type of information server such as web, email, game, print, FTP, etc. policy source

225. It is prohibited to create secondary physical networks, using devices including bridges, routers, or wireless access points, connected to the Harvard network without authorization. policy source

226. Examples of unaccetable use: The operation of any non-educational server or service offering or transferring data in a public manner onto the Internet. This includes but is not limited to HTTP, FTP, mail/news, programs such as Gnutella or Napster (in server modes), etc. policy source

227. Personal, private or departmental switches, routers, wireless access points or DHCP-serving devices may not be connected to centrally-managed administrative network segments, except only as may be agreed to in writing between the device owner and Information Technology Services. policy source

228. The following uses of LLS IT Facilities are prohibited: Setting up or maintaining private servers on campus without explicit written permission from ITD. policy source

229. Users are prohibited from installing or using network devices that are not owned by MSMU. This includes personal wireless access points, servers, hubs, switches, or any other networking equipment. policy source

230. Connection of personal or privately-owned routers and/or wireless access points to the ResNet wired networks is prohibited. policy source

231. Users may not connect to remote resources such as printer, file systems, or any other remote resource, regardless of location on or off the Northeastern network, unless the administrator of the remote resource has first granted permission to do so. policy source

232. In no case shall the following types of servers be connected to the network: DNS, DHCP, BOOTP, or any other server that manages network addresses. policy source

233. Users are prohibited from installing personal routers (wired or wireless) to the network. policy source

234. Prohibited in all halls are portable heaters, air conditioners, large amplifiers (public address system, oversize stereo, acoustic or electric musical instrument and percussion instruments), wireless routers, and halogen/lava lamps. policy source

235. The following activities are strictly prohibited： Introducing honeypots, honeynets, or similar technology on Park University network. policy source

236. You may not operate Dynamic Host Configuration Protocol (DHCP) or Bootstrap Protocol (BootP) servers on the campus networks without authorization. policy source

237. List of Prohibited Network Devices: routers, wireless access points, proxy servers, DSL, modems, gateways or hardware firewalls (software firewalls are allowed). policy source

238. Game station systems are permitted but must be registered. Such devices are prohibited from acting as a network routing device or network server for any purpose. policy source

239. Personally owned servers and other devices are only permitted if they utilize a reasonably small portion of network resources. policy source

240. Users WILL NOT Connect devices (such as switches, routers, hubs, computer systems, and wireless access points) to the network without prior approval from the Campus IT organization. policy source

241. Servers (FTP, WWW, IRC, etc) are not permitted on the USF open-use network. policy source

242. The use of personal routers (wireless or wired) and/or DHCP servers outside of a contained lab environment is strictly prohibited. policy source

243. The use of personal routers (wireless or wired) and/or DHCP servers is strictly prohibited. policy source

244. No units and users may: Connect personal network switches, routers, or wireless access points to the network except where authorized by the Office of Information Technology policy source

245. Unauthorized networking equipment (such as routers and wireless access points, etc.) is prohibited from use on the network. Network services and wiring may not be modified or extended beyond their intended use policy source

246. Users are not prevented from setting up their own computers as servers. However, a service which is inappropriate or degrades network availability will be shut down. Further, the server's owner is responsible for all content. policy source

247. This abuse includes, but is not limited to, the following: Unauthorized Servers: The establishment of a background process that services incoming requests from anonymous users for purposes of gaming, chatting or browsing the Web is prohibited. policy source

248. The establishment of unauthorized servers is prohibited, such as, but not limited to, a background process that services incoming requests from anonymous users for purposes of gaming, chatting, or browsing the Web. policy source

249. Users are prohibited from connecting to any device such as a hub, router, switch, or wireless access point to the provided Ethernet jacks in the room to extend connectivity. For example, a user may not use a hub in their room or office to allow them to connect more than two devices to the network at a time. policy source

250. Users may not advertise routing information on the HMS Network or act as gateways to external or private networks. policy source

251. Only Information Technology Services (ITS), Health Information and Technology, or their authorized designees may: attach networking equipment (including, but not limited to: routers, switches, wireless access points, Dynamic Host Configuration Protocol/Domain Name System servers, etc.) to the University network or modify University network infrastructure. policy source

252. The use of network hubs, routers, wireless access points, or other devices designed to share your network connection with multiple computers or devices is expressly prohibited. policy source

253. Network fan-out devices, such as “hubs,” or “switches” to allow students to connect more than one computer/device to a single network jack, are prohibited without permission from ITS. policy source

254. Hubs, switches, routers and wireless devices should never be connected to the University data network without prior approval from Network and Communication Services. policy source

255. You may not connect any device that provides network-to-network connection services. Some examples are: Hubs Switches Routers Bridges Firewalls Virtual Private Networks (VPNs) Wireless access points Wireless access points are put into the same category as hubs or bridges. Therefore they must not be connected to the University's campus network without prior consultation and approval from Information Technology. policy source

256. You must not connect any devices such as switches, hubs, wireless access points, routers, Xbox or any other game oriented device to the network without the express written permission of the Oakwood University. policy source

257. No user can connect servers of any type, hubs, or network printers. policy source

258. It is against TDS policy for a user or IT support person to connect a network connectivity device (hub, switch, router or wireless access point) to "share" a single jack among multiple computers* policy source

259. Users may not extend or modify the network in any way by installing devices such as repeaters, bridges, switches, routers, gateways, wireless access points, or permanent hubs. policy source

260. Network users may not attempt to defeat or circumvent any network specification. Examples of this are extending the network with unauthorized switch/router/firewall and the use of non-standard electronics and wiring. policy source

261. Users who add unapproved network devices may have their network access disabled in order to ensure that the device does not inhibit the proper function of the network at large. policy source

262. The following activities are nonexclusive examples of those that are not permitted and that may lead to suspension or revocation of use privileges and other penalties or discipline: the unauthorized physical or virtual extension or re-configuration of any portion of the campus network by such means as routers (wired or wireless), wireless access points, network wiring, or other methods. policy source

263. In order to maintain reliable network connectivity, no other department may deploy wireless routers, switches, bridges, and/or DHCP (Dynamic Host Configuration Protocol) services on campus without prior review and approval of SUIT. policy source

264. Some activities deemed inappropriate include, but are not limited to: Attaching unauthorized network devices, including but not limited to wireless routers, gateways DHCP or DNS servers; or a computer set up to act like such a device. policy source

265. The following list, while not exhaustive, contains examples of what TCU deems to be improper use: Using unauthorized network devices, such as routers, firewalls, and wireless access points. policy source

266. Network hubs, switches, routers and Wi-Fi access points may not be connected to office and lab network jacks, unless approved by OTS. When these devices are detected attached to a network jack, the jack will be deactivated remotely without warning. policy source

267. Wireless switches and routers of any kind are not permitted, even if not connected to the campus network. policy source

268. Some activities deemed inappropriate include, but are not limited to: Attaching unauthorized network devices, including but not limited to wireless routers, gateways DHCP or DNS servers. policy source

269. Hubs, switches, wireless access points, routers, and other similar network equipment that constitutes network infrastructure are not permitted. policy source

270. Due to limited network resources, the use of CAMPBELL network facilities for playing graphics-based interactive games is prohibited. policy source

271. Individual users may be required to halt or curtail non-priority use of IT resources, such as recreational activities and non-academic, non-business services. policy source

272. Non-game network traffic has priority at all times. Games that interfere with non-game traffic, even if run within network bandwidth limitations, are prohibited from the Oakwood University network policy source

273. Unacceptable Activities: Recreational game-playing and/or audio/video file sharing that interferes with instructional or work-related use of university-owned computers. policy source

274. Games that interfere with non-game traffic, even if run within network bandwidth limitations, are prohibited from the Oakwood University network. policy source

275. We recommend that you watch for secure web pages ("https", and a padlock-icon) whenever you transmit sensitive information. Instead of "telnet", consider "ssh" to log onto remote servers. policy source

276. Whenever possible, sensitive data should be transferred in encrypted form, e.g., using SSL (Secure Socket Layer) or SSH (Secure Shell). policy source

277. Any protocol or network traffic that has been shown to support an illegal process, or that supports an application posing unacceptable risk to the University, will be blocked by University firewall policy and applications using such protocols may not work properly. policy source

278. Applications which transmit sensitive information over the network in clear text, such as telnet and ftp, are prohibited and will be blocked. Exceptions must be accounted for and explicitly allowed by the CSIRT. Secure free replacements to telnet and ftp are SSH and SFTP. policy source

279. Users of telnet, rlogin, ftp, and other connectivity programs may not realize that their password and data is transmitted across the network unencrypted and can be intercepted by hackers.Use of these "clear text" protocols is therefore strongly discouraged. policy source

280. Telnet and FTP are both considered "insecure protocols" and will not be approved as firewall exceptions. policy source

281. No insecure ports, protocols or services, such as FTP, Telnet, or HTTP are to be used for communicating with the SDE without documented business justification for their use. policy source

282. The use of telnet is ordinarily unneccessary and not recommended (with possible exceptions such as connecting to legacy Departmental devices where all network traffic remains within the Department). Users should instead use ssh. policy source

283. Enterprise Network Firewalls, which are required to protect file servers and workstations in University Departments, allow secure protocols on port 22. They block ports that use insecure protocols, including ports 21 and 25. Insecure protocols include rlogin (remote login), TELNET, rcp (remote copy), and ftp (file transfer). policy source

284. All insecure protocols (protocols that provide no encryption and pass traffic in clear text) may not be allowed through the campus firewall. Example insecure services include telnet, ftp, imap, and pop. policy source

285. Disable or remove insecure services, protocols, or ports that are not necessary. Examples of insecure services, protocols, or ports include but are not limited to FTP, Telnet, POP3, IMAP, and SNMP. policy source

286. Wherever possible, security protocols including IMAPS, FTPS, HTTPS, etc. shall be used. policy source

287. Telnet: Some MFDs provide telnet management interfaces, which are also used by some older management tools. If possible, disable this insecure protocol. policy source

288. Exceptions for inherently insecure protocols such as telnet (port 23) or ftp (port 21) will not be granted. policy source

289. The Telnet service should be disabled, and marked as a manual service. policy source

290. Secure (encrypted) protocol alternatives are deployed in place of insecure protocols (i.e., ssh instead of telnet, sftp in place of ftp). policy source

291. The SFTP file transfer protocol must be used; FTP transfers are not supported. policy source

292. Clear text communications protocols for server administration shall be disabled (encrypt all non-console administrative access). policy source

293. Disable or uninstall any unneeded services. If you do not use services such as ftp, telnet, snmp, http, etc. then they should be disabled. policy source

294. This Procedure prohibits Untrusted Network access to Appalachian State University Trusted Networks via unsecured Clear Text Access mechanisms such as Telnet, FTP and regular HTTP web logins. policy source

295. Users may not use Drexel University's assigned Internet number space for their own domain without the prior express permission of IT. policy source

296. Students are not permitted to register external domain names (i.e., any domain outside of harvard.edu) that reference systems on the Harvard network without authorization. policy source

297. Unauthorized registration of a domain to a Baylor IP address is prohibited. This includes, but is not limited to, direct DNS resolution and DNS aliasing. policy source

298. The registration of commercial hostnames to a SUNY Delhi Wireless IP address is strictly prohibited. policy source

299. Users are not permitted to register external domain names (i.e., any domain outside of harvard.edu) that reference systems on the HMS Network. policy source

300. Use of hard-coded or non-approved IP number is prohibited. policy source