+SC System and Communications Protection
---+SC-01 Policy and Procedures
---+SC-02 Separation of System and User Functionality
------+SC-02(01) Interfaces for Non-privileged Users
------+SC-02(02) Disassociability
---+SC-03 Security Function Isolation
------+SC-03(01) Hardware Separation
------+SC-03(02) Access and Flow Control Functions
------+SC-03(03) Minimize Nonsecurity Functionality
------+SC-03(04) Module Coupling and Cohesiveness
------+SC-03(05) Layered Structures
---+SC-04 Information in Shared System Resources
------+SC-04(02) Multilevel or Periods Processing
---+SC-05 Denial-of-service Protection
------+SC-05(01) Restrict Ability to Attack Other Systems
------+SC-05(02) Capacity, Bandwidth, and Redundancy
------+SC-05(03) Detection and Monitoring
---+SC-06 Resource Availability
---+SC-07 Boundary Protection
------+SC-07(03) Access Points
------+SC-07(04) External Telecommunications Services
------+SC-07(05) Deny by Default — Allow by Exception
------+SC-07(07) Split Tunneling for Remote Devices
------+SC-07(08) Route Traffic to Authenticated Proxy Servers
------+SC-07(09) Restrict Threatening Outgoing Communications Traffic
------+SC-07(10) Prevent Exfiltration
------+SC-07(11) Restrict Incoming Communications Traffic
------+SC-07(12) Host-based Protection
------+SC-07(13) Isolation of Security Tools, Mechanisms, and Support Components
------+SC-07(14) Protect Against Unauthorized Physical Connections
------+SC-07(15) Networked Privileged Accesses
------+SC-07(16) Prevent Discovery of System Components
------+SC-07(17) Automated Enforcement of Protocol Formats
------+SC-07(18) Fail Secure
------+SC-07(19) Block Communication from Non-organizationally Configured Hosts
------+SC-07(20) Dynamic Isolation and Segregation
------+SC-07(21) Isolation of System Components
------+SC-07(22) Separate Subnets for Connecting to Different Security Domains
------+SC-07(23) Disable Sender Feedback on Protocol Validation Failure
------+SC-07(24) Personally Identifiable Information
------+SC-07(25) Unclassified National Security System Connections
------+SC-07(26) Classified National Security System Connections
------+SC-07(27) Unclassified Non-national Security System Connections
------+SC-07(28) Connections to Public Networks
------+SC-07(29) Separate Subnets to Isolate Functions
---+SC-08 Transmission Confidentiality and Integrity
------+SC-08(01) Cryptographic Protection
------+SC-08(02) Pre- and Post-transmission Handling
------+SC-08(03) Cryptographic Protection for Message Externals
------+SC-08(04) Conceal or Randomize Communications
------+SC-08(05) Protected Distribution System
---+SC-09 Transmission Confidentiality
---+SC-10 Network Disconnect
---+SC-11 Trusted Path
------+SC-11(01) Irrefutable Communications Path
---+SC-12 Cryptographic Key Establishment and Management
------+SC-12(01) Availability
------+SC-12(02) Symmetric Keys
------+SC-12(03) Asymmetric Keys
------+SC-12(06) Physical Control of Keys
---+SC-13 Cryptographic Protection
---+SC-14 Public Access Protections
---+SC-15 Collaborative Computing Devices and Applications
------+SC-15(01) Physical or Logical Disconnect
------+SC-15(03) Disabling and Removal in Secure Work Areas
------+SC-15(04) Explicitly Indicate Current Participants
---+SC-16 Transmission of Security and Privacy Attributes
------+SC-16(01) Integrity Verification
------+SC-16(02) Anti-spoofing Mechanisms
------+SC-16(03) Cryptographic Binding
---+SC-17 Public Key Infrastructure Certificates
---+SC-18 Mobile Code
------+SC-18(01) Identify Unacceptable Code and Take Corrective Actions
------+SC-18(02) Acquisition, Development, and Use
------+SC-18(03) Prevent Downloading and Execution
------+SC-18(04) Prevent Automatic Execution
------+SC-18(05) Allow Execution Only in Confined Environments
---+SC-19 Voice Over Internet Protocol
---+SC-20 Secure Name/Address Resolution Service (Authoritative Source)
------+SC-20(02) Data Origin and Integrity
---+SC-21 Secure Name/Address Resolution Service (Recursive or Caching Resolver)
---+SC-22 Architecture and Provisioning for Name/Address Resolution Service
---+SC-23 Session Authenticity
------+SC-23(01) Invalidate Session Identifiers at Logout
------+SC-23(03) Unique System-generated Session Identifiers
------+SC-23(05) Allowed Certificate Authorities
---+SC-24 Fail in Known State
---+SC-25 Thin Nodes
---+SC-26 Decoys
---+SC-27 Platform-independent Applications
---+SC-28 Protection of Information at Rest
------+SC-28(01) Cryptographic Protection
------+SC-28(02) Offline Storage
------+SC-28(03) Cryptographic Keys
---+SC-29 Heterogeneity
------+SC-29(01) Virtualization Techniques
---+SC-30 Concealment and Misdirection
------+SC-30(02) Randomness
------+SC-30(03) Change Processing and Storage Locations
------+SC-30(04) Misleading Information
------+SC-30(05) Concealment of System Components
---+SC-31 Covert Channel Analysis
------+SC-31(01) Test Covert Channels for Exploitability
------+SC-31(02) Maximum Bandwidth
------+SC-31(03) Measure Bandwidth in Operational Environments
---+SC-32 System Partitioning
------+SC-32(01) Separate Physical Domains for Privileged Functions
---+SC-33 Transmission Preparation Integrity
---+SC-34 Non-modifiable Executable Programs
------+SC-34(01) No Writable Storage
------+SC-34(02) Integrity Protection on Read-only Media
---+SC-35 External Malicious Code Identification
---+SC-36 Distributed Processing and Storage
------+SC-36(01) Polling Techniques
------+SC-36(02) Synchronization
---+SC-37 Out-of-band Channels
------+SC-37(01) Ensure Delivery and Transmission
---+SC-38 Operations Security
---+SC-39 Process Isolation
------+SC-39(01) Hardware Separation
------+SC-39(02) Separate Execution Domain Per Thread
---+SC-40 Wireless Link Protection
------+SC-40(01) Electromagnetic Interference
------+SC-40(02) Reduce Detection Potential
------+SC-40(03) Imitative or Manipulative Communications Deception
------+SC-40(04) Signal Parameter Identification
---+SC-41 Port and I/O Device Access
---+SC-42 Sensor Capability and Data
------+SC-42(01) Reporting to Authorized Individuals or Roles
------+SC-42(02) Authorized Use
------+SC-42(04) Notice of Collection
------+SC-42(05) Collection Minimization
---+SC-43 Usage Restrictions
---+SC-44 Detonation Chambers
---+SC-45 System Time Synchronization
------+SC-45(01) Synchronization with Authoritative Time Source
------+SC-45(02) Secondary Authoritative Time Source
---+SC-46 Cross Domain Policy Enforcement
---+SC-47 Alternate Communications Paths
---+SC-48 Sensor Relocation
------+SC-48(01) Dynamic Relocation of Sensors or Monitoring Capabilities
---+SC-49 Hardware-enforced Separation and Policy Enforcement
---+SC-50 Software-enforced Separation and Policy Enforcement
---+SC-51 Hardware-based Protection
|
SC System and Communications Protection
System and Communications Protection
1. Oversigt
| Titel |
Standard |
|
SC-01 Policy and Procedures
|
Control
- Develop, document, and disseminate to [Assignement: organization-defined personnel or roles]:
- [Selection(one-or-more): organization-level; mission/business-process-level; system-level] system and communications protection policy that:
- Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
- Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
- Procedures to facilitate the implementation of the system and communications protection policy and the associated system and communications protection controls;
- Designate an [Assignement: official] to manage the development, documentation, and dissemination of the system and communications protection policy and procedures; and
- Review and update the current system and communications protection:
- Policy [Assignement: frequency] and following [Assignement: events] ; and
- Procedures [Assignement: frequency] and following [Assignement: events].
Discussion
System and communications protection policy and procedures address the controls in the SC family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of system and communications protection policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to system and communications protection policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
Assessment Objective
- a system and communications protection policy is developed and documented;
- the system and communications protection policy is disseminated to [Assignement: personnel or roles];
- system and communications protection procedures to facilitate the implementation of the system and communications protection policy and associated system and communications protection controls are developed and documented;
- the system and communications protection procedures are disseminated to [Assignement: personnel or roles];
- the [Selection(one-or-more): organization-level; mission/business-process-level; system-level] system and communications protection policy addresses purpose;
- the [Selection(one-or-more): organization-level; mission/business-process-level; system-level] system and communications protection policy addresses scope;
- the [Selection(one-or-more): organization-level; mission/business-process-level; system-level] system and communications protection policy addresses roles;
- the [Selection(one-or-more): organization-level; mission/business-process-level; system-level] system and communications protection policy addresses responsibilities;
- the [Selection(one-or-more): organization-level; mission/business-process-level; system-level] system and communications protection policy addresses management commitment;
- the [Selection(one-or-more): organization-level; mission/business-process-level; system-level] system and communications protection policy addresses coordination among organizational entities;
- the [Selection(one-or-more): organization-level; mission/business-process-level; system-level] system and communications protection policy addresses compliance;
- the [Selection(one-or-more): organization-level; mission/business-process-level; system-level] system and communications protection policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines;
- the [Assignement: official] is designated to manage the development, documentation, and dissemination of the system and communications protection policy and procedures;
- the current system and communications protection policy is reviewed and updated [Assignement: frequency];
- the current system and communications protection policy is reviewed and updated following [Assignement: events];
- the current system and communications protection procedures are reviewed and updated [Assignement: frequency];
- the current system and communications protection procedures are reviewed and updated following [Assignement: events].
Assessment Method
Examine
System and communications protection policy
system and communications protection procedures
system security plan
privacy plan
risk management strategy documentation
audit findings
other relevant documents or records
Interview
Organizational personnel with system and communications protection responsibilities
organizational personnel with information security and privacy responsibilities
|
|
SC-02 Separation of System and User Functionality
|
Control
Separate user functionality, including user interface services, from system management functionality.
Discussion
System management functionality includes functions that are necessary to administer databases, network components, workstations, or servers. These functions typically require privileged user access. The separation of user functions from system management functions is physical or logical. Organizations may separate system management functions from user functions by using different computers, instances of operating systems, central processing units, or network addresses; by employing virtualization techniques; or some combination of these or other methods. Separation of system management functions from user functions includes web administrative interfaces that employ separate authentication methods for users of any other system resources. Separation of system and user functions may include isolating administrative interfaces on different domains and with additional access controls. The separation of system and user functionality can be achieved by applying the systems security engineering design principles in [SA-8](#sa-8) , including [SA-8(1)](#sa-8.1), [SA-8(3)](#sa-8.3), [SA-8(4)](#sa-8.4), [SA-8(10)](#sa-8.10), [SA-8(12)](#sa-8.12), [SA-8(13)](#sa-8.13), [SA-8(14)](#sa-8.14) , and [SA-8(18)](#sa-8.18).
Assessment Objective
user functionality, including user interface services, is separated from system management functionality.
Assessment Method
Examine
System and communications protection policy
procedures addressing application partitioning
system design documentation
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
system developer
|
|
SC-03 Security Function Isolation
|
Control
Isolate security functions from nonsecurity functions.
Discussion
Security functions are isolated from nonsecurity functions by means of an isolation boundary implemented within a system via partitions and domains. The isolation boundary controls access to and protects the integrity of the hardware, software, and firmware that perform system security functions. Systems implement code separation in many ways, such as through the provision of security kernels via processor rings or processor modes. For non-kernel code, security function isolation is often achieved through file system protections that protect the code on disk and address space protections that protect executing code. Systems can restrict access to security functions using access control mechanisms and by implementing least privilege capabilities. While the ideal is for all code within the defined security function isolation boundary to only contain security-relevant code, it is sometimes necessary to include nonsecurity functions as an exception. The isolation of security functions from nonsecurity functions can be achieved by applying the systems security engineering design principles in [SA-8](#sa-8) , including [SA-8(1)](#sa-8.1), [SA-8(3)](#sa-8.3), [SA-8(4)](#sa-8.4), [SA-8(10)](#sa-8.10), [SA-8(12)](#sa-8.12), [SA-8(13)](#sa-8.13), [SA-8(14)](#sa-8.14) , and [SA-8(18)](#sa-8.18).
Assessment Objective
security functions are isolated from non-security functions.
Assessment Method
Examine
System and communications protection policy
procedures addressing security function isolation
list of security functions to be isolated from non-security functions
system design documentation
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
system developer
|
|
SC-04 Information in Shared System Resources
|
Control
Prevent unauthorized and unintended information transfer via shared system resources.
Discussion
Preventing unauthorized and unintended information transfer via shared system resources stops information produced by the actions of prior users or roles (or the actions of processes acting on behalf of prior users or roles) from being available to current users or roles (or current processes acting on behalf of current users or roles) that obtain access to shared system resources after those resources have been released back to the system. Information in shared system resources also applies to encrypted representations of information. In other contexts, control of information in shared system resources is referred to as object reuse and residual information protection. Information in shared system resources does not address information remanence, which refers to the residual representation of data that has been nominally deleted; covert channels (including storage and timing channels), where shared system resources are manipulated to violate information flow restrictions; or components within systems for which there are only single users or roles.
Assessment Objective
- unauthorized information transfer via shared system resources is prevented;
- unintended information transfer via shared system resources is prevented.
Assessment Method
Examine
System and communications protection policy
procedures addressing information protection in shared system resources
system design documentation
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
system developer
|
|
SC-05 Denial-of-service Protection
|
Control
- [Selection: protect against; limit] the effects of the following types of denial-of-service events: [Assignement: types of denial-of-service events] ; and
- Employ the following controls to achieve the denial-of-service objective: [Assignement: controls by type of denial-of-service event].
Discussion
Denial-of-service events may occur due to a variety of internal and external causes, such as an attack by an adversary or a lack of planning to support organizational needs with respect to capacity and bandwidth. Such attacks can occur across a wide range of network protocols (e.g., IPv4, IPv6). A variety of technologies are available to limit or eliminate the origination and effects of denial-of-service events. For example, boundary protection devices can filter certain types of packets to protect system components on internal networks from being directly affected by or the source of denial-of-service attacks. Employing increased network capacity and bandwidth combined with service redundancy also reduces the susceptibility to denial-of-service events.
Assessment Objective
- the effects of [Assignement: types of denial-of-service events] are [Selection: protect against; limit];
- [Assignement: controls by type of denial-of-service event] are employed to achieve the denial-of-service protection objective.
Assessment Method
Examine
System and communications protection policy
procedures addressing denial-of-service protection
system design documentation
list of denial-of-service attacks requiring employment of security safeguards to protect against or limit effects of such attacks
list of security safeguards protecting against or limiting the effects of denial-of-service attacks
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel with incident response responsibilities
system developer
|
|
SC-06 Resource Availability
|
Control
Protect the availability of resources by allocating [Assignement: resources] by [Selection(one-or-more): priority; quota; {{ insert: param, sc-06_odp.03 }} ].
Discussion
Priority protection prevents lower-priority processes from delaying or interfering with the system that services higher-priority processes. Quotas prevent users or processes from obtaining more than predetermined amounts of resources.
Assessment Objective
the availability of resources is protected by allocating [Assignement: resources] by [Selection(one-or-more): priority; quota; {{ insert: param, sc-06_odp.03 }} ].
Assessment Method
Examine
System and communications protection policy
procedures addressing prioritization of system resources
system design documentation
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
system developer
|
|
SC-07 Boundary Protection
|
Control
- Monitor and control communications at the external managed interfaces to the system and at key internal managed interfaces within the system;
- Implement subnetworks for publicly accessible system components that are [Selection: physically; logically] separated from internal organizational networks; and
- Connect to external networks or systems only through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security and privacy architecture.
Discussion
Managed interfaces include gateways, routers, firewalls, guards, network-based malicious code analysis, virtualization systems, or encrypted tunnels implemented within a security architecture. Subnetworks that are physically or logically separated from internal networks are referred to as demilitarized zones or DMZs. Restricting or prohibiting interfaces within organizational systems includes restricting external web traffic to designated web servers within managed interfaces, prohibiting external traffic that appears to be spoofing internal addresses, and prohibiting internal traffic that appears to be spoofing external addresses. [SP 800-189](#f5edfe51-d1f2-422e-9b27-5d0e90b49c72) provides additional information on source address validation techniques to prevent ingress and egress of traffic with spoofed addresses. Commercial telecommunications services are provided by network components and consolidated management systems shared by customers. These services may also include third party-provided access lines and other service elements. Such services may represent sources of increased risk despite contract security provisions. Boundary protection may be implemented as a common control for all or part of an organizational network such that the boundary to be protected is greater than a system-specific boundary (i.e., an authorization boundary).
Assessment Objective
- communications at external managed interfaces to the system are monitored;
- communications at external managed interfaces to the system are controlled;
- communications at key internal managed interfaces within the system are monitored;
- communications at key internal managed interfaces within the system are controlled;
- subnetworks for publicly accessible system components are [Selection: physically; logically] separated from internal organizational networks;
- external networks or systems are only connected to through managed interfaces consisting of boundary protection devices arranged in accordance with an organizational security and privacy architecture.
Assessment Method
Examine
System and communications protection policy
procedures addressing boundary protection
list of key internal boundaries of the system
system design documentation
boundary protection hardware and software
system configuration settings and associated documentation
enterprise security architecture documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
system developer
organizational personnel with boundary protection responsibilities
|
|
SC-08 Transmission Confidentiality and Integrity
|
Control
Protect the [Selection(one-or-more): confidentiality; integrity] of transmitted information.
Discussion
Protecting the confidentiality and integrity of transmitted information applies to internal and external networks as well as any system components that can transmit information, including servers, notebook computers, desktop computers, mobile devices, printers, copiers, scanners, facsimile machines, and radios. Unprotected communication paths are exposed to the possibility of interception and modification. Protecting the confidentiality and integrity of information can be accomplished by physical or logical means. Physical protection can be achieved by using protected distribution systems. A protected distribution system is a wireline or fiber-optics telecommunications system that includes terminals and adequate electromagnetic, acoustical, electrical, and physical controls to permit its use for the unencrypted transmission of classified information. Logical protection can be achieved by employing encryption techniques.
Organizations that rely on commercial providers who offer transmission services as commodity services rather than as fully dedicated services may find it difficult to obtain the necessary assurances regarding the implementation of needed controls for transmission confidentiality and integrity. In such situations, organizations determine what types of confidentiality or integrity services are available in standard, commercial telecommunications service packages. If it is not feasible to obtain the necessary controls and assurances of control effectiveness through appropriate contracting vehicles, organizations can implement appropriate compensating controls.
Assessment Objective
the [Selection(one-or-more): confidentiality; integrity] of transmitted information is/are protected.
Assessment Method
Examine
System and communications protection policy
procedures addressing transmission confidentiality and integrity
system design documentation
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
system developer
|
|
SC-09 Transmission Confidentiality
|
Control
Discussion
Assessment Objective
Assessment Method
Examine
Interview
|
|
SC-10 Network Disconnect
|
Control
Terminate the network connection associated with a communications session at the end of the session or after [Assignement: time period] of inactivity.
Discussion
Network disconnect applies to internal and external networks. Terminating network connections associated with specific communications sessions includes de-allocating TCP/IP address or port pairs at the operating system level and de-allocating the networking assignments at the application level if multiple application sessions are using a single operating system-level network connection. Periods of inactivity may be established by organizations and include time periods by type of network access or for specific network accesses.
Assessment Objective
the network connection associated with a communication session is terminated at the end of the session or after [Assignement: time period] of inactivity.
Assessment Method
Examine
System and communications protection policy
procedures addressing network disconnect
system design documentation
security plan
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
system developer
|
|
SC-11 Trusted Path
|
Control
- Provide a [Selection: physically; logically] isolated trusted communications path for communications between the user and the trusted components of the system; and
- Permit users to invoke the trusted communications path for communications between the user and the following security functions of the system, including at a minimum, authentication and re-authentication: [Assignement: security functions].
Discussion
Trusted paths are mechanisms by which users can communicate (using input devices such as keyboards) directly with the security functions of systems with the requisite assurance to support security policies. Trusted path mechanisms can only be activated by users or the security functions of organizational systems. User responses that occur via trusted paths are protected from modification by and disclosure to untrusted applications. Organizations employ trusted paths for trustworthy, high-assurance connections between security functions of systems and users, including during system logons. The original implementations of trusted paths employed an out-of-band signal to initiate the path, such as using the key, which does not transmit characters that can be spoofed. In later implementations, a key combination that could not be hijacked was used (e.g., the + + keys). Such key combinations, however, are platform-specific and may not provide a trusted path implementation in every case. The enforcement of trusted communications paths is provided by a specific implementation that meets the reference monitor concept.
Assessment Objective
- a [Selection: physically; logically] isolated trusted communication path is provided for communications between the user and the trusted components of the system;
- users are permitted to invoke the trusted communication path for communications between the user and the [Assignement: security functions] of the system, including authentication and re-authentication, at a minimum.
Assessment Method
Examine
System and communications protection policy
procedures addressing trusted communication paths
security plan
system design documentation
system configuration settings and associated documentation
assessment results from independent, testing organizations
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
system developer
|
|
SC-12 Cryptographic Key Establishment and Management
|
Control
Establish and manage cryptographic keys when cryptography is employed within the system in accordance with the following key management requirements: [Assignement: requirements].
Discussion
Cryptographic key management and establishment can be performed using manual procedures or automated mechanisms with supporting manual procedures. Organizations define key management requirements in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines and specify appropriate options, parameters, and levels. Organizations manage trust stores to ensure that only approved trust anchors are part of such trust stores. This includes certificates with visibility external to organizational systems and certificates related to the internal operations of systems. [NIST CMVP](#1acdc775-aafb-4d11-9341-dc6a822e9d38) and [NIST CAVP](#84dc1b0c-acb7-4269-84c4-00dbabacd78c) provide additional information on validated cryptographic modules and algorithms that can be used in cryptographic key management and establishment.
Assessment Objective
- cryptographic keys are established when cryptography is employed within the system in accordance with [Assignement: requirements];
- cryptographic keys are managed when cryptography is employed within the system in accordance with [Assignement: requirements].
Assessment Method
Examine
System and communications protection policy
procedures addressing cryptographic key establishment and management
system design documentation
cryptographic mechanisms
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel with responsibilities for cryptographic key establishment and/or management
|
|
SC-13 Cryptographic Protection
|
Control
- Determine the [Assignement: cryptographic uses] ; and
- Implement the following types of cryptography required for each specified cryptographic use: [Assignement: types of cryptography].
Discussion
Cryptography can be employed to support a variety of security solutions, including the protection of classified information and controlled unclassified information, the provision and implementation of digital signatures, and the enforcement of information separation when authorized individuals have the necessary clearances but lack the necessary formal access approvals. Cryptography can also be used to support random number and hash generation. Generally applicable cryptographic standards include FIPS-validated cryptography and NSA-approved cryptography. For example, organizations that need to protect classified information may specify the use of NSA-approved cryptography. Organizations that need to provision and implement digital signatures may specify the use of FIPS-validated cryptography. Cryptography is implemented in accordance with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.
Assessment Objective
- [Assignement: cryptographic uses] are identified;
- [Assignement: types of cryptography] for each specified cryptographic use (defined in SC-13_ODP[01]) are implemented.
Assessment Method
Examine
System and communications protection policy
procedures addressing cryptographic protection
system design documentation
system configuration settings and associated documentation
cryptographic module validation certificates
list of FIPS-validated cryptographic modules
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
system developer
organizational personnel with responsibilities for cryptographic protection
|
|
SC-14 Public Access Protections
|
Control
Discussion
Assessment Objective
Assessment Method
Examine
Interview
|
|
SC-15 Collaborative Computing Devices and Applications
|
Control
- Prohibit remote activation of collaborative computing devices and applications with the following exceptions: [Assignement: exceptions where remote activation is to be allowed] ; and
- Provide an explicit indication of use to users physically present at the devices.
Discussion
Collaborative computing devices and applications include remote meeting devices and applications, networked white boards, cameras, and microphones. The explicit indication of use includes signals to users when collaborative computing devices and applications are activated.
Assessment Objective
- remote activation of collaborative computing devices and applications is prohibited except [Assignement: exceptions where remote activation is to be allowed];
- an explicit indication of use is provided to users physically present at the devices.
Assessment Method
Examine
System and communications protection policy
procedures addressing collaborative computing
access control policy and procedures
system design documentation
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
system developer
organizational personnel with responsibilities for managing collaborative computing devices
|
|
SC-16 Transmission of Security and Privacy Attributes
|
Control
Associate [Assignement: organization-defined security and privacy attributes] with information exchanged between systems and between system components.
Discussion
Security and privacy attributes can be explicitly or implicitly associated with the information contained in organizational systems or system components. Attributes are abstractions that represent the basic properties or characteristics of an entity with respect to protecting information or the management of personally identifiable information. Attributes are typically associated with internal data structures, including records, buffers, and files within the system. Security and privacy attributes are used to implement access control and information flow control policies; reflect special dissemination, management, or distribution instructions, including permitted uses of personally identifiable information; or support other aspects of the information security and privacy policies. Privacy attributes may be used independently or in conjunction with security attributes.
Assessment Objective
- [Assignement: security attributes] are associated with information exchanged between systems;
- [Assignement: security attributes] are associated with information exchanged between system components;
- [Assignement: privacy attributes] are associated with information exchanged between systems;
- [Assignement: privacy attributes] are associated with information exchanged between system components.
Assessment Method
Examine
System and communications protection policy
procedures addressing the transmission of security and privacy attributes
access control policy and procedures
information flow control policy
system design documentation
system configuration settings and associated documentation
system audit records
system security plan
privacy plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security and privacy responsibilities
|
|
SC-17 Public Key Infrastructure Certificates
|
Control
- Issue public key certificates under an [Assignement: certificate policy] or obtain public key certificates from an approved service provider; and
- Include only approved trust anchors in trust stores or certificate stores managed by the organization.
Discussion
Public key infrastructure (PKI) certificates are certificates with visibility external to organizational systems and certificates related to the internal operations of systems, such as application-specific time services. In cryptographic systems with a hierarchical structure, a trust anchor is an authoritative source (i.e., a certificate authority) for which trust is assumed and not derived. A root certificate for a PKI system is an example of a trust anchor. A trust store or certificate store maintains a list of trusted root certificates.
Assessment Objective
- public key certificates are issued under [Assignement: certificate policy] , or public key certificates are obtained from an approved service provider;
- only approved trust anchors are included in trust stores or certificate stores managed by the organization.
Assessment Method
Examine
System and communications protection policy
procedures addressing public key infrastructure certificates
public key certificate policy or policies
public key issuing process
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel with responsibilities for issuing public key certificates
service providers
|
|
SC-18 Mobile Code
|
Control
- Define acceptable and unacceptable mobile code and mobile code technologies; and
- Authorize, monitor, and control the use of mobile code within the system.
Discussion
Mobile code includes any program, application, or content that can be transmitted across a network (e.g., embedded in an email, document, or website) and executed on a remote system. Decisions regarding the use of mobile code within organizational systems are based on the potential for the code to cause damage to the systems if used maliciously. Mobile code technologies include Java applets, JavaScript, HTML5, WebGL, and VBScript. Usage restrictions and implementation guidelines apply to both the selection and use of mobile code installed on servers and mobile code downloaded and executed on individual workstations and devices, including notebook computers and smart phones. Mobile code policy and procedures address specific actions taken to prevent the development, acquisition, and introduction of unacceptable mobile code within organizational systems, including requiring mobile code to be digitally signed by a trusted source.
Assessment Objective
- acceptable mobile code is defined;
- unacceptable mobile code is defined;
- acceptable mobile code technologies are defined;
- unacceptable mobile code technologies are defined;
- the use of mobile code is authorized within the system;
- the use of mobile code is monitored within the system;
- the use of mobile code is controlled within the system.
Assessment Method
Examine
System and communications protection policy
procedures addressing mobile code
mobile code implementation policy and procedures
list of acceptable mobile code and mobile code technologies
list of unacceptable mobile code and mobile technologies
authorization records
system monitoring records
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel with responsibilities for managing mobile code
|
|
SC-19 Voice Over Internet Protocol
|
Control
Technology-specific; addressed as any other technology or protocol.
Discussion
Assessment Objective
Assessment Method
Examine
Interview
|
|
SC-20 Secure Name/Address Resolution Service (Authoritative Source)
|
Control
- Provide additional data origin authentication and integrity verification artifacts along with the authoritative name resolution data the system returns in response to external name/address resolution queries; and
- Provide the means to indicate the security status of child zones and (if the child supports secure resolution services) to enable verification of a chain of trust among parent and child domains, when operating as part of a distributed, hierarchical namespace.
Discussion
Providing authoritative source information enables external clients, including remote Internet clients, to obtain origin authentication and integrity verification assurances for the host/service name to network address resolution information obtained through the service. Systems that provide name and address resolution services include domain name system (DNS) servers. Additional artifacts include DNS Security Extensions (DNSSEC) digital signatures and cryptographic keys. Authoritative data includes DNS resource records. The means for indicating the security status of child zones include the use of delegation signer resource records in the DNS. Systems that use technologies other than the DNS to map between host and service names and network addresses provide other means to assure the authenticity and integrity of response data.
Assessment Objective
- additional data origin authentication is provided along with the authoritative name resolution data that the system returns in response to external name/address resolution queries;
- integrity verification artifacts are provided along with the authoritative name resolution data that the system returns in response to external name/address resolution queries;
- the means to indicate the security status of child zones (and if the child supports secure resolution services) is provided when operating as part of a distributed, hierarchical namespace;
- the means to enable verification of a chain of trust among parent and child domains when operating as part of a distributed, hierarchical namespace is provided.
Assessment Method
Examine
System and communications protection policy
procedures addressing secure name/address resolution services (authoritative source)
system design documentation
system configuration settings and associated documentation
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel with responsibilities for managing DNS
|
|
SC-21 Secure Name/Address Resolution Service (Recursive or Caching Resolver)
|
Control
Request and perform data origin authentication and data integrity verification on the name/address resolution responses the system receives from authoritative sources.
Discussion
Each client of name resolution services either performs this validation on its own or has authenticated channels to trusted validation providers. Systems that provide name and address resolution services for local clients include recursive resolving or caching domain name system (DNS) servers. DNS client resolvers either perform validation of DNSSEC signatures, or clients use authenticated channels to recursive resolvers that perform such validations. Systems that use technologies other than the DNS to map between host and service names and network addresses provide some other means to enable clients to verify the authenticity and integrity of response data.
Assessment Objective
- data origin authentication is requested for the name/address resolution responses that the system receives from authoritative sources;
- data origin authentication is performed on the name/address resolution responses that the system receives from authoritative sources;
- data integrity verification is requested for the name/address resolution responses that the system receives from authoritative sources;
- data integrity verification is performed on the name/address resolution responses that the system receives from authoritative sources.
Assessment Method
Examine
System and communications protection policy
procedures addressing secure name/address resolution services (recursive or caching resolver)
system design documentation
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel with responsibilities for managing DNS
|
|
SC-22 Architecture and Provisioning for Name/Address Resolution Service
|
Control
Ensure the systems that collectively provide name/address resolution service for an organization are fault-tolerant and implement internal and external role separation.
Discussion
Systems that provide name and address resolution services include domain name system (DNS) servers. To eliminate single points of failure in systems and enhance redundancy, organizations employ at least two authoritative domain name system servers—one configured as the primary server and the other configured as the secondary server. Additionally, organizations typically deploy the servers in two geographically separated network subnetworks (i.e., not located in the same physical facility). For role separation, DNS servers with internal roles only process name and address resolution requests from within organizations (i.e., from internal clients). DNS servers with external roles only process name and address resolution information requests from clients external to organizations (i.e., on external networks, including the Internet). Organizations specify clients that can access authoritative DNS servers in certain roles (e.g., by address ranges and explicit lists).
Assessment Objective
- the systems that collectively provide name/address resolution services for an organization are fault-tolerant;
- the systems that collectively provide name/address resolution services for an organization implement internal role separation;
- the systems that collectively provide name/address resolution services for an organization implement external role separation.
Assessment Method
Examine
System and communications protection policy
procedures addressing architecture and provisioning for name/address resolution services
access control policy and procedures
system design documentation
assessment results from independent testing organizations
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel with responsibilities for managing DNS
|
|
SC-23 Session Authenticity
|
Control
Protect the authenticity of communications sessions.
Discussion
Protecting session authenticity addresses communications protection at the session level, not at the packet level. Such protection establishes grounds for confidence at both ends of communications sessions in the ongoing identities of other parties and the validity of transmitted information. Authenticity protection includes protecting against "man-in-the-middle" attacks, session hijacking, and the insertion of false information into sessions.
Assessment Objective
the authenticity of communication sessions is protected.
Assessment Method
Examine
System and communications protection policy
procedures addressing session authenticity
system design documentation
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
|
|
SC-24 Fail in Known State
|
Control
Fail to a [Assignement: known system state] for the following failures on the indicated components while preserving [Assignement: system state information] in failure: [Assignement: types of system failures on system components].
Discussion
Failure in a known state addresses security concerns in accordance with the mission and business needs of organizations. Failure in a known state prevents the loss of confidentiality, integrity, or availability of information in the event of failures of organizational systems or system components. Failure in a known safe state helps to prevent systems from failing to a state that may cause injury to individuals or destruction to property. Preserving system state information facilitates system restart and return to the operational mode with less disruption of mission and business processes.
Assessment Objective
[Assignement: types of system failures on system components] fail to a [Assignement: known system state] while preserving [Assignement: system state information] in failure.
Assessment Method
Examine
System and communications protection policy
procedures addressing system failure to known state
system design documentation
system configuration settings and associated documentation
list of failures requiring system to fail in a known state
state information to be preserved in system failure
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
system developer
|
|
SC-25 Thin Nodes
|
Control
Employ minimal functionality and information storage on the following system components: [Assignement: system components].
Discussion
The deployment of system components with minimal functionality reduces the need to secure every endpoint and may reduce the exposure of information, systems, and services to attacks. Reduced or minimal functionality includes diskless nodes and thin client technologies.
Assessment Objective
- minimal functionality for [Assignement: system components] is employed;
- minimal information storage on [Assignement: system components] is allocated.
Assessment Method
Examine
System and communications protection policy
procedures addressing use of thin nodes
system design documentation
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
|
|
SC-26 Decoys
|
Control
Include components within organizational systems specifically designed to be the target of malicious attacks for detecting, deflecting, and analyzing such attacks.
Discussion
Decoys (i.e., honeypots, honeynets, or deception nets) are established to attract adversaries and deflect attacks away from the operational systems that support organizational mission and business functions. Use of decoys requires some supporting isolation measures to ensure that any deflected malicious code does not infect organizational systems. Depending on the specific usage of the decoy, consultation with the Office of the General Counsel before deployment may be needed.
Assessment Objective
- components within organizational systems specifically designed to be the target of malicious attacks are included to detect such attacks;
- components within organizational systems specifically designed to be the target of malicious attacks are included to deflect such attacks;
- components within organizational systems specifically designed to be the target of malicious attacks are included to analyze such attacks.
Assessment Method
Examine
System and communications protection policy
procedures addressing the use of decoys
system design documentation
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
system developer
|
|
SC-27 Platform-independent Applications
|
Control
Include within organizational systems the following platform independent applications: [Assignement: platform-independent applications].
Discussion
Platforms are combinations of hardware, firmware, and software components used to execute software applications. Platforms include operating systems, the underlying computer architectures, or both. Platform-independent applications are applications with the capability to execute on multiple platforms. Such applications promote portability and reconstitution on different platforms. Application portability and the ability to reconstitute on different platforms increase the availability of mission-essential functions within organizations in situations where systems with specific operating systems are under attack.
Assessment Objective
[Assignement: platform-independent applications] are included within organizational systems.
Assessment Method
Examine
System and communications protection policy
procedures addressing platform-independent applications
system design documentation
system configuration settings and associated documentation
list of platform-independent applications
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
system developer
|
|
SC-28 Protection of Information at Rest
|
Control
Protect the [Selection(one-or-more): confidentiality; integrity] of the following information at rest: [Assignement: information at rest].
Discussion
Information at rest refers to the state of information when it is not in process or in transit and is located on system components. Such components include internal or external hard disk drives, storage area network devices, or databases. However, the focus of protecting information at rest is not on the type of storage device or frequency of access but rather on the state of the information. Information at rest addresses the confidentiality and integrity of information and covers user information and system information. System-related information that requires protection includes configurations or rule sets for firewalls, intrusion detection and prevention systems, filtering routers, and authentication information. Organizations may employ different mechanisms to achieve confidentiality and integrity protections, including the use of cryptographic mechanisms and file share scanning. Integrity protection can be achieved, for example, by implementing write-once-read-many (WORM) technologies. When adequate protection of information at rest cannot otherwise be achieved, organizations may employ other controls, including frequent scanning to identify malicious code at rest and secure offline storage in lieu of online storage.
Assessment Objective
the [Selection(one-or-more): confidentiality; integrity] of [Assignement: information at rest] is/are protected.
Assessment Method
Examine
System and communications protection policy
procedures addressing the protection of information at rest
system design documentation
system configuration settings and associated documentation
cryptographic mechanisms and associated configuration documentation
list of information at rest requiring confidentiality and integrity protections
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
system developer
|
|
SC-29 Heterogeneity
|
Control
Employ a diverse set of information technologies for the following system components in the implementation of the system: [Assignement: system components].
Discussion
Increasing the diversity of information technologies within organizational systems reduces the impact of potential exploitations or compromises of specific technologies. Such diversity protects against common mode failures, including those failures induced by supply chain attacks. Diversity in information technologies also reduces the likelihood that the means adversaries use to compromise one system component will be effective against other system components, thus further increasing the adversary work factor to successfully complete planned attacks. An increase in diversity may add complexity and management overhead that could ultimately lead to mistakes and unauthorized configurations.
Assessment Objective
a diverse set of information technologies is employed for [Assignement: system components] in the implementation of the system.
Assessment Method
Examine
System and communications protection policy
system design documentation
system configuration settings and associated documentation
list of technologies deployed in the system
acquisition documentation
acquisition contracts for system components or services
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel with system acquisition, development, and implementation responsibilities
|
|
SC-30 Concealment and Misdirection
|
Control
Employ the following concealment and misdirection techniques for [Assignement: systems] at [Assignement: time periods] to confuse and mislead adversaries: [Assignement: concealment and misdirection techniques].
Discussion
Concealment and misdirection techniques can significantly reduce the targeting capabilities of adversaries (i.e., window of opportunity and available attack surface) to initiate and complete attacks. For example, virtualization techniques provide organizations with the ability to disguise systems, potentially reducing the likelihood of successful attacks without the cost of having multiple platforms. The increased use of concealment and misdirection techniques and methods—including randomness, uncertainty, and virtualization—may sufficiently confuse and mislead adversaries and subsequently increase the risk of discovery and/or exposing tradecraft. Concealment and misdirection techniques may provide additional time to perform core mission and business functions. The implementation of concealment and misdirection techniques may add to the complexity and management overhead required for the system.
Assessment Objective
[Assignement: concealment and misdirection techniques] are employed for [Assignement: systems] for [Assignement: time periods] to confuse and mislead adversaries.
Assessment Method
Examine
System and communications protection policy
procedures addressing concealment and misdirection techniques for the system
system design documentation
system configuration settings and associated documentation
system architecture
list of concealment and misdirection techniques to be employed for organizational systems
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel with the responsibility to implement concealment and misdirection techniques for systems
|
|
SC-31 Covert Channel Analysis
|
Control
- Perform a covert channel analysis to identify those aspects of communications within the system that are potential avenues for covert [Selection(one-or-more): storage; timing] channels; and
- Estimate the maximum bandwidth of those channels.
Discussion
Developers are in the best position to identify potential areas within systems that might lead to covert channels. Covert channel analysis is a meaningful activity when there is the potential for unauthorized information flows across security domains, such as in the case of systems that contain export-controlled information and have connections to external networks (i.e., networks that are not controlled by organizations). Covert channel analysis is also useful for multilevel secure systems, multiple security level systems, and cross-domain systems.
Assessment Objective
- a covert channel analysis is performed to identify those aspects of communications within the system that are potential avenues for covert [Selection(one-or-more): storage; timing] channels;
- the maximum bandwidth of those channels is estimated.
Assessment Method
Examine
System and communications protection policy
procedures addressing covert channel analysis
system design documentation
system configuration settings and associated documentation
covert channel analysis documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel with covert channel analysis responsibilities
system developers/integrators
|
|
SC-32 System Partitioning
|
Control
Partition the system into [Assignement: system components] residing in separate [Selection: physical; logical] domains or environments based on [Assignement: circumstances for the physical or logical separation of components].
Discussion
System partitioning is part of a defense-in-depth protection strategy. Organizations determine the degree of physical separation of system components. Physical separation options include physically distinct components in separate racks in the same room, critical components in separate rooms, and geographical separation of critical components. Security categorization can guide the selection of candidates for domain partitioning. Managed interfaces restrict or prohibit network access and information flow among partitioned system components.
Assessment Objective
the system is partitioned into [Assignement: system components] residing in separate [Selection: physical; logical] domains or environments based on [Assignement: circumstances for the physical or logical separation of components].
Assessment Method
Examine
System and communications protection policy
procedures addressing system partitioning
system design documentation
system configuration settings and associated documentation
system architecture
list of system physical domains (or environments)
system facility diagrams
system network diagrams
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel installing, configuring, and/or maintaining the system
system developers/integrators
|
|
SC-33 Transmission Preparation Integrity
|
Control
Discussion
Assessment Objective
Assessment Method
Examine
Interview
|
|
SC-34 Non-modifiable Executable Programs
|
Control
For [Assignement: system components] , load and execute:- The operating environment from hardware-enforced, read-only media; and
- The following applications from hardware-enforced, read-only media: [Assignement: applications].
Discussion
The operating environment for a system contains the code that hosts applications, including operating systems, executives, or virtual machine monitors (i.e., hypervisors). It can also include certain applications that run directly on hardware platforms. Hardware-enforced, read-only media include Compact Disc-Recordable (CD-R) and Digital Versatile Disc-Recordable (DVD-R) disk drives as well as one-time, programmable, read-only memory. The use of non-modifiable storage ensures the integrity of software from the point of creation of the read-only image. The use of reprogrammable, read-only memory can be accepted as read-only media provided that integrity can be adequately protected from the point of initial writing to the insertion of the memory into the system, and there are reliable hardware protections against reprogramming the memory while installed in organizational systems.
Assessment Objective
- the operating environment for [Assignement: system components] is loaded and executed from hardware-enforced, read-only media;
- [Assignement: applications] for [Assignement: system components] are loaded and executed from hardware-enforced, read-only media.
Assessment Method
Examine
System and communications protection policy
procedures addressing non-modifiable executable programs
system design documentation
system configuration settings and associated documentation
system architecture
list of operating system components to be loaded from hardware-enforced, read-only media
list of applications to be loaded from hardware-enforced, read-only media
media used to load and execute the system operating environment
media used to load and execute system applications
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
system developer
organizational personnel installing, configuring, and/or maintaining the system
system developers/integrators
|
|
SC-35 External Malicious Code Identification
|
Control
Include system components that proactively seek to identify network-based malicious code or malicious websites.
Discussion
External malicious code identification differs from decoys in [SC-26](#sc-26) in that the components actively probe networks, including the Internet, in search of malicious code contained on external websites. Like decoys, the use of external malicious code identification techniques requires some supporting isolation measures to ensure that any malicious code discovered during the search and subsequently executed does not infect organizational systems. Virtualization is a common technique for achieving such isolation.
Assessment Objective
system components that proactively seek to identify network-based malicious code or malicious websites are included.
Assessment Method
Examine
System and communications protection policy
procedures addressing external malicious code identification
system design documentation
system configuration settings and associated documentation
system components deployed to identify malicious websites and/or web-based malicious code
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel installing, configuring, and/or maintaining the system
system developers/integrators
|
|
SC-36 Distributed Processing and Storage
|
Control
Distribute the following processing and storage components across multiple [Selection: physical locations; logical domains]: [Assignement: organization-defined processing and storage components].
Discussion
Distributing processing and storage across multiple physical locations or logical domains provides a degree of redundancy or overlap for organizations. The redundancy and overlap increase the work factor of adversaries to adversely impact organizational operations, assets, and individuals. The use of distributed processing and storage does not assume a single primary processing or storage location. Therefore, it allows for parallel processing and storage.
Assessment Objective
- [Assignement: processing components] are distributed across [Selection: physical locations; logical domains];
- [Assignement: storage components] are distributed across [Selection: physical locations; logical domains].
Assessment Method
Examine
System and communications protection policy
contingency planning policy and procedures
contingency plan
system design documentation
system configuration settings and associated documentation
system architecture
list of system physical locations (or environments) with distributed processing and storage
system facility diagrams
processing site agreements
storage site agreements
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel installing, configuring, and/or maintaining the system
organizational personnel with contingency planning and plan implementation responsibilities
system developers/integrators
|
|
SC-37 Out-of-band Channels
|
Control
Employ the following out-of-band channels for the physical delivery or electronic transmission of [Assignement: information, system components, or devices] to [Assignement: individuals or systems]: [Assignement: out-of-band channels].
Discussion
Out-of-band channels include local, non-network accesses to systems; network paths physically separate from network paths used for operational traffic; or non-electronic paths, such as the U.S. Postal Service. The use of out-of-band channels is contrasted with the use of in-band channels (i.e., the same channels) that carry routine operational traffic. Out-of-band channels do not have the same vulnerability or exposure as in-band channels. Therefore, the confidentiality, integrity, or availability compromises of in-band channels will not compromise or adversely affect the out-of-band channels. Organizations may employ out-of-band channels in the delivery or transmission of organizational items, including authenticators and credentials; cryptographic key management information; system and data backups; configuration management changes for hardware, firmware, or software; security updates; maintenance information; and malicious code protection updates. For example, cryptographic keys for encrypted files are delivered using a different channel than the file.
Assessment Objective
[Assignement: out-of-band channels] are employed for the physical delivery or electronic transmission of [Assignement: information, system components, or devices] to [Assignement: individuals or systems].
Assessment Method
Examine
System and communications protection policy
procedures addressing the use of out-of-band channels
access control policy and procedures
identification and authentication policy and procedures
system design documentation
system architecture
system configuration settings and associated documentation
list of out-of-band channels
types of information, system components, or devices requiring the use of out-of-band channels for physical delivery or electronic transmission to authorized individuals or systems
physical delivery records
electronic transmission records
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel installing, configuring, and/or maintaining the system
organizational personnel authorizing, installing, configuring, operating, and/or using out-of-band channels
system developers/integrators
|
|
SC-38 Operations Security
|
Control
Employ the following operations security controls to protect key organizational information throughout the system development life cycle: [Assignement: operations security controls].
Discussion
Operations security (OPSEC) is a systematic process by which potential adversaries can be denied information about the capabilities and intentions of organizations by identifying, controlling, and protecting generally unclassified information that specifically relates to the planning and execution of sensitive organizational activities. The OPSEC process involves five steps: identification of critical information, analysis of threats, analysis of vulnerabilities, assessment of risks, and the application of appropriate countermeasures. OPSEC controls are applied to organizational systems and the environments in which those systems operate. OPSEC controls protect the confidentiality of information, including limiting the sharing of information with suppliers, potential suppliers, and other non-organizational elements and individuals. Information critical to organizational mission and business functions includes user identities, element uses, suppliers, supply chain processes, functional requirements, security requirements, system design specifications, testing and evaluation protocols, and security control implementation details.
Assessment Objective
[Assignement: operations security controls] are employed to protect key organizational information throughout the system development life cycle.
Assessment Method
Examine
System and communications protection policy
procedures addressing operations security
security plan
list of operations security safeguards
security control assessments
risk assessments
threat and vulnerability assessments
plans of action and milestones
system development life cycle documentation
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel installing, configuring, and/or maintaining the system
system developers/integrators
|
|
SC-39 Process Isolation
|
Control
Maintain a separate execution domain for each executing system process.
Discussion
Systems can maintain separate execution domains for each executing process by assigning each process a separate address space. Each system process has a distinct address space so that communication between processes is performed in a manner controlled through the security functions, and one process cannot modify the executing code of another process. Maintaining separate execution domains for executing processes can be achieved, for example, by implementing separate address spaces. Process isolation technologies, including sandboxing or virtualization, logically separate software and firmware from other software, firmware, and data. Process isolation helps limit the access of potentially untrusted software to other system resources. The capability to maintain separate execution domains is available in commercial operating systems that employ multi-state processor technologies.
Assessment Objective
a separate execution domain is maintained for each executing system process.
Assessment Method
Examine
System design documentation
system architecture
independent verification and validation documentation
testing and evaluation documentation
other relevant documents or records
Interview
System developers/integrators
system security architect
|
|
SC-40 Wireless Link Protection
|
Control
Protect external and internal [Assignement: organization-defined wireless links] from the following signal parameter attacks: [Assignement: organization-defined types of signal parameter attacks or references to sources for such attacks].
Discussion
Wireless link protection applies to internal and external wireless communication links that may be visible to individuals who are not authorized system users. Adversaries can exploit the signal parameters of wireless links if such links are not adequately protected. There are many ways to exploit the signal parameters of wireless links to gain intelligence, deny service, or spoof system users. Protection of wireless links reduces the impact of attacks that are unique to wireless systems. If organizations rely on commercial service providers for transmission services as commodity items rather than as fully dedicated services, it may not be possible to implement wireless link protections to the extent necessary to meet organizational security requirements.
Assessment Objective
- external [Assignement: wireless links] are protected from [Assignement: types of signal parameter attacks or references to sources for such attacks].
- internal [Assignement: wireless links] are protected from [Assignement: types of signal parameter attacks or references to sources for such attacks].
Assessment Method
Examine
System and communications protection policy
access control policy and procedures
procedures addressing wireless link protection
system design documentation
wireless network diagrams
system configuration settings and associated documentation
system architecture
list of internal and external wireless links
list of signal parameter attacks or references to sources for attacks
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
system developer
organizational personnel installing, configuring, and/or maintaining the system
organizational personnel authorizing, installing, configuring, and/or maintaining internal and external wireless links
|
|
SC-41 Port and I/O Device Access
|
Control
[Selection: physically; logically] disable or remove [Assignement: connection ports or input/output devices] on the following systems or system components: [Assignement: systems or system components].
Discussion
Connection ports include Universal Serial Bus (USB), Thunderbolt, and Firewire (IEEE 1394). Input/output (I/O) devices include compact disc and digital versatile disc drives. Disabling or removing such connection ports and I/O devices helps prevent the exfiltration of information from systems and the introduction of malicious code from those ports or devices. Physically disabling or removing ports and/or devices is the stronger action.
Assessment Objective
[Assignement: connection ports or input/output devices] are [Selection: physically; logically] disabled or removed on [Assignement: systems or system components].
Assessment Method
Examine
System and communications protection policy
access control policy and procedures
procedures addressing port and input/output device access
system design documentation
system configuration settings and associated documentation
system architecture
systems or system components
list of connection ports or input/output devices to be physically disabled or removed on systems or system components
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel installing, configuring, and/or maintaining the system
|
|
SC-42 Sensor Capability and Data
|
Control
- Prohibit [Selection(one-or-more): the use of devices possessing {{ insert: param, sc-42_odp.02 }} in {{ insert: param, sc-42_odp.03 }} ; the remote activation of environmental sensing capabilities on organizational systems or system components with the following exceptions: {{ insert: param, sc-42_odp.04 }} ] ; and
- Provide an explicit indication of sensor use to [Assignement: group of users].
Discussion
Sensor capability and data applies to types of systems or system components characterized as mobile devices, such as cellular telephones, smart phones, and tablets. Mobile devices often include sensors that can collect and record data regarding the environment where the system is in use. Sensors that are embedded within mobile devices include microphones, cameras, Global Positioning System (GPS) mechanisms, and accelerometers. While the sensors on mobiles devices provide an important function, if activated covertly, such devices can potentially provide a means for adversaries to learn valuable information about individuals and organizations. For example, remotely activating the GPS function on a mobile device could provide an adversary with the ability to track the movements of an individual. Organizations may prohibit individuals from bringing cellular telephones or digital cameras into certain designated facilities or controlled areas within facilities where classified information is stored or sensitive conversations are taking place.
Assessment Objective
- [Selection(one-or-more): the use of devices possessing {{ insert: param, sc-42_odp.02 }} in {{ insert: param, sc-42_odp.03 }} ; the remote activation of environmental sensing capabilities on organizational systems or system components with the following exceptions: {{ insert: param, sc-42_odp.04 }} ] is/are prohibited;
- an explicit indication of sensor use is provided to [Assignement: group of users].
Assessment Method
Examine
System and communications protection policy
procedures addressing sensor capabilities and data collection
access control policy and procedures
system design documentation
system configuration settings and associated documentation
system audit records
system security plan
privacy plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security and privacy responsibilities
system developer
organizational personnel installing, configuring, and/or maintaining the system
organizational personnel responsible for sensor capabilities
|
|
SC-43 Usage Restrictions
|
Control
- Establish usage restrictions and implementation guidelines for the following system components: [Assignement: components] ; and
- Authorize, monitor, and control the use of such components within the system.
Discussion
Usage restrictions apply to all system components including but not limited to mobile code, mobile devices, wireless access, and wired and wireless peripheral components (e.g., copiers, printers, scanners, optical devices, and other similar technologies). The usage restrictions and implementation guidelines are based on the potential for system components to cause damage to the system and help to ensure that only authorized system use occurs.
Assessment Objective
- usage restrictions and implementation guidelines are established for [Assignement: components];
- the use of [Assignement: components] is authorized within the system;
- the use of [Assignement: components] is monitored within the system;
- the use of [Assignement: components] is controlled within the system.
Assessment Method
Examine
System and communications protection policy
usage restrictions
procedures addressing usage restrictions
implementation policy and procedures
authorization records
system monitoring records
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel installing, configuring, and/or maintaining the system
|
|
SC-44 Detonation Chambers
|
Control
Employ a detonation chamber capability within [Assignement: system, system component, or location].
Discussion
Detonation chambers, also known as dynamic execution environments, allow organizations to open email attachments, execute untrusted or suspicious applications, and execute Universal Resource Locator requests in the safety of an isolated environment or a virtualized sandbox. Protected and isolated execution environments provide a means of determining whether the associated attachments or applications contain malicious code. While related to the concept of deception nets, the employment of detonation chambers is not intended to maintain a long-term environment in which adversaries can operate and their actions can be observed. Rather, detonation chambers are intended to quickly identify malicious code and either reduce the likelihood that the code is propagated to user environments of operation or prevent such propagation completely.
Assessment Objective
a detonation chamber capability is employed within the [Assignement: system, system component, or location].
Assessment Method
Examine
System and communications protection policy
procedures addressing detonation chambers
system design documentation
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel installing, configuring, and/or maintaining the system
|
|
SC-45 System Time Synchronization
|
Control
Synchronize system clocks within and between systems and system components.
Discussion
Time synchronization of system clocks is essential for the correct execution of many system services, including identification and authentication processes that involve certificates and time-of-day restrictions as part of access control. Denial of service or failure to deny expired credentials may result without properly synchronized clocks within and between systems and system components. Time is commonly expressed in Coordinated Universal Time (UTC), a modern continuation of Greenwich Mean Time (GMT), or local time with an offset from UTC. The granularity of time measurements refers to the degree of synchronization between system clocks and reference clocks, such as clocks synchronizing within hundreds of milliseconds or tens of milliseconds. Organizations may define different time granularities for system components. Time service can be critical to other security capabilities—such as access control and identification and authentication—depending on the nature of the mechanisms used to support the capabilities.
Assessment Objective
system clocks are synchronized within and between systems and system components.
Assessment Method
Examine
System and communications protection policy
procedures addressing time synchronization
system design documentation
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel installing, configuring, and/or maintaining the system
|
|
SC-46 Cross Domain Policy Enforcement
|
Control
Implement a policy enforcement mechanism [Selection: physically; logically] between the physical and/or network interfaces for the connecting security domains.
Discussion
For logical policy enforcement mechanisms, organizations avoid creating a logical path between interfaces to prevent the ability to bypass the policy enforcement mechanism. For physical policy enforcement mechanisms, the robustness of physical isolation afforded by the physical implementation of policy enforcement to preclude the presence of logical covert channels penetrating the security domain may be needed. Contact [ncdsmo@nsa.gov](mailto:ncdsmo@nsa.gov) for more information.
Assessment Objective
a policy enforcement mechanism is [Selection: physically; logically] implemented between the physical and/or network interfaces for the connecting security domains.
Assessment Method
Examine
System and communications protection policy
procedures addressing cross-domain policy enforcement
system design documentation
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel installing, configuring, and/or maintaining the system
|
|
SC-47 Alternate Communications Paths
|
Control
Establish [Assignement: alternate communication paths] for system operations organizational command and control.
Discussion
An incident, whether adversarial- or nonadversarial-based, can disrupt established communications paths used for system operations and organizational command and control. Alternate communications paths reduce the risk of all communications paths being affected by the same incident. To compound the problem, the inability of organizational officials to obtain timely information about disruptions or to provide timely direction to operational elements after a communications path incident, can impact the ability of the organization to respond to such incidents in a timely manner. Establishing alternate communications paths for command and control purposes, including designating alternative decision makers if primary decision makers are unavailable and establishing the extent and limitations of their actions, can greatly facilitate the organization’s ability to continue to operate and take appropriate actions during an incident.
Assessment Objective
[Assignement: alternate communication paths] are established for system operations and operational command and control.
Assessment Method
Examine
System and communications protection policy
procedures addressing communication paths
system design documentation
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
system developers
|
|
SC-48 Sensor Relocation
|
Control
Relocate [Assignement: sensors and monitoring capabilities] to [Assignement: locations] under the following conditions or circumstances: [Assignement: conditions or circumstances].
Discussion
Adversaries may take various paths and use different approaches as they move laterally through an organization (including its systems) to reach their target or as they attempt to exfiltrate information from the organization. The organization often only has a limited set of monitoring and detection capabilities, and they may be focused on the critical or likely infiltration or exfiltration paths. By using communications paths that the organization typically does not monitor, the adversary can increase its chances of achieving its desired goals. By relocating its sensors or monitoring capabilities to new locations, the organization can impede the adversary’s ability to achieve its goals. The relocation of the sensors or monitoring capabilities might be done based on threat information that the organization has acquired or randomly to confuse the adversary and make its lateral transition through the system or organization more challenging.
Assessment Objective
[Assignement: sensors and monitoring capabilities] are relocated to [Assignement: locations] under [Assignement: conditions or circumstances].
Assessment Method
Examine
System and communications protection policy
procedures addressing sensor and monitoring capability relocation
list of sensors/monitoring capabilities to be relocated
change control records
configuration management records
system design documentation
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel installing, configuring, and/or maintaining the system
|
|
SC-49 Hardware-enforced Separation and Policy Enforcement
|
Control
Implement hardware-enforced separation and policy enforcement mechanisms between [Assignement: security domains].
Discussion
System owners may require additional strength of mechanism and robustness to ensure domain separation and policy enforcement for specific types of threats and environments of operation. Hardware-enforced separation and policy enforcement provide greater strength of mechanism than software-enforced separation and policy enforcement.
Assessment Objective
hardware-enforced separation and policy enforcement mechanisms are implemented between [Assignement: security domains].
Assessment Method
Examine
System and communications protection policy
procedures addressing cross-domain policy enforcement
system design documentation
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel installing, configuring, and/or maintaining the system
|
|
SC-50 Software-enforced Separation and Policy Enforcement
|
Control
Implement software-enforced separation and policy enforcement mechanisms between [Assignement: security domains].
Discussion
System owners may require additional strength of mechanism to ensure domain separation and policy enforcement for specific types of threats and environments of operation.
Assessment Objective
software-enforced separation and policy enforcement mechanisms are implemented between [Assignement: security domains].
Assessment Method
Examine
System and communications protection policy
procedures addressing cross-domain policy enforcement
system design documentation
system configuration settings and associated documentation
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel installing, configuring, and/or maintaining the system
|
|
SC-51 Hardware-based Protection
|
Control
- Employ hardware-based, write-protect for [Assignement: system firmware components] ; and
- Implement specific procedures for [Assignement: authorized individuals] to manually disable hardware write-protect for firmware modifications and re-enable the write-protect prior to returning to operational mode.
Discussion
None.
Assessment Objective
- hardware-based write-protect for [Assignement: system firmware components] is employed;
- specific procedures are implemented for [Assignement: authorized individuals] to manually disable hardware write-protect for firmware modifications;
- specific procedures are implemented for [Assignement: authorized individuals] to re-enable the write-protect prior to returning to operational mode.
Assessment Method
Examine
System and communications protection policy
procedures addressing firmware modifications
system design documentation
system configuration settings and associated documentation
system architecture
system audit records
system security plan
other relevant documents or records
Interview
System/network administrators
organizational personnel with information security responsibilities
organizational personnel installing, configuring, and/or maintaining the system
system developers/integrators
|
1.1 Referencer
1.2 Identificerede krav
1.3 Relaterede reguleringer
2. Identificerede krav
3. Relaterede reguleringer
Reguleringer
| Kilde |
Regulering |
|