<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>DataONE Cybersecurity Plan — v2.1.0-beta</title>
<link rel="stylesheet" href="../_static/dataone.css" type="text/css" />
<link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT: '../',
VERSION: '2.1.0-beta',
COLLAPSE_INDEX: false,
FILE_SUFFIX: '.html',
HAS_SOURCE: true,
SOURCELINK_SUFFIX: '.txt'
};
</script>
<script type="text/javascript" src="../_static/mathjax_pre.js"></script>
<script type="text/javascript" src="../_static/jquery.js"></script>
<script type="text/javascript" src="../_static/underscore.js"></script>
<script type="text/javascript" src="../_static/doctools.js"></script>
<script type="text/javascript" src="//cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-MML-AM_CHTML"></script>
<script type="text/javascript" src="../_static/sidebar.js"></script>
<link rel="author" title="About these documents" href="../about.html" />
<link rel="index" title="Index" href="../genindex.html" />
<link rel="search" title="Search" href="../search.html" />
<link rel="next" title="Coordinating Node Internals" href="CoordinatingNodeInternals.html" />
<link rel="prev" title="Querying DataONE" href="querying_content.html" />
<link media="only screen and (max-device-width: 480px)" href="../_static/small_dataone.css" type= "text/css" rel="stylesheet" />
</head>
<body role="document">
<div class="version_notice">
<p>
<span class='bold'>Warning:</span> These documents are under active
development and subject to change (version 2.1.0-beta).<br />
The latest release documents are at:
<a href="https://purl.dataone.org/architecture">https://purl.dataone.org/architecture</a>
</p>
</div>
<div class="related" role="navigation" aria-label="related navigation">
<h3>Navigation</h3>
<ul>
<li class="right" style="margin-right: 10px">
<a href="../genindex.html" title="General Index"
accesskey="I">index</a></li>
<li class="right" >
<a href="../py-modindex.html" title="Python Module Index"
>modules</a> |</li>
<li class="right" >
<a href="CoordinatingNodeInternals.html" title="Coordinating Node Internals"
accesskey="N">next</a> |</li>
<li class="right" >
<a href="querying_content.html" title="Querying DataONE"
accesskey="P">previous</a> |</li>
<li class="nav-item nav-item-0"><a href="../index.html"></a> »</li>
<li class="nav-item nav-item-1"><a href="index.html" accesskey="U"><no title></a> »</li>
</ul>
</div>
<div class="document">
<div class="documentwrapper">
<div class="bodywrapper">
<div class="body">
<div class="section" id="dataone-cybersecurity-plan">
<h1>DataONE Cybersecurity Plan<a class="headerlink" href="#dataone-cybersecurity-plan" title="Permalink to this headline">¶</a></h1>
<table class="docutils field-list" frame="void" rules="none">
<col class="field-name" />
<col class="field-body" />
<tbody valign="top">
<tr class="field-odd field"><th class="field-name">About:</th><td class="field-body">This document forms Appendix C of the <a class="reference external" href="https://docs.dataone.org/member-area/documents/management/project-management-plans-pmp/">DataONE management plan</a>, version 3.0</td>
</tr>
</tbody>
</table>
<div class="section" id="general-principles">
<h2>General Principles<a class="headerlink" href="#general-principles" title="Permalink to this headline">¶</a></h2>
<p>Cybersecurity for DataONE is predicated on the fact that DataONE is a
collaboration of researchers, data providers, institutions, coordinating
nodes, member nodes, data collections and other infrastructure components. As
such it is inherently a virtual organization. DataONE as an entity spans many
organizations and administrative domains. The goal of the cybersecurity in
DataONE is to protect the infrastructure that those organizations and
administrative domains contribute to DataONE as well as the data collections
and the DataONE user community. DataONE, as a virtual organization, will
naturally need to accommodate the highly variable security regimes that are in
use in its various partners. In planning for cybersecurity in this
environment, a layered approach must be used. Each DataONE entity must
simultaneously meet requirements of its local institution and must also
integrate into the DataONE cyberinfrastructure. DataONE is also a mixture of
operational systems to accept and deliver scientific data and research
endeavors to improve the overall data management lifecycle. The cybersecurity
management for DataONE will need to be flexible enough to support the very
different needs of research and operations. The cybersecurity posture of
DataONE will evolve over time both because of continuing maturation of DataONE
operational strategies and because of an ever-evolving cybersecurity
landscape.</p>
</div>
<div class="section" id="dataone-institutional-components">
<h2>DataONE Institutional Components<a class="headerlink" href="#dataone-institutional-components" title="Permalink to this headline">¶</a></h2>
<p>DataONE consists of several types of components both in terms of humans,
systems, institutions, and organizations. This section is a brief summary of
those components and their DataONE roles in terms of cybersecurity:</p>
<p><strong>Scientific Researchers</strong></p>
<p>DataONE will host data and provide access to data for science researchers.
DataONE will frame appropriate data curation policies as part of Partnership
Agreements with Member Nodes. Data integrity must be maintained throughout the
data life cycle when managed by DataONE.</p>
<p><strong>DataONE staff and team members</strong></p>
<p>DataONE funded staff will operate DataONE resources and develop DataONE
software and tools in accordance with DataONE cybersecurity policies and the
policies of their home institutions. DataONE coordinating nodes: A critical
part of the DataONE physical cyber- infrastructure will be located at the
Coordinating Nodes. These components will be operated within the current
acceptable policy environments of these host institutions. In addition, these
resources must meet the requirements for DataONE nodes.</p>
<p><strong>DataONE member nodes</strong></p>
<p>All data collectively managed by DataONE will be located at the member nodes.
These components will be operated within the current acceptable policy
environments of these host institutions. In addition, these resources must
meet the requirements for DataONE nodes. Member nodes will vary in terms of
size, sophistication, and current and future management that will be
accommodated. Specific organizational data security policies and practices
will be adhered to within DataONE in the process of sharing data through or
within the DataONE network.</p>
<p><strong>DataONE data collection owners/contributors/stewards</strong></p>
<p>Data aggregated in DataONE will, in many cases, be delivered by or derived
from existing datasets. The obligations and expectations of DataONE and these
collections sources will be documented in Partnership Agreements by the
involved organizations/institutions.</p>
<p><strong>DataONE data collections</strong></p>
<p>One of the key goals of the cybersecurity plan is protecting the integrity,
availability and confidentiality of the data collections managed by DataONE.
DataONE will develop the necessary policies, practices, and processes to
insure data are properly protected and available only to those permitted
access.</p>
<p><strong>Research organizations that generate long-lived data</strong></p>
<p>DataONE will engage with data creators to host, replicate, and/or curate data
collections. DataONE will use appropriate Partnership Agreements to specify
how these activities will occur, including cybersecurity agreements.</p>
<p><strong>Research Libraries</strong></p>
<p>DataONE will engage with research libraries both as contributors of data
provided by DataONE and as institutional users of DataONE digital data
services. Appropriate Partnership Agreements will be created and executed in
order to understand the agreed levels of mutual service between DataONE and
research libraries. Educational Institutions: DataONE will view educational
institutions as users and outreach and education opportunities. DataONE will
engage with institutions and their students as individuals or a group to
define user access rules and acceptable use policy</p>
<p><strong>Standards Bodies</strong></p>
<p>DataONE will use several data and computing standards both for operations and
as cybersecurity policy and plan guidelines.</p>
<p><strong>DataNet Partners</strong></p>
<p>All DataNet awardees will, in concert, develop appropriate uniform approaches
to data management and curation for the DataNet program. DataONE cybersecurity
policies and posture will need to be compatible with DataNet guidelines.</p>
<p><strong>The U.S. National Science Foundation (NSF)</strong></p>
<p>DataONE and DataNet project and program sponsor. DataONE is responsible to NSF
for cybersecurity operations and any Foundation specific policies or
practices.</p>
</div>
<div class="section" id="institutional-cybersecurity-requirements">
<h2>Institutional Cybersecurity Requirements<a class="headerlink" href="#institutional-cybersecurity-requirements" title="Permalink to this headline">¶</a></h2>
<p>Cyber-infrastructure resources in the form of data collections, access
methods, data storage, and computational resources will need to operate within
the established operational envelope of home institution of each DataONE
component. In many instances this will be an institution of higher education
where the operational envelope is defined by the institution in a process that
may vary from informal to quite formal. In addition, some DataONE
cyber-resources will originate within US agencies where FIPS and other NIST
standards will need to be applied in order to receive a formal authorization
for operations. Future DataONE cyber-resources will be located at institutions
under foreign government institutions, where the governing laws, policies, and
social practices may have significant differences from those at US
institutions. In each instance, the home institution’s policy environment will
be recognized and observed where possible. Where the home institution’s
policies are not compatible with DataONE needs, home institution policy
exceptions will be sought and obtained or we will find some other mechanism to
address the incompatibility.</p>
<p>Cybersecurity requirements will originate from the requirements of the data
itself, primarily in the form of maintaining data integrity, but also
availability and, in some cases, confidentiality.</p>
</div>
<div class="section" id="dataone-wide-cybersecurity-requirements">
<h2>DataONE Wide Cybersecurity Requirements<a class="headerlink" href="#dataone-wide-cybersecurity-requirements" title="Permalink to this headline">¶</a></h2>
<p>In addition to the home institutions policy frameworks, DataONE resources as a
collective entity will have an overlay cybersecurity framework that will
integrate the diverse home institution policies in order to achieve DataONE
goals. Specifically, DataONE will:</p>
<blockquote>
<div><p>Initiate a DataONE cybersecurity coordination group. This group will help
develop and implement policy at all DataONE components. In general, this
policy will be guided by generally accepted best practices and is expected
to establish a set of base requirements and a means to map those
requirements to common frameworks (such as NIST and FIPS documents). This
policy will also provide a framework for the consistent application of
common policy guidelines, such as FIPS 199 information security
classification, by providing more specific examples of terms and
applications within the DataONE context.</p>
<p>Develop cybersecurity language (or appropriate pointers to such language)
within Partnership Agreements in order to document agreements and expected
service levels between DataONE and its fundamental entities:</p>
<ul class="simple">
<li>Users</li>
<li>Data contributors</li>
<li>Coordinating nodes</li>
<li>Member nodes</li>
<li>DataONE staff at sub-awardee institutions</li>
<li>DataONE Collaboration and Public web presence</li>
<li>Document DataONE uniform operational requirements and best practices as
appropriate</li>
<li>Develop a DataONE-wide incidence response playbook, including a point of
contact at each DataONE component.</li>
<li>Analyze the emergent behavior issues that, from a DataONE-wide point of
view, are highly important to DataONE’s success. Such issue will include,
among other things: data integrity and availability; data access control;
and federated identity.</li>
<li>Develop an incident sharing mechanism and policy among DataONE components,
including real-time data sharing and available, sufficiently secure
communication means for during an incident.</li>
</ul>
</div></blockquote>
<p>In this fashion, DataONE will attempt to create an integrated cybersecurity
environment that meets its needs while not being overly burdensome.</p>
</div>
<div class="section" id="dataone-cybersecurity-planning-posture-progression-through-project-lifetime">
<h2>DataONE Cybersecurity Planning Posture Progression Through Project Lifetime<a class="headerlink" href="#dataone-cybersecurity-planning-posture-progression-through-project-lifetime" title="Permalink to this headline">¶</a></h2>
<p>The DataONE cybersecurity plan and subsidiary documents are living efforts.
They will be reviewed and potentially revised annually. In addition, annual
assessments will focus on parts of the cybersecurity environment where issues
or improvements can be made either because of identified vulnerabilities of
because of evolving cybersecurity issues.</p>
</div>
<div class="section" id="cybersecurity-milestones-in-dataone-project-year-one">
<h2>Cybersecurity Milestones in DataONE Project Year One<a class="headerlink" href="#cybersecurity-milestones-in-dataone-project-year-one" title="Permalink to this headline">¶</a></h2>
<p>The DataONE cybersecurity coordination group will be constituted. It will
consist of the deputy director for operations, selected CCIT members,
leadership team representation, working group leads from the Federated
Security group, and other members as appropriate. This group will:</p>
<ul class="simple">
<li>draft a charter and get it approved as a project document</li>
<li>Develop DataONE security policies for coordinating node, member nodes, and
data collection providers as part of their DataONE Partnership Agreements</li>
<li>Develop DataONE acceptable use policy and appropriate user access
acknowledgement format</li>
<li>Draft the initial DataONE cybersecurity plan.</li>
<li>Plan for annual assessment and revision to include, for example, a DataONE
wide security incident response contact list and a DataONE wide security
incident playbook</li>
</ul>
</div>
<div class="section" id="approval-workflow">
<h2>Approval Workflow<a class="headerlink" href="#approval-workflow" title="Permalink to this headline">¶</a></h2>
<p>This section is the initial cybersecurity plan for DataONE. Its approval
process is via the DataONE leadership team and PI. This initial cybersecurity
plan is part of the overall DataONE project management plan. Future annual
revisions of the cybersecurity plan will be via a standalone document that
will be drawn from this section of the project management plan.</p>
</div>
</div>
</div>
</div>
</div>
<div class="sphinxsidebar" role="navigation" aria-label="main navigation">
<div class="sphinxsidebarwrapper">
<p class="logo"><a href="http://dataone.org">
<img class="logo" src="../_static/dataone_logo.png" alt="Logo"/>
</a></p>
<h3><a href="../index.html">Table Of Contents</a></h3>
<ul>
<li><a class="reference internal" href="#">DataONE Cybersecurity Plan</a><ul>
<li><a class="reference internal" href="#general-principles">General Principles</a></li>
<li><a class="reference internal" href="#dataone-institutional-components">DataONE Institutional Components</a></li>
<li><a class="reference internal" href="#institutional-cybersecurity-requirements">Institutional Cybersecurity Requirements</a></li>
<li><a class="reference internal" href="#dataone-wide-cybersecurity-requirements">DataONE Wide Cybersecurity Requirements</a></li>
<li><a class="reference internal" href="#dataone-cybersecurity-planning-posture-progression-through-project-lifetime">DataONE Cybersecurity Planning Posture Progression Through Project Lifetime</a></li>
<li><a class="reference internal" href="#cybersecurity-milestones-in-dataone-project-year-one">Cybersecurity Milestones in DataONE Project Year One</a></li>
<li><a class="reference internal" href="#approval-workflow">Approval Workflow</a></li>
</ul>
</li>
</ul>
<h3>Related Topics</h3>
<ul>
<li><a href="../index.html">Documentation Overview</a><ul>
<li><a href="index.html"><no title></a><ul>
<li>Previous: <a href="querying_content.html" title="previous chapter">Querying DataONE</a></li>
<li>Next: <a href="CoordinatingNodeInternals.html" title="next chapter">Coordinating Node Internals</a></li>
</ul></li>
</ul></li>
</ul>
<div id="searchbox" style="display: none" role="search">
<h3>Quick search</h3>
<form class="search" action="../search.html" method="get">
<div><input type="text" name="q" /></div>
<div><input type="submit" value="Go" /></div>
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
</div>
<script type="text/javascript">$('#searchbox').show(0);</script>
</div>
</div>
<div class="clearer"></div>
</div>
<div class="footer">
<div id="copyright">
© Copyright <a href="http://www.dataone.org">2009-2017, DataONE</a>.
[ <a href="../_sources/design/security-plan.txt"
rel="nofollow">Page Source</a> |
<a href='https://redmine.dataone.org/projects/d1/repository/changes/documents/Projects/cicore/architecture/api-documentation/source/design/security-plan.txt'
rel="nofollow">Revision History</a> ]
</div>
<div id="acknowledgement">
<p>This material is based upon work supported by the National Science Foundation
under Grant Numbers <a href="http://www.nsf.gov/awardsearch/showAward?AWD_ID=0830944">083094</a> and <a href="http://www.nsf.gov/awardsearch/showAward?AWD_ID=1430508">1430508</a>.</p>
<p>Any opinions, findings, and conclusions or recommendations expressed in this
material are those of the author(s) and do not necessarily reflect the views
of the National Science Foundation.</p>
</div>
</div>
<!--
<hr />
<div id="HCB_comment_box"><a href="http://www.htmlcommentbox.com">HTML Comment Box</a> is loading comments...</div>
<link rel="stylesheet" type="text/css" href="_static/skin.css" />
<script type="text/javascript" language="javascript" id="hcb">
/*<! -*/
(function()
{s=document.createElement("script");
s.setAttribute("type","text/javascript");
s.setAttribute("src", "http://www.htmlcommentbox.com/jread?page="+escape((typeof hcb_user !== "undefined" && hcb_user.PAGE)||(""+window.location)).replace("+","%2B")+"&mod=%241%24wq1rdBcg%24Gg8J5iYSHJWwAJtlYu/yU."+"&opts=21407&num=10");
if (typeof s!="undefined") document.getElementsByTagName("head")[0].appendChild(s);})();
/* ->*/
</script>
-->
</body>
</html>