Campuses:
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| computing:policies:network_connection [2016/04/15 17:21] – [Required for all network-connected devices] allan | computing:policies:network_connection [2021/01/11 09:35] (current) – cse-sull0153 | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== Required for all network-connected devices ===== | ===== Required for all network-connected devices ===== | ||
| - All systems connected to the PAN network must be running an operating system which is still supported by its vendor for security updates. | - All systems connected to the PAN network must be running an operating system which is still supported by its vendor for security updates. | ||
| - | * For example, (at the time of writing) the minimum acceptable version of Windows is Windows | + | * For example, (at the time of writing) the minimum acceptable version of Windows is Windows |
| * Apple generally provide support for two concurrent OS releases, __for example__ when 10.6 is available then 10.5 is also supported but 10.4 becomes unsupported and so unacceptable by this policy. | * Apple generally provide support for two concurrent OS releases, __for example__ when 10.6 is available then 10.5 is also supported but 10.4 becomes unsupported and so unacceptable by this policy. | ||
| * The same overall requirement applies to Unix, Linux, and other systems such as embedded data acquisition devices. | * The same overall requirement applies to Unix, Linux, and other systems such as embedded data acquisition devices. | ||
| - Only one device may be connected to any physical network port. No hubs, switches, wireless access points or routing devices may be connected, directly or indirectly, without prior discussion with and agreement from School computing staff. | - Only one device may be connected to any physical network port. No hubs, switches, wireless access points or routing devices may be connected, directly or indirectly, without prior discussion with and agreement from School computing staff. | ||
| - | - Non-departmentally-managed systems may not inhabit the same network subnet as departmentally-managed systems. | + | - Non-departmentally-managed systems |
| - **Data Security** | - **Data Security** | ||
| - For any Windows or Macintosh computers which you connect to the School network: | - For any Windows or Macintosh computers which you connect to the School network: | ||
| Line 22: | Line 22: | ||
| If you cannot meet the above criteria, or do not wish to install the required antivirus software, your computer must be placed on a separate protected network segment. For example, you may have a lab data acquisition or control system, where a software update and reboot may be unacceptable. You must declare that such a system will not be used to store or process any University private data. By default, it may not receive incoming network connections, | If you cannot meet the above criteria, or do not wish to install the required antivirus software, your computer must be placed on a separate protected network segment. For example, you may have a lab data acquisition or control system, where a software update and reboot may be unacceptable. You must declare that such a system will not be used to store or process any University private data. By default, it may not receive incoming network connections, | ||
| - | * School web sites, mail services, and secure shell. | + | * Network connections are only allowed to/from University networks. |
| - | * Printing, either via the School' | + | * Printing |
| We are able to set up specific protected networks for research groups, which can have custom access controls, for example, to connect to lab data acquisition and control systems | We are able to set up specific protected networks for research groups, which can have custom access controls, for example, to connect to lab data acquisition and control systems | ||