The Utah Emulab network testbed (”Emulab”) is a general-purpose
testbed facility designed to support experimentation related to networking,
computer systems, distributed systems, cloud computing, virtualization, and
security. Its purpose is to support research and education in computer science
and computing. All uses of Emulab should be consistent with this high-level
The authorized use of Emulab for research and educational purposes is allowed.
A simple litmus test for whether a particular activity counts as
“research” is whether the experimenter intends to disseminate his
or her findings through scholarly venues such as journals or academic
conferences. “Educational” use includes class projects and the
development of courseware.
All uses of Emulab must be authorized through Emulab's testbed-management
software. the testbed-management software manages accounts for organizations
(“projects”) and individual people (“users”), and
controls access to testbed resources. A person may access Emulab only through
an account that is associated exclusively with that user, and a user may access
only those testbed resources that are properly made available to that user by
Emulab (i.e., allocated to the user or the user's organization). All access to
Emulab testbed resources by unauthorized users is prohibited.
All attempts to load-test, penetration-test, “red team,” or
otherwise interfere with Emulab's testbed-management infrastructure are
Emulab may not be used for any illegal or commercial activity.
The use of Emulab is actively monitored by operational staff. Emulab staff
have the right to exercise judgment with respect to the use of Emulab and its
resources in order to maintain the testbed facility and its security,
integrity, and availability; ensure that the testbed is used only for
acceptable purposes; control the allocation of resources to users; and resolve
operational issues as they arise. Emulab staff have the right to restrict or
terminate any user's access to Emulab as they see fit.
Node Usage Rules
A user should utilize existing security mechanisms to prevent unauthorized
access to the resources that are allocated to him or her. For example, all
shell-level access to Emulab nodes must be via SSH.
A user should not allow the devices that he or she has allocated to be idle
for long periods of time. Emulab is a space-shared facility: a device that
is allocated to one user is not available to others, so an allocated but
idle resource is effectively wasted. This prohibition of long-idle devices
includes situations in which a user holds on to a large set of resources
when only a small subset are actively being used.
A user must not circumvent Emulab's accounting and auditing mechanisms.
Among these, Emulab includes mechanisms for tracking idle resources. A
user may not not disable or attempt to subvert these mechanisms without the
approval of Emulab staff.
Network Usage Rules
The following rules apply to the Emulab “control network,” which is
connected to the Internet.
A user may not use the control network in a way that interferes with other
users of the testbed and/or their activities. Among other possible abuses,
this rule prohibits activities that flood the control network with traffic.
This rule also prohibits running software that interfere with testbed
services such as routing and DHCP.
A user may not run any application that a third party could interpret as
being a security threat, intrusion, or privacy violation. Among other
possible abuses, this rule prohibits running network scans of third parties.
Emulab provides isolation between experiments for the purpose of performance
predictability, but it makes no guarantees with respect to the privacy of data
stored within it or transmitted on its networks. Users should not use Emulab
to transmit or store data that is protected by privacy regulations.
Emulab does not provide guarantees with respect to the reliability of the
storage it provides. Every user is responsible for keeping his or her own
copies of files and other data that are important.
While the Emulab staff are usually the first point of contact for complaints
about misbehaving experiments, Emulab staff may in some cases put the
complainant in direct contact with the user who is responsible for the
Violation of this Acceptable Use Policy may result in any or all of the
revocation of any or all of the Emulab resources allocated to a user or
disabling the accounts associated with a user or organization