X hits on this document

33 views

0 shares

0 downloads

0 comments

7 / 12

<Project Name>

Categorization – Based on an estimate of FIPS 199 impact, this system is provisionally defined as a <LOW, MODERATE or HIGH>

Boundaries –  [Describe at a high-level what security services or components are to be included in the part of the system]

Dependencies –  [Describe the security services or components being inherited from a GSS or MA]

Interconnections – [Describe other system interconnections established for data sharing, business continuity, or backup]

4.2 Sub-Systems

Description – <System Name> is a new system under development intended to <describe system purpose>.  

Security Manager – [Identify the security manager for this system]

Characterization – <System Name> is characterized as a <GSS, MA, or Other>.  

Categorization – Based on an estimate of FIPS 199 impact, this system is provisionally defined as a <LOW, MODERATE or HIGH>

Boundaries –  [Describe at a high-level what security services or components are to be included in the part of the system]

Dependencies –  [Describe the security services or components being inherited from a GSS or MA]

Interconnections – [Describe other system interconnections established for data sharing, business continuity, or backup]

4.3 Interconnected Systems

Description – <System Name>  is a new system under development intended to <describe system purpose>.  

Security Contact – [Include contact information for this system]

Interconnections – [Describe other system interconnections established for data sharing, business continuity, or backup]

5 PROGRAMMATIC activities

[Use this section to define administrative and management activities that support the overall security approach.  These include activities such as training, configuration management, risk management, and communication plans.]

5.1 Team Training

[Outline specific training related to security.  Include any database or developer training that applies to development activities.  Include any specific rules of behavior or special security considerations on which team members need to be educated.]

5.2 Requirements Management

Baseline security requirements for each system have been integrated into the Requirements Management process documented in <Project Management or Requirements Management document name> located on <full network path

EPLC Security Approach (v<1.0>)Page 6 of 12

[Insert appropriate disclaimer(s)]

Document info
Document views33
Page views33
Page last viewedSat Dec 10 12:49:41 UTC 2016
Pages12
Paragraphs226
Words1820

Comments