Guidelines: Residence Hall Technology Equipment Exceptions
1. Purpose
Provide a controlled process that allows students enrolled in academic programs requiring specialized technology or lab environments to use such technology within university housing while protecting the security, stability, and reliability of the residence hall network.
2. Eligibility
Students must demonstrate a legitimate academic, research, or university-sponsored need.
Examples:
- Course requirements
- Senior design projects
- Cybersecurity coursework
- Computer networking coursework
- Software development coursework
Personal interest, hobby projects, cryptocurrency mining, media hosting, or commercial activities are not acceptable justifications.
3. Request Process
Step 1: Student Submission
Student submits a TeamDynamix (TDX) ticket containing:
- Academic program/major
- Course number (if applicable)
- Faculty sponsor (if applicable)
- Description of device(s)
- Network requirements
- Ports/services required
- Duration of need
- Academic justification
Student must acknowledge compliance with:
- UW-System Acceptable Use Policy
- Applicable residence hall network requirements
Step 2: Initial Review
Infrastructure Services Networking Team reviews:
- Academic justification
- Technical requirements
- Network impact
- Security implications
Requests involving elevated risk are escalated to:
- Systems Engineers
- Information Security
- Infrastructure leadership
- Housing (if necessary)
Step 3: Risk Assessment
The following questions are evaluated:
Network Risk
Could the device:
- Generate excessive traffic?
- Create network loops?
- Bridge network segments?
- Interfere with campus infrastructure?
- Circumvent security monitoring?
Security Risk
Could the device:
- Expose vulnerable services?
- Allow unauthorized access?
- Be used for network reconnaissance?
- Host malicious content?
- Be used as a pivot point into university systems?
Operational Risk
Could the device:
- Disrupt residence hall services?
- Impact other residents?
- Consume excessive power, cooling, or network resources?
4. Prohibited Technologies
The following are some examples of technologies NOT permitted in residence halls:
Network Control Devices
- Routers performing campus network routing
- Layer 2 switches that can create loops
- Devices capable of spanning-tree manipulation
- Devices generating or responding to BPDUs
- Devices causing BPDU Guard violations
Wireless Equipment
- Wireless access points
- Mesh wireless systems
- Wireless bridges
Network Monitoring/Sniffing
- Packet capture application
- Passive taps
- Network monitoring systems
- Unauthorized IDS/IPS systems
- Traffic interception devices
Academic cybersecurity coursework may require special review and containment.
Addressing and Infrastructure Services
Students may not operate:
- DHCP servers
- DNS servers serving campus networks
- NTP servers
- Network authentication services
- Proxy services intended for public use
Public Internet Services
Unless specifically approved:
- Public-facing websites
- Game hosting services
- Streaming services
- File-sharing systems
- Email servers
- VPN concentrators
- Commercial hosting platforms
High-Risk Activities
- Cryptocurrency mining
- Botnets
- Vulnerability scanning of campus assets
- Penetration testing of university systems
- Traffic redirection
- ARP spoofing
- Man-in-the-middle tools
- Rogue certificates or certificate authorities
5. Technical Requirements
Approved systems must:
- Use university-provided network connectivity only.
- Use approved operating systems.
- Remain fully patched.
- Use strong authentication.
- Run supported software versions.
- Not share credentials.
- Not bypass security controls.
Infrastructure Services reserves the right to:
- Require vulnerability remediation.
- Require configuration changes.
- Restrict ports and protocols.
- Move systems to a separate network segment if available.
- Remove access immediately if risk is identified.
6. Approval Duration
Approvals are temporary.
Automatic Expiration
Approval expires at the earliest of:
- Withdrawal from course
- Termination of housing contract
- Departure from university housing
Students must submit a new request for continued use.
7. Compliance Monitoring
Infrastructure Services may:
- Review network activity
- Investigate complaints
- Verify device configurations
- Conduct security assessments where appropriate
- Revoke approvals at any time
Failure to comply may result in:
- Immediate network disconnection
- Revocation of exception
- Student conduct referral
- Housing notification
8. Documentation Requirements
Every approved exception should be recorded in TeamDynamix including:
- Student
- Room location
- Device type
- Approval date
- Expiration date
- Reviewer
- Academic justification
- Risk assessment notes
- Any restrictions imposed
9. Annual Reporting
Infrastructure Services will provide Housing an annual summary report.
Report should include by semester:
- Student name
- Major/program
- Residence hall
- Device type
- Approval date
- Expiration date
- Current status
- Approval authority
Housing may also review active and historical approvals directly within TeamDynamix.
10. Revocation Criteria
Approval may be revoked if:
- Academic justification no longer exists.
- Housing contract ends.
- Device creates operational issues.
- Security vulnerabilities are not remediated.
- Device violates policy.
- Device interferes with residence hall networking.
- User fails to cooperate with Infrastructure Services.
