Test 2015-01-15-1052 ([project acronym not provided]) [project id not provided] System Security Plan

System Environment

{This section should discuss the physical environment of the information system including any special circumstances that may increase the risk of the operating the system - For example: The system does not not reside in a DHS Datacenter (DC1 or DC2).

This section should also detail any system elements, hardware or software that mitigates the security risks of operating the system. }

8. NSS Physical Environment Considerations

{This section should address the types of encryption solutions deployed for the information system.}

Table 1-11 NSS Physical Environment Considerations

Is the secure facility authorized or approved to process and store information at the level covered by this SSP?	[ ]Yes [ ] No
Who authorized or approved the facility?
Provide date and location of approval letter.
State the classification and level approved for the facility.	[ ] Secret [ ] Top Secret [ ] Others (Please Specify)
Is the system approved for unattended processing?	[ ]Yes [ ] No
Is the facility approved for 24-hour operation?	[ ]Yes [ ] No

9. System Interconnection/Information Sharing

1. Information Flow

{This section should discuss how data flows across each interconnection listed in the tables above as well as describe the flow of data across key internal system boundaries.}

2. System Interconnections

There is no system interconnection/information sharing associated with your project.

3. Cross Domain Solutions

{Is there a Cross Domain Solution associated with the system? A CDS is required for any information that crosses a security domain electronically. Manual (i.e., sneaker-net) transfers must also be identified. If there is a cross domain system associated with the system a table like the one below should be completed. }

Table 1-13: Cross Domain Solutions

Hostname	MFR	Model	Version	Ticket No.	Location

4. Cloud Service Layers

Information systems, particularly those based on cloud architecture models, are made up of different service layers. The layers of the Test_2015-01-15-1052 that are defined in this SSP, and are not leveraged by any other Provisional Authorizations, are indicated in the table that follows.

Table 1-14: Cloud Service Layers Represented in this SSP

Service Provider Architecture Layers
[ ]	Software as a Service (SaaS)	Major Application
[ ]	Platform as a Service (PaaS)	Major Application
[ ]	Infrastructure as a Service (IaaS)	General Support System
[ ]	Other	Explain:

5. Mobile Code

{This section should declare the use and approval of any mobile code deployed within the boundaries of the information system.}

6. Ports, Protocols, & Services

10. Privacy Considerations

{Section 208 of the E-Government Act of 2002 and Section 522 of the Consolidated Appropriations Act of 2005 require that when developing or procuring IT systems or projects that collect, use, store, and/or disclose information in identifiable form from or about members of the public or organization employees (the latter prescribed by sect. 522), to identify potential privacy risks and implement appropriate privacy controls and compliance requirements. Insert the system "does" or "does not" contain privacy information. Determine and document if the Privacy Act applies to this system. If the Privacy Act applies and the system contains privacy information, insert a reference to privacy-related documentation (e.g., A Privacy Impact Assessment (PIA), Privacy Threshold Analysis (PTA) was conducted as part of the current authorization process), and the date the documentation was submitted.}

11.