14.03.2015 Views

GOES-R MANAGEMENT CONTROL PLAN (MCP)

GOES-R MANAGEMENT CONTROL PLAN (MCP)

GOES-R MANAGEMENT CONTROL PLAN (MCP)

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

• DOC IT Security Program Policy and Minimum Implementation Standards<br />

• NIST SP 800-18, Revision 1, Guide for Developing Security Plans for Information Technology<br />

Systems.<br />

• NIST SP 800-28 Guidelines on Active Content and Mobile Code<br />

• NIST SP 800-30, Risk Management Guide for Information Technology Systems<br />

• NIST SP 800-34, Contingency Planning Guide for Information Technology Systems<br />

• NIST SP 800-37, Guide for the Security Certification and Accreditation of Federal Information<br />

Systems<br />

• NIST SP 800-42, Guideline on Network Security Testing<br />

• NIST SP 800-47, Security Guide for Interconnecting Information Technology Systems<br />

• NIST SP 800-53, and -53 Revision 1, Recommended Security Controls for Federal Information<br />

Systems<br />

• NIST SP 800-53A, Guide for Assessing Security Controls in Federal Information Systems<br />

• NIST SP 800-60, Guide for Mapping Types of Information and Information Systems to Security<br />

Categories<br />

• NIST SP 800-64, Security Consideration in the Information System Development Life Cycle<br />

• NIST SP 800-94, Guide to Intrusion Detection and Prevention Systems<br />

Other guidance utilized:<br />

• OMB A-130, Appendix III, Security of Federal Automated Information Resources<br />

• Federal Information Security Management Act of 2002<br />

• OMB M06-16, Protection of Sensitive Agency Information<br />

• Federal Information Processing Standard (FIPS) 200, Minimum Security Requirements for Federal<br />

Information and Information Systems<br />

• FIPS 199, Standard for Security Categorization of Federal Information and Information Systems<br />

• NOAA Administrative Order 212-13, Information Technology Security Policy<br />

• NOAA IT Security Manual, NOAA 212-1300 through 1305<br />

10 FACILITIES <strong>MANAGEMENT</strong><br />

For efficiency, the <strong>GOES</strong>-R Program intends to maximize collocation of personnel within the program<br />

and with <strong>GOES</strong> NOP and POES programs. Office space is allocated to each project/division based on<br />

current staffing requirements. Each project/division is responsible for assigning and managing office<br />

space within its allocated area, with approval from the DSPD. Each year, as a minimum, Program<br />

Control will assess space requirements and allocations with projects. This assessment will be reviewed<br />

by the SMT. Any significant changes in overall <strong>GOES</strong>-R space requirements will be managed via the<br />

GSFC space management board process.<br />

10.1 Co-located <strong>GOES</strong>-R Program and Project GSFC Offices<br />

The <strong>GOES</strong>-R Program and Ground Segment Project staff includes government and contractor personnel<br />

collocated on multiple floors within Building 6 at GSFC which share common resources such as power,<br />

water, telecommunications, computer support and other resources. The facilities are owned and operated<br />

by NASA and provided based upon a MOU agreement between NOAA and NASA, a copy of which can<br />

be found in Appendix B of this document.<br />

10.2 NOAA Satellite Operations Facility (NSOF) Spaces<br />

Space for up to 30 <strong>GOES</strong>-R Program/Ops Project staff members (government and contractors) will be<br />

required at NSOF during the A&O Phase of the GS implementation. This is to ensure that proper<br />

oversight and management can be provided through this phase.<br />

Page 58 of 75

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!