usage_policy.html 2.25 KB
Newer Older
Mark Stenglein's avatar
Mark Stenglein committed
1
---
2
title: "Usage & Disclosure Policy"
Mark Stenglein's avatar
Mark Stenglein committed
3
4
permalink: "/documents/usage_policy/"
---
Daniel W Bond's avatar
Daniel W Bond committed
5

6
7
<div class="row">
  <div class="col-sm-10">
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
      <p>All users of SRCT systems must agree to George Mason's University's
      <a href="http://universitypolicy.gmu.edu/policies/responsible-use-of-computing/">
      Responsible Use of Computing</a> Policy and abide by all other university
      <a href="http://universitypolicy.gmu.edu/">policies</a>. Usage is
      restricted to Mason affiliates.</p>

    <p>Systems are generally owned by the <a href="http://virginia.gov/">
    Commonwealth of Virginia</a>, and may be subject to additional policies
    and laws.  Services are provided best-effort, and users are not entitled
    to or guaranteed access. Access may be removed at any time, at the
    discretion of
    <a href="http://wiki.srct.gmu.edu/index.php/Systems_Administrator">
    Systems Administrator</a> and SRCT.</p>

    <p>In addition, individuals given advanced access to administer and manage SRCT
    systems or resources must agree to the
    <a href="https://www.usenix.org/lisa/system-administrators-code-ethics">
    System Administrator's Code of Ethics</a>, as defined by
    <a href="https://www.usenix.org/lisa">LISA</a>.</p>

    <legend>Handling abuse</legend>
    <p>Misuse of SRCT systems should be addressed by emailing the
30
    <a href="abuse@srct.gmu.edu">abuse team</a>.
31
    SRCT members will investigate the issue and take corrective action as
32
33
34
35
36
37
    deemed necessary. This may include disabling user access, taking down content,
    etc to ensure SRCT serves the educational goals of the University. Abuse
    reports may be forwarded to Mason's
    <a href="http://www.gmu.edu/resources/committee/srp/stopit.html">StopIt</a>
    team if appropriate.</p>

38
    <p>System administrators are the primary point of contact for urgent issues.</p>
39
40
41
42
43
44

    <legend>Handling service interruptions</legend>
    <p>SRCT will make an effort to let users know about known service interruptions
    ahead of time. In case of sudden outages, updates will be provided as soon as
    information is available and a full post-mortem will be posted. Mailing lists
    for this to be determined.</p>
45
46


47
48
49
  </div>
  
  <div class="col-sm-2 hidden-xs">
50
    {% include documents_menu.html %}
51
52
53
54
  </div>

</div>