290-004

management operations Directorate

Internet Protocol Operational\
Network (IONet) Access Protection Policy and Requirements

Revision 3

June 2004

![](media/image1.emf)

![](media/image2.wmf)

![](media/image3.jpeg){width="6.305555555555555in"
height="8.647916666666667in"}

[]{#__RefHeading___Toc58296322 .anchor}Preface

The *Internet Protocol Operational Network (IONet) Access Protection
Policys and Requirements* document establishes the rules and
responsibilities for ensuring adequate levels of security and integrity
for the IONet.

Hyperlinks are used in this document to provide access to those
applicable documents that are hosted on a Web site and to view
bookmarked material within the document and return with ease to the
point of departure.

This document is under configuration control. The Information Services
Division (ISD) is responsible for processing all changes to it. Changes
to this document will be issued by Document Change Notice (DCN) or,
where applicable, by complete revision. Any questions, recommended
changes, or comments concerning this document should be addressed to:

> Network Security Officer (NSO)\
> Code 297\
> Goddard Space Flight Center\
> Greenbelt, Maryland 20771

Change Information Page

+----------------------+-----------+---+---------------+----------------+
| **List of Effective  |           |   |               |                |
| Pages**              |           |   |               |                |
+----------------------+-----------+---+---------------+----------------+
| **Page Number**      |           | * |               |                |
|                      |           | * |               |                |
|                      |           | I |               |                |
|                      |           | s |               |                |
|                      |           | s |               |                |
|                      |           | u |               |                |
|                      |           | e |               |                |
|                      |           | * |               |                |
|                      |           | * |               |                |
+----------------------+-----------+---+---------------+----------------+
| > ii through vii     |           | > |               |                |
| >                    |           |   |               |                |
| > 1-1 through 1-3    |           | R |               |                |
| >                    |           | e |               |                |
| > 2-1 through 2-4    |           | v |               |                |
| >                    |           | i |               |                |
| > 3-1 through 3-9    |           | s |               |                |
| >                    |           | i |               |                |
| > 4-1 through 4-4    |           | o |               |                |
| >                    |           | n |               |                |
| > 5-1 through 5-2    |           | > |               |                |
| >                    |           |   |               |                |
| > A-1 through A-2    |           | 3 |               |                |
| >                    |           | > |               |                |
| > B-1 through B-3    |           | > |               |                |
| >                    |           |   |               |                |
| > GL-1 through GL-4  |           | R |               |                |
| >                    |           | e |               |                |
| > AB-1 through AB-3  |           | v |               |                |
|                      |           | i |               |                |
|                      |           | s |               |                |
|                      |           | i |               |                |
|                      |           | o |               |                |
|                      |           | n |               |                |
|                      |           | > |               |                |
|                      |           |   |               |                |
|                      |           | 3 |               |                |
|                      |           | > |               |                |
|                      |           | > |               |                |
|                      |           |   |               |                |
|                      |           | R |               |                |
|                      |           | e |               |                |
|                      |           | v |               |                |
|                      |           | i |               |                |
|                      |           | s |               |                |
|                      |           | i |               |                |
|                      |           | o |               |                |
|                      |           | n |               |                |
|                      |           | > |               |                |
|                      |           |   |               |                |
|                      |           | 3 |               |                |
|                      |           | > |               |                |
|                      |           | > |               |                |
|                      |           |   |               |                |
|                      |           | R |               |                |
|                      |           | e |               |                |
|                      |           | v |               |                |
|                      |           | i |               |                |
|                      |           | s |               |                |
|                      |           | i |               |                |
|                      |           | o |               |                |
|                      |           | n |               |                |
|                      |           | > |               |                |
|                      |           |   |               |                |
|                      |           | 3 |               |                |
|                      |           | > |               |                |
|                      |           | > |               |                |
|                      |           |   |               |                |
|                      |           | R |               |                |
|                      |           | e |               |                |
|                      |           | v |               |                |
|                      |           | i |               |                |
|                      |           | s |               |                |
|                      |           | i |               |                |
|                      |           | o |               |                |
|                      |           | n |               |                |
|                      |           | > |               |                |
|                      |           |   |               |                |
|                      |           | 3 |               |                |
|                      |           | > |               |                |
|                      |           | > |               |                |
|                      |           |   |               |                |
|                      |           | R |               |                |
|                      |           | e |               |                |
|                      |           | v |               |                |
|                      |           | i |               |                |
|                      |           | s |               |                |
|                      |           | i |               |                |
|                      |           | o |               |                |
|                      |           | n |               |                |
|                      |           | > |               |                |
|                      |           |   |               |                |
|                      |           | 3 |               |                |
|                      |           | > |               |                |
|                      |           | > |               |                |
|                      |           |   |               |                |
|                      |           | R |               |                |
|                      |           | e |               |                |
|                      |           | v |               |                |
|                      |           | i |               |                |
|                      |           | s |               |                |
|                      |           | i |               |                |
|                      |           | o |               |                |
|                      |           | n |               |                |
|                      |           | > |               |                |
|                      |           |   |               |                |
|                      |           | 3 |               |                |
|                      |           | > |               |                |
|                      |           | > |               |                |
|                      |           |   |               |                |
|                      |           | R |               |                |
|                      |           | e |               |                |
|                      |           | v |               |                |
|                      |           | i |               |                |
|                      |           | s |               |                |
|                      |           | i |               |                |
|                      |           | o |               |                |
|                      |           | n |               |                |
|                      |           | > |               |                |
|                      |           |   |               |                |
|                      |           | 3 |               |                |
|                      |           | > |               |                |
|                      |           | > |               |                |
|                      |           |   |               |                |
|                      |           | R |               |                |
|                      |           | e |               |                |
|                      |           | v |               |                |
|                      |           | i |               |                |
|                      |           | s |               |                |
|                      |           | i |               |                |
|                      |           | o |               |                |
|                      |           | n |               |                |
|                      |           | > |               |                |
|                      |           |   |               |                |
|                      |           | 3 |               |                |
|                      |           | > |               |                |
|                      |           | > |               |                |
|                      |           |   |               |                |
|                      |           | R |               |                |
|                      |           | e |               |                |
|                      |           | v |               |                |
|                      |           | i |               |                |
|                      |           | s |               |                |
|                      |           | i |               |                |
|                      |           | o |               |                |
|                      |           | n |               |                |
|                      |           | > |               |                |
|                      |           |   |               |                |
|                      |           | 3 |               |                |
+----------------------+-----------+---+---------------+----------------+
|                      |           |   |               |                |
+----------------------+-----------+---+---------------+----------------+
|                      |           |   |               |                |
+----------------------+-----------+---+---------------+----------------+
|                      |           |   |               |                |
+----------------------+-----------+---+---------------+----------------+
|                      |           |   |               |                |
+----------------------+-----------+---+---------------+----------------+
|                      |           |   |               |                |
+----------------------+-----------+---+---------------+----------------+
| **Document History** |           |   |               |                |
+----------------------+-----------+---+---------------+----------------+
| **Document Number**  | **Statu   |   | **Publication | **CCR Number** |
|                      | s/Issue** |   | Date**        |                |
+----------------------+-----------+---+---------------+----------------+
| 290-004              | >         |   | > September   | > 290-003      |
|                      |  Original |   | > 1999        |                |
+----------------------+-----------+---+---------------+----------------+
| 290-004              | >         |   | > January     | > 290-244      |
|                      |  Revision |   | > 2001        |                |
|                      | > 1       |   |               |                |
+----------------------+-----------+---+---------------+----------------+
| 290-004              | >         |   | > May 2001    | > 290-301      |
|                      |  Revision |   |               |                |
|                      | > 2       |   |               |                |
+----------------------+-----------+---+---------------+----------------+
| 290-004              | >         |   | > June 2004   | > 290-764      |
|                      |  Revision |   |               |                |
|                      | > 3       |   |               |                |
+----------------------+-----------+---+---------------+----------------+
|                      |           |   |               |                |
+----------------------+-----------+---+---------------+----------------+
|                      |           |   |               |                |
+----------------------+-----------+---+---------------+----------------+
|                      |           |   |               |                |
+----------------------+-----------+---+---------------+----------------+
|                      |           |   |               |                |
+----------------------+-----------+---+---------------+----------------+

Contents

Preface [iii](#__RefHeading___Toc58296322)

Section 1. Introduction [1-1](#introduction)

1.1 General [1-1](#general)

1.2 Purpose [1-1](#purpose)

1.3 Applicability [1-2](#applicability)

1.4 Applicable Documents [1-2](#applicable-documents)

1.5 Authority [1-3](#authority)

1.6 Contents and Organization [1-3](#contents-and-organization)

Section 2. Security Roles and Responsibilities
[2-1](#security-roles-and-responsibilities)

2.1 General [2-1](#general-1)

2.2 ISD [2-1](#isd)

2.3 ISD Configuration Management [2-2](#isd-configuration-management)

2.4 NASA Centers, International Partners, Contractors, and Commercial
Ground Stations
[2-2](#nasa-centers-international-partners-contractors-and-commercial-ground-stations)

2.5 System Administrators and System Security Administrators
[2-3](#system-administrators-and-system-security-administrators)

2.6 System Users [2-4](#system-users)

2.7 IONet Audit Team [2-4](#ionet-audit-team)

[Section 3. IONet Policies and Security Requirements
3-1](#ionet-policies-and-security-requirements)

[3.1 General IONet Security 3-1](#general-ionet-security)

[3.1.1 IONet Host and Device Registration
3-1](#ionet-host-and-device-registration)

[3.1.2 Electronic Mail Relay Services
3-2](#electronic-mail-relay-services)

[3.1.3 Domain Name Service (DNS) 3-2](#domain-name-service-dns)

[3.1.4 Host and Device Registration 3-2](#host-and-device-registration)

[3.1.5 Encryption 3-2](#encryption)

[3.1.6 Virtual Local Area Network (VLAN)
3-2](#virtual-local-area-network-vlan)

[3.1.7 Network Information System (NIS)
3-2](#network-information-system-nis)

[3.1.8 Network File System (NFS) 3-3](#network-file-system-nfs)

[3.1.9 Dynamic Host Configuration Protocol (DHCP)
3-3](#dynamic-host-configuration-protocol-dhcp)

[3.1.10 Network Address Translation (NAT)
3-3](#network-address-translation-nat)

[3.1.11 Wireless 3-3](#wireless)

[3.1.12 National Agency Check 3-3](#national-agency-check)

[3.1.13 Dual-Boot Systems 3-4](#dual-boot-systems)

[3.1.14 Remote Access 3-4](#remote-access)

[3.1.15 Network Information Security 3-5](#network-information-security)

[3.2 Physical Security 3-5](#physical-security)

[3.3 IONet Policies and Restrictions
3-6](#ionet-policies-and-restrictions)

[3.3.1 Closed IONet Policies and Restrictions
3-7](#closed-ionet-policies-and-restrictions)

[3.3.2 Restricted IONet Policies and Restrictions
3-7](#restricted-ionet-policies-and-restrictions)

[3.3.3 Open IONet Policies and Restrictions
3-8](#open-ionet-policies-and-restrictions)

[3.4 Communication Security (COMSEC)
3-8](#communication-security-comsec)

[3.5 Remote Control 3-9](#remote-control)

[3.6 Individual Accountability 3-9](#individual-accountability)

Section 4. ISD-Sponsored Audits [4-1](#isd-sponsored-audits)

4.1 Audit Team Authority and Responsibility
[4-1](#audit-team-authority-and-responsibility)

4.2 Audit [4-1](#audit)

4.2.1 Connection Request [4-1](#connection-request)

4.2.2 Project Audits and IONet NSO Requested Audits
[4-2](#project-audits-and-ionet-nso-requested-audits)

4.2.3 Re-Audits [4-2](#re-audits)

4.3 Audit Process [4-2](#audit-process)

4.3.1 Step 1 - Documentation Delivery
[4-2](#step-1---documentation-delivery)

4.3.2 Step 2 - Documentation Review
[4-2](#step-2---documentation-review)

4.3.3 Step 3 - Question Follow-ups [4-3](#step-3---question-follow-ups)

4.3.4 Step 4 - Optional Site Visit [4-3](#step-4---optional-site-visit)

4.3.5 Step 5 - Audit Findings [4-3](#step-5---audit-findings)

4.3.6 Step 6 - Waiver Request [4-4](#step-6---waiver-request)

4.4 Protection of Audit Report and Checklists
[4-4](#protection-of-audit-report-and-checklists)

Section 5. Connection Request Procedure and Required Security
Documentation
[5-1](#connection-request-procedure-and-required-security-documentation)

5.1 General [5-1](#general-2)

5.2 Required Security Documentation
[5-1](#required-security-documentation)

5.3 Obtaining an IONet Connection [5-1](#obtaining-an-ionet-connection)

Appendix A. Sample Rules of Behavior for IT Resources Connected to the
Closed IONet
[A-1](#sample-rules-of-behavior-for-it-resources-connected-to-the-closed-ionet)

Appendix B. IONet Access Protection Policy Waivers
[B-1](#ionet-access-protection-policy-waivers)

B.1 Waiver Process [B-1](#b.1-waiver-process)

B.2 Waiver Duration [B-1](#b.2-waiver-duration)

B.3 Submission of Waiver Requests B-2

B.4 Waiver Approvals B-2

Internet Protocol Operational Network (IONet) Access Protection Policy
Waiver Request [B-3](#__RefHeading___Toc58296384)

Glossary GL-[1](#__RefHeading___Toc58296384)

Abbreviations and Acronyms AB-[1](#__RefHeading___Toc58296386)

# Introduction

## General

The [Internet](#Internet) Protocol (IP) Operational [Network](#Network)
(IONet) is a NASA-wide IP network managed from the Goddard Space Flight
Center (GSFC). The [users](#User) are NASA space flight programs and the
United States Government, international partners, contractor employees
located both inside and outside the United States, universities,
commercial ground stations, and other commercial facilities, which
support NASA space flight mission requirements.

The IONet supports missions on a 24-hour basis with real-time
operational data (attitude, command, orbit, ephemeris, telemetry, state
vectors). In addition, IONet supports non-real-time data (space
experiments' data products, quick-look image data). The IONet is divided
into three networks: the most secure Closed IONet, the secure Restricted
IONet, and the less secure Open IONet. The IP Transition network is an
integral part of the Closed IONet. The Information Services Division
(ISD), Code 290, GSFC, Greenbelt, Maryland, maintains a Secure Gateway
(firewall) to prevent penetration of hosts on the Closed IONet from
external networks. The idea behind the Restricted IONet is to establish
an IONet network outside the Secure Gateway that supports real-time
critical mission flows for projects that have requirements for
connections to other networks. The most prevalent example is mission
control centers located at universities. The Closed IONet security
levels remain unchanged. The Restricted IONet projects have a lower
degree of protection than the Closed IONet, because of its perimeter
negotiations.

This document will use the term *IONet* when referring to all three
networks. Otherwise, it will specify whether the material pertains
specifically to the Open, Restricted, or Closed IONet

The project and user hosts connected to the IONet provide their own
local host security; however, they must satisfy the requirements
presented in this document and [NPR
2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main).
This document presents additional [information technology](#InfoTech)
(IT) policies specific to the IONet.

Projects and sites connected to the IONet are subject to an
[audit](#Audit) by ISD's established IONet audit team to ensure that
projects provide adequate security for network resources and that they
can prevent the propagation of a security infiltration activity.

## Purpose

This document

a.  States the policy for limiting unauthorized access to the IONet from
    any IT resource connected to the IONet

b.  Specifies the security requirements that must be met by systems
    using the IONet

c.  Describes the audit procedures used to evaluate the security
    [controls](#Control) of IT resource(s) connected to the IONet

d.  Describes the procedure for obtaining a connection to the IONet

e.  Describes the project's IT security documentation that must exist
    before an IONet connection request will be granted

f.  Provides sample Rules of Behavior

g.  Outlines the procedures for submission of [waiver](#Waiver) requests
    for deviations from the policies and requirements levied by this
    document

This document does not replace any security directive, document, or
policy created by the local NASA center or by NASA Headquarters. It does
specify additional requirements for any IT resource that has (or is
requesting) an interface to the IONet. In case of differences between
this document and any other user's/institution's requirements, the [more
stringent security requirement takes precedence](#stringent).

## Applicability

This document is applicable to all NASA field centers, stations,
facilities, NASA program offices, NASA contractors, international
partner agencies, universities, and commercial ground stations. ISD
expects all projects having IONet access or interface(s) to incorporate
the required security safeguards into their contracts with their users,
domestic or foreign.

## Applicable Documents

Applicable documents are those that by virtue of their inclusion in this
paragraph become part of this document and have the same force and
authority as if physically reproduced and incorporated as part of this
document.

a.  [NTISSP 200](http://www.nstissc.gov/Assets/pdf/NTISSP_200.pdf),
    [National Policy on Controlled Access Protection (for automated
    information systems)]{.underline}, July 15, 1987

b.  [H.R.2458](http://www.legaltech.com.br/Legis/E-government Act 2001.pdf),
    [E-Government Act of 2002]{.underline}, Title 3, "Federal
    Information Security Management Act of 2002"

c.  [NPD
    2800.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PD_2800_0001_&page_name=main),
    [Managing Information Technology]{.underline}, March 23, 1998

d.  [NPD
    2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PD_2810_0001_&page_name=main),
    [Security of Information Technology]{.underline}, October 1, 1998

e.  [NPR
    2800.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2800_0001_&page_name=main),
    [Managing Information Technology]{.underline}, September 17, 1998

f.  [NPR
    2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main),[]{#appdoc_f
    .anchor} [Security of Information Technology]{.underline}, August
    26, 1999

g.  [GPG
    2810.1](http://msc-docsrv.gsfc.nasa.gov/GDMS_docs/GPG2000/GPG-2810.1-.pdf),
    [Security of Information Technology Goddard Procedures and
    Guidelines (GPG)]{.underline}, April 16, 2003

h.  [290-003](http://code297.gsfc.nasa.gov/docs/ionet/ionetsp-final-rev1a.doc),[]{#appdoc_h
    .anchor} [IP Operational Network (IONet) Security Plan]{.underline},
    Revision 1, October 2000

i.  [290-001](http://forbin2.gsfc.nasa.gov/290 iso/documentation/ISAT CMP Rev1.pdf),[]{#appdoc_i
    .anchor} [Information Services and Advanced Technology Division
    Configuration Management Plan]{.underline}, Revision 1, January 2001

j.  [290-WI-8072.1.1](http://msc-docsrv.gsfc.nasa.gov/GDMS_docs/Pgwi200/290-WI-8072.1.1-.pdf),[]{#appdoc_k
    .anchor} [Communications Service Request Process]{.underline}, June
    1, 1999

k.  Office of Management and Budget (OMB) [Circular
    A-130](http://www.whitehouse.gov/omb/circulars/a130/a130.html),
    [Appendix III -- Security of Federal Automated Information
    Resources]{.underline}, February 8, 1996

## Authority

[NPR
2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main),
[Security of Information Technology,]{.underline} describes the NASA IT
Security Program, providing direction to ensure that safeguards for the
protection of the [integrity](#Integrity),
[availability](#Availability), and [confidentiality](#Confidentiality)
of IT resources (e.g., data, information, applications, and systems) are
integrated into and support the missions of NASA. IONet sensitivity and
criticality were determined in accordance with the requirements
delineated in [NPR
2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main),
Chapter 4, Section 4.2.9, as Mission (MSN) Information. This designation
means that if the IONet information, software applications, network, or
computer systems are altered, destroyed, or unavailable, the impact on
NASA could be catastrophic. The result could be the loss of major or
unique assets, a threat to human life, or prevention of NASA from
preparing or training for a critical agency mission. The Closed IONet
handles the data that is critical for mission operations and manned
flight; the Restricted IONet, although having a significantly lower
degree of protection because of its perimeter negotiations, will support
Closed data; whereas the Open IONet handles non-real-time data such as
experimenters' data and command data for unmanned spacecraft or
experiments onboard a spacecraft.

Because the category level of all three networks has been determined as
MSN, [NPR
2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main)
establishes the protective-measures that are appropriate when the
information is processed by an IT resource or transmitted over a
communications network. Using [NPR
2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main)
and the other applicable documents listed in Section 1.4, this document
ensures that the IT resources interfacing with the IONet apply a
consistent set of security measures.

## Contents and Organization

The remainder of this document is composed of the following sections and
appendixes:

a.  [Section 2](#security-roles-and-responsibilities). Security Roles
    and Responsibility

b.  [Section 3](#ionet-policies-and-security-requirements). IONet
    Policies and Security Requirements

c.  [Section 4](#isd-sponsored-audits). ISD**-**Sponsored Audits

d.  [Section
    5](#connection-request-procedure-and-required-security-documentation).
    Connection Request Procedure and Required Security Documentation

e.  [Appendix
    A](#sample-rules-of-behavior-for-it-resources-connected-to-the-closed-ionet).
    Sample Rules of Behavior

f.  [Appendix B](#ionet-access-protection-policy-waivers). IONet Access
    Protection Policy Waivers

g.  [Glossary](#glossary)

h.  [Abbreviations and Acronyms](#__RefHeading___Toc58296386)

# Security Roles and Responsibilities

## General

NASA has established an agency-wide Information Technology Security
(ITS) Program to provide guidance for securing NASA IT resources (see
[NPR
2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main)).
[NPR
2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main),
Section 4.4.11.5, addresses "Misuse of I[nformation Technology
Resources](#InfoTechResource)"; Section 4.8 addresses "Appropriate Use
of Information Technology Resources"; and Section 4.2 provides direction
on IT Security Planning. IONet personnel have and use this guidance to
assist in providing security. ISD has been assigned project
responsibility for the IONet.

Note:

A "three strikes and you're out" policy applies for the IONet. If the
same workstation or piece of networking equipment has been compromised
three times or found with the same vulnerability three times without
mitigation, it will be removed from the IONet and never allowed back
onto the IONet.

The IONet, like other NASA networks, is designed to provide integrity
(i.e., ensure that transmitted data is received intact) and availability
(i.e., network services are performed within an acceptable timeframe).
The owner of the node, system, or application must provide data
confidentiality, if needed. ISD, being the designer, builder, and
manager of the IONet, has the responsibility to provide network
security. In exercising this responsibility, ISD has the right to define
requirements that must be met by all locations that have access to the
IONet resources and to audit those locations to ensure their compliance.
Sections 2.2 through 2.7 of this document outline the security roles and
responsibilities of the various groups and organizations using the
IONet.

## ISD

ISD is responsible for the network's security, the availability of the
IONet resources, and data integrity during transmission; however, ISD
has no direct control over other NASA Centers or other IONet user
installations. Therefore, these NASA Centers and user installations play
an important part in the overall security operations of the IONet and
must comply with the requirements outlined in this document. Users must
realize that security is only as strong as its weakest point. ISD is
responsible for the following:

a.  Making sure that the security of the IONet is within the bounds of
    established government, agency, and GSFC requirements

b.  Establishing overall IONet security policies and requirements

c.  Establishing the rules for connectivity to the IONet

d.  Providing a complete set of operational guidelines and procedures
    for the Internet Protocol Network Operations Center (IPNOC)

e.  Providing a real-time network management system to continuously
    monitor the network

f.  Performing security audits of projects/sites and performing network
    scanning of equipment that is connected to the IONet to ensure
    compliance with the security requirements provided in this document

g.  Authorizing Virtual Private Networks (VPNs), encrypted channels, or
    deviations to this policy

h.  Approving and implementing the IONet Secure Gateway (firewall)
    rules; these rules determine what traffic is allowed to flow between
    the Open, Restricted, and Closed IONet

i.  Configuring the [routers](#Routers) connecting the users to the
    IONet

j.  Maintaining an active configuration management (CM) organization to
    watch over the IONet's configuration and changes thereto

ISD has a security structure in place to provide this security. This
structure is outlined in the IONet Security Plan **(**refer to
[Applicable Documents 1.4.h](#appdoc_h)). [NPR
2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main),
Appendix A, Section 7 (refer to [Applicable Documents
1.4.f](#appdoc_f)), outlines the network security requirements that ISD
must implement.

## ISD Configuration Management

The ISD Configuration Control Board (CCB) process controls the IONet CM.
A Configuration Change Request (CCR) accomplishes changes to a
documented baseline; an Engineering Change (EC) accomplishes changes to
an engineering baseline; and a Software Change Request (SCR) documents
changes to software. Changes to the facility are accomplished through
Work Orders.

Forms, procedures, reviews, audits, and other factors in the CM process
are described in the ISD Configuration Management Plan, 290-001 (refer
to [Applicable Documents 1.4.i](#appdoc_i)).

## NASA Centers, International Partners, Contractors, and Commercial Ground Stations

All NASA centers, international partners, contractors, and commercial
ground stations that have connectivity to the IONet are responsible for
the following:

a.  Providing security for their IT resources connected to the IONet

b.  Adhering to all local security requirements and the requirements
    listed in this document and [NPR
    2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main)

c.  Providing a secure environment for all IONet equipment and for local
    computers connected to any portion or extension of the IONet

d.  Ensuring that equipment connected to the IONet has adequate security
    to prevent propagation of a security infiltration

e.  Ensuring that there are no connections to the Open, Restricted, and
    Closed IONet from the same resource, nor to the Closed IONet and any
    other network

f.  Reporting all [security incidents](#SecIncident) to local
    authorities and to the IONet Network Security Officer (NSO)

g.  Submitting the required documentation ([see Section
    5.2](#required-security-documentation)) with each connection
    request, when requested by Code 297, or when major changes to
    connectivity occur

Note:

The security evaluation must be completed before a new connection can be
installed. Please allow at least 4 weeks for this evaluation and submit
all the required documentation accordingly. In addition, projects must
be aware of the NASA requirement to have all documentation approved and
signed 30 days prior to the applicable Mission Readiness Review.

h.  Assisting the IONet Audit Team in performing the local audit

i.  Performing or obtaining personnel background screening, including
    fingerprinting, as required

j.  Establishing that each person using the IONet interfaces at his/her
    job location has a need-to-know

Note:

A firewall between local networks does not provide the required
isolation for the Closed IONet. A fundamental [security
policy](#SctyPolicy) of the Closed IONet is that there is no trust
relationship between Closed IONet and the perimeter.

## System Administrators and System Security Administrators

Each system will have a system administrator (SA) and/or a system
security administrator (SSA), hereinafter referred to simply as
*administrator*, who will ensure that the protective [security
measures](#SctyMeas) of the system are functional and who will maintain
its security posture. In addition to the administrator requirements
listed in [NPR
2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main),
Section 2.2.8, the administrator is responsible for the following:

a.  Maintaining a file of user request forms, signed by a manager, for
    all new accounts entered into the system

b.  Correcting all known vulnerabilities and reporting on and writing
    waiver requests for the uncorrected vulnerabilities

c.  Keeping all security patches up to date

Note:

If an administrator commits three security violations as a result of
negligence, the IONet NSO may recommend that his/her National Agency
Check (NAC) or security clearance be withdrawn. Any attempt to access
the system after the NAC or clearance is withdrawn will be considered an
act of unauthorized access to a United States Government computer and,
therefore, be subject to federal prosecution.

## System Users

All system users with connectivity to the IONet are responsible for the
following:

a.  Submitting a formal request for a User Identifier (ID)

b.  Following all mandated security procedures

c.  Following the requirements outlined in this document, as well as
    local regulations and [NPR
    2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main)

d.  Reporting all security incidents to local authorities and to the
    IONet NSO

e.  Signing a statement of responsibility (also known as Rules of
    Behavior), indicating understanding of the requirements for using
    and safeguarding the information for which access is granted (see
    [Appendix
    A](#sample-rules-of-behavior-for-it-resources-connected-to-the-closed-ionet))

## IONet Audit Team

The IONet audit team is responsible for the following:

a.  Reviewing all documentation submitted with circuit (connection)
    requests or reaudits and making recommendations to the IONet NSO

b.  Performing periodic security audits of all facilities connected to
    the IONet

c.  Running network scan programs as requested by the IONet NSO

d.  Evaluating security technology as agreed to by the IONet NSO

e.  Evaluating all waiver requests submitted and making recommendations
    to the IONet NSO for their disposition

f.  Performing physical site audits as requested and/or approved by the
    IONet NSO

# IONet Policies and Security Requirements

The IONet will only be used for mission activities. All workstations and
computers connected to the IONet, with the exception of the ISD
equipment used to monitor or control the network, are the responsibility
of the parent organization or contractor. ISD has established the
restrictions contained in this document. They must be implemented before
connections are installed.

## General IONet Security

The configurations of all IONet-supplied components that interconnect
the GSFC IONet to its external user locations are controlled by ISD
personnel/contractors at GSFC. The configuration of these components
(routers and conversion devices) is performed at GSFC within the
restricted access facilities provided by ISD. The security of these
devices must meet the requirements for [boundary systems](#Boundary) as
given in [NPR
2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main),
Section A.7.4.4. To assist in securing the IONet, users must adhere to
the policies and restrictions described in this section. Unless
otherwise stated, the following policies and restrictions apply to Open,
Restricted, and Closed IONet.

### IONet Host and Device Registration

All project systems/hosts that physically connect to the IONet (Open,
Closed, IP Transition, or Restricted segments), are required to be
registered with the ISD/\
Enterprise IT Security Branch (Code 297). Submissions should be made to
the attention of Matt Kirichok.

Line managers shall approve and submit to Code 297 the name(s) of the
user(s) responsible for the registration of the systems. The users are
responsible for keeping the information about the host current.

It is understood that line manager approval authority shall be at or as
close to the first line of supervision or group/task leadership as is
determined by the home organization to be appropriate.

The information is to be submitted using the template at
<http://eitsb.gsfc.nasa.gov/admin.stm> and must include the following
information:

> Host name
>
> IP address
>
> SA responsible for the host
>
> SA phone and email
>
> Org. Code responsible for system
>
> Project(s) that this system supports
>
> Submissions are required to be made in hard copy form to:
>
> NASA/GSFC
>
> M. Kirichok/297
>
> Greenbelt, MD 20771
>
> Effective Date:

This policy is effective immediately. Any systems that are found to be
noncompliant with this policy will be disabled from the network until
the systems are made compliant.

### Electronic Mail Relay Services

Electronic mail (e-mail) relay services shall be controlled and
registered with the ISD division through the IONet NSO. The IONet NSO is
the only official with the authority to approve the registration and
configuration of those services within the IONet.

### Domain Name Service (DNS)

The ISD Network Engineering Branch, through the IONet NSO, shall be the
provider of the DNS services within the IONet. Projects shall not run
any DNS service. Projects behind firewalls and others that may request
to provide their own DNS service are required to register these services
with the IONet NSO for approval. The IONet NSO is the only official with
the authority to approve the registration and configuration of any DNS
server outside the service provided by the IONet.

### Host and Device Registration

Before any project's system is connected to the IONet, that system is
required to be registered with the ISD Network Engineering Board (NEB).
Line managers shall approve and submit to the NEB the name of the
point-of-contact (POC) person responsible for the registration of the
systems. This POC is responsible for keeping the information about the
host current.

### Encryption

Encrypted traffic is prohibited (shall not be sent) through the IONet
Secure Gateway. VPN, Secure Shell (SSH), Secure Socket Layer (SSL), and
other encrypted data traffic is permitted within the confines of the
IONet, provided that it is not transmitted from one segment of the IONet
to another, such as from the Open IONet to the Closed IONet. However,
the IONet NSO must be notified and have approved the use of encryption
before it is employed. Troubleshooting will not be provided.

### Virtual Local Area Network (VLAN)

VLANs are not generally allowed on the IONet because they create holes
that IONet cannot troubleshoot or control. However, Code 290 recognizes
that in special and rare instances, a project with an installed and
operating VLAN may require connection to the IONet. Requests for VLAN
use will be evaluated case by case. Under no circumstances will traffic
to/from a VLAN be allowed to pass through the IONet firewalls. The NSO
must approve all VLAN implementations.

### Network Information System (NIS)

If NIS is used, each host client or server computer in the system has
knowledge about the entire system. A user at any host can gain
synchronized access to files or applications on another host in the
network using a generic user [identification](#Identification) login and
[password](#Password). (NIS was originally called *Yellow Pages*.) This
violates the IONet IT security policy requiring each user to have a
unique login and password. Implementation of the use of NIS can be
considered on a case-by-case basis. However, an NIS will only be
considered for approval if (1) its use is restricted to within the
project, (2) it is blocked between routers, and (3) it is registered
with and approved by the IONet NSO.

### Network File System (NFS)

An NFS is a client/server application that lets a computer user view,
store, and update files on a remote computer as though located on the
user's local computer. The local computer must have an NFS client, and
the remote computer must run the NFS server process. The NFS protocol
uses the Remote Procedure Call (RPC) method of communication between
computers. Using NFS, the user or an SA can mount (designate as
accessible) all or a portion of a file system (which is a portion of the
hierarchical tree in any file directory and subdirectory). The portion
of the file system that is mounted can be accessed with the privileges
necessary to open each file for read-only or read-write purposes. NFS is
not allowed between networks, only within a network. NFS must be
configured securely, and the IONet NSO must approve the implementation
before connection to the IONet is allowed.

### Dynamic Host Configuration Protocol (DHCP)

[DHCP](#dhcp) is not allowed on the IONet because it dynamically assigns
IP addresses, thereby making the tracking of IP addresses (and
subsequent troubleshooting) more difficult.

### Network Address Translation (NAT)

The use of NAT is allowed on the IONet if, and only if, there is a
one-to-one mapping of addresses. NAT is the translation of an IP address
used within one network to a different IP address known within another
network. One network is designated the inside network, and the other is
the outside network. Typically, an organization translates or "maps" its
local inside network addresses to one or more global outside IP
addresses and then translates the global IP addresses on incoming
packets back into local IP addresses. This practice helps ensure
security because each outgoing or incoming request must go through a
translation process that also offers the opportunity to qualify or
authenticate the request or match it to a previous request. The IONet
NSO must approve its use.

### Wireless

Wireless technology is not permitted for use within the IONet because of
the frailty of the encryption schema employed.

### National Agency Check 

All individuals requiring privileged access or limited privileged access
to an IONet resource require background screening that includes
fingerprinting. *Privileged* or *limited privileged access* means that
the individual with this access can bypass, modify, or disable the
technical or operational system security controls for part of the system
or application. This level of access is often referred to as *root* or
*administrative access*. All personnel who transmit or receive data,
and/or have connection or access to the IONet require a NAC. (See [NPR
2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main),
Section 4.5.)

When one or more of the following conditions pertain, a NAC is required
for all individuals:

a.  Requiring a connection to or already possessing access to the IONet

b.  Needing to transmit or receive data on the IONet

c.  Requiring access to IONet IT equipment

Note:

United States citizens with privileged access or limited privilege
access must have a NAC. A NAC in progress is not sufficient. Foreign
nationals (including those with a Green Card) fall into one of the two
categories: non-international partners and international partners.
Non-international partners may not under any circumstances have limited
privileged or privileged access to IT resources. For international
partners, the control center must obtain a copy of a signed Memorandum
of Understanding (MOU) from headquarters that defines the international
partner agreement. The MOU represents the project's assurance that the
appropriate screening has been performed.

d.  Requiring access to the physical confines of a control center

Note:

A NAC is a minimum requirement. Specific facilities may require a
security clearance. A security clearance is above a NAC and meets the
minimum requirement. An individual without a NAC must be escorted while
in the control center. The control center should have a local operating
procedure (LOP) for the escort so the escort knows his or her
responsibilities. The control center should have a list of all
appropriately screened individuals (NACs or clearances) confirmed and
available.

Be aware that everyone granted access to IONet equipment must have a
need to know. *Need to know* is a determination that a prospective
recipient of information or access requires the information or access to
perform tasks or services essential to fulfilling his/her job.
Determination of the need to know is based on job assignment and
requires approval from the IONet NSO or the project manager.

### Dual-Boot Systems

[Dual-boot](#DualBoot) systems are allowed, but they are not allowed to
hop networks. Dual-boot systems must be registered and approved by the
IONet NSO.

### Remote Access

All remote access is prohibited on the Restricted IONet and the Closed
IONet. Modem and Internet access to nonprivileged accounts is permitted
on the Open IONet. Remote access to a privileged account requires
authorization of the responsible line manager. Internet access must be
restricted to known/trusted IP addresses. The IONet NSO must approve all
modems connected to the Open IONet. This approval is done case by case.
Use of additional security, such as one-time passwords, VPN connection,
encrypted channel, and secure modems, is recommended if commands to
unmanned spacecraft or to onboard experiments are being transmitted. All
remote logins and traffic must be logged.

### Network Information Security

The list shown below contains general network information security
guidelines for IONet users. All users shall do the following:

a.  Protect all information related to the development or operation of
    the IONet

b.  Protect and limit distribution of firewall and router rules for all
    devices connected to the IONet

Note:

The rules for all IONet-owned firewalls and routers are the sole
responsibility of ISD.

c.  Protect IP addresses and special use port numbers as sensitive
    information

d.  Restrict access to all network drawings containing IP addresses to
    those who have a need to know

e.  Forbid clear text transmission of e-mail containing Closed IONet IP
    addresses

f.  Protect the rules sets in use within user institutions connected to
    the Open IONet that have their own firewall(s) and router(s) as
    sensitive information

Note:

User-owned firewalls are not allowed on the Closed IONet.

g.  Handle completed checklists, network scan results, risk assessments,
    and audit reports as ADMINISTRATIVELY CONTROLLED INFORMATION (ACI)

Note:

ACI is not to be transmitted via clear text e-mail.

Be aware that confidentiality of data transmitted over the IONet is the
responsibility of the owner of the application using the data. (See [NPR
2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main),
Appendix A.7.1.)

## Physical Security

[Physical security](#PhySec) protects IT resources from human, natural,
and accidental damage. It is not the intent of this section to specify
requirements for facility construction, protection of IT resources from
fire and water, electric power, or facility housekeeping. This section
describes only entry/access controls for IT resources comprised in or
connected to the IONet. Physical security is an important part of any
security program and is an essential component of the IONet's security
posture. [NPR
2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main),
Section A.8, provides additional requirements for physical security
(such as electrical power and protection from fire and water).

All ISD-supplied equipment, all other networking equipment, and all IT
resources connected to the Closed and the Restricted IONet must be
situated within limited-access, locked facilities. Only personnel with
defined business needs may be authorized to enter these controlled
areas. Authorized personnel will be issued appropriate badges and
keycard/keys to permit entry. A list of individuals with ongoing access
must be maintained and reconciled at least annually. Personnel who need
to enter occasionally should be escorted or issued temporary badges and
access. A record must be kept of each visitor and visit.

Other IT resources connected to the Open IONet should be in locked
environments. Strict rules for the issuance of user IDs and passwords
must be enforced. Rules for user ID management and passwords are given
in [NPR
2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main),
Section A.6.2 and A.6.3. Projects must also meet the requirement and
time limits to remove user IDs when an individual no longer has a need
to use the resource, as prescribed in [NPR
2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main).

## IONet Policies and Restrictions

The following restrictions are applicable to all equipment connected to
the IONet.

a.  Traffic between the Closed and the Restricted or Open IONet must go
    unencrypted through the IONet Secure Gateway.

b.  VPN and encrypted data traffic is prohibited through the IONet
    Secure Gateway. VPN and encrypted data traffic may be permitted
    within the Closed IONet, but troubleshooting will not be provided.
    The IPNOC must be advised when using encrypted data transmissions.

Note:

The IONet NSO must authorize all VPN or encrypted channels on the Closed
IONet. This is done case-by-case. These channels cannot go through the
firewall; therefore, they can be used only between users on the Closed
Network. All devices must connect via 290-managed user interface
switches.

c.  Network scanning of a project's local subnet by the project is
    permitted if prior IONet NSO authorization is obtained. ISD
    personnel do all other scanning and penetration testing. A project
    may request the testing.

d.  A project may implement an Intrusion Detection System (IDS) on the
    project's subnet; however, prior IONet NSO authorization is required
    and all components/software of the IDS must be within the project's
    local subnet.

e.  Remote services, finger, and port mapper must be removed or
    disabled.

f.  All unused Transmission Control Protocol (TCP)/IP services on
    servers and systems must be disabled.

g.  All IT resources connected to the IONet either must have an
    automatic logoff or pause with password reactivation or must require
    users to pause/logoff during extended periods (30 minutes) of
    inactivity.

Note:

IT resources used for operations that are staffed 24 hours per day are
exempt from this requirement.

### Closed IONet Policies and Restrictions

All equipment connected to the Closed IONet must also adhere to the
following restrictions:

a.  Communications between systems on the Closed IONet, the Restricted
    IONet or Open IONet must be initiated by systems from the Closed
    IONet, including file transfer protocol (FTP) sessions. Exceptions
    require IONet NSO approval.

b.  Only a Closed IONet project/user may request connections (i.e.,
    firewall rules) to the Restricted IONet or Open IONet through the
    IONet Secure Gateway.

c.  Development systems are prohibited.

d.  E-mail servers are prohibited.

e.  Outbound X-Terminal display transmission is prohibited.

f.  Inbound FTP sessions must be limited and approved by the IONet NSO.

g.  Telnet sessions across the IONet are prohibited. Telnet is allowed
    only within the Mission Operations Center (MOC).

h.  Software development is prohibited.

i.  Project firewalls are prohibited.

j.  Restricted physical access to all equipment is required.

k.  Access from modems and other networks is prohibited.

l.  [Dual-homed](#DualHomed) systems are prohibited. (*Dual-homed* means
    the IT resource has two or more network interfaces, each connected
    to a different network.)

m.  Software on computers connected to the Closed IONet must be licensed
    or approved by project management.

Note:

[Firewalls](#Firewall) between local networks do not provide the
required isolation for the Closed IONet. Proposed plans to isolate
networks must be approved by the NSO.

### Restricted IONet Policies and Restrictions

All equipment connected to the Restricted IONet must also adhere to the
following conditions:

a.  Development systems are prohibited**.**

b.  Outbound X-Terminal display transmission is prohibited.

c.  Dual-homed systems are prohibited. (*Dual-homed* means that the IT
    resource has two or more network interfaces, each connected to a
    different network.)

d.  All e-mail into and out of the Restricted IONet must go through the
    ISD mail gateway. All other e-mail will be blocked. The mail gateway
    will offer pop service. All mail will be denied until this server is
    up.

e.  Only outbound FTP connections are allowed.

f.  Project firewalls will be allowed. At a minimum, they must meet the
    GSFC firewall rules set, and they must drop their firewall to allow
    for quarterly Goddard IT Security Vulnerability Scanning Team
    (GITSVST) scanning of 100 percent of NASA devices.

g.  All approved external connections behind the project firewall must
    be approved by the IONet NSO. All non-Restricted IONet connections
    must be certified.

h.  Non-encrypted connections to the Restricted IONet are allowed only
    from approved hosts on the Open IONet.

i.  X-term and telnet connections are allowed only from within the
    Restricted IONet.

### Open IONet Policies and Restrictions

All equipment connected to the Open IONet must also adhere to the
following restrictions:

a.  Encrypted data is permitted within the Open IONet; however,
    troubleshooting will not be provided. The IPNOC must be advised when
    using encrypted data transmissions.

b.  A project may implement an IDS on the project's local subnet.
    However, prior IONet NSO authorization is required, and all
    components/software of the IDS must be within the project's local
    subnet.

c.  The IONet NSO must approve all VPN or encrypted channels on the Open
    IONet case by case.

d.  Internet and modem connections are permitted with approval of the
    IONet NSO case by case.

e.  Dual-homed systems, including firewalls, must be configured to
    ensure that the proper level of network isolation is provided.
    Additionally, these systems must meet the requirements for boundary
    systems as listed in NPR 2810.1, paragraph A.7.4.4.

f.  Software on computers connected to the Open IONet must adhere to the
    software security policy of the NASA center, contractor, or
    international partner, or to the best security practices of
    government and industry.

g.  If required, an isolated network or server for public read-only
    access may be established.

## Communication Security (COMSEC)

The IONet does not provide COMSEC. Encryption is the responsibility of
the data owner. Encryption must be coordinated with and approved by the
IONet NSO.

Note:

IONet does not provide encryption and decryption of voice and data. If
COMSEC services are required, contact the IONet NSO, the IONet customer
service representative, or the NASA Integrated Services Network (NISN)
Network Service Manager (NSM) for assistance.

## Remote Control

Remote control of any configurable network component connected to the
Closed IONet (such as routers, switches, firewalls) is prohibited.

Note:

If additional security controls are in place, remote control of a
configurable network component may be permitted. This additional
security should be in the form of one-time passwords, VPN connection,
encrypted channel, secure modems, and so forth. The IONet NSO must
approve the additional security method before to the access is
implemented. Approval is granted case by case..

## Individual Accountability

Individuals are held accountable for their actions and must have an
individual account to access the IONet IT resources. Operational logs
can be used for this accountability. User identification and
[authentication](#Authentication) are performed through use of logon ID
and unique passwords, as specified in [NPR
2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main).

# ISD-Sponsored Audits

## Audit Team Authority and Responsibility

ISD has created an IONet audit team, hereinafter referred to as the
*audit team*, to perform security audits for projects connecting or
connected to the IONet. The audit team ensures that users comply with
the policy and requirements in this document and [NPR
2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main).
The audit team reports to and takes direction from the IONet NSO.

The IONet NSO has given the audit team authorization to view all
security features of a system being audited. This authorization includes
but is not limited to management controls, access controls, [audit
trails](#AuditTrail), password management, monitoring capabilities for
IT resources, security-related operational procedures, listings of all
authorized users, and interface descriptions.

The audit team will not attempt to gain physical access to or log onto
any system but may perform network scans during the audit process. The
audit team may also request a demonstration of or additional information
on any system security feature(s).

The audit team maintains security clearances for material up to the
SECRET level. Audit team members' security clearances are forwarded to
the Project/Site Security Office, upon request, before any site visit.

## Audit 

Any of the following activities will result in the initiation of an ISD
audit:

a.  Connection request -- All requests for new or additional connections
    to the IONet

b.  Project audits -- Expansion of a project's subnet connected to the
    IONet to support an additional spacecraft or mission

c.  IONet NSO requested audits -- Anytime the IONet NSO requests an
    audit

d.  Re-audits -- Performed approximately every 3 years or when a major
    configuration change occurs

e.  Incident triggered -- Anytime a project has had an IT security
    incident, such as a compromised system

### Connection Request 

The *customer service representative* at GSFC informs a project issuing
a connection request that a security audit will be performed in parallel
with the processing of the Communication Service Request (CSR) or a NISN
Service Request (NSR). The audit team or the customer service
representative requests the project POC to provide required
documentation (refer to [Section 5.2](#required-security-documentation)
of this document). The audit then proceeds as described in Section 4.3
of this document..

Note:

A project must be audited before the connection is approved and
implemented. [A minimum of 6 weeks is required for this
process.]{.underline}

### Project Audits and IONet NSO Requested Audits

Audits may be conducted at the request of a project or the IONet NSO. On
receiving an audit request, the audit team notifies the project of the
intent to conduct a security audit. The audit then proceeds as described
in Section 4.3 of this document.

### Re-Audits

A complete audit may be performed on all systems that have not been
audited in the last 3 years. Re-audits follow the standard audit process
described in Section 4.3 of this document.

Re-audits concentrate on the following:

a.  Correction of vulnerabilities identified in previous audits

b.  [Significant changes](#SignifChange) to the system configuration
    since the previous audit

A *significant change* is any modification that affects the security of
a critical system or general support system and requires a new risk
analysis. Significant changes include but are not limited to a
modification, deletion, or addition to a system that might reduce the
effectiveness of protective controls or necessitate additional
protection.

## Audit Process

The audit process is identical for all audits and proceeds as described
in Sections 4.3.1 through 4.3.6.

### Step 1 - Documentation Delivery

The project POC or designated person(s) completes the IONet Access
Control Compliance Checklist for the IT resource/network that has an
IONet interface. They also provide the audit team with all other
required documentation for the IT resource/network connection being
audited. (Hereafter, the IONet Access Control Compliance Checklist will
be referred to as *checklist*.)

Note:

The checklist, security plans, and risk analysis are considered ACI and
must not be sent via clear text e-mail because of the sensitivity of the
information.

### Step 2 - Documentation Review

The audit team reviews the checklist, the network diagram(s), data flow
diagram(s), security plan, Rules of Behavior, and risk analysis that are
required by [Section 5.2](#required-security-documentation) of this
document. The audit team may request the following types of additional
information:

a.  System-level block diagrams showing the major system components and
    external interfaces

b.  Operational procedures, especially if these procedures are part of
    the system security

c.  All waiver requests submitted or being submitted and those already
    approved for the system

d.  Firewall rules sets

### Step 3 - Question Follow-Ups

Documentation and checklist questions can be misinterpreted; information
can be incomplete; or the information can generate additional questions.
Therefore, it is often necessary for an audit team member to follow-up
on responses. Follow up is conducted through e-mail correspondence. A
detailed e-mail is written listing all open issues and questions that
must be addressed. This e-mail is the audit team's report back. In
addition, telephone conversations and/or face-to-face meetings can
occur. The POC or designated person(s) assists the audit team by
arranging for follow-up activities with the system managers (SMs) and
SAs and any other personnel who helped in completing the checklist. The
POC, or designate, must ensure the audit team's questions are answered.
The audit team updates each checklist based on information gained during
the follow-up.

### Step 4 - Optional Site Visit

Under certain circumstances, a physical site visit may be required. The
audit team determines whether a site visit is necessary based on
information obtained during documentation review and follow-up
activities. The audit team notifies the project about the intent to
conduct a site visit. The POC makes the necessary arrangements to
provide the audit team with visitor badges, if required. A knowledgeable
SM or SA conducts a system walkthrough with the audit team and is
prepared to perform any requested demonstrations.

Depending on the size of the individual project and the availability of
personnel, the audit team may perform security audits of more than one
project during a single visit to a site.

### Step 5 - Audit Findings

During the audit process, the audit team discusses its findings with the
POC or designated person(s). The findings are documented in a final
audit report. The audit team delivers the audit report to the IONet NSO.
The IONet NSO reviews the audit report and originates one of the
following:

a.  Approves a Connection -- An e-mail is sent to the POC, the IPNOC
    engineers, and the applicable IONet engineer to allow the connection
    or continue the connection based on the security audit findings.

b.  Directs Disconnection -- An e-mail is sent to the Project Mission
    Manager to identify the issues that have not been resolved. The
    e-mail will state the deadline by which they must be resolved and
    the date of disconnection if no response is received.

### Step 6 - Waiver Request

If the audit team identifies something that does not comply with IONet
requirements or [NPR
2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main),
the audit team notes the deficiency, brings it to the attention of the
project POC, and reports it in the audit report to the IONet NSO. The
IONet NSO requires the responsible manager either to correct the
deficiency or to submit a waiver request. The audit team then verifies
that the deficiencies have been corrected.

## Protection of Audit Report and Checklists

Audit reports and checklists may contain sensitive information.
Therefore, all completed checklists and reports are handled as ACI and
receive limited distribution only to those with a need to know.

# Connection Request Procedure and Required Security Documentation

## General

The procedure for obtaining a connection to the IONet includes the
preparation and submission of significant items of documentation and a
dialog with the CSR assigned to a project to ensure completeness.

## Required Security Documentation

The following documentation is required before a connection to the IONet
is granted:

a.  Security Plan (see [NPR
    2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main),
    Section 5)

b.  Risk Analysis/Risk Reduction (see [NPR
    2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main),
    Sections 4.2.10.4 & A.6.10.1)

c.  Completed IONet Access Control Compliance Checklist (located at
    <http://code297.gsfc.nasa.gov/docs/ionet.htm> )

d.  Detailed network and data flow diagrams

e.  Authorization to Process statement signed by the organizational
    Computer Security Official or Project Manager (see [NPR
    2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main),
    Section 3.5)

f.  Logon banner on all NASA-owned or NASA-funded IT systems (see [NPR
    2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main),
    Section 4.10.1)

g.  Individual signed statement of responsibility (see [NPR
    2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main),
    Section A.6. 2.1), often called *Rules of Behavior* (See [Appendix
    A](#sample-rules-of-behavior-for-it-resources-connected-to-the-closed-ionet).)

h.  Contingency/Disaster Recovery Plan (see [NPR
    2810.1](http://nodis3.gsfc.nasa.gov/library/displayDir.cfm?Internal_ID=N_PG_2810_0001_&page_name=main),
    Section 5.3)

i.  Review of firewall rules for project-controlled firewalls

In addition to the above documentation, the security team will perform a
[vulnerability](#Vulnerability) scan of all of the project's systems on
the network. In some cases, the team may also perform a physical audit.
The audit report and the email detailing the authorization to connect
must be completed and placed in the project's file before connection.

Note:

By NASA policy, the documentation listed above must all be approved and
signed not less than 30 days before the project's Mission Readiness
Review (MRR).

## Obtaining an IONet Connection

In addition to the IT security issues and paperwork that must be
addressed before obtaining a connection to the IONet, other issues must
be identified and worked. For assistance in these activities, projects
should contact their CSR or NSM. The CSR or NSM coordinates with various
Human Space Flight, Deep Space, Aeronautical, and Scientific Satellite
projects located at GSFC and around the world to identify and define the
requirements for global ground communication facilities and operations.
The CSR or NSM translates and finalizes these requirements into a
specified number of voice, data, and video services. This includes
requirements for switching, monitoring, and data bandwidth, as well as
the determination of the optimum circuit configuration consistent with
the technical and operational capability of the complex IONET. The CSR
or NSM makes recommendations and ensures authoritative validation of all
project requirements before commitment of detailed engineering effort
and agency funds. A listing of Customer Service Representatives is
available at <http://code294.gsfc.nasa.gov/projectassignments.html>. A
description of the complete Communications Service Request process for
any project communications requirement is provided in [Applicable
Document 1.4.j](#appdoc_k).

######## Sample Rules of Behavior for IT Resources Connected to the Closed IONet

The rules listed below are for the users of \<Project Name\> Information
Technology (IT) resources. The purpose of these rules is to increase
individual awareness and responsibility, and to ensure that all users
employ IT resources in an efficient, ethical, and lawful manner.

You understand that:

1.  Your IT resource account is established only for official use in the
    conduct of your assigned duties.

2.  You must protect all software on the IT resource in accordance with
    NASA and Federal Government security and control procedures. You
    must use licensed software in accordance with the license.

3.  You consent to monitoring and security testing to ensure proper
    security procedures and appropriate usage are being observed.

4.  You must not use the IT resources for fraudulent purposes,
    harassment, or obscene messages and/or materials.

5.  When you no longer need access to the IT resources, you must notify
    the appropriate responsible parties and make no further attempt to
    access these IT resources.

6.  You are not permitted to transmit X-terminal displays.

7.  You must not remove any IT resource from the facility without a
    property pass from the appropriate authority.

8.  You must erase fixed [media](#Media) prior to transferring the IT
    resources or designating the IT resources as excess.

9.  You are prohibited from tampering with another user\'s account,
    files or [processes](#Process) without the other user\'s express
    permission.

10. You are prohibited from using system resources for personal purposes
    or any other unauthorized activities.

11. You are prohibited from transferring or sharing Login IDs and
    passwords for any reason.

12. You must not leave active logons unattended. Workstations must be
    paused when unattended even for short periods of time (less than 30
    minutes).

13. You must not logon to more than one workstation/terminal unless they
    are under your constant surveillance.

14. You understand that all accounts on the IT resources require
    passwords.

15. Your passwords:

```{=html}
<!-- -->
```
a.  Must be a minimum of 8 characters consisting of 3 out of 4 of the
    following: lowercase alpha, numeric, uppercase alpha, and special
    character

b.  Must be changed at least every 90 days, 30 days for root/privileged
    user

c.  Must not appear in an English or foreign-language dictionary

d.  Must be memorized and not written down

e.  Must not be stored in keyboard macros or .bat files

f.  Must not consist of personal or easily guessed information

```{=html}
<!-- -->
```
16. You must challenge anyone in the facility that does not have the
    appropriate badge displayed.

17. The IT resource must be situated in locked rooms/buildings except
    when such workstations or terminals are located in continuously
    staffed operational areas.

18. You are not allowed Internet or modem access to the IT resource.

19. You must notify the System Administrator if you notice any unused
    service or port that has not been disabled on the IT resource.

20. You may not install any personal or downloaded software without
    prior management approval.

21. You must not enter any classified information into the IT resources.

22. You are not allowed to use e-mail, anonymous FTP, or telnet sessions
    on the Closed IONet.

23. You must report promptly any unauthorized penetration attempt,
    unauthorized system use, or virus activity to the system security
    official.

24. You must protect all system IP addresses and special use port
    numbers as sensitive information.

25. You are not allowed to perform any software development on IT
    resources connected to the Closed IONet.

You further understand that failure to adhere to these rules may
constitute grounds for termination of access privileges, administrative
action, and/or civil or criminal prosecution.

**Declaration**

I HAVE READ AND UNDERSTAND THE RULES OF BEHAVIOR FOR THE USE OF CLOSED
IONET INFORMATION TECHNOLOGY (IT) RESOURCES AND AGREE TO ABIDE BY THEM.

I fully understand my responsibilities as a user of this system/network.

User Name: (please print)
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

User Signature:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Organization Code/Contractor Name:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Date: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

######## IONet Access Protection Policy Waivers

## B.1 Waiver Process {#b.1-waiver-process .unnumbered}

If the project or IONet Audit Team uncovers a recognizable system
vulnerability that will not be corrected within 3 months, the project
must prepare and submit a waiver request to the IONet NSO.

The waiver request form provided at the end of this appendix contains
the format for the essential elements of a waiver request. The waiver
request form lists the primary subjects to be addressed (i.e., system
name, deficiency description, requested duration of the waiver,
justification, and mitigation). The responsible organization will
provide the description of the deficiency and the wording of the waiver
request necessary to allow an understanding and evaluation of the
deficiency by the IONet NSO. A detailed mitigation for the vulnerability
must be included. The mitigation should be explained in detail to ensure
it is fully understood. The IT resource name and deficiency description
should be sufficiently unique to allow their use to track the identity
of the submission. The responsible organization will submit each waiver
request on a separate form to assist in the control and processing of
requests.

However, there are certain Federal requirements that cannot be waived.
The following is a list of those requirements.

-   Participating in an IT Security Program (OMB Cir A-130)

-   Protecting personal information contained in a system of records (PL
    93-579, as amended) (Privacy Act)

-   Authorization of major applications (OMB Cir A-130)

-   Assessment, analysis and management of risks (OMB Cir A-130)

-   Personnel screening for IT access (OMB Cir A-130)

-   IT security awareness and training (OMB Cir A-130)

-   Response to and reporting of IT security incidents (OMB Cir A-130)

-   Mandatory compliance with National Institute of Standards and
    Technology (NIST) guidance

## B.2 Waiver Duration {#b.2-waiver-duration .unnumbered}

When a deficiency is recognized, the organization responsible for the IT
resource (sponsor) will estimate the time and cost to develop a
solution. An estimate of the length of time for which the waiver is
needed expedites the decision-making process for waiver approval and, in
addition, establishes a target date for rectification of the
vulnerability.

For convenience of reference, waivers have been divided into two
classes:

> Type 1: Temporary (3 to 6 months)
>
> Type 2: Long-term (7 to 12 months)

Note:

A waiver is valid for up to 1 year and must be renewed if the waived
condition has not been corrected by the end of 1 year.

B.3 Submission of Waiver Requests

All requests for waivers of security deficiencies found in an IT
resource interfacing with IONet shall be forwarded to:

Network Security Officer\
Information Services Division\
Code 290\
Goddard Space Flight Center\
Greenbelt, Maryland 20771\
Facsimile number: 301-286-1723

B.4 Waiver Approvals

The ISD will designate a team of communications engineers and IT
specialists to evaluate all waiver request submissions. If the
submission lacks adequate information for a comprehensive evaluation,
this team will contact the submitting sponsor for additional input.
Normally, this approval sequence will be completed within 60 days,
unless the waiver is of a magnitude that requires consultation with NASA
Headquarters.

### Internet Protocol Operational Network (IONet) Access Protection Policy Waiver Request {#internet-protocol-operational-network-ionet-access-protection-policy-waiver-request .unnumbered}

PROJECT NAME: DATE:

FACILITY: SYSTEM NAME:

TECHNICAL CONTACT: MAILING ADDRESS:

PHONE NUMBER: FAX NUMBER: EMAIL ADDRESS:

DESCRIPTION OF VULNERABILITY (keyed to policy or Checklist):

WAIVER REQUESTED (Specific operational deviation):

DESCRIPTION OF MITIGATION (Details of how vulnerability will be
mitigated)

TYPE (1, 2): 1 = Temporary (3 to 6 months)

2 = Long-Term (7 to 12 months)

ESTIMATED RESOLUTION DATE:

JUSTIFICATION (use additional sheets):

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Signature of Requester

\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\--

(To be filled out by IONet and returned to requester)

Date received: WR NO.
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Security Analyst:

Analyst\'s comments:

\_\_\_\_\_\_ APPROVED

\_\_\_\_\_\_ DISAPPROVED

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

IONet Network Security Officer (NSO)

\_\_\_\_\_\_\_ CONCUR Signature
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Date: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Chief, Information Services Division**,** Code 290

NOTE: Each deficiency is to be identified by a separate waiver request

[]{#__RefHeading___Toc58296384 .anchor}Glossary

[]{#glossary .anchor}Access A specific type of interaction between a
subject and an [object](#Object) that results in the flow of information
from one to the other.

Access Control The process of limiting accesses to information or
resources of a system to authorized users only.

[]{#Audit .anchor}Audit The official review, examination, and
verification of system records and activities to ensure the adequacy of
established IT security controls and procedures and to identify any
nonfunctional controls or new vulnerabilities.

[]{#AuditTrail .anchor}Audit Trail A set of records that collectively
provide documentary evidence of processing, used to aid in tracing from
the original transactions forward to related records and reports and
backward from records and reports to their component source
transactions.

[]{#Authentication .anchor}Authentication 1) The procedure of
identifying or verifying the eligibility of a station, originator, or
individual to access specific categories of information.

2\) The plan designed to provide protection against fraudulent
transmissions by establishing the validity of a transmission, message,
station, or originator.

[]{#Availability .anchor}Availability The state wherein information,
data, and systems are in the place needed by the user, at the proper
time, and in the form that the user requests.

[]{#Boundary .anchor}Boundary System A system that is topographically
located at the crossroads between an internal local area network
(LAN)/wide area network (WAN)and the Internet, usually associated with
routing, firewalling, and other security-oriented purposes; it provides
isolation and security services to the systems within a security
perimeter.

[]{#Confidentiality .anchor}Confidentiality The state that exists when
data are held in confidence and are protected from unauthorized
disclosure.

[]{#Control .anchor}Control Regulating access to the system.

[]{#DualBoot .anchor}Dual-boot System A computer system in which two
operating systems are installed on the same hard drive, allowing either
operating system to be loaded and given control.

[]{#DualHomed .anchor}Dual-Homed A computer system with two or more
network interfaces, each of which is connected to a different network.
In a firewall configuration, the firewall usually acts to block or
filter some or all of the traffic trying to pass between the networks.

[]{#dhcp .anchor}DHCP Dynamic Host Configuration Protocol is an Internet
Protocol used for automating the configuration of computers that use
TCP/IP. DHCP can be used to assign IP addresses automatically, to
deliver TCP/IP stack configuration parameters such as the subnet mask
and default router, and to provide other configuration information such
as the addresses for printer, time, and news servers.

[]{#Firewall .anchor}Firewall A collection of components used to block
or filter transmission of certain classes of traffic; the three types of
firewalls are packet filtering, circuit gateways, and application
gateways.

[]{#Identification .anchor}Identification The process of providing
personal, equipment, or organizational characteristics or codes to gain
access to computer resources.

[]{#InfoTech .anchor}IT The hardware and software operated by a Federal
agency or by a contractor of a Federal agency or other organization that
processes information on behalf of the Federal Government to accomplish
a Federal function, regardless of the technology involved, whether
computers, telecommunications systems, automatic data processing
equipment, or other.

[]{#InfoTechResource .anchor}IT Resources Data and information;
computers, ancillary equipment, software, firmware, and similar
products; facilities that house such resources; services, including
support services; and related resources used for the acquisition,
storage, manipulation, management, movement, control, display,
switching, interchange, transmission, or reception of data. IT resources
include telecommunications systems, network systems, and human
resources.

[]{#Integrity .anchor}Integrity The state that exists when computerized
data is the same as in the source documents or has been correctly
computed from source data and has not been exposed to accidental or
malicious alteration or destruction.

International Partners Foreign entities with which business and/or
research is conducted; foreign partners may include individuals, small
firms, large corporations, and/or foreign governments.

[]{#Internet .anchor}Internet A collection of two or more disparate
networks tied together via a common protocol, more specifically, the
global Internet of IP-linked computer networks.

[]{#Media .anchor}Media Any and all materials where data and/or
information may be stored, including floppy disks, Compact Disc -- Read
Only Memory (CD-ROMs), hard drives, software manuals, and papers.

> Discussion: different federal agencies, international partners, and
> institutions with which NASA does business have different security
> requirements and policies. In agencies with requirements that can be
> described as stricter than those of NASA, (e.g., the Department of
> Defense) the NASA requirements are considered to be included in those
> of the other agency. Those agencies with requirements considered less
> strict than those of NASA (e.g., a NOAA control center) will have to
> do whatever is necessary to come into compliance with NASA's
> requirements.

[]{#Network .anchor}Network A communications medium, and all components
attached to that medium, that is responsible for the transfer of
information. Such components may include computers, packet switches,
telecommunications controllers, key distribution centers, control
devices, and other networks.

[]{#Object .anchor}Object A passive entity that contains or receives
information. Access to an object potentially implies access to the
information it contains. Examples of objects are records, blocks, pages,
files, directories, directory trees, and programs, as well as bits,
bytes, words, fields, processors, video displays, keyboards, clocks,
printers, and network nodes.

[]{#Password .anchor}Password A protected word, phrase, or a string of
symbols that is used to authenticate the identity of a user. Knowledge
of the password associated with a particular user ID is considered proof
of authorization to use the capabilities associated with that user ID.

[]{#PhySec .anchor}Physical Security The application of measures
necessary to protect systems and their contents from damage by
intruders, fire, accident, and environmental hazards. These measures
include electronic security systems, sensors and alarms, lighting, other
physical security aids and equipment, and integrated operating
procedures.

[]{#Process .anchor}Process A program in execution. A process is
completely characterized by a single, current execution point
(represented by the machine state) and address space.

Risk Analysis The breakdown and dissection of perceived risks with
regard to IT security issues. Analysis of risk involves identifying
system vulnerabilities and potential system compromises and indexing the
findings in a detailed report.

[]{#Routers .anchor}Routers Routers connect LANs with common protocols
at the network layer and above. Because routers connect at the network
layer, they are protocol-sensitive and, thus, can link two TCP/IP,
DECnet, or Xerox Network System-based LANs, but not their combinations.

[]{#SecIncident .anchor}Security Incident Any circumstance or event,
that has harmed or has the potential to harm the system in the form of
destruction, disclosure, modification of data, and/or denial of service.

[]{#SctyMeas .anchor}Security Measures The physical, personnel,
information, communications, and computer security protective features
and procedures applied to systems and facilities to protect classified
information and national resources.

Security Plan A basic overview of the security and privacy requirements
of the subject system and the project\'s plan for meeting those
requirements.

[]{#SctyPolicy .anchor}Security Policy Security policies define access
limitations to a project LAN, WAN, Internet, Intranet, and Extranet.
Security policies must be established before other security provisions
can be implemented, such as firewalls and network security standards.
Security policies include:

-   Definitions of what is on the trusted and untrusted sides of the
    network

-   Policies for protocols to and from the Internet

-   Access limitations by group and by user to the project network
    resources, Intranet, and Extranet and to the Internet

-   Access limitations to network resources by external users, both
    project employees and others

[]{#SignifChange .anchor}Significant Change A modification that affects
the security of a critical system or general support system and that
requires a new risk analysis. A significant change includes but is not
limited to a change in the information category of data processed or
stored, replacement of IT equipment with equipment of a different type,
new IT equipment to perform new functions, new external interfaces,
major changes in connectivity, and relocation of or major changes to the
physical environment of an IT resource.

[]{#User .anchor}User Person or process accessing an IT resource either
by direct connection (i.e., via terminals) or by indirect connection
(i.e., via preparation of input data or receipt of output data that are
not reviewed for content or classification by a responsible individual).

[]{#Vulnerability .anchor}Vulnerability A weakness in system security
procedures, system designs, implementation, internal controls, or other
system elements that could be exploited to violate system security
policy.

[]{#Waiver .anchor}Waiver A formal grant of relief from meeting a
security standard or practice until a satisfactory solution can be
implemented to correct a known deficiency.

[]{#__RefHeading___Toc58296386 .anchor}Abbreviations and Acronyms

ACI Administratively Controlled Information

CCB Configuration Control Board

CCR Configuration Change Request

CD-ROM Compact Disc -- Read Only Memory

CM Configuration Management

CNE Center Network Environment

COMSEC Communications Security

CSR Communications Service Request

DCN Document Change Notice

DHCP Dynamic Host Configuration Protocol

DNS Domain Name Service

EC Engineering Change

E-mail Electronic Mail

FDDI Fiber Distributed Data Interface

FTP File Transfer Protocol

GITSVST Goddard Information Technology Security Vulnerability Scanning
Team

GPG Goddard Procedures and Guidelines

GSFC Goddard Space Flight Center

ID or IDs User Identifier(s)

IDS Intrusion Detection System

IONet Internet Protocol Operational Network

IP Internet Protocol

IPNOC IP Network Operations Center

ISD Information Services Division

IT Information Technology

ITS Information Technology Security

LAN or LANs Local Area Network(s)

LOP Local Operating Procedure

MOC Mission Operations Center

MOU Memorandum of Understanding

MRR Mission Readiness Review

MSN Mission

NAC National Agency Check

NASA National Aeronautics and Space Administration

NAT Network Address Translation

NEB Network Engineering Board

NFS Network File System

NIS Network Information System

NISN NASA Integrated Services Network

NPD NASA Policy Directive

NPR NASA Procedural Requirements

NSM NISN Service Manager

NSO Network Security Officer

NSR NISN Service Request

NTISSP National Telecommunications and Information Systems Security
Policy

OMB Office of Management and Budget

POC point of contact

RPC Remote Procedure Call

SA System Administrator

SCR Software Change Request

SM System Manager

SSA System Security Administrator

SSH Secure Shell (Secure Socket Shell)

SSL Secure Socket Layer

TCP Transmission Control Protocol

VLAN Virtual Local Area Network

VPN Virtual Private Network

WAN Wide Area Network

**290-004**

**Revision 3**