Executive Summary
The objective of system security planning is to improve protection of information
technology (IT) resources. All federal systems have some level of sensitivity and require
protection as part of good management practice. The protection of a system must be documented in a system security plan. The completion of system security plans is a
requirement of the Office of Management and Budget (0MB) Circular A- 130, "Management of Federal hiformation Resources," Appendix III, "Security of Federal Automated Information Resources," and Public Law 100-235, "Computer Security Act of
1987."
The purpose of the security plan is to provide an overview of the security requirements of
the system and describe the controls in place or plarmed for meeting those requirements. The system security plan also delineates responsibilities and expected behavior of all
individuals who access the system. The security plan should be viewed as documentation
of the structured process of planning adequate, cost-effective security protection for a
system. It should reflect input from various managers with responsibilities concerning
the system, including information owners, the system operator, and the system security
manager. Additional information may be included in the basic plan and the structure and
format organized according to agency needs, so long as the major sections described in
this document are adequately covered and readily identifiable.
In order for the plans to adequately reflect the protection of the resources, a management
official must authorize a system to process information or operate. The authorization of a
system to process information, granted by a management official, provides an important
quality control. By authorizing processing in a system, the manager accepts its
associated risk.
Management authorization should be based on an assessment of management,
operational, and technical controls. Since the security plan establishes and documents the
security controls, it should form the basis for the authorization, supplemented by more
specific studies as needed. In addition, a periodic review of controls should also
contribute to fiiture authorizations. Re-authorization should occur prior to a significant
change in processing, but at least every three years. It should be done more often where
there is a high risk and potential magnitude of harm.
iii
Guide for Developing Security
Plans for Information Technology Systems
1
Introduction
Today's rapidly changing technical environment requires federal agencies to adopt a minimum set of management controls to protect their information technology (IT)
resources. These management controls are directed at individual information technology
users in order to reflect the distributed nature of today's technology. Technical and
operational controls support management controls. To be effective, these controls all must interrelate. This document provides a guideline for federal agencies to follow when
developing the security plans that document the management, technical, and operational
controls for federal automated information systems.
1.1
Background
The completion of system security plans is a requirement of the Office of Management and Budget (0MB) Circular A- 130, "Management of Federal Information Resources,"
Appendix EI, "Security of Federal Automated hiformation Resources," updated in 1996,
and of Public Law 100-235, "Computer Security Act of 1987."
0MB Circular A- 130, Appendix III, does not distinguish between sensitive and non-
sensitive systems. Rather, consistent with the Computer Security Act of 1987, the
Circular recognizes that federal automated information systems have varied sensitivity and criticality. All federal systems have some level of sensitivity and require protection
as part of good management practice. The generic term "system" is used in this document to mean either a major application or a general support system.
* 1.2 Major Application or General Support System Plans
All applications and systems must be covered by system security plans if they are
categorized as a "major application" or "general support system." Specific security
plans for other applications are not required because the security controls for those
applications or systems would be provided by the general support systems in which they
operate. For example, a department-wide Financial Management System would be a major application requiring its own security plan. A local program designed to track
expenditures against an office budget might not be considered a major application and would be covered by a general support system security plan for an office automation
system or a local area network (LAN). Standard commercial off-the-shelf software (such
as word processing software, electronic mail software, utility software, or other general-
purpose software) would not typically be considered a major application and would be
covered by the plans for the general support system on which they are installed.
1 Usefor All Systems
Guide for Developing Security
Plans for Information Technology Systems
1.5 Security Plan Responsibilities
The System Owner' is responsible for ensuring that the security plan is prepared and for implementing the plan and monitoring its effectiveness. Security plans should reflect
input from various individuals with responsibilities concerning the system, including
functional "end users," Information Owners,^ the System Administrator, and the System
Security Manager.
Agencies may require contractor compliance with this guide as a contract requirement. A
security plan in the format specified in this document or in another agreed upon format is suggested in those cases where vendors are operating a system under contract to the
federal government. In those instances where a contractor or other entity (e.g., state or
local government) operates a system that supports a federal function, a security plan is
required.
0MB Circular A- 130 requires a summary of the security plan to be incorporated into the
strategic IRM plan required by the Paperwork Reduction Act (44 U.S.C. Chapter 35).
Agencies should develop policy on the security planning process. Security plans are
living documents that require periodic reviews, modifications, and milestone or completion dates for planned controls. Procedures should be in place outlining who
reviews the plans and follows up on planned controls. In addition, procedures are needed
describing how security plans will be used in the authorization for processing process.
1.6 Recommended Format
While the format in this guide is recommended, it is recognized that some agencies have developed plans using other formats that meet the A- 130 requirements described in this document. This document is intended as guidance only and should not be construed as
the only format allowed. A standardized approach, however, not only makes the development of the plan easier by providing examples, but also provides a baseline to
review plans. The level of detail included within the plan should be consistent with the
criticality and value of the system to the organization's mission (i.e., a more detailed plan
is required for systems critical to the organization's mission). The security plan should
fiilly identify and describe the controls currently in place or planned for the system and
should include a list of rules of behavior.
The System Owner is responsible for defming the system's operating parameters, authorized
functions, and security requirements. The information owner for information stored within, processed by,
or transmitted by a system may or may not be the same as the System Owner. Also, a single system may
utilize information from multiple Information Owners.
^ The Information Owner is responsible for establishing the rules for appropriate use and protection
of the subject data/information (rules of behavior). The Information Ovmer retains that responsibility even when the data/information are shared with other organizations.
3 Usefor All Systems
Guide for Developing Security
Plans for Information Technology Systems
Describe the primary computing platform(s) used (e.g., mainframe, desk top, LAN or Wide Area Network (WAN). Include a general description of the principal system components, including hardware, software, and communications resources. Discuss the
type of communications included (e.g., dedicated circuits, dial circuits, public data/voice
networks, Internet). Describe controls used to protect communication lines in the
appropriate sections of the security plan.
Include any security software protecting the system and information. Describe in general
terms the type of security protection provided (e.g., access control to the computing
platform and stored files at the operating system level or access to data records within an
application). Include only controls that have been implemented or are planned, rather
than listing the controls that are available in the software. Controls that are available, but
not implemented, provide no protection.
3.6 System Interconnection/Information Sharing
System interconnection is the direct connection of systems for the purpose of sharing
information resources. System interconnection, if not appropriately protected, may result
in a compromise of all connected systems and the data they store, process, or transmit. It
is important that system operators, information owners, and management obtain as much
information as possible about the vulnerabilities associated with system interconnection and information sharing and the increased controls required to mitigate those
vulnerabilities. The security plan for the systems often serves as a mechanism to effect
this security information exchange and allows management to make informed decisions
regarding risk reduction and acceptance.
0MB Circular A- 130 requires that written management authorization (often in the form
of a Memorandum of Understanding or Agreement,) be obtained prior to connecting with
other systems and/or sharing sensitive data/information. The written authorization shall
detail the rules of behavior and controls that must be maintained by the interconnecting
systems. A description of the rules for interconnecting systems and for protecting shared
data must be included with this security plan. See Section 4.3, Rules of Behavior.
In this section, provide the following information concerning the authorization for the
connection to other systems or the sharing of information:
• List of interconnected systems (including Internet);
• Unique system identifiers, if appropriate;
• Name of system(s);
• Organization owning the other system(s);
• Type of interconnection (TCP/IP, Dial, SNA, etc.);
13 Usefor All Systems
Guide for Developing Security
Plans for Information Technology Systems
• Short discussion of major concerns or considerations in determining interconnection
(do not repeat the system rules included in Section 4.3);
• Name and title of authorizing management official(s);
• Date of authorization;
• System of Record, if applicable (Privacy Act data);
• Sensitivity level of each system;
• Interaction among systems; and
• Security concerns and Rules of Behavior of the other systems that need to be
considered in the protection of this system.
3.7 Sensitivity of Information Handled
This section provides a description of the types of information handled by the system and
an analysis of the criticality of the information. The sensitivity and criticality of the
information stored within, processed by, or transmitted by a system provides a basis for
the value of the system and is one of the major factors in risk management. The
description will provide information to a variety of users, including:
• Analysts/programmers who will use it to help design appropriate security controls;
• Internal and external auditors evaluating system security measures; and
• Managers making decisions about the reasonableness of security countermeasures.
The nature of the information sensitivity and criticality must be described in this section. The description must contain information on applicable laws, regulations, and policies
affecting the system and a general description of sensitivity as discussed below.
3.7.1 Laws, Regulations, and Policies Affecting the System
List any laws, regulations, or policies that establish specific requirements for
confidentiality, integrity, or availability of data/information in the system. The Computer Security Act of 1987, 0MB Circular A- 130, and general agency security
requirements need not be listed since they mandate security for all systems. Each
organization should decide on the level of laws, regulations, and policies to include in the
security plan. Examples might include the Privacy Act or a specific statute or regulation concerning the information processed (e.g., tax or census information). If the system
14 Usefor All Systems
Guide for Developing Security
Plans for Information Technology Systems
4 Management Controls
In this seetion, describe the management control measures (in place or planned) that are
intended to meet the protection requirements of the major application or general support
system. Management controls focus on the management of the computer security system and the management of risk for a system. The types of control measures shall be
consistent with the need for protection of the major application or general support system. To aid the reader, a brief explanation of the various management controls is provided.
For more detail on management controls, see NIST Special Publication 800-12, An
Introduction to Computer Security: The NIST Handbook.
4.1 Risk Assessment and Management
0MB Circular A- 130 no longer requires the preparation of a formal risk analysis. It
does, however, require an assessment of risk as part of a risk-based approach to
determining adequate, cost-effective security for a system. The methods used to assess
the nature and level of risk to the system should include a consideration of the major
factors in risk management: the value of the system or application, threats,
vulnerabilities, and the effectiveness of current or proposed safeguards. The methods
used should be described in at least one paragraph. For example, did the selected risk
assessment methodology identify threats, vulnerabilities, and the additional security measures required to mitigate or eliminate the potential that those threats/vuhierabilities
could have on the system or its assets? Include the date that the system risk assessment was conducted. State how the identified risks relate to the requirements for
confidentiality, integrity, and availability determined for the system.
If there is no risk assessment for your system, include a milestone date (month and year)
for completion of the risk assessment. If the risk assessment is more than three years old
or there have been major changes to the system or functions, include a milestone date (month and year) for completion of a new or updated risk assessment. Assessing the risk
to a system should be an ongoing activity to ensure that new threats and vulnerabilities
are identified and appropriate security measures are implemented.
4.2 Review of Security Controls
0MB Circular A- 130 requires that at least every three years an independent review of the
security controls for each major application be performed. For general support systems, 0MB Circular A- 130 requires that the security controls be reviewed by an independent
audit or self review at least every three years. Describe the type of review and findings
conducted on the general support system or major application in the last three years.
Include information about the last independent audit or review of the system and who
conducted the review. Discuss any findings or recommendations from the review and
include information concerning correction of any deficiencies or completion of any
recommendations. Indicate if the review identified a deficiency reportable under 0MB
19 Usefor All Systems
Guide for Developing Security
Plans for Information Technology Systems
examines either the system or the users, hi general, the more "real-time" an activity
is, the more it falls into the category of monitoring.
4.4.5 Disposal Phase
The disposal phase of the IT system life cycle involves the disposition of information,
hardware, and software. If the system or part of the system is at the end of the life cycle,
briefly describe in this section how the following items are disposed:
• Information. Information may be moved to another system, archived, discarded, or
destroyed. When archiving information, consider the method for retrieving the
information in the future. While electronic information is generally easier to retrieve and store, the technology used to create the records may not be readily available in
the ftiture. Measures may also have to be taken for the future use of data that has been encrypted, such as taking appropriate steps to ensure the secure long-term
storage of cryptographic keys. It is important to consider legal requirements for
records retention when disposing of IT systems. For federal systems, system management officials should consult with their office responsible for retaining and
archiving federal records.
• Media Sanitization. The removal of information from a storage medium (such as a
hard disk or tape) is called sanitization. Different kinds of sanitization provide
different levels of protection. A distinction can be made between clearing
information (rendering it unrecoverable by keyboard attack) and purging (rendering
information unrecoverable against laboratory attack). There are three general methods of purging media: overwriting, degaussing (for magnetic media only), and
destruction.
4.5 Authorize Processing
The term "authorize processing" is the authorization granted by a management official
for a system to process information. (Note: Some agencies refer to this authorization as
accreditation.) Authorization provides a form of quality control and is required under 0MB Circular A- 130. It forces managers and technical staff to find the best fit for
security, given technical constraints, operational constraints, and mission requirements. By authorizing processing in a system, a manager accepts the risk associated with it. In
this section of the plan, include the date of authorization, name, and title of management
official. If not authorized, provide the name and title of manager requesting approval to
operate and date of request.
Both the security official and the authorizing management official have security
responsibilities. The security official is closer to the day-to-day operation of the system and will direct, perform, or monitor security tasks. The authorizing official will normally have general responsibility for the organization supported by the system. Authorization is
24 Usefor All Systems
Guide for Developing Security
Plans for Information Technology Systems
5.MA.8 Security Awareness and Training
The Computer Security Act requires federal agencies to provide for the mandatory
periodic training in computer security awareness and accepted computer security
practices for all employees who are involved with the management, use, or operation of a
federal computer system within or under the supervision of the federal agency. This
includes contractors as well as employees of the agency. 0MB Circular A- 130, Appendix III, issued in 1996, enforces such mandatory training by requiring its
completion prior to granting access to the system and through periodic refresher training
for continued access. Therefore, each user must be versed in acceptable rules of
behavior for the application before being allowed access to the system. The training program should also inform the user on how to get help when having difficulty using the
system and procedures for reporting security incidents.
Access provided to members of the public should be constrained by controls in the
applications, and training should be within the context of those controls and may consist
only of notification at the time of access.
hiclude in this section of the plan information about the following:
• The awareness program for the application (posters, booklets, and trinkets).
• The type and frequency of application-specific training provided to employees and
contractor personnel (seminars, workshops, formal classroom, focus groups, role-
based training, and on-the-job training).
• The type and frequency of general support system training provided to employees and
contractor personnel (seminars, workshops, formal classroom, focus groups, role-
based training, and on-the-job training).
• The procedures for assuring that employees and contractor personnel have been
provided adequate training.
Note: Contractor employees are required to receive the same level of automated
information systems security awareness and training as federal employees. This training
requirement should be included as appropriate in all contracts.
36 Usefor Major Application
Guide for Developing Security
Plans for Information Technology Systems
contractors as well as employees of the agency. 0MB Circular A- 130, Appendix III,
issued in 1 996, enforces such mandatory training by requiring its completion prior to
granting access to the system and through periodic refresher training for continued
access. Therefore, each user must be versed in acceptable rules of behavior for the system before being allowed access to the system. The training program should also
inform the user on how to get help when having difficulty using the system and
procedures for reporting security incidents.
Access provided to members of the public should be constrained by controls in the
applications, and training should be within the context of those controls and may consist
only of notification at the time of access.
Include in this section of the plan information about the following:
• The awareness program for the system (posters, booklets, and trinkets).
• The type and frequency of system-specific training provided to employees and
contractor personnel (seminars, workshops, formal classroom, focus groups, role- based training, and on-the-job training).
• The procedures for assuring that employees and contractor personnel have been
provided adequate training.
Note: Contractor employees are required to receive the same level of automated
information systems security awareness and training as federal employees. This training
requirement should be included as appropriate in all contracts.
5.GSS.9 Incident Response Capability
A computer security incident is an adverse event in a computer system or network caused by a failure of a security mechanism or an attempted or threatened breach of these mechanisms\ Computer security incidents are becoming more common and their impact
far-reaching. When faced with an incident, an organization should be able to respond
quickly in a manner that both protects its own information and helps to protect the
information of others that might be affected by the incident. 0MB Circular A- 130
requires each agency to ensure that there is a capability to provide help to users when a
security incident occurs in the system and to share information concerning common
vulnerabilities and threats. In this section, describe the incident handling procedures in
place for the general support system. Areas of consideration include:
^ Schultz, Brown, Longstaff Responding to Computer Security Incidents: Guidelines for Incident
Handling, U.C. Technical Report UCRL- 1 04689, 1 990.
Usefor General Support System
Appendix E
References
References
Guttman, Barbara and Roback, Edward An Introduction to Computer Security: The NIST Handbook. Special Publication 800-12. Gaithersburg, MD: National Institute of
Standards and Technology, October 1995.
NIST Computer Security Resource Clearinghouse Web site URL: http://csrc.nist.gov
Office of Management and Budget. Circular A- 130, "Management of Federal
Information Resources," Appendix III, "Security of Federal Automated Information
Resources." 1996.
Public Law 100-235, "Computer Security Act of 1987."
[Schultz90] Schultz, Eugene. Project Leader, Lawrence Livermore National Laboratory. CERT Workshop, Pleasanton, CA, 1990.
Swanson, Marianne and Guttman, Barbara . Generally Accepted Principles and Practices
for Securing Information Technology Systems. Special Publication 800- 1 4.
Gaithersburg, MD: National Institute of Standards and Technology, September 1996.
IE
Index
0MB Circular A- 130, Appendix III, 1, 36, 56 one-way encryption, 39, 60
overwrite, 31,51
password, 21, 34, 38, 39, 41, 54, 59, 60, 62
personnel security, 27, 47
PIN, 38, 59, 60
planned, iii, 2, 3, 6, 13, 19, 23, 25, 27, 37, 47, 48, 52, 58
policies, 14, 25, 33, 35, 39, 40, 53, 55, 60, 61
processing, iii, 1, 3, 6, 7, 8, 12, 23, 24, 25, 27, 32, 34, 43, 47, 52, 54, 55, 64
reconciliation, 34, 54
risk, iii, 6, 13, 14, 15, 16, 19, 20, 21, 24, 25, 27, 28, 29, 47, 48, 49
risk assessment, 6, 19, 20, 25
risk management, 14, 15, 19, 20
rules, 3, 5, 13, 14, 20, 21, 25, 35, 36, 47, 55, 56
screen warning banner, 42, 63
security awareness and training, 2 1 , 36, 56
security responsibility, 20
sensitivity, iii, 1, 6, 9, 14, 15, 22, 25, 27, 31, 42, 47, 51, 63
sensitivity level, 9, 27, 47
separation of duties, 27, 40, 45, 47, 61, 65
storage, 5, 18, 24, 31, 39, 41, 44, 51, 61, 62
system boundaries, 5
system identification, 9
system interconnection, 1
3
technical controls, iii, 4, 1 1, 20, 23, 25, 27, 37, 41, 47, 58, 62
threat, 28, 44, 48
token, 38, 59, 60
unauthorized access, 16, 37, 41, 58, 62
vulnerabilities, 5, 13, 19, 22, 41, 56, 57, 62, 3, 12 wide area network, 4 1 , 62