Acceptable Use Guidelines for CAS Computing Resources

Purpose

This document defines acceptable use of computing resources operated or managed by the Hampton University Center for Atmospheric Sciences (CAS). These resources include, but are not limited to, high performance computing clusters, JupyterHub services, data storage systems, and associated login or application servers.

The intent of this document is to provide clear, minimal expectations for responsible use. It is not a comprehensive policy document and should be read in conjunction with the Hampton University Code of Conduct and applicable university IT policies.

Scope

These guidelines apply to all users granted access to CAS-managed computing resources, including faculty, staff, students, visiting researchers, collaborators, and automated processes acting on a user’s behalf.

Access to these systems is a privilege granted for academic, research, instructional, and operational purposes that support the mission of Hampton University.

Guiding Principles

Users are expected to:

  • Act in a lawful, ethical, and professional manner
  • Respect the rights, privacy, and work of others
  • Use shared resources responsibly and efficiently
  • Protect the security and integrity of systems and data

All use must remain consistent with the Hampton University Code of Conduct.

Acceptable Use

The following activities are generally permitted, provided they comply with resource-specific rules and do not interfere with others:

  • Academic and scientific research
  • Coursework, instruction, and training
  • Data analysis, modeling, and visualization
  • Development and testing of software related to approved work
  • Use of JupyterHub and related tools for interactive computing

Prohibited Use

The following activities are not permitted on CAS computing resources:

  • Any activity that violates local, state, or federal law
  • Use that violates the Hampton University Code of Conduct
  • Harassment, discrimination, or abusive behavior
  • Unauthorized access to systems, accounts, or data
  • Circumventing security controls or usage limits
  • Running cryptocurrency mining, botnets, or similar exploitative workloads
  • Excessive or careless use of resources that degrades system performance for others
  • Hosting public-facing services without explicit approval
  • Using systems for personal commercial gain or non-university business

Account and Credential Responsibility

Users are responsible for all activity conducted under their account.

  • Accounts are for individual use only and may not be shared
  • Credentials must be protected and not disclosed to others
  • Users must promptly report suspected credential compromise

Data Responsibility

Users are responsible for the data they store and process.

  • Sensitive or regulated data must only be used with explicit authorization
  • Users should follow best practices for data management and backups
  • CAS makes reasonable efforts to maintain system reliability but does not guarantee data preservation

Resource Management

CAS systems are shared environments.

  • Users must follow published job scheduling, storage, and usage guidelines
  • Long-running or resource-intensive workloads must be run using appropriate batch or managed services
  • Administrators may limit, suspend, or terminate workloads that negatively impact system stability

Monitoring and Enforcement

To ensure reliable operation and security, CAS may monitor system usage, logs, and performance.

Violations of these guidelines may result in actions including:

  • Warning or required corrective action
  • Temporary suspension of access
  • Permanent revocation of access
  • Referral to university authorities under applicable conduct policies

Changes and Acknowledgment

These guidelines may be updated as systems and requirements evolve. Continued use of CAS computing resources constitutes acknowledgment and acceptance of the current version of this document.

Questions regarding acceptable use or interpretation of these guidelines should be directed to CAS system administrators.