--
-- Host: localhost    Database: osa_controls
-- ------------------------------------------------------


--
-- Table structure for table `cobit41`
--

CREATE TABLE `cobit41` (
  `cobit_id` smallint(5) unsigned NOT NULL AUTO_INCREMENT,
  `c_id` char(5) DEFAULT NULL,
  `cobit41` varchar(10) DEFAULT NULL,
  PRIMARY KEY (`cobit_id`)
) ENGINE=InnoDB AUTO_INCREMENT=204 DEFAULT CHARSET=latin1;

--
-- Dumping data for table `cobit41`
--

INSERT INTO `cobit41` VALUES (1,'AC-01','DS11.6'),(2,'AC-01','PC5'),(3,'AC-02','DS5.4'),(4,'AC-03','PO2.3'),(5,'AC-03','AI2.4'),(6,'AC-03','DS11.6'),(7,'AC-04','DS5.10'),(8,'AC-05','PO4.11'),(9,'AC-06','PO4.11'),(10,'AC-10','AC6'),(11,'AC-13','PO4.10'),(12,'AC-15','PO2.3'),(13,'AC-15','DS11.6'),(14,'AC-15','AC2'),(15,'AC-16','PO2.3'),(16,'AC-16','DS11.6'),(17,'AT-01','DS7.1'),(18,'AT-01','PC5'),(19,'AT-02','PO7.4'),(20,'AT-03','PO7.4'),(21,'AT-03','DS7.2'),(22,'AT-04','DS7.2'),(23,'AU-01','PC2'),(24,'AU-01','PC5'),(25,'AU-02','AI2.3'),(26,'AU-06','DS5.5'),(27,'AU-10','DS5.11'),(28,'CA-01','PO10.12'),(29,'CA-01','PC5'),(30,'CA-02','DS5.5'),(31,'CA-04','AI7.7'),(32,'CA-05','ME2.7'),(33,'CA-06','AI7.7'),(34,'CA-06','DS5.5'),(35,'CA-07','PO1.3'),(36,'CA-07','DS5.5'),(37,'CM-01','PO2.1'),(38,'CM-01','AI6.1'),(39,'CM-01','DS9.1'),(40,'CM-01','PC5'),(41,'CM-02','PO1.6'),(42,'CM-02','PO2.1'),(43,'CM-02','DS9.1'),(44,'CM-03','AI6.1'),(45,'CM-03','AI6.3'),(46,'CM-03','DS9.2'),(47,'CM-04','DS5.5'),(48,'CM-04','DS9.3'),(49,'CP-01','DS4.1'),(50,'CP-01','PC5'),(51,'CP-02','DS4.2'),(52,'CP-03','DS4.6'),(53,'CP-04','DS4.2'),(54,'CP-04','DS4.5'),(55,'CP-05','DS4.4'),(56,'CP-06','DS4.1'),(57,'CP-06','DS4.9'),(58,'CP-07','DS4.1'),(59,'CP-07','DS4.8'),(60,'CP-08','DS4.1'),(61,'CP-09','DS4.2'),(62,'CP-09','DS4.9'),(63,'CP-09','DS11.5'),(64,'CP-10','DS4.8'),(65,'CP-10','DS11.5'),(66,'IA-01','DS5.3'),(67,'IA-01','PC5'),(68,'IA-02','AI2.4'),(69,'IA-02','DS5.3'),(70,'IA-04','DS5.3'),(71,'IA-04','DS5.4'),(72,'IR-01','PO9.5'),(73,'IR-01','PO9.6'),(74,'IR-01','DS5.6'),(75,'IR-01','DS8.2'),(76,'IR-01','PC5'),(77,'IR-04','PO9.5'),(78,'IR-04','PO9.6'),(79,'IR-04','DS8.2'),(80,'IR-05','DS8.2'),(81,'IR-05','DS8.4'),(82,'IR-06','DS5.6'),(83,'IR-07','DS8.1'),(84,'MA-01','PC5'),(85,'MA-02','AI2.10'),(86,'MP-01','DS11.1'),(87,'MP-01','DS11.6'),(88,'MP-01','PC5'),(89,'MP-02','DS11.6'),(90,'MP-03','DS11.6'),(91,'MP-04','DS11.2'),(92,'MP-04','DS11.6'),(93,'MP-05','DS11.4'),(94,'MP-05','DS11.6'),(95,'MP-06','DS11.4'),(96,'MP-06','DS11.6'),(97,'PE-01','DS12.1'),(98,'PE-01','DS12.5'),(99,'PE-01','PC5'),(100,'PE-02','DS12.3'),(101,'PE-03','DS12.2'),(102,'PE-04','DS5.7'),(103,'PE-04','DS12.2'),(104,'PE-05','DS12.2'),(105,'PE-06','DS12.3'),(106,'PE-07','DS12.3'),(107,'PE-08','DS12.3'),(108,'PE-09','DS12.4'),(109,'PE-10','DS12.4'),(110,'PE-11','DS12.4'),(111,'PE-12','DS12.4'),(112,'PE-13','DS12.4'),(113,'PE-14','DS12.4'),(114,'PE-15','DS12.4'),(115,'PE-16','DS12.2'),(116,'PE-18','DS12.1'),(117,'PE-19','DS12.2'),(118,'PL-01','DS5.2'),(119,'PL-01','PC5'),(120,'PL-02','PO1.4'),(121,'PL-02','DS5.2'),(122,'PL-03','PO1.4'),(123,'PL-04','PO6.5'),(124,'PL-04','DS5.2'),(125,'PL-04','PC4'),(126,'PS-01','PO4.6'),(127,'PS-01','PO7.3'),(128,'PS-01','PC5'),(129,'PS-02','PO4.13'),(130,'PS-02','PO7.3'),(131,'PS-03','PO7.6'),(132,'PS-04','PO7.8'),(133,'PS-05','PO7.8'),(134,'PS-06','DS5.4'),(135,'PS-07','PO4.14'),(136,'PS-07','DS2.2'),(137,'RA-01','PO9.1'),(138,'RA-01','PC5'),(139,'RA-02','PO9.2'),(140,'RA-03','PO9.3'),(141,'RA-03','PO9.4'),(142,'RA-03','AI1.1'),(143,'RA-04','PO9.4'),(144,'RA-05','PO9.3'),(145,'RA-05','DS5.5'),(146,'SA-01','AI2.5'),(147,'SA-01','AI5.1'),(148,'SA-01','PC5'),(149,'SA-02','PO1.1'),(150,'SA-02','PO5.2'),(151,'SA-03','PO8.3'),(152,'SA-03','AI2.7'),(153,'SA-04','AI2.4'),(154,'SA-04','AI5.4'),(155,'SA-05','DS5.7'),(156,'SA-06','DS9.3'),(157,'SA-07','DS9.3'),(158,'SA-08','AI2.4'),(159,'SA-09','DS1.6'),(160,'SA-09','DS2.3'),(161,'SA-09','ME3.1'),(162,'SA-09','ME3.3'),(163,'SA-11','AI2.8'),(164,'SC-01','DS5.2'),(165,'SC-01','PC5'),(166,'SC-02','AI2.4'),(167,'SC-03','DS5.7'),(168,'SC-07','DS5.10'),(169,'SC-08','AC6'),(170,'SC-09','DS5.11'),(171,'SC-09','AC6'),(172,'SC-11','DS5.11'),(173,'SC-11','AC6'),(174,'SC-12','DS5.8'),(175,'SC-13','DS5.8'),(176,'SC-16','DS5.11'),(177,'SC-18','DS5.9'),(178,'SC-23','AC6'),(179,'SC-23','DS5.11'),(180,'SI-01','PO2.4'),(181,'SI-01','PC5'),(182,'SI-03','DS5.9'),(183,'SI-04','PO2.4'),(184,'SI-04','DS5.5'),(185,'SI-04','DS5.10'),(186,'SI-07','PO2.4'),(187,'SI-07','AI2.4'),(188,'SI-07','DS5.9'),(189,'SI-08','DS5.9'),(190,'SI-09','AC1'),(191,'SI-09','AC2'),(192,'SI-10','PO2.4'),(193,'SI-10','AI2.3'),(194,'SI-10','AI2.4'),(195,'SI-10','DS11.1'),(196,'SI-10','DS11.6'),(197,'SI-10','AC3'),(198,'SI-10','AC4'),(199,'SI-10','AC6'),(200,'SI-11','AC5'),(201,'SI-12','DS11.1'),(202,'SI-12','DS11.6'),(203,'SI-12','AC5');

--
-- Table structure for table `controls`
--

CREATE TABLE `controls` (
  `c_id` char(5) NOT NULL DEFAULT '',
  `NIST_id` char(5) DEFAULT NULL,
  `alias` varchar(20) DEFAULT NULL,
  `name` varchar(100) DEFAULT NULL,
  `description` varchar(5000) DEFAULT NULL,
  `supplemental_guidance` varchar(5000) DEFAULT NULL,
  `baseline` varchar(100) DEFAULT NULL,
  `family` varchar(100) DEFAULT NULL,
  `class` varchar(100) DEFAULT NULL,
  `URL` varchar(200) DEFAULT NULL,
  PRIMARY KEY (`c_id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `controls`
--

INSERT INTO `controls` VALUES ('AC-01','AC-1','08_02_AC-01','Access Control Policy And Procedures','The organization develops, disseminates, and periodically reviews/updates: (i) a formal, documented, access control policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (ii) formal, documented procedures to facilitate the implementation of the access control policy and associated access controls.','The access control policy and procedures are consistent with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance. The access control policy can be included as part of the general information security policy for the organization. Access control procedures can be developed for the security program in general, and for a particular information system, when required. NIST Special Publication 800-12 provides guidance on security policies and procedures.','LOW AC-1 MOD AC-1 HIGH AC-1','Access Control','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/23-08_02_AC-01'),('AC-02','AC-2','08_02_AC-02','Account Management','The organization manages information system accounts, including establishing, activating, modifying, reviewing, disabling, and removing accounts. The organization reviews information system accounts [Assignment: organization-defined frequency, at least annually].','Account management includes the identification of account types (i.e., individual, group, and system), establishment of conditions for group membership, and assignment of associated authorizations. The organization identifies authorized users of the information system and specifies access rights/privileges. The organization grants access to the information system based on: (i) a valid need-to-know/need-to-share that is determined by assigned official duties and satisfying all personnel security criteria; and (ii) intended system usage. The organization requires proper identification for requests to establish information system accounts and approves all such requests. The organization specifically authorizes and monitors the use of guest/anonymous accounts and removes, disables, or otherwise secures unnecessary accounts. Account managers are notified when information system users are terminated or transferred and associated accounts are removed, disabled, or otherwise secured. Account managers are also notified when users information system usage or need-to-know/need-to-share changes.','LOW AC-2 MOD AC-2 (1) (2) (3) (4) HIGH AC-2 (1) (2) (3) (4)','Access Control','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/24-08_02_AC-02'),('AC-03','AC-3','08_02_AC-03','Access Enforcement','The information system enforces assigned authorizations for controlling access to the system in accordance with applicable policy.','Access control policies (e.g., identity-based policies, role-based policies, rule-based policies) and associated access enforcement mechanisms (e.g., access control lists, access control matrices, cryptography) are employed by organizations to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, domains) in the information system. In addition to controlling access at the information system level, access enforcement mechanisms are employed at the application level, when necessary, to provide increased information security for the organization. Consideration is given to the implementation of a controlled, audited, and manual override of automated mechanisms in the event of emergencies or other serious events. If encryption of stored information is employed as an access enforcement mechanism, the cryptography used is FIPS 140-2 (as amended) compliant. Related security control: SC-13.','LOW AC-3 MOD AC-3 (1) HIGH AC-3 (1)','Access Control','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/25-08_02_AC-03'),('AC-04','AC-4','08_02_AC-04','Information Flow Enforcement','The information system enforces assigned authorizations for controlling the flow of information within the system and between interconnected systems in accordance with applicable policy.','Information flow control regulates where information is allowed to travel within an information system and between information systems (as opposed to who is allowed to access the information) and without explicit regard to subsequent accesses to that information. A few, of many, generalized examples of possible restrictions that are better expressed as flow control than access control are: keeping export controlled information from being transmitted in the clear to the Internet, blocking outside traffic that claims to be from within the organization, and not passing any web requests to the Internet that are not from the internal web proxy. Information flow control policies and enforcement mechanisms are commonly employed by organizations to control the flow of information between designated sources and destinations (e.g., networks, individuals, devices) within information systems and between interconnected systems. Flow control is based on the characteristics of the information and/or the information path. Specific examples of flow control enforcement can be found in boundary protection devices (e.g., proxies, gateways, guards, encrypted tunnels, firewalls, and routers) that employ rule sets or establish configuration settings that restrict information system services or provide a packet filtering capability. Related security control: SC-7.','LOW Not Selected MOD AC-4 HIGH AC-4','Access Control','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/26-08_02_AC-04'),('AC-05','AC-5','08_02_AC-05','Separation Of Duties','The information system enforces separation of duties through assigned access authorizations.','The organization establishes appropriate divisions of responsibility and separates duties as needed to eliminate conflicts of interest in the responsibilities and duties of individuals. There is access control software on the information system that prevents users from having all of the necessary authority or information access to perform fraudulent activity without collusion. Examples of separation of duties include: (i) mission functions and distinct information system support functions are divided among different individuals/roles; (ii) different individuals perform information system support functions (e.g., system management, systems programming, quality assurance/testing, configuration management, and network security); and (iii) security personnel who administer access control functions do not administer audit functions.','LOW Not Selected MOD AC-5 HIGH AC-5','Access Control','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/27-08_02_AC-05'),('AC-06','AC-6','08_02_AC-06','Least Privilege','The information system enforces the most restrictive set of rights/privileges or accesses needed by users (or processes acting on behalf of users) for the performance of specified tasks.','The organization employs the concept of least privilege for specific duties and information systems (including specific ports, protocols, and services) in accordance with risk assessments as necessary to adequately mitigate risk to organizational operations, organizational assets, and individuals.','LOW Not Selected MOD AC-6 HIGH AC-6','Access Control','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/28-08_02_AC-06'),('AC-07','AC-7','08_02_AC-07','Unsuccessful Login Attempts','The information system enforces a limit of [Assignment: organization-defined number] consecutive invalid access attempts by a user during a [Assignment: organization-defined time period] time period. The information system automatically [Selection: locks the account/node for an [Assignment: organization-defined time period], delays next login prompt according to [Assignment: organization-defined delay algorithm.]] when the maximum number of unsuccessful attempts is exceeded.','Due to the potential for denial of service, automatic lockouts initiated by the information system are usually temporary and automatically release after a predetermined time period established by the organization.','LOW AC-7 MOD AC-7 HIGH AC-7','Access Control','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/29-08_02_AC-07'),('AC-08','AC-8','08_02_AC-08','System Use Notification','The information system displays an approved, system use notification message before granting system access informing potential users: (i) that the user is accessing a U.S. Government information system; (ii) that system usage may be monitored, recorded, and subject to audit; (iii) that unauthorized use of the system is prohibited and subject to criminal and civil penalties; and (iv) that use of the system indicates consent to monitoring and recording. The system use notification message provides appropriate privacy and security notices (based on associated privacy and security policies or summaries) and remains on the screen until the user takes explicit actions to log on to the information system.','Privacy and security policies are consistent with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance. System use notification messages can be implemented in the form of warning banners displayed when individuals log in to the information system. For publicly accessible systems: (i) the system use information is available and when appropriate, is displayed before granting access; (ii) any references to monitoring, recording, or auditing are in keeping with privacy accommodations for such systems that generally prohibit those activities; and (iii) the notice given to public users of the information system includes a description of the authorized uses of the system.','LOW AC-8 MOD AC-8 HIGH AC-8','Access Control','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/30-08_02_AC-08'),('AC-09','AC-9','08_02_AC-09','Previous Logon Notification','The information system notifies the user, upon successful logon, of the date and time of the last logon, and the number of unsuccessful logon attempts since the last successful logon.','None.','LOW Not Selected MOD Not Selected HIGH Not Selected','Access Control','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/31-08_02_AC-09'),('AC-10','AC-10','08_02_AC-10','Concurrent Session Control','The information system limits the number of concurrent sessions for any user to [Assignment: organization-defined number of sessions].','None.','LOW Not Selected MOD Not Selected HIGH AC-10','Access Control','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/32-08_02_AC-10'),('AC-11','AC-11','08_02_AC-11','Session Lock','The information system prevents further access to the system by initiating a session lock after [Assignment: organization-defined time period] of inactivity, and the session lock remains in effect until the user reestablishes access using appropriate identification and authentication procedures.','Users can directly initiate session lock mechanisms. A session lock is not a substitute for logging out of the information system. Organization-defined time periods of inactivity comply with federal policy; for example, in accordance with OMB Memorandum 06-16, the organization-defined time period is no greater than thirty minutes for remote access and portable devices.','LOW Not Selected MOD AC-11 HIGH AC-11','Access Control','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/33-08_02_AC-11'),('AC-12','AC-12','08_02_AC-12','Session Termination','The information system automatically terminates a remote session after [Assignment: organization-defined time period] of inactivity.','A remote session is initiated whenever an organizational information system is accessed by a user (or an information system) communicating through an external, non- organization-controlled network (e.g., the Internet).','LOW Not Selected MOD AC-12 HIGH AC-12 (1)','Access Control','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/34-08_02_AC-12'),('AC-13','AC-13','08_02_AC-13','Supervision And Review - Access Control','The organization supervises and reviews the activities of users with respect to the enforcement and usage of information system access controls.','The organization reviews audit records (e.g., user activity logs) for inappropriate activities in accordance with organizational procedures. The organization investigates any unusual information system-related activities and periodically reviews changes to access authorizations. The organization reviews more frequently the activities of users with significant information system roles and responsibilities. The extent of the audit record reviews is based on the FIPS 199 impact level of the information system. For example, for low-impact systems, it is not intended that security logs be reviewed frequently for every workstation, but rather at central points such as a web proxy or email servers and when specific circumstances warrant review of other audit records. NIST Special Publication 800-92 provides guidance on computer security log management.','LOW AC-13 MOD AC-13 (1) HIGH AC-13 (1)#','Access Control','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/35-08_02_AC-13'),('AC-14','AC-14','08_02_AC-14','Permitted Actions Without Identification Or Authentication','The organization identifies and documents specific user actions that can be performed on the information system without identification or authentication.','The organization allows limited user activity without identification and authentication for public websites or other publicly available information systems (e.g., individuals accessing a federal information system at http://www.firstgov.gov). Related security control: IA-2.','LOW AC-14 MOD AC-14 (1) HIGH AC-14 (1)','Access Control','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/38-08_02_AC-14'),('AC-15','AC-15','08_02_AC-15','Automated Marking','The information system marks output using standard naming conventions to identify any special dissemination, handling, or distribution instructions.','Automated marking refers to markings employed on external media (e.g., hardcopy documents output from the information system). The markings used in external marking are distinguished from the labels used on internal data structures described in AC-16.','LOW Not Selected MOD Not Selected HIGH AC-15','Access Control','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/197-08_02_AC-15'),('AC-16','AC-16','08_02_AC-16','Automated Labeling','The information system appropriately labels information in storage, in process, and in transmission.','Automated labeling refers to labels employed on internal data structures (e.g., records, files) within the information system. Information labeling is accomplished in accordance with: (i) access control requirements; (ii) special dissemination, handling, or distribution instructions; or (iii) as otherwise required to enforce information system security policy.','LOW Not Selected MOD Not Selected HIGH Not Selected','Access Control','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/198-08_02_AC-16'),('AC-17','AC-17','08_02_AC-17','Remote Access','The organization authorizes, monitors, and controls all methods of remote access to the information system.','Remote access is any access to an organizational information system by a user (or an information system) communicating through an external, non-organization-controlled network (e.g., the Internet). Examples of remote access methods include dial-up, broadband, and wireless. Remote access controls are applicable to information systems other than public web servers or systems specifically designed for public access. The organization restricts access achieved through dial-up connections (e.g., limiting dial-up access based upon source of request) or protects against unauthorized connections or subversion of authorized connections (e.g., using virtual private network technology). NIST Special Publication 800-63 provides guidance on remote electronic authentication. If the federal Personal Identity Verification (PIV) credential is used as an identification token where cryptographic token-based access control is employed, the access control system conforms to the requirements of FIPS 201 and NIST Special Publications 800-73 and 800-78. NIST Special Publication 800-77 provides guidance on IPsec-based virtual private networks. Related security control: IA-2.','LOW AC-17 MOD AC-17 (1) (2) (3) (4) HIGH AC-17 (1) (2) (3) (4)','Access Control','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/199-08_02_AC-17'),('AC-18','AC-18','08_02_AC-18','Wireless Access Restrictions','The organization: (i) establishes usage restrictions and implementation guidance for wireless technologies; and (ii) authorizes, monitors, controls wireless access to the information system.','NIST Special Publications 800-48 and 800-97 provide guidance on wireless network security. NIST Special Publication 800-94 provides guidance on wireless intrusion detection and prevention.','LOW AC-18 MOD AC-18 (1) HIGH AC-18 (1) (2)','Access Control','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/200-08_02_AC-18'),('AC-19','AC-19','08_02_AC-19','Access Control For Portable And Mobile Devices','The organization: (i) establishes usage restrictions and implementation guidance for organization-controlled portable and mobile devices; and (ii) authorizes, monitors, and controls device access to organizational information systems.','Portable and mobile devices (e.g., notebook computers, personal digital assistants, cellular telephones, and other computing and communications devices with network connectivity and the capability of periodically operating in different physical locations) are only allowed access to organizational information systems in accordance with organizational security policies and procedures. Security policies and procedures include device identification and authentication, implementation of mandatory protective software (e.g., malicious code detection, firewall), configuration management, scanning devices for malicious code, updating virus protection software, scanning for critical software updates and patches, conducting primary operating system (and possibly other resident software) integrity checks, and disabling unnecessary hardware (e.g., wireless, infrared). Protecting information residing on portable and mobile devices (e.g., employing cryptographic mechanisms to provide confidentiality and integrity protections during storage and while in transit when outside of controlled areas) is covered in the media protection family. Related security controls: MP-4, MP-5.','LOW Not Selected MOD AC-19 HIGH AC-19','Access Control','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/201-08_02_AC-19'),('AC-20','AC-20','08_02_AC-20','Use Of External Information Systems','The organization establishes terms and conditions for authorized individuals to: (i) access the information system from an external information system; and (ii) process, store, and/or transmit organization-controlled information using an external information system.','External information systems are information systems or components of information systems that are outside of the accreditation boundary established by the organization and for which the organization typically has no direct control over the application of required security controls or the assessment of security control effectiveness. External information systems include, but are not limited to, personally owned information systems (e.g., computers, cellular telephones, or personal digital assistants); privately owned computing and communications devices resident in commercial or public facilities (e.g., hotels, convention centers, or airports); information systems owned or controlled by nonfederal governmental organizations; and federal information systems that are not owned by, operated by, or under the direct control of the organization. Authorized individuals include organizational personnel, contractors, or any other individuals with authorized access to the organizational information system. This control does not apply to the use of external information systems to access organizational information systems and information that are intended for public access (e.g., individuals accessing federal information through public interfaces to organizational information systems). The organization establishes terms and conditions for the use of external information systems in accordance with organizational security policies and procedures. The terms and conditions address as a minimum; (i) the types of applications that can be accessed on the organizational information system from the external information system; and (ii) the maximum FIPS 199 security category of information that can be processed, stored, and transmitted on the external information system.','LOW AC-20 MOD AC-20 (1) HIGH AC-20 (1)','Access Control','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/202-08_02_AC-20'),('AT-01','AT-1','08_02_AT-01','Security Awareness And Training Policy And Procedures','The organization develops, disseminates, and periodically reviews/updates: (i) a formal, documented, security awareness and training policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (ii) formal, documented procedures to facilitate the implementation of the security awareness and training policy and associated security awareness and training controls.','The security awareness and training policy and procedures are consistent with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance. The security awareness and training policy can be included as part of the general information security policy for the organization. Security awareness and training procedures can be developed for the security program in general, and for a particular information system, when required. NIST Special Publications 800-16 and 800-50 provide guidance on security awareness and training. NIST Special Publication 800-12 provides guidance on security policies and procedures.','LOW AT-1 MOD AT-1 HIGH AT-1','Awareness And Training','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/167-08_02_AT-01'),('AT-02','AT-2','08_02_AT-02','Security Awareness','The organization provides basic security awareness training to all information system users (including managers and senior executives) before authorizing access to the system, when required by system changes, and [Assignment: organization-defined frequency, at least annually] thereafter.','The organization determines the appropriate content of security awareness training based on the specific requirements of the organization and the information systems to which personnel have authorized access. The organization’s security awareness program is consistent with the requirements contained in C.F.R. Part 5 Subpart C (5 C.F.R 930.301) and with the guidance in NIST Special Publication 800-50.','LOW AT-2 MOD AT-2 HIGH AT-2','Awareness And Training','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/168-08_02_AT-02'),('AT-03','AT-3','08_02_AT-03','Security Training','The organization identifies personnel that have significant information system security roles and responsibilities during the system development life cycle, documents those roles and responsibilities, and provides appropriate information system security training: (i) before authorizing access to the system or performing assigned duties; (ii) when required by system changes; and (iii) [Assignment: organization-defined frequency] thereafter.','The organization determines the appropriate content of security training based on the specific requirements of the organization and the information systems to which personnel have authorized access. In addition, the organization provides system managers, system and network administrators, and other personnel having access to system-level software, adequate technical training to perform their assigned duties. The organization’s security training program is consistent with the requirements contained in C.F.R. Part 5 Subpart C (5 C.F.R 930.301) and with the guidance in NIST Special Publication 800-50.','LOW AT-3 MOD AT-3 HIGH AT-3','Awareness And Training','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/169-08_02_AT-03'),('AT-04','AT-4','08_02_AT-04','Security Training Records','The organization documents and monitors individual information system security training activities including basic security awareness training and specific information system security training.','None.','LOW AT-4 MOD AT-4 HIGH AT-4','Awareness And Training','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/170-08_02_AT-04'),('AT-05','AT-5','08_02_AT-05','Contacts With Security Groups And Associations','The organization establishes and maintains contacts with special interest groups, specialized forums, professional associations, news groups, and/or peer groups of security professionals in similar organizations to stay up to date with the latest recommended security practices, techniques, and technologies and to share the latest security-related information including threats, vulnerabilities, and incidents.','To facilitate ongoing security education and training for organizational personnel in an environment of rapid technology changes and dynamic threats, the organization establishes and institutionalizes contacts with selected groups and associations within the security community. The groups and associations selected are in keeping with the organization’s mission requirements. Information sharing activities regarding threats, vulnerabilities, and incidents related to information systems are consistent with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance.','LOW Not Selected MOD Not Selected HIGH Not Selected','Awareness And Training','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/171-08_02_AT-05'),('AU-01','AU-1','08_02_AU-01','Audit And Accountability Policy And Procedures','The organization develops, disseminates, and periodically reviews/updates: (i) a formal, documented, audit and accountability policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (ii) formal, documented procedures to facilitate the implementation of the audit and accountability policy and associated audit and accountability controls.','The audit and accountability policy and procedures are consistent with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance. The audit and accountability policy can be included as part of the general information security policy for the organization. Audit and accountability procedures can be developed for the security program in general, and for a particular information system, when required. NIST Special Publication 800-12 provides guidance on security policies and procedures.','LOW AU-1 MOD AU-1 HIGH AU-1','Audit And Accountability','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/36-08_02_AU-01'),('AU-02','AU-2','08_02_AU-02','Auditable Events','The information system generates audit records for the following events: [Assignment: organization-defined auditable events].','The purpose of this control is to identify important events which need to be audited as significant and relevant to the security of the information system. The organization specifies which information system components carry out auditing activities. Auditing activity can affect information system performance. Therefore, the organization decides, based upon a risk assessment, which events require auditing on a continuous basis and which events require auditing in response to specific situations. Audit records can be generated at various levels of abstraction, including at the packet level as information traverses the network. Selecting the right level of abstraction for audit record generation is a critical aspect of an audit capability and can facilitate the identification of root causes to problems. Additionally, the security audit function is coordinated with the network health and status monitoring function to enhance the mutual support between the two functions by the selection of information to be recorded by each function. The checklists and configuration guides at http://csrc.nist.gov/pcig/cig.html provide recommended lists of auditable events. The organization defines auditable events that are adequate to support after- the-fact investigations of security incidents. NIST Special Publication 800-92 provides guidance on computer security log management.','LOW AU-2 MOD AU-2 (3) HIGH AU-2 (1) (2) (3)','Audit And Accountability','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/37-08_02_AU-02'),('AU-03','AU-3','08_02_AU-03','Content Of Audit Records','The information system produces audit records that contain sufficient information to establish what events occurred, the sources of the events, and the outcomes of the events.','Audit record content includes, for most audit records: (i) date and time of the event; (ii) the component of the information system (e.g., software component, hardware component) where the event occurred; (iii) type of event; (iv) user/subject identity; and (v) the outcome (success or failure) of the event. NIST Special Publication 800-92 provides guidance on computer security log management.','LOW AU-3 MOD AU-3 (1) HIGH AU-3 (1) (2)','Audit And Accountability','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/172-08_02_AU-03'),('AU-04','AU-4','08_02_AU-04','Audit Storage Capacity','The organization allocates sufficient audit record storage capacity and configures auditing to reduce the likelihood of such capacity being exceeded.','The organization provides sufficient audit storage capacity, taking into account the auditing to be performed and the online audit processing requirements. Related security controls: AU-2, AU-5, AU-6, AU-7, SI-4.','LOW AU-4 MOD AU-4 HIGH AU-4','Audit And Accountability','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/173-08_02_AU-04'),('AU-05','AU-5','08_02_AU-05','Response To Audit Processing Failures','The information system alerts appropriate organizational officials in the event of an audit processing failure and takes the following additional actions: [Assignment: organization-defined actions to be taken (e.g., shut down information system, overwrite oldest audit records, stop generating audit records)].','Audit processing failures include, for example, software/hardware errors, failures in the audit capturing mechanisms, and audit storage capacity being reached or exceeded. Related security control: AU-4.','LOW AU-5 MOD AU-5 HIGH AU-5 (1) (2)','Audit And Accountability','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/174-08_02_AU-05'),('AU-06','AU-6','08_02_AU-06','Audit Monitoring, Analysis, And Reporting','The organization regularly reviews/analyzes information system audit records for indications of inappropriate or unusual activity, investigates suspicious activity or suspected violations, reports findings to appropriate officials, and takes necessary actions.','Organizations increase the level of audit monitoring and analysis activity within the information system whenever there is an indication of increased risk to organizational operations, organizational assets, or individuals based on law enforcement information, intelligence information, or other credible sources of information.','LOW Not Selected MOD AU-6 (2) HIGH AU-6 (1) (2)','Audit And Accountability','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/175-08_02_AU-06'),('AU-07','AU-7','08_02_AU-07','Audit Reduction And Report Generation','The information system provides an audit reduction and report generation capability.','Audit reduction, review, and reporting tools support after-the-fact investigations of security incidents without altering original audit records.','LOW Not Selected MOD AU-7 (1) HIGH AU-7 (1)','Audit And Accountability','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/176-08_02_AU-07'),('AU-08','AU-8','08_02_AU-08','Time Stamps','The information system provides time stamps for use in audit record generation.','Time stamps (including date and time) of audit records are generated using internal system clocks.','LOW AU-8 MOD AU-8 (1) HIGH AU-8 (1)','Audit And Accountability','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/177-08_02_AU-08'),('AU-09','AU-9','08_02_AU-09','Protection Of Audit Information','The information system protects audit information and audit tools from unauthorized access, modification, and deletion.','Audit information includes all information (e.g., audit records, audit settings, and audit reports) needed to successfully audit information system activity.','LOW AU-9 MOD AU-9 HIGH AU-9','Audit And Accountability','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/178-08_02_AU-09'),('AU-10','AU-10','08_02_AU-10','Non-Repudiation','The information system provides the capability to determine whether a given individual took a particular action.','Examples of particular actions taken by individuals include creating information, sending a message, approving information (e.g., indicating concurrence or signing a contract), and receiving a message. Non-repudiation protects against later false claims by an individual of not having taken a specific action. Non-repudiation protects individuals against later claims by an author of not having authored a particular document, a sender of not having transmitted a message, a receiver of not having received a message, or a signatory of not having signed a document. Non-repudiation services can be used to determine if information originated from an individual, or if an individual took specific actions (e.g., sending an email, signing a contract, approving a procurement request) or received specific information. Non-repudiation services are obtained by employing various techniques or mechanisms (e.g., digital signatures, digital message receipts, time stamps).','LOW Not Selected MOD Not Selected HIGH Not Selected','Audit And Accountability','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/179-08_02_AU-10'),('AU-11','AU-11','08_02_AU-11','Audit Record Retention','The organization retains audit records for [Assignment: organization-defined time period] to provide support for after-the-fact investigations of security incidents and to meet regulatory and organizational information retention requirements.','The organization retains audit records until it is determined that they are no longer needed for administrative, legal, audit, or other operational purposes. This includes, for example, retention and availability of audit records relative to Freedom of Information Act (FOIA) requests, subpoena, and law enforcement actions. Standard categorizations of audit records relative to such types of actions and standard response processes for each type of action are developed and disseminated. NIST Special Publication 800-61 provides guidance on computer security incident handling and audit record retention.','LOW AU-11 MOD AU-11 HIGH AU-11','Audit And Accountability','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/180-08_02_AU-11'),('CA-01','CA-1','08_02_CA-01','Certification, Accreditation, And Security Assessment Policies And Procedures','The organization develops, disseminates, and periodically reviews/updates: (i) formal, documented, security assessment and certification and accreditation policies that address purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (ii) formal, documented procedures to facilitate the implementation of the security assessment and certification and accreditation policies and associated assessment, certification, and accreditation controls.','The security assessment and certification and accreditation policies and procedures are consistent with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance. The security assessment and certification and accreditation policies can be included as part of the general information security policy for the organization. Security assessment and certification and accreditation procedures can be developed for the security program in general, and for a particular information system, when required. The organization defines what constitutes a significant change to the information system to achieve consistent security reaccreditations. NIST Special Publication 800-53A provides guidance on security control assessments. NIST Special Publication 800-37 provides guidance on security certification and accreditation. NIST Special Publication 800-12 provides guidance on security policies and procedures.','LOW CA-1 MOD CA-1 HIGH CA-1','Certification, Accreditation, And Security Assessments','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/160-08_02_CA-01'),('CA-02','CA-2','08_02_CA-02','Security Assessments','The organization conducts an assessment of the security controls in the information system [Assignment: organization-defined frequency, at least annually] to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting the security requirements for the system.','This control is intended to support the FISMA requirement that the management, operational, and technical controls in each information system contained in the inventory of major information systems be assessed with a frequency depending on risk, but no less than annually. The FISMA requirement for (at least) annual security control assessments should not be interpreted by organizations as adding additional assessment requirements to those requirements already in place in the security certification and accreditation process. To satisfy the annual FISMA assessment requirement, organizations can draw upon the security control assessment results from any of the following sources, including but not limited to: (i) security certifications conducted as part of an information system accreditation or reaccreditation process (see CA-4); (ii) continuous monitoring activities (see CA-7); or (iii) testing and evaluation of the information system as part of the ongoing system development life cycle process (provided that the testing and evaluation results are current and relevant to the determination of security control effectiveness). Existing security assessment results are reused to the extent that they are still valid and are supplemented with additional assessments as needed. Reuse of assessment information is critical in achieving a broad-based, cost-effective, and fully integrated security program capable of producing the needed evidence to determine the actual security status of the information system. OMB does not require an annual assessment of all security controls employed in an organizational information system. In accordance with OMB policy, organizations must annually assess a subset of the security controls based on: (i) the FIPS 199 security categorization of the information system; (ii) the specific security controls selected and employed by the organization to protect the information system; and (iii) the level of assurance (or confidence) that the organization must have in determining the effectiveness of the security controls in the information system. It is expected that the organization will assess all of the security controls in the information system during the three-year accreditation cycle. The organization can use the current year’s assessment results obtained during security certification to meet the annual FISMA assessment requirement (see CA- 4). NIST Special Publication 800-53A provides guidance on security control assessments to include reuse of existing assessment results. Related security controls: CA-4, CA-6, CA-7, SA- 11.','LOW CA-2 MOD CA-2 HIGH CA-2','Certification, Accreditation, And Security Assessments','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/161-08_02_CA-02'),('CA-03','CA-3','08_02_CA-03','Information System Connections','The organization authorizes all connections from the information system to other information systems outside of the accreditation boundary through the use of system connection agreements and monitors/controls the system connections on an ongoing basis.','Since FIPS 199 security categorizations apply to individual information systems, the organization carefully considers the risks that may be introduced when systems are connected to other information systems with different security requirements and security controls, both within the organization and external to the organization. Risk considerations also include information systems sharing the same networks. NIST Special Publication 800-47 provides guidance on connecting information systems. Related security controls: SC-7, SA-9.','LOW CA-3 MOD CA-3 HIGH CA-3','Certification, Accreditation, And Security Assessments','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/162-08_02_CA-03'),('CA-04','CA-4','08_02_CA-04','Security Certification','The organization conducts an assessment of the security controls in the information system to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting the security requirements for the system.','A security certification is conducted by the organization in support of the OMB Circular A-130, Appendix III requirement for accrediting the information system. The security certification is a key factor in all security accreditation (i.e., authorization) decisions and is integrated into and spans the system development life cycle. The organization assesses all security controls in an information system during the initial security accreditation. Subsequent to the initial accreditation and in accordance with OMB policy, the organization assesses a subset of the controls annually during continuous monitoring (see CA-7). The organization can use the current year’s assessment results obtained during security certification to meet the annual FISMA assessment requirement (see CA-2). NIST Special Publication 800-53A provides guidance on security control assessments. NIST Special Publication 800-37 provides guidance on security certification and accreditation. Related security controls: CA-2, CA-6, SA-11.','LOW CA-4 MOD CA-4 (1) HIGH CA-4 (1)','Certification, Accreditation, And Security Assessments','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/163-08_02_CA-04'),('CA-05','CA-5','08_02_CA-05','Plan Of Action And Milestones','The organization develops and updates [Assignment: organization-defined frequency], a plan of action and milestones for the information system that documents the organization’s planned, implemented, and evaluated remedial actions to correct deficiencies noted during the assessment of the security controls and to reduce or eliminate known vulnerabilities in the system.','The plan of action and milestones is a key document in the security accreditation package developed for the authorizing official and is subject to federal reporting requirements established by OMB. The plan of action and milestones updates are based on the findings from security control assessments, security impact analyses, and continuous monitoring activities. OMB FISMA reporting guidance contains instructions regarding organizational plans of action and milestones. NIST Special Publication 800-37 provides guidance on the security certification and accreditation of information systems. NIST Special Publication 800-30 provides guidance on risk mitigation.','LOW CA-5 MOD CA-5 HIGH CA-5','Certification, Accreditation, And Security Assessments','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/164-08_02_CA-05'),('CA-06','CA-6','08_02_CA-06','Security Accreditation','The organization authorizes (i.e., accredits) the information system for processing before operations and updates the authorization [Assignment: organization-defined frequency, at least every three years] or when there is a significant change to the system. A senior organizational official signs and approves the security accreditation.','OMB Circular A-130, Appendix III, establishes policy for security accreditations of federal information systems. The organization assesses the security controls employed within the information system before and in support of the security accreditation. Security assessments conducted in support of security accreditations are called security certifications. The security accreditation of an information system is not a static process. Through the employment of a comprehensive continuous monitoring process (the fourth and final phase of the certification and accreditation process), the critical information contained in the accreditation package (i.e., the system security plan, the security assessment report, and the plan of action and milestones) is updated on an ongoing basis providing the authorizing official and the information system owner with an up-to-date status of the security state of the information system. To reduce the administrative burden of the three-year reaccreditation process, the authorizing official uses the results of the ongoing continuous monitoring process to the maximum extent possible as the basis for rendering a reaccreditation decision. NIST Special Publication 800-37 provides guidance on the security certification and accreditation of information systems. Related security controls: CA-2, CA-4, CA-7.','LOW CA-6 MOD CA-6 HIGH CA-6','Certification, Accreditation, And Security Assessments','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/165-08_02_CA-06'),('CA-07','CA-7','08_02_CA-07','Continuous Monitoring','The organization monitors the security controls in the information system on an ongoing basis.','Continuous monitoring activities include configuration management and control of information system components, security impact analyses of changes to the system, ongoing assessment of security controls, and status reporting. The organization assesses all security controls in an information system during the initial security accreditation. Subsequent to the initial accreditation and in accordance with OMB policy, the organization assesses a subset of the controls annually during continuous monitoring. The selection of an appropriate subset of security controls is based on: (i) the FIPS 199 security categorization of the information system; (ii) the specific security controls selected and employed by the organization to protect the information system; and (iii) the level of assurance (or grounds for confidence) that the organization must have in determining the effectiveness of the security controls in the information system. The organization establishes the selection criteria and subsequently selects a subset of the security controls employed within the information system for assessment. The organization also establishes the schedule for control monitoring to ensure adequate coverage is achieved. Those security controls that are volatile or critical to protecting the information system are assessed at least annually. All other controls are assessed at least once during the information system’s three- year accreditation cycle. The organization can use the current year’s assessment results obtained during continuous monitoring to meet the annual FISMA assessment requirement (see CA-2). This control is closely related to and mutually supportive of the activities required in monitoring configuration changes to the information system. An effective continuous monitoring program results in ongoing updates to the information system security plan, the security assessment report, and the plan of action and milestones—the three principle documents in the security accreditation package. A rigorous and well executed continuous monitoring process significantly reduces the level of effort required for the reaccreditation of the information system. NIST Special Publication 800-37 provides guidance on the continuous monitoring process. NIST Special Publication 800-53A provides guidance on the assessment of security controls. Related security controls: CA-2, CA-4, CA-5, CA-6, CM-4.','LOW CA-7 MOD CA-7 HIGH CA-7','Certification, Accreditation, And Security Assessments','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/166-08_02_CA-07'),('CM-01','CM-1','08_02_CM-01','Configuration Management Policy And Procedures','The organization develops, disseminates, and periodically reviews/updates: (i) a formal, documented, configuration management policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (ii) formal, documented procedures to facilitate the implementation of the configuration management policy and associated configuration management controls.','The configuration management policy and procedures are consistent with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance. The configuration management policy can be included as part of the general information security policy for the organization. Configuration management procedures can be developed for the security program in general, and for a particular information system, when required. NIST Special Publication 800-12 provides guidance on security policies and procedures.','LOW CM-1 MOD CM-1 HIGH CM-1','Configuration Management','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/152-08_02_CM-01'),('CM-02','CM-2','08_02_CM-02','Baseline Configuration','The organization develops, documents, and maintains a current baseline configuration of the information system.','This control establishes a baseline configuration for the information system. The baseline configuration provides information about a particular component’s makeup (e.g., the standard software load for a workstation or notebook computer including updated patch information) and the component’s logical placement within the information system architecture. The baseline configuration also provides the organization with a well-defined and documented specification to which the information system is built and deviations, if required, are documented in support of mission needs/objectives. The baseline configuration of the information system is consistent with the Federal Enterprise Architecture. Related security controls: CM-6, CM-8.','LOW CM-2 MOD CM-2 (1) HIGH CM-2 (1) (2)','Configuration Management','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/153-08_02_CM-02'),('CM-03','CM-3','08_02_CM-03','Configuration Change Control','The organization authorizes, documents, and controls changes to the information system.','The organization manages configuration changes to the information system using an organizationally approved process (e.g., a chartered Configuration Control Board). Configuration change control involves the systematic proposal, justification, implementation, test/evaluation, review, and disposition of changes to the information system, including upgrades and modifications. Configuration change control includes changes to the configuration settings for information technology products (e.g., operating systems, firewalls, routers). The organization includes emergency changes in the configuration change control process, including changes resulting from the remediation of flaws. The approvals to implement a change to the information system include successful results from the security analysis of the change. The organization audits activities associated with configuration changes to the information system. Related security controls: CM-4, CM-6, SI-2.','LOW Not Selected MOD CM-3 HIGH CM-3 (1)','Configuration Management','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/154-08_02_CM-03'),('CM-04','CM-4','08_02_CM-04','Monitoring Configuration Changes','The organization monitors changes to the information system conducting security impact analyses to determine the effects of the changes.','Prior to change implementation, and as part of the change approval process, the organization analyzes changes to the information system for potential security impacts. After the information system is changed (including upgrades and modifications), the organization checks the security features to verify that the features are still functioning properly. The organization audits activities associated with configuration changes to the information system. Monitoring configuration changes and conducting security impact analyses are important elements with regard to the ongoing assessment of security controls in the information system. Related security control: CA-7.','LOW Not Selected MOD CM-4 HIGH CM-4','Configuration Management','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/155-08_02_CM-04'),('CM-05','CM-5','08_02_CM-05','Access Restrictions For Change','The organization: (i) approves individual access privileges and enforces physical and logical access restrictions associated with changes to the information system; and (ii) generates, retains, and reviews records reflecting all such changes.','Planned or unplanned changes to the hardware, software, and/or firmware components of the information system can have significant effects on the overall security of the system. Accordingly, only qualified and authorized individuals obtain access to information system components for purposes of initiating changes, including upgrades, and modifications.','LOW Not Selected MOD CM-5 HIGH CM-5 (1)','Configuration Management','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/156-08_02_CM-05'),('CM-06','CM-6','08_02_CM-06','Configuration Settings','The organization: (i) establishes mandatory configuration settings for information technology products employed within the information system; (ii) configures the security settings of information technology products to the most restrictive mode consistent with operational requirements; (iii) documents the configuration settings; and (iv) enforces the configuration settings in all components of the information system.','Configuration settings are the configurable parameters of the information technology products that compose the information system. Organizations monitor and control changes to the configuration settings in accordance with organizational policies and procedures. OMB FISMA reporting instructions provide guidance on configuration requirements for federal information systems. NIST Special Publication 800-70 provides guidance on producing and using configuration settings for information technology products employed in organizational information systems. Related security controls: CM-2, CM-3, SI-4.','LOW CM-6 MOD CM-6 HIGH CM-6 (1)','Configuration Management','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/157-08_02_CM-06'),('CM-07','CM-7','08_02_CM-07','Least Functionality','The organization configures the information system to provide only essential capabilities and specifically prohibits and/or restricts the use of the following functions, ports, protocols, and/or services: [Assignment: organization-defined list of prohibited and/or restricted functions, ports, protocols, and/or services].','Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, provided by default, may not be necessary to support essential organizational operations (e.g., key missions, functions). Additionally, it is sometimes convenient to provide multiple services from a single component of an information system, but doing so increases risk over limiting the services provided by any one component. Where feasible, the organization limits component functionality to a single function per device (e.g., email server or web server, not both). The functions and services provided by information systems, or individual components of information systems, are carefully reviewed to determine which functions and services are candidates for elimination (e.g., Voice Over Internet Protocol, Instant Messaging, File Transfer Protocol, Hyper Text Transfer Protocol, file sharing).','LOW Not Selected MOD CM-7 HIGH CM-7 (1)','Configuration Management','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/158-08_02_CM-07'),('CM-08','CM-8','08_02_CM-08','Information System Component Inventory','The organization develops, documents, and maintains a current inventory of the components of the information system and relevant ownership information.','The organization determines the appropriate level of granularity for the information system components included in the inventory that are subject to management control (i.e., tracking, and reporting). The inventory of information system components includes any information determined to be necessary by the organization to achieve effective property accountability (e.g., manufacturer, model number, serial number, software license information, system/component owner). The component inventory is consistent with the accreditation boundary of the information system. Related security controls: CM-2, CM-6.','LOW CM-8 MOD CM-8 (1) HIGH CM-8 (1) (2)','Configuration Management','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/159-08_02_CM-08'),('CP-01','CP-1','08_02_CP-01','Contingency Planning Policy And Procedures','The organization develops, disseminates, and periodically reviews/updates: (i) a formal, documented, contingency planning policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (ii) formal, documented procedures to facilitate the implementation of the contingency planning policy and associated contingency planning controls.','The contingency planning policy and procedures are consistent with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance. The contingency planning policy can be included as part of the general information security policy for the organization. Contingency planning procedures can be developed for the security program in general, and for a particular information system, when required. NIST Special Publication 800-34 provides guidance on contingency planning. NIST Special Publication 800-12 provides guidance on security policies and procedures.','LOW CP-1 MOD CP-1 HIGH CP-1','Contingency Planning','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/142-08_02_CP-01'),('CP-02','CP-2','08_02_CP-02','Contingency Plan','The organization develops and implements a contingency plan for the information system addressing contingency roles, responsibilities, assigned individuals with contact information, and activities associated with restoring the system after a disruption or failure. Designated officials within the organization review and approve the contingency plan and distribute copies of the plan to key contingency personnel.','None.','LOW CP-2 MOD CP-2 (1) HIGH CP-2 (1) (2)','Contingency Planning','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/143-08_02_CP-02'),('CP-03','CP-3','08_02_CP-03','Contingency Training','The organization trains personnel in their contingency roles and responsibilities with respect to the information system and provides refresher training [Assignment: organization- defined frequency, at least annually].','None.','LOW Not Selected MOD CP-3 HIGH CP-3 (1)','Contingency Planning','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/144-08_02_CP-03'),('CP-04','CP-4','08_02_CP-04','Contingency Plan Testing And Exercises','The organization: (i) tests and/or exercises the contingency plan for the information system [Assignment: organization-defined frequency, at least annually] using [Assignment: organization-defined tests and/or exercises] to determine the plan’s effectiveness and the organization’s readiness to execute the plan; and (ii) reviews the contingency plan test/exercise results and initiates corrective actions.','There are several methods for testing and/or exercising contingency plans to identify potential weaknesses (e.g., full-scale contingency plan testing, functional/tabletop exercises). The depth and rigor of contingency plan testing and/or exercises increases with the FIPS 199 impact level of the information system. Contingency plan testing and/or exercises also include a determination of the effects on organizational operations and assets (e.g., reduction in mission capability) and individuals arising due to contingency operations in accordance with the plan. NIST Special Publication 800-84 provides guidance on test, training, and exercise programs for information technology plans and capabilities.','LOW CP-4 MOD CP-4 (1) HIGH CP-4 (1) (2)','Contingency Planning','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/145-08_02_CP-04'),('CP-05','CP-5','08_02_CP-05','Contingency Plan Update','The organization reviews the contingency plan for the information system [Assignment: organization-defined frequency, at least annually] and revises the plan to address system/organizational changes or problems encountered during plan implementation, execution, or testing.','Organizational changes include changes in mission, functions, or business processes supported by the information system. The organization communicates changes to appropriate organizational elements responsible for related plans (e.g., Business Continuity Plan, Disaster Recovery Plan, Continuity of Operations Plan, Business Recovery Plan, Incident Response Plan, Emergency Action Plan).','LOW CP-5 MOD CP-5 HIGH CP-5','Contingency Planning','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/146-08_02_CP-05'),('CP-06','CP-6','08_02_CP-06','Alternate Storage Site','The organization identifies an alternate storage site and initiates necessary agreements to permit the storage of information system backup information.','The frequency of information system backups and the transfer rate of backup information to the alternate storage site (if so designated) are consistent with the organization’s recovery time objectives and recovery point objectives.','LOW Not Selected MOD CP-6 (1) (3) HIGH CP-6 (1) (2) (3)','Contingency Planning','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/147-08_02_CP-06'),('CP-07','CP-7','08_02_CP-07','Alternate Processing Site','The organization identifies an alternate processing site and initiates necessary agreements to permit the resumption of information system operations for critical mission/business functions within [Assignment: organization-defined time period] when the primary processing capabilities are unavailable.','Equipment and supplies required to resume operations within the organization-defined time period are either available at the alternate site or contracts are in place to support delivery to the site. Timeframes to resume information system operations are consistent with organization-established recovery time objectives.','LOW Not Selected MOD CP-7 (1) (2) (3) HIGH CP-7 (1) (2) (3) (4)','Contingency Planning','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/148-08_02_CP-07'),('CP-08','CP-8','08_02_CP-08','Telecommunications Services','The organization identifies primary and alternate telecommunications services to support the information system and initiates necessary agreements to permit the resumption of system operations for critical mission/business functions within [Assignment: organization-defined time period] when the primary telecommunications capabilities are unavailable.','In the event that the primary and/or alternate telecommunications services are provided by a common carrier, the organization requests Telecommunications Service Priority (TSP) for all telecommunications services used for national security emergency preparedness (see http://tsp.ncs.gov for a full explanation of the TSP program).','LOW Not Selected MOD CP-8 (1) (2) HIGH CP-8 (1) (2) (3) (4)','Contingency Planning','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/149-08_02_CP-08'),('CP-09','CP-9','08_02_CP-09','Information System Backup','The organization conducts backups of user-level and system-level information (including system state information) contained in the information system [Assignment: organization-defined frequency] and protects backup information at the storage location.','The frequency of information system backups and the transfer rate of backup information to alternate storage sites (if so designated) are consistent with the organization’s recovery time objectives and recovery point objectives. While integrity and availability are the primary concerns for system backup information, protecting backup information from unauthorized disclosure is also an important consideration depending on the type of information residing on the backup media and the FIPS 199 impact level. An organizational assessment of risk guides the use of encryption for backup information. The protection of system backup information while in transit is beyond the scope of this control. Related security controls: MP-4, MP-5.','LOW CP-9 MOD CP-9 (1) (4) HIGH CP-9 (1) (2) (3) (4)','Contingency Planning','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/150-08_02_CP-09'),('CP-10','CP-10','08_02_CP-10','Information System Recovery And Reconstitution','The organization employs mechanisms with supporting procedures to allow the information system to be recovered and reconstituted to a known secure state after a disruption or failure.','Information system recovery and reconstitution to a known secure state means that all system parameters (either default or organization-established) are set to secure values, security-critical patches are reinstalled, security-related configuration settings are reestablished, system documentation and operating procedures are available, application and system software is reinstalled and configured with secure settings, information from the most recent, known secure backups is loaded, and the system is fully tested.','LOW CP-10 MOD CP-10 HIGH CP-10 (1)','Contingency Planning','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/151-08_02_CP-10'),('IA-01','IA-1','08_02_IA-01','Identification And Authentication Policy And Procedures','The organization develops, disseminates, and periodically reviews/updates: (i) a formal, documented, identification and authentication policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (ii) formal, documented procedures to facilitate the implementation of the identification and authentication policy and associated identification and authentication controls.','The identification and authentication policy and procedures are consistent with: (i) FIPS 201 and Special Publications 800-73, 800-76, and 800-78; and (ii) other applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance. The identification and authentication policy can be included as part of the general information security policy for the organization. Identification and authentication procedures can be developed for the security program in general, and for a particular information system, when required. NIST Special Publication 800-12 provides guidance on security policies and procedures. NIST Special Publication 800-63 provides guidance on remote electronic authentication.','LOW IA-1 MOD IA-1 HIGH IA-1','Identification And Authentication','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/181-08_02_IA-01'),('IA-02','IA-2','08_02_IA-02','User Identification And Authentication','The information system uniquely identifies and authenticates users (or processes acting on behalf of users).','Users are uniquely identified and authenticated for all accesses other than those accesses explicitly identified and documented by the organization in accordance security control AC-14. Authentication of user identities is accomplished through the use of passwords, tokens, biometrics, or in the case of multifactor authentication, some combination thereof. NIST Special Publication 800-63 provides guidance on remote electronic authentication including strength of authentication mechanisms. For purposes of this control, the guidance provided in Special Publication 800-63 is applied to both local and remote access to information systems. Remote access is any access to an organizational information system by a user (or an information system) communicating through an external, non-organization-controlled network (e.g., the Internet). Local access is any access to an organizational information system by a user (or an information system) communicating through an internal organization-controlled network (e.g., local area network) or directly to a device without the use of a network. Unless a more stringent control enhancement is specified, authentication for both local and remote information system access is NIST Special Publication 800-63 level 1 compliant. FIPS 201 and Special Publications 800-73, 800-76, and 800-78 specify a personal identity verification (PIV) credential for use in the unique identification and authentication of federal employees and contractors. In addition to identifying and authenticating users at the information system level (i.e., at system logon), identification and authentication mechanisms are employed at the application level, when necessary, to provide increased information security for the organization. In accordance with OMB policy and E-Authentication E-Government initiative, authentication of public users accessing federal information systems may also be required to protect nonpublic or privacy-related information. The e-authentication risk assessment conducted in accordance with OMB Memorandum 04-04 is used in determining the NIST Special Publication 800-63 compliance requirements for such accesses with regard to the IA-2 control and its enhancements. Scalability, practicality, and security issues are simultaneously considered in balancing the need to ensure ease of use for public access to such information and information systems with the need to protect organizational operations, organizational assets, and individuals. Related security controls: AC-14, AC-17.','LOW IA-2 MOD IA-2 (1) HIGH IA-2 (2) (3)','Identification And Authentication','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/22-08_02_IA-02'),('IA-03','IA-3','08_02_IA-03','Device Identification And Authentication','The information system identifies and authenticates specific devices before establishing a connection.','The information system typically uses either shared known information (e.g., Media Access Control (MAC) or Transmission Control Protocol/Internet Protocol (TCP/IP) addresses) or an organizational authentication solution (e.g., IEEE 802.1x and Extensible Authentication Protocol (EAP) or a Radius server with EAP-Transport Layer Security (TLS) authentication) to identify and authenticate devices on local and/or wide area networks. The required strength of the device authentication mechanism is determined by the FIPS 199 security categorization of the information system with higher impact levels requiring stronger authentication.','LOW Not Selected MOD IA-3 HIGH IA-3','Identification And Authentication','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/182-08_02_IA-03'),('IA-04','IA-4','08_02_IA-04','Identifier Management','The organization manages user identifiers by: (i) uniquely identifying each user; (ii) verifying the identity of each user; (iii) receiving authorization to issue a user identifier from an appropriate organization official; (iv) issuing the user identifier to the intended party; (v) disabling the user identifier after [Assignment: organization-defined time period] of inactivity; and (vi) archiving user identifiers.','Identifier management is not applicable to shared information system accounts (e.g., guest and anonymous accounts). FIPS 201 and Special Publications 800-73, 800- 76, and 800-78 specify a personal identity verification (PIV) credential for use in the unique identification and authentication of federal employees and contractors.','LOW IA-4 MOD IA-4 HIGH IA-4','Identification And Authentication','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/183-08_02_IA-04'),('IA-05','IA-5','08_02_IA-05','Authenticator Management','The organization manages information system authenticators by: (i) defining initial authenticator content; (ii) establishing administrative procedures for initial authenticator distribution, for lost/compromised, or damaged authenticators, and for revoking authenticators; (iii) changing default authenticators upon information system installation; and (iv) changing/refreshing authenticators periodically.','Information system authenticators include, for example, tokens, PKI certificates, biometrics, passwords, and key cards. Users take reasonable measures to safeguard authenticators including maintaining possession of their individual authenticators, not loaning or sharing authenticators with others, and reporting lost or compromised authenticators immediately. For password-based authentication, the information system: (i) protects passwords from unauthorized disclosure and modification when stored and transmitted; (ii) prohibits passwords from being displayed when entered; (iii) enforces password minimum and maximum lifetime restrictions; and (iv) prohibits password reuse for a specified number of generations. For PKI- based authentication, the information system: (i) validates certificates by constructing a certification path to an accepted trust anchor; (ii) establishes user control of the corresponding private key; and (iii) maps the authenticated identity to the user account. In accordance with OMB policy and related E-authentication initiatives, authentication of public users accessing federal information systems (and associated authenticator management) may also be required to protect nonpublic or privacy-related information. FIPS 201 and Special Publications 800-73, 800-76, and 800-78 specify a personal identity verification (PIV) credential for use in the unique identification and authentication of federal employees and contractors. NIST Special Publication 800-63 provides guidance on remote electronic authentication.','LOW IA-5 MOD IA-5 HIGH IA-5','Identification And Authentication','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/184-08_02_IA-05'),('IA-06','IA-6','08_02_IA-06','Authenticator Feedback','The information system obscures feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.','The feedback from the information system does not provide information that would allow an unauthorized user to compromise the authentication mechanism. Displaying asterisks when a user types in a password is an example of obscuring feedback of authentication information.','LOW IA-6 MOD IA-6 HIGH IA-6','Identification And Authentication','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/185-08_02_IA-06'),('IA-07','IA-7','08_02_IA-07','Cryptographic Module Authentication','The information system employs authentication methods that meet the requirements of applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module.','The applicable federal standard for authentication to a cryptographic module is FIPS 140-2 (as amended). Validation certificates issued by the NIST Cryptographic Module Validation Program (including FIPS 140-1, FIPS 140-2, and future amendments) remain in effect, and the modules remain available for continued use and purchase until a validation certificate is specifically revoked. Additional information on the use of validated cryptography is available at http://csrc.nist.gov/cryptval.','LOW IA-7 MOD IA-7 HIGH IA-7','Identification And Authentication','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/186-08_02_IA-07'),('IR-01','IR-1','08_02_IR-01','Incident Response Policy And Procedures','The organization develops, disseminates, and periodically reviews/updates: (i) a formal, documented, incident response policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (ii) formal, documented procedures to facilitate the implementation of the incident response policy and associated incident response controls.','The incident response policy and procedures are consistent with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance. The incident response policy can be included as part of the general information security policy for the organization. Incident response procedures can be developed for the security program in general, and for a particular information system, when required. NIST Special Publication 800-12 provides guidance on security policies and procedures. NIST Special Publication 800-61 provides guidance on incident handling and reporting. NIST Special Publication 800-83 provides guidance on malware incident handling and prevention.','LOW IR-1 MOD IR-1 HIGH IR-1','Incident Response','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/135-08_02_IR-01'),('IR-02','IR-2','08_02_IR-02','Incident Response Training','The organization trains personnel in their incident response roles and responsibilities with respect to the information system and provides refresher training [Assignment: organization- defined frequency, at least annually].','None.','LOW Not Selected MOD IR-2 HIGH IR-2 (1)','Incident Response','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/136-08_02_IR-02'),('IR-03','IR-3','08_02_IR-03','Incident Response Testing And Exercises','The organization tests and/or exercises the incident response capability for the information system [Assignment: organization-defined frequency, at least annually] using [Assignment: organization-defined tests and/or exercises] to determine the incident response effectiveness and documents the results.','NIST Special Publication 800-84 provides guidance on test, training, and exercise programs for information technology plans and capabilities.','LOW Not Selected MOD IR-3 HIGH IR-3 (1)','Incident Response','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/137-08_02_IR-03'),('IR-04','IR-4','08_02_IR-04','Incident Handling','The organization implements an incident handling capability for security incidents that includes preparation, detection and analysis, containment, eradication, and recovery.','Incident-related information can be obtained from a variety of sources including, but not limited to, audit monitoring, network monitoring, physical access monitoring, and user/administrator reports. The organization incorporates the lessons learned from ongoing incident handling activities into the incident response procedures and implements the procedures accordingly. Related security controls: AU-6, PE-6.','LOW IR-4 MOD IR-4 (1) HIGH IR-4 (1)','Incident Response','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/138-08_02_IR-04'),('IR-05','IR-5','08_02_IR-05','Incident Monitoring','The organization tracks and documents information system security incidents on an ongoing basis.','None.','LOW Not Selected MOD IR-5 HIGH IR-5 (1)','Incident Response','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/139-08_02_IR-05'),('IR-06','IR-6','08_02_IR-06','Incident Reporting','The organization promptly reports incident information to appropriate authorities.','The types of incident information reported, the content and timeliness of the reports, and the list of designated reporting authorities or organizations are consistent with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance. Organizational officials report cyber security incidents to the United States Computer Emergency Readiness Team (US-CERT) at http://www.us-cert.gov within the specified timeframe designated in the US-CERT Concept of Operations for Federal Cyber Security Incident Handling. In addition to incident information, weaknesses and vulnerabilities in the information system are reported to appropriate organizational officials in a timely manner to prevent security incidents. NIST Special Publication 800-61 provides guidance on incident reporting.','LOW IR-6 MOD IR-6 (1) HIGH IR-6 (1)','Incident Response','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/140-08_02_IR-06'),('IR-07','IR-7','08_02_IR-07','Incident Response Assistance','The organization provides an incident response support resource that offers advice and assistance to users of the information system for the handling and reporting of security incidents. The support resource is an integral part of the organization’s incident response capability.','Possible implementations of incident response support resources in an organization include a help desk or an assistance group and access to forensics services, when required.','LOW IR-7 MOD IR-7 (1) HIGH IR-7 (1)','Incident Response','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/141-08_02_IR-07'),('MA-01','MA-1','08_02_MA-01','System Maintenance Policy And Procedures','The organization develops, disseminates, and periodically reviews/updates: (i) a formal, documented, information system maintenance policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (ii) formal, documented procedures to facilitate the implementation of the information system maintenance policy and associated system maintenance controls.','The information system maintenance policy and procedures are consistent with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance. The information system maintenance policy can be included as part of the general information security policy for the organization. System maintenance procedures can be developed for the security program in general, and for a particular information system, when required. NIST Special Publication 800-12 provides guidance on security policies and procedures.','LOW MA-1 MOD MA-1 HIGH MA-1','Maintenance','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/128-08_02_MA-01'),('MA-02','MA-2','08_02_MA-02','Controlled Maintenance','The organization schedules, performs, documents, and reviews records of routine preventative and regular maintenance (including repairs) on the components of the information system in accordance with manufacturer or vendor specifications and/or organizational requirements.','All maintenance activities to include routine, scheduled maintenance and repairs are controlled; whether performed on site or remotely and whether the equipment is serviced on site or removed to another location. Organizational officials approve the removal of the information system or information system components from the facility when repairs are necessary. If the information system or component of the system requires off-site repair, the organization removes all information from associated media using approved procedures. After maintenance is performed on the information system, the organization checks all potentially impacted security controls to verify that the controls are still functioning properly.','LOW MA-2 MOD MA-2 (1) HIGH MA-2 (1) (2)','Maintenance','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/129-08_02_MA-02'),('MA-03','MA-3','08_02_MA-03','Maintenance Tools','The organization approves, controls, and monitors the use of information system maintenance tools and maintains the tools on an ongoing basis.','The intent of this control is to address hardware and software brought into the information system specifically for diagnostic/repair actions (e.g., a hardware or software packet sniffer that is introduced for the purpose of a particular maintenance activity). Hardware and/or software components that may support information system maintenance, yet are a part of the system (e.g., the software implementing “ping,” “ls,” “ipconfig,” or the hardware and software implementing the monitoring port of an Ethernet switch) are not covered by this control.','LOW Not Selected MOD MA-3 HIGH MA-3 (1) (2) (3)','Maintenance','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/130-08_02_MA-03'),('MA-04','MA-4','08_02_MA-04','Remote Maintenance','The organization authorizes, monitors, and controls any remotely executed maintenance and diagnostic activities, if employed.','Remote maintenance and diagnostic activities are conducted by individuals communicating through an external, non-organization-controlled network (e.g., the Internet). The use of remote maintenance and diagnostic tools is consistent with organizational policy and documented in the security plan for the information system. The organization maintains records for all remote maintenance and diagnostic activities. Other techniques and/or controls to consider for improving the security of remote maintenance include: (i) encryption and decryption of communications; (ii) strong identification and authentication techniques, such as Level 3 or 4 tokens as described in NIST Special Publication 800-63; and (iii) remote disconnect verification. When remote maintenance is completed, the organization (or information system in certain cases) terminates all sessions and remote connections invoked in the performance of that activity. If password-based authentication is used to accomplish remote maintenance, the organization changes the passwords following each remote maintenance service. NIST Special Publication 800-88 provides guidance on media sanitization. The National Security Agency provides a listing of approved media sanitization products at http://www.nsa.gov/ia/government/mdg.cfm. Related security controls: IA-2, MP-6.','LOW MA-4 MOD MA-4 (1) (2) HIGH MA-4 (1) (2) (3)','Maintenance','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/131-08_02_MA-04'),('MA-05','MA-5','08_02_MA-05','Maintenance Personnel','The organization allows only authorized personnel to perform maintenance on the information system.','Maintenance personnel (whether performing maintenance locally or remotely) have appropriate access authorizations to the information system when maintenance activities allow access to organizational information or could result in a future compromise of confidentiality, integrity, or availability. When maintenance personnel do not have needed access authorizations, organizational personnel with appropriate access authorizations supervise maintenance personnel during the performance of maintenance activities on the information system.','LOW MA-5 MOD MA-5 HIGH MA-5','Maintenance','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/132-08_02_MA-05'),('MA-06','MA-6','08_02_MA-06','Timely Maintenance','The organization obtains maintenance support and spare parts for [Assignment: organization-defined list of key information system components] within [Assignment: organization-defined time period] of failure.','None.','LOW Not Selected MOD MA-6 HIGH MA-6','Maintenance','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/133-08_02_MA-06'),('MP-01','MP-1','08_02_MP-01','Media Protection Policy And Procedures','The organization develops, disseminates, and periodically reviews/updates: (i) a formal, documented, media protection policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (ii) formal, documented procedures to facilitate the implementation of the media protection policy and associated media protection controls.','The media protection policy and procedures are consistent with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance. The media protection policy can be included as part of the general information security policy for the organization. Media protection procedures can be developed for the security program in general, and for a particular information system, when required. NIST Special Publication 800-12 provides guidance on security policies and procedures.','LOW MP-1 MOD MP-1 HIGH MP-1','Media Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/122-08_02_MP-01'),('MP-02','MP-2','08_02_MP-02','Media Access','The organization restricts access to information system media to authorized individuals.','Information system media includes both digital media (e.g., diskettes, magnetic tapes, external/removable hard drives, flash/thumb drives, compact disks, digital video disks) and non-digital media (e.g., paper, microfilm). This control also applies to portable and mobile computing and communications devices with information storage capability (e.g., notebook computers, personal digital assistants, cellular telephones). An organizational assessment of risk guides the selection of media and associated information contained on that media requiring restricted access. Organizations document in policy and procedures, the media requiring restricted access, individuals authorized to access the media, and the specific measures taken to restrict access. The rigor with which this control is applied is commensurate with the FIPS 199 security categorization of the information contained on the media. For example, fewer protection measures are needed for media containing information determined by the organization to be in the public domain, to be publicly releasable, or to have limited or no adverse impact on the organization or individuals if accessed by other than authorized personnel. In these situations, it is assumed that the physical access controls where the media resides provide adequate protection.','LOW MP-2 MOD MP-2 (1) HIGH MP-2 (1)','Media Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/123-08_02_MP-02'),('MP-03','MP-3','08_02_MP-03','Media Labeling','The organization: (i) affixes external labels to removable information system media and information system output indicating the distribution limitations, handling caveats and applicable security markings (if any) of the information; and (ii) exempts [Assignment: organization-defined list of media types or hardware components] from labeling so long as they remain within [Assignment: organization-defined protected environment].','An organizational assessment of risk guides the selection of media requiring labeling. Organizations document in policy and procedures, the media requiring labeling and the specific measures taken to afford such protection. The rigor with which this control is applied is commensurate with the FIPS 199 security categorization of the information contained on the media. For example, labeling is not required for media containing information determined by the organization to be in the public domain or to be publicly releasable.','LOW Not Selected MOD Not Selected HIGH MP-3','Media Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/124-08_02_MP-03'),('MP-04','MP-4','08_02_MP-04','Media Storage','The organization physically controls and securely stores information system media within controlled areas.','Information system media includes both digital media (e.g., diskettes, magnetic tapes, external/removable hard drives, flash/thumb drives, compact disks, digital video disks) and non-digital media (e.g., paper, microfilm). A controlled area is any area or space for which the organization has confidence that the physical and procedural protections provided are sufficient to meet the requirements established for protecting the information and/or information system. This control applies to portable and mobile computing and communications devices with information storage capability (e.g., notebook computers, personal digital assistants, cellular telephones). Telephone systems are also considered information systems and may have the capability to store information on internal media (e.g., on voicemail systems). Since telephone systems do not have, in most cases, the identification, authentication, and access control mechanisms typically employed in other information systems, organizational personnel exercise extreme caution in the types of information stored on telephone voicemail systems. An organizational assessment of risk guides the selection of media and associated information contained on that media requiring physical protection. Organizations document in policy and procedures, the media requiring physical protection and the specific measures taken to afford such protection. The rigor with which this control is applied is commensurate with the FIPS 199 security categorization of the information contained on the media. For example, fewer protection measures are needed for media containing information determined by the organization to be in the public domain, to be publicly releasable, or to have limited or no adverse impact on the organization or individuals if accessed by other than authorized personnel. In these situations, it is assumed that the physical access controls to the facility where the media resides provide adequate protection. The organization protects information system media identified by the organization until the media are destroyed or sanitized using approved equipment, techniques, and procedures. As part of a defense-in-depth protection strategy, the organization considers routinely encrypting information at rest on selected secondary storage devices. FIPS 199 security categorization guides the selection of appropriate candidates for secondary storage encryption. The organization implements effective cryptographic key management in support of secondary storage encryption and provides protections to maintain the availability of the information in the event of the loss of cryptographic keys by users. NIST Special Publications 800-56 and 800-57 provide guidance on cryptographic key establishment and cryptographic key management. Related security controls: CP-9, RA-2.','LOW Not Selected MOD MP-4 HIGH MP-4','Media Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/125-08_02_MP-04'),('MP-05','MP-5','08_02_MP-05','Media Transport','The organization protects and controls information system media during transport outside of controlled areas and restricts the activities associated with transport of such media to authorized personnel.','Information system media includes both digital media (e.g., diskettes, tapes, removable hard drives, flash/thumb drives, compact disks, digital video disks) and non- digital media (e.g., paper, microfilm). A controlled area is any area or space for which the organization has confidence that the physical and procedural protections provided are sufficient to meet the requirements established for protecting the information and/or information system. This control also applies to portable and mobile computing and communications devices with information storage capability (e.g., notebook computers, personal digital assistants, cellular telephones) that are transported outside of controlled areas. Telephone systems are also considered information systems and may have the capability to store information on internal media (e.g., on voicemail systems). Since telephone systems do not have, in most cases, the identification, authentication, and access control mechanisms typically employed in other information systems, organizational personnel exercise extreme caution in the types of information stored on telephone voicemail systems that are transported outside of controlled areas. An organizational assessment of risk guides the selection of media and associated information contained on that media requiring protection during transport. Organizations document in policy and procedures, the media requiring protection during transport and the specific measures taken to protect such transported media. The rigor with which this control is applied is commensurate with the FIPS 199 security categorization of the information contained on the media. An organizational assessment of risk also guides the selection and use of appropriate storage containers for transporting non-digital media. Authorized transport and courier personnel may include individuals from outside the organization (e.g., U.S. Postal Service or a commercial transport or delivery service).','LOW Not Selected MOD MP-5 (1) (2) HIGH MP-5 (1) (2) (3)','Media Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/126-08_02_MP-05'),('MP-06','MP-6','08_02_MP-06','Media Sanitization And Disposal','The organization sanitizes information system media, both digital and non-digital, prior to disposal or release for reuse.','Sanitization is the process used to remove information from information system media such that there is reasonable assurance, in proportion to the confidentiality of the information, that the information cannot be retrieved or reconstructed. Sanitization techniques, including clearing, purging, and destroying media information, prevent the disclosure of organizational information to unauthorized individuals when such media is reused or disposed. The organization uses its discretion on sanitization techniques and procedures for media containing information deemed to be in the public domain or publicly releasable, or deemed to have no adverse impact on the organization or individuals if released for reuse or disposed. NIST Special Publication 800-88 provides guidance on media sanitization. The National Security Agency also provides media sanitization guidance and maintains a listing of approved sanitization products at http://www.nsa.gov/ia/government/mdg.cfm.','LOW MP-6 MOD MP-6 HIGH MP-6 (1) (2)','Media Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/127-08_02_MP-06'),('PE-01','PE-1','08_02_PE-01','Physical And Environmental Protection Policy And Procedures','The organization develops, disseminates, and periodically reviews/updates: (i) a formal, documented, physical and environmental protection policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (ii) formal, documented procedures to facilitate the implementation of the physical and environmental protection policy and associated physical and environmental protection controls.','The physical and environmental protection policy and procedures are consistent with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance. The physical and environmental protection policy can be included as part of the general information security policy for the organization. Physical and environmental protection procedures can be developed for the security program in general, and for a particular information system, when required. NIST Special Publication 800-12 provides guidance on security policies and procedures.','LOW PE-1 MOD PE-1 HIGH PE-1','Physical And Environmental Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/95-08_02_PE-01'),('PE-02','PE-2','08_02_PE-02','Physical Access Authorizations','The organization develops and keeps current a list of personnel with authorized access to the facility where the information system resides (except for those areas within the facility officially designated as publicly accessible) and issues appropriate authorization credentials. Designated officials within the organization review and approve the access list and authorization credentials [Assignment: organization-defined frequency, at least annually].','Appropriate authorization credentials include, for example, badges, identification cards, and smart cards. The organization promptly removes from the access list personnel no longer requiring access to the facility where the information system resides.','LOW PE-2 MOD PE-2 HIGH PE-2','Physical And Environmental Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/96-08_02_PE-02'),('PE-03','PE-3','08_02_PE-03','Physical Access Control','The organization controls all physical access points (including designated entry/exit points) to the facility where the information system resides (except for those areas within the facility officially designated as publicly accessible) and verifies individual access authorizations before granting access to the facility. The organization controls access to areas officially designated as publicly accessible, as appropriate, in accordance with the organization’s assessment of risk.','The organization uses physical access devices (e.g., keys, locks, combinations, card readers) and/or guards to control entry to facilities containing information systems. The organization secures keys, combinations, and other access devices and inventories those devices regularly. The organization changes combinations and keys: (i) periodically; and (ii) when keys are lost, combinations are compromised, or individuals are transferred or terminated. Workstations and associated peripherals connected to (and part of) an organizational information system may be located in areas designated as publicly accessible with access to such devices being appropriately controlled. Where federal Personal Identity Verification (PIV) credential is used as an identification token and token-based access control is employed, the access control system conforms to the requirements of FIPS 201 and NIST Special Publication 800-73. If the token- based access control function employs cryptographic verification, the access control system conforms to the requirements of NIST Special Publication 800-78. If the token-based access control function employs biometric verification, the access control system conforms to the requirements of NIST Special Publication 800-76.','LOW PE-3 MOD PE-3 HIGH PE-3 (1)','Physical And Environmental Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/97-08_02_PE-03'),('PE-04','PE-4','08_02_PE-04','Access Control For Transmission Medium','The organization controls physical access to information system distribution and transmission lines within organizational facilities.','Physical protections applied to information system distribution and transmission lines help prevent accidental damage, disruption, and physical tampering. Additionally, physical protections are necessary to help prevent eavesdropping or in transit modification of unencrypted transmissions. Protective measures to control physical access to information system distribution and transmission lines include: (i) locked wiring closets; (ii) disconnected or locked spare jacks; and/or (iii) protection of cabling by conduit or cable trays.','LOW Not Selected MOD Not Selected HIGH PE-4','Physical And Environmental Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/98-08_02_PE-04'),('PE-05','PE-5','08_02_PE-05','Access Control For Display Medium','The organization controls physical access to information system devices that display information to prevent unauthorized individuals from observing the display output.','None.','LOW Not Selected MOD PE-5 HIGH PE-5','Physical And Environmental Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/99-08_02_PE-05'),('PE-06','PE-6','08_02_PE-06','Monitoring Physical Access','The organization monitors physical access to the information system to detect and respond to physical security incidents.','The organization reviews physical access logs periodically and investigates apparent security violations or suspicious physical access activities. Response to detected physical security incidents is part of the organization’s incident response capability.','LOW PE-6 MOD PE-6 (1) HIGH PE-6 (1) (2)','Physical And Environmental Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/100-08_02_PE-06'),('PE-07','PE-7','08_02_PE-07','Visitor Control','The organization controls physical access to the information system by authenticating visitors before authorizing access to the facility where the information system resides other than areas designated as publicly accessible.','Government contractors and others with permanent authorization credentials are not considered visitors. Personal Identity Verification (PIV) credentials for federal employees and contractors conform to FIPS 201, and the issuing organizations for the PIV credentials are accredited in accordance with the provisions of NIST Special Publication 800-79.','LOW PE-7 MOD PE-7 (1) HIGH PE-7 (1)','Physical And Environmental Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/101-08_02_PE-07'),('PE-08','PE-8','08_02_PE-08','Access Records','The organization maintains visitor access records to the facility where the information system resides (except for those areas within the facility officially designated as publicly accessible) that includes: (i) name and organization of the person visiting; (ii) signature of the visitor; (iii) form of identification; (iv) date of access; (v) time of entry and departure; (vi) purpose of visit; and (vii) name and organization of person visited. Designated officials within the organization review the visitor access records [Assignment: organization-defined frequency].','None.','LOW PE-8 MOD PE-8 HIGH PE-8 (1) (2)','Physical And Environmental Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/102-08_02_PE-08'),('PE-09','PE-9','08_02_PE-09','Power Equipment And Power Cabling','The organization protects power equipment and power cabling for the information system from damage and destruction.','None.','LOW Not Selected MOD PE-9 HIGH PE-9','Physical And Environmental Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/103-08_02_PE-09'),('PE-10','PE-10','08_02_PE-10','Emergency Shutoff','The organization provides, for specific locations within a facility containing concentrations of information system resources, the capability of shutting off power to any information system component that may be malfunctioning or threatened without endangering personnel by requiring them to approach the equipment.','Facilities containing concentrations of information system resources may include, for example, data centers, server rooms, and mainframe rooms.','LOW Not Selected MOD PE-10 HIGH PE-10 (1)','Physical And Environmental Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/104-08_02_PE-10'),('PE-11','PE-11','08_02_PE-11','Emergency Power','The organization provides a short-term uninterruptible power supply to facilitate an orderly shutdown of the information system in the event of a primary power source loss.','None.','LOW Not Selected MOD PE-11 HIGH PE-11 (1)','Physical And Environmental Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/105-08_02_PE-11'),('PE-12','PE-12','08_02_PE-12','Emergency Lighting','The organization employs and maintains automatic emergency lighting that activates in the event of a power outage or disruption and that covers emergency exits and evacuation routes.','None.','LOW PE-12 MOD PE-12 HIGH PE-12','Physical And Environmental Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/106-08_02_PE-12'),('PE-13','PE-13','08_02_PE-13','Fire Protection','The organization employs and maintains fire suppression and detection devices/systems that can be activated in the event of a fire.','Fire suppression and detection devices/systems include, but are not limited to, sprinkler systems, handheld fire extinguishers, fixed fire hoses, and smoke detectors.','LOW PE-13 MOD PE-13 (1) (2) (3) HIGH PE-13 (1) (2) (3)','Physical And Environmental Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/107-08_02_PE-13'),('PE-14','PE-14','08_02_PE-14','Temperature And Humidity Controls','The organization regularly maintains, within acceptable levels, and monitors the temperature and humidity within the facility where the information system resides.','None.','LOW PE-14 MOD PE-14 HIGH PE-14','Physical And Environmental Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/108-08_02_PE-14'),('PE-15','PE-15','08_02_PE-15','Water Damage Protection','The organization protects the information system from water damage resulting from broken plumbing lines or other sources of water leakage by providing master shutoff valves that are accessible, working properly, and known to key personnel.','None.','LOW PE-15 MOD PE-15 HIGH PE-15 (1)','Physical And Environmental Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/109-08_02_PE-15'),('PE-16','PE-16','08_02_PE-16','Delivery And Removal','The organization authorizes and controls information system-related items entering and exiting the facility and maintains appropriate records of those items.','The organization controls delivery areas and, if possible, isolates the areas from the information system and media libraries to avoid unauthorized physical access.','LOW PE-16 MOD PE-16 HIGH PE-16','Physical And Environmental Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/110-08_02_PE-16'),('PE-17','PE-17','08_02_PE-17','Alternate Work Site','The organization employs appropriate management, operational, and technical information system security controls at alternate work sites.','The organization provides a means for employees to communicate with information system security staff in case of security problems. NIST Special Publication 800-46 provides guidance on security in telecommuting and broadband communications.','LOW Not Selected MOD PE-17 HIGH PE-17','Physical And Environmental Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/111-08_02_PE-17'),('PE-18','PE-18','08_02_PE-18','Location Of Information System Components','The organization positions information system components within the facility to minimize potential damage from physical and environmental hazards and to minimize the opportunity for unauthorized access.','Physical and environmental hazards include, for example, flooding, fire, tornados, earthquakes, hurricanes, acts of terrorism, vandalism, electrical interference, and electromagnetic radiation. Whenever possible, the organization also considers the location or site of the facility with regard to physical and environmental hazards.','LOW Not Selected MOD PE-18 HIGH PE-18 (1)','Physical And Environmental Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/112-08_02_PE-18'),('PE-19','PE-19','08_02_PE-19','Information Leakage','The organization protects the information system from information leakage due to electromagnetic signals emanations.','The FIPS 199 security categorization (for confidentiality) of the information system and organizational security policy guides the application of safeguards and countermeasures employed to protect the information system against information leakage due to electromagnetic signals emanations.','LOW Not Selected MOD Not Selected HIGH Not Selected','Physical And Environmental Protection','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/113-08_02_PE-19'),('PL-01','PL-1','08_02_PL-01','Security Planning Policy And Procedures','The organization develops, disseminates, and periodically reviews/updates: (i) a formal, documented, security planning policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (ii) formal, documented procedures to facilitate the implementation of the security planning policy and associated security planning controls.','The security planning policy and procedures are consistent with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance. The security planning policy addresses the overall policy requirements for confidentiality, integrity, and availability and can be included as part of the general information security policy for the organization. Security planning procedures can be developed for the security program in general, and for a particular information system, when required. NIST Special Publication 800-18 provides guidance on security planning. NIST Special Publication 800-12 provides guidance on security policies and procedures.','LOW PL-1 MOD PL-1 HIGH PL-1','Planning','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/89-08_02_PL-01'),('PL-02','PL-2','08_02_PL-02','System Security Plan','The organization develops and implements a security plan for the information system that provides an overview of the security requirements for the system and a description of the security controls in place or planned for meeting those requirements. Designated officials within the organization review and approve the plan.','The security plan is aligned with the organization’s information system architecture and information security architecture. NIST Special Publication 800-18 provides guidance on security planning.','LOW PL-2 MOD PL-2 HIGH PL-2','Planning','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/90-08_02_PL-02'),('PL-03','PL-3','08_02_PL-03','System Security Plan Update','The organization reviews the security plan for the information system [Assignment: organization-defined frequency, at least annually] and revises the plan to address system/organizational changes or problems identified during plan implementation or security control assessments.','Significant changes are defined in advance by the organization and identified in the configuration management process. NIST Special Publication 800-18 provides guidance on security plan updates.','LOW PL-3 MOD PL-3 HIGH PL-3','Planning','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/91-08_02_PL-03'),('PL-04','PL-4','08_02_PL-04','Rules Of Behavior','The organization establishes and makes readily available to all information system users, a set of rules that describes their responsibilities and expected behavior with regard to information and information system usage. The organization receives signed acknowledgment from users indicating that they have read, understand, and agree to abide by the rules of behavior, before authorizing access to the information system and its resident information.','Electronic signatures are acceptable for use in acknowledging rules of behavior unless specifically prohibited by organizational policy. NIST Special Publication 800-18 provides guidance on preparing rules of behavior.','LOW PL-4 MOD PL-4 HIGH PL-4','Planning','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/92-08_02_PL-04'),('PL-05','PL-5','08_02_PL-05','Privacy Impact Assessment','The organization conducts a privacy impact assessment on the information system in accordance with OMB policy.','OMB Memorandum 03-22 provides guidance for implementing the privacy provisions of the E-Government Act of 2002.','LOW PL-5 MOD PL-5 HIGH PL-5','Planning','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/93-08_02_PL-05'),('PL-06','PL-6','08_02_PL-06','Security-0Related Activity Planning','The organization plans and coordinates security-related activities affecting the information system before conducting such activities in order to reduce the impact on organizational operations (i.e., mission, functions, image, and reputation), organizational assets, and individuals.','Routine security-related activities include, but are not limited to, security assessments, audits, system hardware and software maintenance, security certifications, and testing/exercises. Organizational advance planning and coordination includes both emergency and non-emergency (i.e., routine) situations.','LOW Not Selected MOD PL-6 HIGH PL-6','Planning','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/94-08_02_PL-06'),('PS-01','PS-1','08_02_PS-01','Personnel Security Policy And Procedures','The organization develops, disseminates, and periodically reviews/updates: (i) a formal, documented, personnel security policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (ii) formal, documented procedures to facilitate the implementation of the personnel security policy and associated personnel security controls.','The personnel security policy and procedures are consistent with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance. The personnel security policy can be included as part of the general information security policy for the organization. Personnel security procedures can be developed for the security program in general, and for a particular information system, when required. NIST Special Publication 800-12 provides guidance on security policies and procedures.','LOW PS-1 MOD PS-1 HIGH PS-1','Personnel Security','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/114-08_02_PS-01'),('PS-02','PS-2','08_02_PS-02','Position Categorization','The organization assigns a risk designation to all positions and establishes screening criteria for individuals filling those positions. The organization reviews and revises position risk designations [Assignment: organization-defined frequency].','Position risk designations are consistent with 5 CFR 731.106(a) and Office of Personnel Management policy and guidance.','LOW PS-2 MOD PS-2 HIGH PS-2','Personnel Security','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/115-08_02_PS-02'),('PS-03','PS-3','08_02_PS-03','Personnel Screening','The organization screens individuals requiring access to organizational information and information systems before authorizing access.','Screening is consistent with: (i) 5 CFR 731.106; (ii) Office of Personnel Management policy, regulations, and guidance; (iii) organizational policy, regulations, and guidance; (iv) FIPS 201 and Special Publications 800-73, 800-76, and 800-78; and (v) the criteria established for the risk designation of the assigned position.','LOW PS-3 MOD PS-3 HIGH PS-3','Personnel Security','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/116-08_02_PS-03'),('PS-04','PS-4','08_02_PS-04','Personnel Termination','The organization, upon termination of individual employment, terminates information system access, conducts exit interviews, retrieves all organizational information system-related property, and provides appropriate personnel with access to official records created by the terminated employee that are stored on organizational information systems.','Information system-related property includes, for example, keys, identification cards, and building passes. Timely execution of this control is particularly essential for employees or contractors terminated for cause.','LOW PS-4 MOD PS-4 HIGH PS-4','Personnel Security','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/117-08_02_PS-04'),('PS-05','PS-5','08_02_PS-05','Personnel Transfer','The organization reviews information systems/facilities access authorizations when personnel are reassigned or transferred to other positions within the organization and initiates appropriate actions.','Appropriate actions that may be required include: (i) returning old and issuing new keys, identification cards, building passes; (ii) closing old accounts and establishing new accounts; (iii) changing system access authorizations; and (iv) providing for access to official records created or controlled by the employee at the old work location and in the old accounts.','LOW PS-5 MOD PS-5 HIGH PS-5','Personnel Security','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/118-08_02_PS-05'),('PS-06','PS-6','08_02_PS-06','Access Agreements','The organization completes appropriate signed access agreements for individuals requiring access to organizational information and information systems before authorizing access and reviews/updates the agreements [Assignment: organization-defined frequency].','Access agreements include, for example, nondisclosure agreements, acceptable use agreements, rules of behavior, and conflict-of-interest agreements. Electronic signatures are acceptable for use in acknowledging access agreements unless specifically prohibited by organizational policy.','LOW PS-6 MOD PS-6 HIGH PS-6','Personnel Security','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/119-08_02_PS-06'),('PS-07','PS-7','08_02_PS-07','Third-0Party Personnel Security','The organization establishes personnel security requirements including security roles and responsibilities for third-party providers and monitors provider compliance.','Third-party providers include, for example, service bureaus, contractors, and other organizations providing information system development, information technology services, outsourced applications, and network and security management. The organization explicitly includes personnel security requirements in acquisition-related documents. NIST Special Publication 800-35 provides guidance on information technology security services.','LOW PS-7 MOD PS-7 HIGH PS-7','Personnel Security','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/120-08_02_PS-07'),('PS-08','PS-8','08_02_PS-08','Personnel Sanctions','The organization employs a formal sanctions process for personnel failing to comply with established information security policies and procedures.','The sanctions process is consistent with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance. The sanctions process can be included as part of the general personnel policies and procedures for the organization.','LOW PS-8 MOD PS-8 HIGH PS-8','Personnel Security','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/121-08_02_PS-08'),('RA-01','RA-1','08_02_RA-01','Risk Assessment Policy And Procedures','The organization develops, disseminates, and periodically reviews/updates: (i) a formal, documented risk assessment policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (ii) formal, documented procedures to facilitate the implementation of the risk assessment policy and associated risk assessment controls.','The risk assessment policy and procedures are consistent with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance. The risk assessment policy can be included as part of the general information security policy for the organization. Risk assessment procedures can be developed for the security program in general, and for a particular information system, when required. NIST Special Publications 800-30 provides guidance on the assessment of risk. NIST Special Publication 800-12 provides guidance on security policies and procedures.','LOW RA-1 MOD RA-1 HIGH RA-1','Risk Assessment','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/84-08_02_RA-01'),('RA-02','RA-2','08_02_RA-02','Security Categorization','The organization categorizes the information system and the information processed, stored, or transmitted by the system in accordance with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance and documents the results (including supporting rationale) in the system security plan. Designated senior-level officials within the organization review and approve the security categorizations.','The applicable federal standard for security categorization of nonnational security information and information systems is FIPS 199. The organization conducts FIPS 199 security categorizations as an organization-wide activity with the involvement of the chief information officer, senior agency information security officer, information system owners, and information owners. The organization also considers potential impacts to other organizations and, in accordance with the USA PATRIOT Act of 2001 and Homeland Security Presidential Directives, potential national-level impacts in categorizing the information system. As part of a defense-in-depth protection strategy, the organization considers partitioning higher-impact information systems into separate physical domains (or environments) and restricting or prohibiting network access in accordance with an organizational assessment of risk. NIST Special Publication 800-60 provides guidance on determining the security categories of the information types resident on the information system. Related security controls: MP-4, SC-7.','LOW RA-2 MOD RA-2 HIGH RA-2','Risk Assessment','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/85-08_02_RA-02'),('RA-03','RA-3','08_02_RA-03','Risk Assessment','The organization conducts assessments of the risk and magnitude of harm that could result from the unauthorized access, use, disclosure, disruption, modification, or destruction of information and information systems that support the operations and assets of the agency (including information and information systems managed/operated by external parties).','Risk assessments take into account vulnerabilities, threat sources, and security controls planned or in place to determine the resulting level of residual risk posed to organizational operations, organizational assets, or individuals based on the operation of the information system. The organization also considers potential impacts to other organizations and, in accordance with the USA PATRIOT Act and Homeland Security Presidential Directives, potential national-level impacts in categorizing the information system. Risk assessments also take into account risk posed to organizational operations, organizational assets, or individuals from external parties (e.g., service providers, contractors operating information systems on behalf of the organization, individuals accessing organizational information systems, outsourcing entities). In accordance with OMB policy and related E-authentication initiatives, authentication of public users accessing federal information systems may also be required to protect nonpublic or privacy-related information. As such, organizational assessments of risk also address public access to federal information systems. The General Services Administration provides tools supporting that portion of the risk assessment dealing with public access to federal information systems. NIST Special Publication 800-30 provides guidance on conducting risk assessments including threat, vulnerability, and impact assessments.','LOW RA-3 MOD RA-3 HIGH RA-3','Risk Assessment','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/86-08_02_RA-03'),('RA-04','RA-4','08_02_RA-04','Risk Assessment Update','The organization updates the risk assessment [Assignment: organization-defined frequency] or whenever there are significant changes to the information system, the facilities where the system resides, or other conditions that may impact the security or accreditation status of the system.','The organization develops and documents specific criteria for what is considered significant change to the information system. NIST Special Publication 800-30 provides guidance on conducting risk assessment updates.','LOW RA-4 MOD RA-4 HIGH RA-4','Risk Assessment','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/87-08_02_RA-04'),('RA-05','RA-5','08_02_RA-05','Vulnerability Scanning','The organization scans for vulnerabilities in the information system [Assignment: organization-defined frequency] or when significant new vulnerabilities potentially affecting the system are identified and reported.','Vulnerability scanning is conducted using appropriate scanning tools and techniques. The organization trains selected personnel in the use and maintenance of vulnerability scanning tools and techniques. Vulnerability scans are scheduled and/or random in accordance with organizational policy and assessment of risk. The information obtained from the vulnerability scanning process is freely shared with appropriate personnel throughout the organization to help eliminate similar vulnerabilities in other information systems. Vulnerability analysis for custom software and applications may require additional, more specialized approaches (e.g., vulnerability scanning tools for applications, source code reviews, static analysis of source code). NIST Special Publication 800-42 provides guidance on network security testing. NIST Special Publication 800-40 (Version 2) provides guidance on patch and vulnerability management.','LOW Not Selected MOD RA-5 HIGH RA-5 (1) (2)','Risk Assessment','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/88-08_02_RA-05'),('SA-01','SA-1','08_02_SA-01','System And Services Acquisition Policy And Procedures','The organization develops, disseminates, and periodically reviews/updates: (i) a formal, documented, system and services acquisition policy that includes information security considerations and that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (ii) formal, documented procedures to facilitate the implementation of the system and services acquisition policy and associated system and services acquisition controls.','The system and services acquisition policy and procedures are consistent with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance. The system and services acquisition policy can be included as part of the general information security policy for the organization. System and services acquisition procedures can be developed for the security program in general, and for a particular information system, when required. NIST Special Publication 800-12 provides guidance on security policies and procedures.','LOW SA-1 MOD SA-1 HIGH SA-1','System And Services Acquisition','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/51-08_02_SA-01'),('SA-02','SA-2','08_02_SA-02','Allocation Of Resources','The organization determines, documents, and allocates as part of its capital planning and investment control process, the resources required to adequately protect the information system.','The organization includes the determination of security requirements for the information system in mission/business case planning and establishes a discrete line item for information system security in the organization’s programming and budgeting documentation. NIST Special Publication 800-65 provides guidance on integrating security into the capital planning and investment control process.','LOW SA-2 MOD SA-2 HIGH SA-2','System And Services Acquisition','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/52-08_02_SA-02'),('SA-03','SA-3','08_02_SA-03','Life Cycle Support','The organization manages the information system using a system development life cycle methodology that includes information security considerations.','NIST Special Publication 800-64 provides guidance on security considerations in the system development life cycle.','LOW SA-3 MOD SA-3 HIGH SA-3','System And Services Acquisition','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/53-08_02_SA-03'),('SA-04','SA-4','08_02_SA-04','Acquisitions','The organization includes security requirements and/or security specifications, either explicitly or by reference, in information system acquisition contracts based on an assessment of risk and in accordance with applicable laws, Executive Orders, directives, policies, regulations, and standards.','(1) Solicitation Documents; The solicitation documents (e.g., Requests for Proposals) for information systems and services include, either explicitly or by reference, security requirements that describe: (i) required security capabilities (security needs and, as necessary, specific security controls and other specific FISMA requirements); (ii) required design and development processes; (iii) required test and evaluation procedures; and (iv) required documentation. The requirements in the solicitation documents permit updating security controls as new threats/vulnerabilities are identified and as new technologies are implemented. NIST Special Publication 800-36 provides guidance on the selection of information security products. NIST Special Publication 800-35 provides guidance on information technology security services. NIST Special Publication 800-64 provides guidance on security considerations in the system development life cycle. (2) Information System Documentation; The solicitation documents include requirements for appropriate information system documentation. The documentation addresses user and systems administrator guidance and information regarding the implementation of the security controls in the information system. The level of detail required in the documentation is based on the FIPS 199 security category for the information system. (3) Use of Tested, Evaluated, and Validated Products; NIST Special Publication 800-23 provides guidance on the acquisition and use of tested/evaluated information technology products. (4) Configuration Settings and Implementation Guidance; The information system required documentation includes security configuration settings and security implementation guidance. OMB FISMA reporting instructions provide guidance on configuration requirements for federal information systems. NIST Special Publication 800-70 provides guidance on configuration settings for information technology products.','LOW SA-4 MOD SA-4 (1) HIGH SA-4 (1)','System And Services Acquisition','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/54-08_02_SA-04'),('SA-05','SA-5','08_02_SA-05','Information System Documentation','The organization obtains, protects as required, and makes available to authorized personnel, adequate documentation for the information system.','Documentation includes administrator and user guides with information on: (i) configuring, installing, and operating the information system; and (ii) effectively using the system’s security features. When adequate information system documentation is either unavailable or non existent (e.g., due to the age of the system or lack of support from the vendor/manufacturer), the organization documents attempts to obtain such documentation and provides compensating security controls, if needed.','LOW SA-5 MOD SA-5 (1) HIGH SA-5 (1) (2)','System And Services Acquisition','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/55-08_02_SA-05'),('SA-06','SA-6','08_02_SA-06','Software Usage Restrictions','The organization complies with software usage restrictions.','Software and associated documentation are used in accordance with contract agreements and copyright laws. For software and associated documentation protected by quantity licenses, the organization employs tracking systems to control copying and distribution. The organization controls and documents the use of publicly accessible peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work.','LOW SA-6 MOD SA-6 HIGH SA-6','System And Services Acquisition','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/56-08_02_SA-06'),('SA-07','SA-7','08_02_SA-07','User Installed Software','The organization enforces explicit rules governing the installation of software by users.','If provided the necessary privileges, users have the ability to install software. The organization identifies what types of software installations are permitted (e.g., updates and security patches to existing software) and what types of installations are prohibited (e.g., software that is free only for personal, not government use, and software whose pedigree with regard to being potentially malicious is unknown or suspect).','LOW SA-7 MOD SA-7 HIGH SA-7','System And Services Acquisition','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/57-08_02_SA-07'),('SA-08','SA-8','08_02_SA-08','Security Engineering Principles','The organization designs and implements the information system using security engineering principles.','NIST Special Publication 800-27 provides guidance on engineering principles for information system security. The application of security engineering principles is primarily targeted at new development information systems or systems undergoing major upgrades and is integrated into the system development life cycle. For legacy information systems, the organization applies security engineering principles to system upgrades and modifications, to the extent feasible, given the current state of the hardware, software, and firmware components within the system.','LOW Not Selected MOD SA-8 HIGH SA-8','System And Services Acquisition','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/58-08_02_SA-08'),('SA-09','SA-9','08_02_SA-09','External Information System Services','The organization: (i) requires that providers of external information system services employ adequate security controls in accordance with applicable laws, Executive Orders, directives, policies, regulations, standards, guidance, and established service-level agreements; and (ii) monitors security control compliance.','An external information system service is a service that is implemented outside of the accreditation boundary of the organizational information system (i.e., a service that is used by, but not a part of, the organizational information system). Relationships with external service providers are established in a variety of ways, for example, through joint ventures, business partnerships, outsourcing arrangements (i.e., through contracts, interagency agreements, lines of business arrangements), licensing agreements, and/or supply chain exchanges. Ultimately, the responsibility for adequately mitigating risks to the organization’s operations and assets, and to individuals, arising from the use of external information system services remains with the authorizing official. Authorizing officials must require that an appropriate chain of trust be established with external service providers when dealing with the many issues associated with information system security. For services external to the organization, a chain of trust requires that the organization establish and retain a level of confidence that each participating service provider in the potentially complex consumer-provider relationship provides adequate protection for the services rendered to the organization. Where a sufficient level of trust cannot be established in the external services and/or service providers, the organization employs compensating security controls or accepts the greater degree of risk to its operations and assets, or to individuals. The external information system services documentation includes government, service provider, and end user security roles and responsibilities, and any service-level agreements. Service-level agreements define the expectations of performance for each required security control, describe measurable outcomes, and identify remedies and response requirements for any identified instance of non-compliance. NIST Special Publication 800-35 provides guidance on information technology security services. NIST Special Publication 800-64 provides guidance on the security considerations in the system development life cycle.','LOW SA-9 MOD SA-9 HIGH SA-9','System And Services Acquisition','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/59-08_02_SA-09'),('SA-10','SA-10','08_02_SA-10','Developer Configuration Management','The organization requires that information system developers create and implement a configuration management plan that controls changes to the system during development, tracks security flaws, requires authorization of changes, and provides documentation of the plan and its implementation.','This control also applies to the development actions associated with information system changes.','LOW Not Selected MOD Not Selected HIGH SA-10','System And Services Acquisition','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/60-08_02_SA-10'),('SA-11','SA-11','08_02_SA-11','Developer Security Testing','The organization requires that information system developers create a security test and evaluation plan, implement the plan, and document the results.','Developmental security test results are used to the greatest extent feasible after verification of the results and recognizing that these results are impacted whenever there have been security relevant modifications to the information system subsequent to developer testing. Test results may be used in support of the security certification and accreditation process for the delivered information system. Related security controls: CA-2, CA-4.','LOW Not Selected MOD SA-11 HIGH SA-11','System And Services Acquisition','Management','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/249-08-02-SA-11'),('SC-01','SC-1','08_02_SC-01','System And Communications Protection Policy And Procedures','The organization develops, disseminates, and periodically reviews/updates: (i) a formal, documented, system and communications protection policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (ii) formal, documented procedures to facilitate the implementation of the system and communications protection policy and associated system and communications protection controls.','The system and communications protection policy and procedures are consistent with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance. The system and communications protection policy can be included as part of the general information security policy for the organization. System and communications protection procedures can be developed for the security program in general, and for a particular information system, when required. NIST Special Publication 800-12 provides guidance on security policies and procedures.','LOW SC-1 MOD SC-1 HIGH SC-1','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/61-08_02_SC-01'),('SC-02','SC-2','08_02_SC-02','Application Partitioning','The information system separates user functionality (including user interface services) from information system management functionality.','The information system physically or logically separates user interface services (e.g., public web pages) from information storage and management services (e.g., database management). Separation may be accomplished through the use of different computers, different central processing units, different instances of the operating system, different network addresses, combinations of these methods, or other methods as appropriate.','LOW Not Selected MOD SC-2 HIGH SC-2','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/62-08_02_SC-02'),('SC-03','SC-3','08_02_SC-03','Security Function Isolation','The information system isolates security functions from nonsecurity functions.','The information system isolates security functions from nonsecurity functions by means of partitions, domains, etc., including control of access to and integrity of, the hardware, software, and firmware that perform those security functions. The information system maintains a separate execution domain (e.g., address space) for each executing process.','LOW Not Selected MOD Not Selected HIGH SC-3','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/63-08_02_SC-03'),('SC-04','SC-4','08_02_SC-04','Information Remnance','The information system prevents unauthorized and unintended information transfer via shared system resources.','Control of information system remnance, sometimes referred to as object reuse, or data remnance, prevents information, including encrypted representations of information, produced by the actions of a prior user/role (or the actions of a process acting on behalf of a prior user/role) from being available to any current user/role (or current process) that obtains access to a shared system resource (e.g., registers, main memory, secondary storage) after that resource has been released back to the information system.','LOW Not Selected MOD SC-4 HIGH SC-4','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/64-08_02_SC-04'),('SC-05','SC-5','08_02_SC-05','Denial Of Service Protection','The information system protects against or limits the effects of the following types of denial of service attacks: [Assignment: organization-defined list of types of denial of service attacks or reference to source for current list].','A variety of technologies exist to limit, or in some cases, eliminate the effects of denial of service attacks. For example, boundary protection devices can filter certain types of packets to protect devices on an organization’s internal network from being directly affected by denial of service attacks. Information systems that are publicly accessible can be protected by employing increased capacity and bandwidth combined with service redundancy.','LOW SC-5 MOD SC-5 HIGH SC-5','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/65-08_02_SC-05'),('SC-06','SC-6','08_02_SC-06','Resource Priority','The information system limits the use of resources by priority.','Priority protection helps prevent a lower-priority process from delaying or interfering with the information system servicing any higher-priority process.','LOW Not Selected MOD Not Selected HIGH Not Selected','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/66-08_02_SC-06'),('SC-07','SC-7','08_02_SC-07','Boundary Protection','The information system monitors and controls communications at the external boundary of the information system and at key internal boundaries within the system.','Any connections to the Internet, or other external networks or information systems, occur through managed interfaces consisting of appropriate boundary protection devices (e.g., proxies, gateways, routers, firewalls, guards, encrypted tunnels) arranged in an effective architecture (e.g., routers protecting firewalls and application gateways residing on a protected subnetwork commonly referred to as a demilitarized zone or DMZ). Information system boundary protections at any designated alternate processing sites provide the same levels of protection as that of the primary site. As part of a defense-in-depth protection strategy, the organization considers partitioning higher- impact information systems into separate physical domains (or environments) and applying the concepts of managed interfaces described above to restrict or prohibit network access in accordance with an organizational assessment of risk. FIPS 199 security categorization guides the selection of appropriate candidates for domain partitioning. The organization carefully considers the intrinsically shared nature of commercial telecommunications services in the implementation of security controls associated with the use of such services. Commercial telecommunications services are commonly based on network components and consolidated management systems shared by all attached commercial customers, and may include third party provided access lines and other service elements. Consequently, such interconnecting transmission services may represent sources of increased risk despite contract security provisions. Therefore, when this situation occurs, the organization either implements appropriate compensating security controls or explicitly accepts the additional risk. NIST Special Publication 800-77 provides guidance on virtual private networks. Related security controls: MP- 4, RA-2.','LOW SC-7 MOD SC-7 (1) (2) (3) (4) (5) HIGH SC-7 (1) (2) (3) (4) (5) (6)','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/67-08_02_SC-07'),('SC-08','SC-8','08_02_SC-08','Transmission Integrity','The information system protects the integrity of transmitted information.','If the organization is relying on a commercial service provider for transmission services as a commodity item rather than a fully dedicated service, it may be more difficult to obtain the necessary assurances regarding the implementation of needed security controls for transmission integrity. When it is infeasible or impractical to obtain the necessary security controls and assurances of control effectiveness through appropriate contracting vehicles, the organization either implements appropriate compensating security controls or explicitly accepts the additional risk. NIST Special Publication 800-52 provides guidance on protecting transmission integrity using Transport Layer Security (TLS). NIST Special Publication 800-77 provides guidance on protecting transmission integrity using IPsec. NIST Special Publication 800-81 provides guidance on Domain Name System (DNS) message authentication and integrity verification. NSTISSI No. 7003 contains guidance on the use of Protective Distribution Systems.','LOW Not Selected MOD SC-8 HIGH SC-8 (1)','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/68-08_02_SC-08'),('SC-09','SC-9','08_02_SC-09','Transmission Confidentiality','The information system protects the confidentiality of transmitted information.','If the organization is relying on a commercial service provider for transmission services as a commodity item rather than a fully dedicated service, it may be more difficult to obtain the necessary assurances regarding the implementation of needed security controls for transmission confidentiality. When it is infeasible or impractical to obtain the necessary security controls and assurances of control effectiveness through appropriate contracting vehicles, the organization either implements appropriate compensating security controls or explicitly accepts the additional risk. NIST Special Publication 800-52 provides guidance on protecting transmission confidentiality using Transport Layer Security (TLS). NIST Special Publication 800-77 provides guidance on protecting transmission confidentiality using IPsec. NSTISSI No. 7003 contains guidance on the use of Protective Distribution Systems. Related security control: AC-17.','LOW Not Selected MOD SC-9 HIGH SC-9 (1)','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/69-08_02_SC-09'),('SC-10','SC-10','08_02_SC-10','Network Disconnect','The information system terminates a network connection at the end of a session or after [Assignment: organization-defined time period] of inactivity.','The organization applies this control within the context of risk management that considers specific mission or operational requirements.','LOW Not Selected MOD SC-10 HIGH SC-10','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/70-08_02_SC-10'),('SC-11','SC-11','08_02_SC-11','Trusted Path','The information system establishes a trusted communications path between the user and the following security functions of the system: [Assignment: organization-defined security functions to include at a minimum, information system authentication and reauthentication].','A trusted path is employed for high-confidence connections between the security functions of the information system and the user (e.g., for login).','LOW Not Selected MOD Not Selected HIGH Not Selected','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/71-08_02_SC-11'),('SC-12','SC-12','08_02_SC-12','Cryptographic Key Establishment And Management','When cryptography is required and employed within the information system, the organization establishes and manages cryptographic keys using automated mechanisms with supporting procedures or manual procedures.','NIST Special Publication 800-56 provides guidance on cryptographic key establishment. NIST Special Publication 800-57 provides guidance on cryptographic key management.','LOW Not Selected MOD SC-12 HIGH SC-12','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/72-08_02_SC-12'),('SC-13','SC-13','08_02_SC-13','Use Of Cryptography','For information requiring cryptographic protection, the information system implements cryptographic mechanisms that comply with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance.','The applicable federal standard for employing cryptography in nonnational security information systems is FIPS 140-2 (as amended). Validation certificates issued by the NIST Cryptographic Module Validation Program (including FIPS 140-1, FIPS 140-2, and future amendments) remain in effect and the modules remain available for continued use and purchase until a validation certificate is specifically revoked. NIST Special Publications 800-56 and 800-57 provide guidance on cryptographic key establishment and cryptographic key management. Additional information on the use of validated cryptography is available at http://csrc.nist.gov/cryptval.','LOW SC-13 MOD SC-13 HIGH SC-13','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/73-08_02_SC-13'),('SC-14','SC-14','08_02_SC-14','Public Access Protections','The information system protects the integrity and availability of publicly available information and applications.','None.','LOW SC-14 MOD SC-14 HIGH SC-14','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/74-08_02_SC-14'),('SC-15','SC-15','08_02_SC-15','Collaborative Computing','The information system prohibits remote activation of collaborative computing mechanisms and provides an explicit indication of use to the local users.','Collaborative computing mechanisms include, for example, video and audio conferencing capabilities. Explicit indication of use includes, for example, signals to local users when cameras and/or microphones are activated.','LOW Not Selected MOD SC-15 HIGH SC-15','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/75-08_02_SC-15'),('SC-16','SC-16','08_02_SC-16','Transmission Of Security Parameters','The information system reliably associates security parameters with information exchanged between information systems.','Security parameters include, for example, security labels and markings. Security parameters may be explicitly or implicitly associated with the information contained within the information system.','LOW Not Selected MOD Not Selected HIGH Not Selected','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/76-08_02_SC-16'),('SC-17','SC-17','08_02_SC-17','Public Key Infrastructure Certificates','The organization issues public key certificates under an appropriate certificate policy or obtains public key certificates under an appropriate certificate policy from an approved service provider.','For user certificates, each agency either establishes an agency certification authority cross-certified with the Federal Bridge Certification Authority at medium assurance or higher or uses certificates from an approved, shared service provider, as required by OMB Memorandum 05-24. NIST Special Publication 800-32 provides guidance on public key technology. NIST Special Publication 800-63 provides guidance on remote electronic authentication.','LOW Not Selected MOD SC-17 HIGH SC-17','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/77-08_02_SC-17'),('SC-18','SC-18','08_02_SC-18','Mobile Code','The organization: (i) establishes usage restrictions and implementation guidance for mobile code technologies based on the potential to cause damage to the information system if used maliciously; and (ii) authorizes, monitors, and controls the use of mobile code within the information system.','Mobile code technologies include, for example, Java, JavaScript, ActiveX, PDF, Postscript, Shockwave movies, Flash animations, and VBScript. Usage restrictions and implementation guidance apply to both the selection and use of mobile code installed on organizational servers and mobile code downloaded and executed on individual workstations. Control procedures prevent the development, acquisition, or introduction of unacceptable mobile code within the information system. NIST Special Publication 800-28 provides guidance on active content and mobile code.','LOW Not Selected MOD SC-18 HIGH SC-18','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/78-08_02_SC-18'),('SC-19','SC-19','08_02_SC-19','Voice Over Internet Protocol','The organization: (i) establishes usage restrictions and implementation guidance for Voice over Internet Protocol (VoIP) technologies based on the potential to cause damage to the information system if used maliciously; and (ii) authorizes, monitors, and controls the use of VoIP within the information system.','NIST Special Publication 800-58 provides guidance on security considerations for VoIP technologies employed in information systems.','LOW Not Selected MOD SC-19 HIGH SC-19','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/79-08_02_SC-19'),('SC-20','SC-20','08_02_SC-20','Secure Name / Address Resolution Service (Authoritative Source)','The information system that provides name/address resolution service provides additional data origin and integrity artifacts along with the authoritative data it returns in response to resolution queries.','This control enables remote clients to obtain origin authentication and integrity verification assurances for the name/address resolution information obtained through the service. A domain name system (DNS) server is an example of an information system that provides name/address resolution service; digital signatures and cryptographic keys are examples of additional artifacts; and DNS resource records are examples of authoritative data. NIST Special Publication 800-81 provides guidance on secure domain name system deployment.','LOW Not Selected MOD SC-20 HIGH SC-20','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/80-08_02_SC-20'),('SC-21','SC-21','08_02_SC-21','Secure Name / Address Resolution Service (Recursive Or Caching Resolver)','The information system that provides name/address resolution service for local clients performs data origin authentication and data integrity verification on the resolution responses it receives from authoritative sources when requested by client systems.','A resolving or caching domain name system (DNS) server is an example of an information system that provides name/address resolution service for local clients and authoritative DNS servers are examples of authoritative sources. NIST Special Publication 800-81 provides guidance on secure domain name system deployment.','LOW Not Selected MOD Not Selected HIGH SC-21','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/81-08_02_SC-21'),('SC-22','SC-22','08_02_SC-22','Architecture And Provisioning For Name / Address Resolution Service','The information systems that collectively provide name/address resolution service for an organization are fault tolerant and implement role separation.','A domain name system (DNS) server is an example of an information system that provides name/address resolution service. To eliminate single points of failure and to enhance redundancy, there are typically at least two authoritative domain name system (DNS) servers, one configured as primary and the other as secondary. Additionally, the two servers are commonly located in two different network subnets and geographically separated (i.e., not located in the same physical facility). If organizational information technology resources are divided into those resources belonging to internal networks and those resources belonging to external networks, authoritative DNS servers with two roles (internal and external) are established. The DNS server with the internal role provides name/address resolution information pertaining to both internal and external information technology resources while the DNS server with the external role only provides name/address resolution information pertaining to external information technology resources. The list of clients who can access the authoritative DNS server of a particular role is also specified. NIST Special Publication 800-81 provides guidance on secure DNS deployment.','LOW Not Selected MOD SC-22 HIGH SC-22','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/82-08_02_SC-22'),('SC-23','SC-23','08_02_SC-23','Session Authenticity','The information system provides mechanisms to protect the authenticity of communications sessions.','This control focuses on communications protection at the session, versus packet, level. The intent of this control is to implement session-level protection where needed (e.g., in service-oriented architectures providing web-based services). NIST Special Publication 800-52 provides guidance on the use of transport layer security (TLS) mechanisms. NIST Special Publication 800-77 provides guidance on the deployment of IPsec virtual private networks (VPNs) and other methods of protecting communications sessions. NIST Special Publication 800-95 provides guidance on secure web services.','LOW Not Selected MOD SC-23 HIGH SC-23','System And Communications Protection','Technical','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/83-08_02_SC-23'),('SI-01','SI-1','08_02_SI-01','System And Information Integrity Policy And Procedures','The organization develops, disseminates, and periodically reviews/updates: (i) a formal, documented, system and information integrity policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and (ii) formal, documented procedures to facilitate the implementation of the system and information integrity policy and associated system and information integrity controls.','The system and information integrity policy and procedures are consistent with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance. The system and information integrity policy can be included as part of the general information security policy for the organization. System and information integrity procedures can be developed for the security program in general, and for a particular information system, when required. NIST Special Publication 800-12 provides guidance on security policies and procedures.','LOW SI-1 MOD SI-1 HIGH SI-1','System And Information Integrity','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/39-08_02_SI-01'),('SI-02','SI-2','08_02_SI-02','Flaw Remediation','The organization identifies, reports, and corrects information system flaws.','The organization identifies information systems containing software affected by recently announced software flaws (and potential vulnerabilities resulting from those flaws). The organization (or the software developer/vendor in the case of software developed and maintained by a vendor/contractor) promptly installs newly released security relevant patches, service packs, and hot fixes, and tests patches, service packs, and hot fixes for effectiveness and potential side effects on the organization’s information systems before installation. Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling are also addressed expeditiously. Flaw remediation is incorporated into configuration management as an emergency change. NIST Special Publication 800-40, provides guidance on security patch installation and patch management. Related security controls: CA-2, CA-4, CA-7, CM-3, IR-4, SI-11.','LOW SI-2 MOD SI-2 (2) HIGH SI-2 (1) (2)','System And Information Integrity','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/40-08_02_SI-02'),('SI-03','SI-3','08_02_SI-03','Malicious Code Protection','The information system implements malicious code protection.','The organization employs malicious code protection mechanisms at critical information system entry and exit points (e.g., firewalls, electronic mail servers, web servers, proxy servers, remote-access servers) and at workstations, servers, or mobile computing devices on the network. The organization uses the malicious code protection mechanisms to detect and eradicate malicious code (e.g., viruses, worms, Trojan horses, spyware) transported: (i) by electronic mail, electronic mail attachments, Internet accesses, removable media (e.g., USB devices, diskettes or compact disks), or other common means; or (ii) by exploiting information system vulnerabilities. The organization updates malicious code protection mechanisms (including the latest virus definitions) whenever new releases are available in accordance with organizational configuration management policy and procedures. The organization considers using malicious code protection software products from multiple vendors (e.g., using one vendor for boundary devices and servers and another vendor for workstations). The organization also considers the receipt of false positives during malicious code detection and eradication and the resulting potential impact on the availability of the information system. NIST Special Publication 800-83 provides guidance on implementing malicious code protection.','LOW SI-3 MOD SI-3 (1) (2) HIGH SI-3 (1) (2)','System And Information Integrity','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/41-08_02_SI-03'),('SI-04','SI-4','08_02_SI-04','Information System Monitoring Tools And Techniques','The organization employs tools and techniques to monitor events on the information system, detect attacks, and provide identification of unauthorized use of the system.','Information system monitoring capability is achieved through a variety of tools and techniques (e.g., intrusion detection systems, intrusion prevention systems, malicious code protection software, audit record monitoring software, network monitoring software). Monitoring devices are strategically deployed within the information system (e.g., at selected perimeter locations, near server farms supporting critical applications) to collect essential information. Monitoring devices are also deployed at ad hoc locations within the system to track specific transactions. Additionally, these devices are used to track the impact of security changes to the information system. The granularity of the information collected is determined by the organization based upon its monitoring objectives and the capability of the information system to support such activities. Organizations consult appropriate legal counsel with regard to all information system monitoring activities. Organizations heighten the level of information system monitoring activity whenever there is an indication of increased risk to organizational operations, organizational assets, or individuals based on law enforcement information, intelligence information, or other credible sources of information. NIST Special Publication 800-61 provides guidance on detecting attacks through various types of security technologies. NIST Special Publication 800-83 provides guidance on detecting malware-based attacks through malicious code protection software. NIST Special Publication 800-92 provides guidance on monitoring and analyzing computer security event logs. NIST Special Publication 800-94 provides guidance on intrusion detection and prevention. Related security control: AC-8.','LOW Not Selected MOD SI-4 (4) HIGH SI-4 (2) (4) (5)','System And Information Integrity','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/42-08_02_SI-04'),('SI-05','SI-5','08_02_SI-05','Security Alerts And Advisories','The organization receives information system security alerts/advisories on a regular basis, issues alerts/advisories to appropriate personnel, and takes appropriate actions in response.','The organization documents the types of actions to be taken in response to security alerts/advisories. The organization also maintains contact with special interest groups (e.g., information security forums) that: (i) facilitate sharing of security-related information (e.g., threats, vulnerabilities, and latest security technologies); (ii) provide access to advice from security professionals; and (iii) improve knowledge of security best practices. NIST Special Publication 800-40 provides guidance on monitoring and distributing security alerts and advisories.','LOW SI-5 MOD SI-5 HIGH SI-5 (1)','System And Information Integrity','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/43-08_02_SI-05'),('SI-06','SI-6','08_02_SI-06','Security Functionality Verification','The information system verifies the correct operation of security functions [Selection (one or more): upon system startup and restart, upon command by user with appropriate privilege, periodically every [Assignment: organization-defined time-period]] and [Selection (one or more): notifies system administrator, shuts the system down, restarts the system] when anomalies are discovered.','The need to verify security functionality applies to all security functions. For those security functions that are not able to execute automated self-tests, the organization either implements compensating security controls or explicitly accepts the risk of not performing the verification as required.','LOW Not Selected MOD Not Selected HIGH SI-6','System And Information Integrity','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/44-08_02_SI-06'),('SI-07','SI-7','08_02_SI-07','Software And Information Integrity','The information system detects and protects against unauthorized changes to software and information.','The organization employs integrity verification applications on the information system to look for evidence of information tampering, errors, and omissions. The organization employs good software engineering practices with regard to commercial off-the-shelf integrity mechanisms (e.g., parity checks, cyclical redundancy checks, cryptographic hashes) and uses tools to automatically monitor the integrity of the information system and the applications it hosts.','LOW Not Selected MOD Not Selected HIGH SI-7 (1) (2)','System And Information Integrity','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/45-08_02_SI-07'),('SI-08','SI-8','08_02_SI-08','Spam Protection','The information system implements spam protection.','The organization employs spam protection mechanisms at critical information system entry points (e.g., firewalls, electronic mail servers, remote-access servers) and at workstations, servers, or mobile computing devices on the network. The organization uses the spam protection mechanisms to detect and take appropriate action on unsolicited messages transported by electronic mail, electronic mail attachments, Internet accesses, or other common means. Consideration is given to using spam protection software products from multiple vendors (e.g., using one vendor for boundary devices and servers and another vendor for workstations). NIST Special Publication 800-45 provides guidance on electronic mail security.','LOW Not Selected MOD SI-8 HIGH SI-8 (1)','System And Information Integrity','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/46-08_02_SI-08'),('SI-09','SI-9','08_02_SI-09','Information Input Restrictions','The organization restricts the capability to input information to the information system to authorized personnel.','Restrictions on personnel authorized to input information to the information system may extend beyond the typical access controls employed by the system and include limitations based on specific operational/project responsibilities.','LOW Not Selected MOD SI-9 HIGH SI-9','System And Information Integrity','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/47-08_02_SI-09'),('SI-10','SI-10','08_02_SI-10','Information Accuracy, Completeness, Validity, And Authenticity','The information system checks information for accuracy, completeness, validity, and authenticity.','Checks for accuracy, completeness, validity, and authenticity of information are accomplished as close to the point of origin as possible. Rules for checking the valid syntax of information system inputs (e.g., character set, length, numerical range, acceptable values) are in place to verify that inputs match specified definitions for format and content. Inputs passed to interpreters are prescreened to prevent the content from being unintentionally interpreted as commands. The extent to which the information system is able to check the accuracy, completeness, validity, and authenticity of information is guided by organizational policy and operational requirements.','LOW Not Selected MOD SI-10 HIGH SI-10','System And Information Integrity','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/48-08_02_SI-10'),('SI-11','SI-11','08_02_SI-11','Error Handling','The information system identifies and handles error conditions in an expeditious manner without providing information that could be exploited by adversaries.','The structure and content of error messages are carefully considered by the organization. Error messages are revealed only to authorized personnel. Error messages generated by the information system provide timely and useful information without revealing potentially harmful information that could be used by adversaries. Sensitive information (e.g., account numbers, social security numbers, and credit card numbers) are not listed in error logs or associated administrative messages. The extent to which the information system is able to identify and handle error conditions is guided by organizational policy and operational requirements.','LOW Not Selected MOD SI-11 HIGH SI-11','System And Information Integrity','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/49-08_02_SI-11'),('SI-12','SI-12','08_02_SI-12','Information Output Handling And Retention','The organization handles and retains output from the information system in accordance with applicable laws, Executive Orders, directives, policies, regulations, standards, and operational requirements.','None.','LOW Not Selected MOD SI-12 HIGH SI-12','System And Information Integrity','Operational','http://www.opensecurityarchitecture.org/cms/library/08_02_control-catalogue/50-08_02_SI-12');

--
-- Table structure for table `enhancements`
--

CREATE TABLE `enhancements` (
  `e_id` smallint(5) unsigned NOT NULL AUTO_INCREMENT,
  `c_id` char(5) DEFAULT NULL,
  `enhancement` varchar(5000) DEFAULT NULL,
  PRIMARY KEY (`e_id`)
) ENGINE=InnoDB AUTO_INCREMENT=262 DEFAULT CHARSET=latin1;

--
-- Dumping data for table `enhancements`
--

INSERT INTO `enhancements` VALUES (1,'AC-01','(0) None.'),(2,'AC-02','(1) The organization employs automated mechanisms to support the management of information system accounts.'),(3,'AC-02','(2) The information system automatically terminates temporary and emergency accounts after [Assignment: organization-defined time period for each type of account].'),(4,'AC-02','(3) The information system automatically disables inactive accounts after [Assignment: organization- defined time period].'),(5,'AC-02','(4) The organization employs automated mechanisms to audit account creation, modification, disabling, and termination actions and to notify, as required, appropriate individuals.'),(6,'AC-03','(1) The information system restricts access to privileged functions (deployed in hardware, software, and firmware) and security-relevant information to explicitly authorized personnel.'),(7,'AC-03','Enhancement Supplemental Guidance: Explicitly authorized personnel include, for example, security administrators, system and network administrators, and other privileged users. Privileged users are individuals who have access to system control, monitoring, or administration functions (e.g., system administrators, information system security officers, maintainers, system programmers).'),(8,'AC-04','(1) The information system implements information flow control enforcement using explicit labels on information, source, and destination objects as a basis for flow control decisions.'),(9,'AC-04','Enhancement Supplemental Guidance: Information flow control enforcement using explicit labels is used, for example, to control the release of certain types of information.'),(10,'AC-04','(2) The information system implements information flow control enforcement using protected processing domains (e.g., domain type-enforcement) as a basis for flow control decisions.'),(11,'AC-04','(3) The information system implements information flow control enforcement using dynamic security policy mechanisms as a basis for flow control decisions.'),(12,'AC-05','(0) None.'),(13,'AC-06','(0) None.'),(14,'AC-07','(1) The information system automatically locks the account/node until released by an administrator when the maximum number of unsuccessful attempts is exceeded.'),(15,'AC-08','(0) None.'),(16,'AC-09','(0) None.'),(17,'AC-10','(0) None.'),(18,'AC-11','(0) None.'),(19,'AC-12','(1) Automatic session termination applies to local and remote sessions.'),(20,'AC-13','(1) The organization employs automated mechanisms to facilitate the review of user activities.'),(21,'AC-14','(1) The organization permits actions to be performed without identification and authentication only to the extent necessary to accomplish mission objectives.'),(22,'AC-15','(0) None.'),(23,'AC-16','(0) None.'),(24,'AC-17','(1) The organization employs automated mechanisms to facilitate the monitoring and control of remote access methods.'),(25,'AC-17','(2) The organization uses cryptography to protect the confidentiality and integrity of remote access sessions.'),(26,'AC-17','(3) The organization controls all remote accesses through a limited number of managed access control points.'),(27,'AC-17','(4) The organization permits remote access for privileged functions only for compelling operational needs and documents the rationale for such access in the security plan for the information system.'),(28,'AC-18','(1) The organization uses authentication and encryption to protect wireless access to the information system.'),(29,'AC-18','(2) The organization scans for unauthorized wireless access points [Assignment: organization-defined frequency] and takes appropriate action if such an access points are discovered.'),(30,'AC-18','Enhancement Supplemental Guidance: Organizations conduct a thorough scan for unauthorized wireless access points in facilities containing high-impact information systems. The scan is not limited to only those areas within the facility containing the high-impact information systems.'),(31,'AC-19','(0) None.'),(32,'AC-20','(1) The organization prohibits authorized individuals from using an external information system to access the information system or to process, store, or transmit organization-controlled information except in situations where the organization: (i) can verify the employment of required security controls on the external system as specified in the organization’s information security policy and system security plan; or (ii) has approved information system connection or processing agreements with the organizational entity hosting the external information system.'),(33,'AU-01','(0) None.'),(34,'AU-02','(1) The information system provides the capability to compile audit records from multiple components throughout the system into a systemwide (logical or physical), time-correlated audit trail.'),(35,'AU-02','(2) The information system provides the capability to manage the selection of events to be audited by individual components of the system.'),(36,'AU-02','(3) The organization periodically reviews and updates the list of organization-defined auditable events.'),(37,'AU-03','(1) The information system provides the capability to include additional, more detailed information in the audit records for audit events identified by type, location, or subject.'),(38,'AU-03','(2) The information system provides the capability to centrally manage the content of audit records generated by individual components throughout the system.'),(39,'AU-04','(0) None.'),(40,'AU-05','(1) The information system provides a warning when allocated audit record storage volume reaches [Assignment: organization-defined percentage of maximum audit record storage capacity].'),(41,'AU-05','(2) The information system provides a real-time alert when the following audit failure events occur: [Assignment: organization-defined audit failure events requiring real-time alerts].'),(42,'AU-06','(1) The organization employs automated mechanisms to integrate audit monitoring, analysis, and reporting into an overall process for investigation and response to suspicious activities.'),(43,'AU-06','(2) The organization employs automated mechanisms to alert security personnel of the following inappropriate or unusual activities with security implications: [Assignment: organization-defined list of inappropriate or unusual activities that are to result in alerts].'),(44,'AU-07','(1) The information system provides the capability to automatically process audit records for events'),(45,'AU-07','of interest based upon selectable, event criteria.'),(46,'AU-08','(1) The organization synchronizes internal information system clocks [Assignment: organization- defined frequency].'),(47,'AU-09','(1) The information system produces audit records on hardware-enforced, write-once media.'),(48,'AU-10','(0) None.'),(49,'AU-11','(0) None.'),(50,'AT-01','(0) None.'),(51,'AT-02','(0) None.'),(52,'AT-03','(0) None.'),(53,'AT-04','(0) None.'),(54,'AT-05','(0) None.'),(55,'CA-01','(0) None.'),(56,'CA-02','(0) None.'),(57,'CA-03','(0) None.'),(58,'CA-04','(1) The organization employs an independent certification agent or certification team to conduct an assessment of the security controls in the information system. Enhancement Supplemental Guidance: An independent certification agent or certification team is any individual or group capable of conducting an impartial assessment of an organizational information system. Impartiality implies that the assessors are free from any perceived or actual conflicts of interest with respect to the developmental, operational, and/or management chain of command associated with the information system or to the determination of security control effectiveness. Independent security certification services can be obtained from other elements within the organization or can be contracted to a public or private sector entity outside of the organization. Contracted certification services are considered independent if the information system owner is not directly involved in the contracting process or cannot unduly influence the independence of the certification agent or certification team conducting the assessment of the security controls in the information system. The authorizing official decides on the required level of certifier independence based on the criticality and sensitivity of the information system and the ultimate risk to organizational operations and organizational assets, and to individuals. The authorizing official determines if the level of certifier independence is sufficient to provide confidence that the assessment results produced are sound and can be used to make a credible, risk-based decision. In special situations, for example when the organization that owns the information system is small or the organizational structure requires that the assessment of the security controls be accomplished by individuals that are in the developmental, operational, and/or management chain of the system owner or authorizing official, independence in the certification process can be achieved by ensuring the assessment results are carefully reviewed and analyzed by an independent team of experts to validate the completeness, consistency, and veracity of the results. The authorizing official should consult with the Office of the Inspector General, the senior agency information security officer, and the chief information officer to fully discuss the implications of any decisions on certifier independence in the types of special circumstances described above.'),(59,'CA-05','(0) None.'),(60,'CA-06','(0) None.'),(61,'CA-07','(1) The organization employs an independent certification agent or certification team to monitor the security controls in the information system on an ongoing basis.'),(62,'CA-07','Enhancement Supplemental Guidance: The organization can extend and maximize the value of the ongoing assessment of security controls during the continuous monitoring process by requiring an independent certification agent or team to assess all of the security controls during the information system’s three-year accreditation cycle. Related security controls: CA-2, CA-4, CA-5, CA-6, CM-4.'),(63,'CM-01','(0) None.'),(64,'CM-02','(1) The organization updates the baseline configuration of the information system as an integral part of information system component installations.'),(65,'CM-02','(2) The organization employs automated mechanisms to maintain an up-to-date, complete, accurate, and readily available baseline configuration of the information system.'),(66,'CM-03','(1) The organization employs automated mechanisms to: (i) document proposed changes to the information system; (ii) notify appropriate approval authorities; (iii) highlight approvals that have not been received in a timely manner; (iv) inhibit change until necessary approvals are received; and (v) document completed changes to the information system.'),(67,'CM-04','(0) None.'),(68,'CM-05','(1) The organization employs automated mechanisms to enforce access restrictions and support auditing of the enforcement actions.'),(69,'CM-06','(1) The organization employs automated mechanisms to centrally manage, apply, and verify configuration settings.'),(70,'CM-07','(1) The organization reviews the information system [Assignment: organization-defined frequency], to identify and eliminate unnecessary functions, ports, protocols, and/or services.'),(71,'CM-08','(1) The organization updates the inventory of information system components as an integral part of component installations.'),(72,'CM-08','(2) The organization employs automated mechanisms to help maintain an up-to-date, complete, accurate, and readily available inventory of information system components.'),(73,'CP-01','(0) None.'),(74,'CP-02','(1) The organization coordinates contingency plan development with organizational elements responsible for related plans.'),(75,'CP-02','Enhancement Supplemental Guidance: Examples of related plans include Business Continuity Plan, Disaster Recovery Plan, Continuity of Operations Plan, Business Recovery Plan, Incident Response Plan, and Emergency Action Plan.'),(76,'CP-02','(2) The organization conducts capacity planning so that necessary capacity for information processing, telecommunications, and environmental support exists during crisis situations.'),(77,'CP-03','(1) The organization incorporates simulated events into contingency training to facilitate effective response by personnel in crisis situations.'),(78,'CP-03','(2) The organization employs automated mechanisms to provide a more thorough and realistic training environment.'),(79,'CP-04','(1) The organization coordinates contingency plan testing and/or exercises with organizational elements responsible for related plans.'),(80,'CP-04','Enhancement Supplemental Guidance: Examples of related plans include Business Continuity Plan, Disaster Recovery Plan, Continuity of Operations Plan, Business Recovery Plan, Incident Response Plan, and Emergency Action Plan.'),(81,'CP-04','(2) The organization tests/exercises the contingency plan at the alternate processing site to familiarize contingency personnel with the facility and available resources and to evaluate the site’s capabilities to support contingency operations.'),(82,'CP-04','(3) The organization employs automated mechanisms to more thoroughly and effectively test/exercise the contingency plan by providing more complete coverage of contingency issues, selecting more realistic test/exercise scenarios and environments, and more effectively stressing the information system and supported missions.'),(83,'CP-05','(0) None.'),(84,'CP-06','(1) The organization identifies an alternate storage site that is geographically separated from the primary storage site so as not to be susceptible to the same hazards.'),(85,'CP-06','(2) The organization configures the alternate storage site to facilitate timely and effective recovery operations.'),(86,'CP-06','(3) The organization identifies potential accessibility problems to the alternate storage site in the event of an area-wide disruption or disaster and outlines explicit mitigation actions.'),(87,'CP-07','(1) The organization identifies an alternate processing site that is geographically separated from the primary processing site so as not to be susceptible to the same hazards.'),(88,'CP-07','(2) The organization identifies potential accessibility problems to the alternate processing site in the event of an area-wide disruption or disaster and outlines explicit mitigation actions.'),(89,'CP-07','(3) The organization develops alternate processing site agreements that contain priority-of-service provisions in accordance with the organization’s availability requirements.'),(90,'CP-07','(4) The organization fully configures the alternate processing site so that it is ready to be used as the operational site supporting a minimum required operational capability.'),(91,'CP-08','(1) The organization develops primary and alternate telecommunications service agreements that contain priority-of-service provisions in accordance with the organization’s availability requirements.'),(92,'CP-08','(2) The organization obtains alternate telecommunications services that do not share a single point of failure with primary telecommunications services.'),(93,'CP-08','(3) The organization obtains alternate telecommunications service providers that are sufficiently separated from primary service providers so as not to be susceptible to the same hazards.'),(94,'CP-08','(4) The organization requires primary and alternate telecommunications service providers to have adequate contingency plans.'),(95,'CP-09','(1) The organization tests backup information [Assignment: organization-defined frequency] to verify media reliability and information integrity.'),(96,'CP-09','(2) The organization selectively uses backup information in the restoration of information system functions as part of contingency plan testing.'),(97,'CP-09','(3) The organization stores backup copies of the operating system and other critical information system software in a separate facility or in a fire-rated container that is not collocated with the operational software.'),(98,'CP-09','(4) The organization protects system backup information from unauthorized modification. Enhancement Supplemental Guidance: The organization employs appropriate mechanisms (e.g., digital signatures, cryptographic hashes) to protect the integrity of information system backups. Protecting the confidentiality of system backup information is beyond the scope of this control. Related security controls: MP-4, MP-5.'),(99,'CP-10','(1) The organization includes a full recovery and reconstitution of the information system as part of contingency plan testing.'),(100,'IA-01','(0) None.'),(101,'IA-02','(1) The information system employs multifactor authentication for remote system access that is NIST Special Publication 800-63 [Selection: organization-defined level 3, level 3 using a hardware authentication device, or level 4] compliant.'),(102,'IA-02','(2) The information system employs multifactor authentication for local system access that is NIST Special Publication 800-63 [Selection: organization-defined level 3 or level 4] compliant.'),(103,'IA-02','(3) The information system employs multifactor authentication for remote system access that is NIST Special Publication 800-63 level 4 compliant.'),(104,'IA-03','(0) None.'),(105,'IA-04','(0) None.'),(106,'IA-05','(0) None.'),(107,'IA-06','(0) None.'),(108,'IA-07','(0) None.'),(109,'IR-01','(0) None.'),(110,'IR-02','(1) The organization incorporates simulated events into incident response training to facilitate effective response by personnel in crisis situations.'),(111,'IR-02','(2) The organization employs automated mechanisms to provide a more thorough and realistic training environment.'),(112,'IR-03','(1) The organization employs automated mechanisms to more thoroughly and effectively test/exercise the incident response capability.'),(113,'IR-03','Enhancement Supplemental Guidance: Automated mechanisms can provide the ability to more thoroughly and effectively test or exercise the capability by providing more complete coverage of incident response issues, selecting more realistic test/exercise scenarios and environments, and more effectively stressing the response capability.'),(114,'IR-04','(1) The organization employs automated mechanisms to support the incident handling process.'),(115,'IR-05','(1) The organization employs automated mechanisms to assist in the tracking of security incidents and in the collection and analysis of incident information.'),(116,'IR-06','(1) The organization employs automated mechanisms to assist in the reporting of security incidents.'),(117,'IR-07','(1) The organization employs automated mechanisms to increase the availability of incident response- related information and support.'),(118,'MA-01','(0) None.'),(119,'MA-02','(1) The organization maintains maintenance records for the information system that include: (i) the date and time of maintenance; (ii) name of the individual performing the maintenance; (iii) name of escort, if necessary; (iv) a description of the maintenance performed; and (v) a list of equipment removed or replaced (including identification numbers, if applicable).'),(120,'MA-02','(2) The organization employs automated mechanisms to schedule and conduct maintenance as required, and to create up-to date, accurate, complete, and available records of all maintenance actions, both needed and completed.'),(121,'MA-03','(1) The organization inspects all maintenance tools carried into a facility by maintenance personnel for obvious improper modifications.'),(122,'MA-03','Enhancement Supplemental Guidance: Maintenance tools include, for example, diagnostic and test equipment used to conduct maintenance on the information system.'),(123,'MA-03','(2) The organization checks all media containing diagnostic and test programs for malicious code before the media are used in the information system.'),(124,'MA-03','(3) The organization checks all maintenance equipment with the capability of retaining information so that no organizational information is written on the equipment or the equipment is appropriately sanitized before release; if the equipment cannot be sanitized, the equipment remains within the facility or is destroyed, unless an appropriate organization official explicitly authorizes an exception.'),(125,'MA-03','(4) The organization employs automated mechanisms to restrict the use of maintenance tools to authorized personnel only.'),(126,'MA-04','(1) The organization audits all remote maintenance and diagnostic sessions and appropriate organizational personnel review the maintenance records of the remote sessions.'),(127,'MA-04','(2) The organization addresses the installation and use of remote maintenance and diagnostic links in the security plan for the information system.'),(128,'MA-04','(3) The organization does not allow remote maintenance or diagnostic services to be performed by a provider that does not implement for its own information system, a level of security at least as high as that implemented on the system being serviced, unless the component being serviced is removed from the information system and sanitized (with regard to organizational information) before the service begins and also sanitized (with regard to potentially malicious software) after the service is performed and before being reconnected to the information system.'),(129,'MA-05','(0) None.'),(130,'MA-06','(0) None.'),(131,'MP-01','(0) None.'),(132,'MP-02','(1) The organization employs automated mechanisms to restrict access to media storage areas and to audit access attempts and access granted.'),(133,'MP-02','Enhancement Supplemental Guidance: This control enhancement is primarily applicable to designated media storage areas within an organization where a significant volume of media is stored and is not intended to apply to every location where some media is stored (e.g., in individual offices).'),(134,'MP-03','(0) None.'),(135,'MP-04','(0) None.'),(136,'MP-05','(1) The organization protects digital and non-digital media during transport outside of controlled areas using [Assignment: organization-defined security measures, e.g., locked container, cryptography]. Enhancement Supplemental Guidance: Physical and technical security measures for the protection of digital and non-digital media are approved by the organization, commensurate with the FIPS 199 security categorization of the information residing on the media, and consistent with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidance. Cryptographic mechanisms can provide confidentiality and/or integrity protections depending upon the mechanisms used.'),(137,'MP-05','(2) The organization documents, where appropriate, activities associated with the transport of information system media using [Assignment: organization-defined system of records]. Enhancement Supplemental Guidance: Organizations establish documentation requirements for activities associated with the transport of information system media in accordance with the organizational assessment of risk.'),(138,'MP-05','(3) The organization employs an identified custodian at all times to transport information system media.'),(139,'MP-05','Enhancement Supplemental Guidance: Organizations establish documentation requirements for activities associated with the transport of information system media in accordance with the organizational assessment of risk.'),(140,'MP-06','(1) The organization tracks, documents, and verifies media sanitization and disposal actions.'),(141,'MP-06','(2) The organization periodically tests sanitization equipment and procedures to verify correct performance.'),(142,'PS-01','(0) None.'),(143,'PS-02','(0) None.'),(144,'PS-03','(0) None.'),(145,'PS-04','(0) None.'),(146,'PS-05','(0) None.'),(147,'PS-06','(0) None.'),(148,'PS-07','(0) None.'),(149,'PS-08','(0) None.'),(150,'PE-01','(0) None.'),(151,'PE-02','(0) None.'),(152,'PE-03','(1) The organization controls physical access to the information system independent of the physical access controls for the facility.'),(153,'PE-03','Enhancement Supplemental Guidance: This control enhancement, in general, applies to server rooms, communications centers, or any other areas within a facility containing large concentrations of information system components or components with a higher impact level than that of the majority of the facility. The intent is to provide an additional layer of physical security for those areas where the organization may be more vulnerable due to the concentration of information system components or the impact level of the components. The control enhancement is not intended to apply to workstations or peripheral devices that are typically dispersed throughout the facility and used routinely by organizational personnel.'),(154,'PE-04','(0) None.'),(155,'PE-05','(0) None.'),(156,'PE-06','(1) The organization monitors real-time physical intrusion alarms and surveillance equipment.'),(157,'PE-06','(2) The organization employs automated mechanisms to recognize potential intrusions and initiate appropriate response actions.'),(158,'PE-07','(1) The organization escorts visitors and monitors visitor activity, when required.'),(159,'PE-08','(1) The organization employs automated mechanisms to facilitate the maintenance and review of access records.'),(160,'PE-08','(2) The organization maintains a record of all physical access, both visitor and authorized individuals.'),(161,'PE-09','(1) The organization employs redundant and parallel power cabling paths.'),(162,'PE-10','(1) The organization protects the emergency power-off capability from accidental or unauthorized activation.'),(163,'PE-11','(1) The organization provides a long-term alternate power supply for the information system that is capable of maintaining minimally required operational capability in the event of an extended loss of the primary power source.'),(164,'PE-11','(2) The organization provides a long-term alternate power supply for the information system that is self-contained and not reliant on external power generation.'),(165,'PE-12','(0) None.'),(166,'PE-13','(1) The organization employs fire detection devices/systems that activate automatically and notify the organization and emergency responders in the event of a fire.'),(167,'PE-13','(2) The organization employs fire suppression devices/systems that provide automatic notification of any activation to the organization and emergency responders.'),(168,'PE-13','(3) The organization employs an automatic fire suppression capability in facilities that are not staffed on a continuous basis.'),(169,'PE-14','(0) None.'),(170,'PE-15','(1) The organization employs mechanisms that, without the need for manual intervention, protect the information system from water damage in the event of a significant water leak.'),(171,'PE-16','(0) None.'),(172,'PE-17','(0) None.'),(173,'PE-18','(1) The organization plans the location or site of the facility where the information system resides with regard to physical and environmental hazards and for existing facilities, considers the physical and environmental hazards in its risk mitigation strategy.'),(174,'PE-19','(0) None.'),(175,'PL-01','(0) None.'),(176,'PL-02','(0) None.'),(177,'PL-03','(0) None.'),(178,'PL-04','(0) None.'),(179,'PL-05','(0) None.'),(180,'PL-06','(0) None.'),(181,'RA-01','(0) None.'),(182,'RA-02','(0) None.'),(183,'RA-03','(0) None.'),(184,'RA-04','(0) None.'),(185,'RA-05','(1) The organization employs vulnerability scanning tools that include the capability to readily update the list of information system vulnerabilities scanned.'),(186,'RA-05','(2) The organization updates the list of information system vulnerabilities scanned [Assignment: organization-defined frequency] or when significant new vulnerabilities are identified and reported.'),(187,'RA-05','(3) The organization employs vulnerability scanning procedures that can demonstrate the breadth and depth of scan coverage, including vulnerabilities checked and information system components scanned.'),(188,'SC-01','(0) None.'),(189,'SC-02','(0) None.'),(190,'SC-03','(1) The information system employs underlying hardware separation mechanisms to facilitate security function isolation.'),(191,'SC-03','(2) The information system isolates critical security functions (i.e., functions enforcing access and information flow control) from both nonsecurity functions and from other security functions.'),(192,'SC-03','(3) The information system minimizes the number of nonsecurity functions included within the isolation boundary containing security functions.'),(193,'SC-03','(4) The information system security functions are implemented as largely independent modules that avoid unnecessary interactions between modules.'),(194,'SC-03','(5) The information system security functions are implemented as a layered structure minimizing interactions between layers of the design and avoiding any dependence by lower layers on the functionality or correctness of higher layers.'),(195,'SC-04','(0) None.'),(196,'SC-05','(1) The information system restricts the ability of users to launch denial of service attacks against other information systems or networks.'),(197,'SC-05','(2) The information system manages excess capacity, bandwidth, or other redundancy to limit the effects of information flooding types of denial of service attacks.'),(198,'SC-06','(0) None.'),(199,'SC-07','(1) The organization physically allocates publicly accessible information system components to separate subnetworks with separate, physical network interfaces.'),(200,'SC-07','Enhancement Supplemental Guidance: Publicly accessible information system components include, for example, public web servers.'),(201,'SC-07','(2) The organization prevents public access into the organization’s internal networks except as appropriately mediated.'),(202,'SC-07','(3) The organization limits the number of access points to the information system to allow for better monitoring of inbound and outbound network traffic.'),(203,'SC-07','(4) The organization implements a managed interface (boundary protection devices in an effective security architecture) with any external telecommunication service, implementing controls appropriate to the required protection of the confidentiality and integrity of the information being transmitted.'),(204,'SC-07','(5) The information system denies network traffic by default and allows network traffic by exception (i.e., deny all, permit by exception).'),(205,'SC-07','(6) The organization prevents the unauthorized release of information outside of the information system boundary or any unauthorized communication through the information system boundary when there is an operational failure of the boundary protection mechanisms.'),(206,'SC-08','(1) The organization employs cryptographic mechanisms to recognize changes to information during transmission unless otherwise protected by alternative physical measures.'),(207,'SC-08','Enhancement Supplemental Guidance: Alternative physical protection measures include, for example, protected distribution systems.'),(208,'SC-09','(1) The organization employs cryptographic mechanisms to prevent unauthorized disclosure of information during transmission unless otherwise protected by alternative physical measures.'),(209,'SC-09','Enhancement Supplemental Guidance: Alternative physical protection measures include, for example, protected distribution systems.'),(210,'SC-10','(0) None.'),(211,'SC-11','(0) None.'),(212,'SC-12','(0) None.'),(213,'SC-13','(0) None.'),(214,'SC-14','(0) None.'),(215,'SC-15','(1) The information system provides physical disconnect of camera and microphone in a manner that supports ease of use.'),(216,'SC-16','(0) None.'),(217,'SC-17','(0) None.'),(218,'SC-18','(0) None.'),(219,'SC-19','(0) None.'),(220,'SC-20','(1) The information system, when operating as part of a distributed, hierarchical namespace, provides the means to indicate the security status of child subspaces and (if the child supports secure resolution services) enable verification of a chain of trust among parent and child domains.'),(221,'SC-20','Enhancement Supplemental Guidance: An example means to indicate the security status of child subspaces is through the use of delegation signer resource records.'),(222,'SC-21','(1) The information system performs data origin authentication and data integrity verification on all resolution responses whether or not local clients explicitly request this service.'),(223,'SC-21','Enhancement Supplemental Guidance: Local clients include, for example, DNS stub resolvers.'),(224,'SC-22','(0) None.'),(225,'SC-23','(0) None.'),(226,'SI-01','(0) None.'),(227,'SI-02','(1) The organization centrally manages the flaw remediation process and installs updates automatically.'),(228,'SI-02','(2) The organization employs automated mechanisms to periodically and upon demand determine the state of information system components with regard to flaw remediation.'),(229,'SI-03','(1) The organization centrally manages malicious code protection mechanisms.'),(230,'SI-03','(2) The information system automatically updates malicious code protection mechanisms.'),(231,'SI-04','(1) The organization interconnects and configures individual intrusion detection tools into a systemwide intrusion detection system using common protocols.'),(232,'SI-04','(2) The organization employs automated tools to support near-real-time analysis of events.'),(233,'SI-04','(3) The organization employs automated tools to integrate intrusion detection tools into access control and flow control mechanisms for rapid response to attacks by enabling reconfiguration of these mechanisms in support of attack isolation and elimination.'),(234,'SI-04','(4) The information system monitors inbound and outbound communications for unusual or unauthorized activities or conditions.'),(235,'SI-04','Enhancement Supplemental Guidance: Unusual/unauthorized activities or conditions include, for example, the presence of malicious code, the unauthorized export of information, or signaling to an external information system.'),(236,'SI-04','(5) The information system provides a real-time alert when the following indications of compromise or potential compromise occur: [Assignment: organization-defined list of compromise indicators].'),(237,'SI-05','(1) The organization employs automated mechanisms to make security alert and advisory information available throughout the organization as needed.'),(238,'SI-06','(1) The organization employs automated mechanisms to provide notification of failed automated security tests.'),(239,'SI-06','(2) The organization employs automated mechanisms to support management of distributed security testing.'),(240,'SI-07','(1) The organization reassesses the integrity of software and information by performing [Assignment: organization-defined frequency] integrity scans of the system.'),(241,'SI-07','(2) The organization employs automated tools that provide notification to appropriate individuals upon discovering discrepancies during integrity verification.'),(242,'SI-07','(3) The organization employs centrally managed integrity verification tools.'),(243,'SI-08','(1) The organization centrally manages spam protection mechanisms.'),(244,'SI-08','(2) The information system automatically updates spam protection mechanisms.'),(245,'SI-09','(0) None.'),(246,'SI-10','(0) None.'),(247,'SI-11','(0) None.'),(248,'SI-12','(0) None.'),(249,'SA-01','(0) None.'),(250,'SA-02','(0) None.'),(251,'SA-03','(0) None.'),(252,'SA-04','(1) The organization requires in solicitation documents that appropriate documentation be provided describing the functional properties of the security controls employed within the information system with sufficient detail to permit analysis and testing of the controls.'),(253,'SA-04','(2) The organization requires in solicitation documents that appropriate documentation be provided describing the design and implementation details of the security controls employed within the information system with sufficient detail to permit analysis and testing of the controls (including functional interfaces among control components).'),(254,'SA-05','(1) The organization includes, in addition to administrator and user guides, documentation, if available from the vendor/manufacturer, describing the functional properties of the security controls employed within the information system with sufficient detail to permit analysis and testing of the controls.'),(255,'SA-05','(2) The organization includes, in addition to administrator and user guides, documentation, if available from the vendor/manufacturer, describing the design and implementation details of the security controls employed within the information system with sufficient detail to permit analysis and testing of the controls (including functional interfaces among control components).'),(256,'SA-06','(0) None.'),(257,'SA-07','(0) None.'),(258,'SA-08','(0) None.'),(259,'SA-09','(0) None.'),(260,'SA-10','(0) None.'),(261,'SA-11','(0) None.');

--
-- Table structure for table `iso17799`
--

CREATE TABLE `iso17799` (
  `iso_id` smallint(5) unsigned NOT NULL AUTO_INCREMENT,
  `c_id` char(5) DEFAULT NULL,
  `iso17799` varchar(10) DEFAULT NULL,
  PRIMARY KEY (`iso_id`)
) ENGINE=InnoDB AUTO_INCREMENT=329 DEFAULT CHARSET=latin1;

--
-- Dumping data for table `iso17799`
--

INSERT INTO `iso17799` VALUES (1,'AC-01','11.1.1'),(2,'AC-01','11.4.1'),(3,'AC-01','15.1.1'),(4,'AC-02','6.2.2'),(5,'AC-02','6.2.3'),(6,'AC-02','8.3.3'),(7,'AC-02','11.2.1'),(8,'AC-02','11.2.2'),(9,'AC-02','11.2.4'),(10,'AC-02','11.7.2'),(11,'AC-03','11.2.4'),(12,'AC-03','11.4.5'),(13,'AC-04','10.6.2'),(14,'AC-04','11.4.5'),(15,'AC-04','11.4.6'),(16,'AC-04','11.4.7'),(17,'AC-05','10.1.3'),(18,'AC-05','10.6.1'),(19,'AC-05','10.10.1'),(20,'AC-06','11.2.2'),(21,'AC-07','11.5.1'),(22,'AC-08','11.5.1'),(23,'AC-08','15.1.5'),(24,'AC-09','11.5.1'),(25,'AC-11','11.3.2'),(26,'AC-12','11.3.2'),(27,'AC-12','11.5.5'),(28,'AC-13','10.10.2'),(29,'AC-13','11.2.4'),(30,'AC-15','7.2.2'),(31,'AC-16','7.2.2'),(32,'AC-17','11.4.2'),(33,'AC-17','11.4.3'),(34,'AC-17','11.4.4'),(35,'AC-18','11.4.2'),(36,'AC-18','11.7.1'),(37,'AC-18','11.7.2'),(38,'AC-19','11.7.1'),(39,'AC-20','6.1.4'),(40,'AC-20','9.2.5'),(41,'AC-20','11.7.1'),(42,'AT-01','5.1.1'),(43,'AT-01','8.2.2'),(44,'AT-01','15.1.1'),(45,'AT-02','6.2.3'),(46,'AT-02','8.2.2'),(47,'AT-02','10.4.1'),(48,'AT-02','11.7.1'),(49,'AT-02','13.1.1'),(50,'AT-02','14.1.4'),(51,'AT-02','15.1.4'),(52,'AT-03','8.2.2'),(53,'AT-03','10.3.2'),(54,'AT-03','11.7.1'),(55,'AT-03','13.1.1'),(56,'AT-03','14.1.4'),(57,'AT-05','6.1.7'),(58,'AU-01','10.10'),(59,'AU-01','15.1.1'),(60,'AU-02','10.10.1'),(61,'AU-03','10.10.1'),(62,'AU-03','10.10.4'),(63,'AU-04','10.10.3'),(64,'AU-05','10.10.3'),(65,'AU-06','10.10.2'),(66,'AU-06','10.10.4'),(67,'AU-06','13.2.1'),(68,'AU-07','10.10.3'),(69,'AU-08','10.10.6'),(70,'AU-09','10.10.3'),(71,'AU-09','15.1.3'),(72,'AU-09','15.3.2'),(73,'AU-10','10.8.2'),(74,'AU-10','10.9.1'),(75,'AU-10','12.3.1'),(76,'AU-11','10.10.1'),(77,'AU-11','15.1.3'),(78,'CA-01','6.1.4'),(79,'CA-01','10.3.2'),(80,'CA-01','15.1.1'),(81,'CA-02','6.1.8'),(82,'CA-02','15.2.1'),(83,'CA-02','15.2.2'),(84,'CA-03','10.6.2'),(85,'CA-03','10.9.1'),(86,'CA-03','11.4.5'),(87,'CA-03','11.4.6'),(88,'CA-03','11.4.7'),(89,'CA-04','10.3.2'),(90,'CA-05','15.2.1'),(91,'CA-06','10.3.2'),(92,'CA-07','15.2.1'),(93,'CA-07','15.2.2'),(94,'CM-01','12.4.1'),(95,'CM-01','12.5.1'),(96,'CM-01','15.1.1'),(97,'CM-02','7.1.1'),(98,'CM-02','15.1.2'),(99,'CM-03','10.1.2'),(100,'CM-03','10.2.3'),(101,'CM-03','12.4.1'),(102,'CM-03','12.5.1'),(103,'CM-03','12.5.2'),(104,'CM-03','12.5.3'),(105,'CM-04','10.1.2'),(106,'CM-05','11.6.1'),(107,'CM-08','7.1.1'),(108,'CM-08','15.1.2'),(109,'CP-01','5.1.1'),(110,'CP-01','10.4.1'),(111,'CP-01','14.1.1'),(112,'CP-01','14.1.3'),(113,'CP-01','15.1.1'),(114,'CP-02','10.3.2'),(115,'CP-02','10.4.1'),(116,'CP-02','10.8.5'),(117,'CP-02','14.1.3'),(118,'CP-02','14.1.4'),(119,'CP-03','14.1.3'),(120,'CP-03','14.1.4'),(121,'CP-04','10.5.1'),(122,'CP-04','14.1.5'),(123,'CP-05','14.1.3'),(124,'CP-05','14.1.5'),(125,'CP-06','10.5.1'),(126,'CP-07','14.1.4'),(127,'CP-08','14.1.4'),(128,'CP-09','10.5.1'),(129,'CP-09','11.7.1'),(130,'CP-10','14.1.4'),(131,'IA-01','15.1.1'),(132,'IA-02','11.2.3'),(133,'IA-02','11.4.2'),(134,'IA-02','11.5.2'),(135,'IA-03','11.4.2'),(136,'IA-03','11.4.3'),(137,'IA-03','11.7.1'),(138,'IA-04','11.2.3'),(139,'IA-04','11.5.2'),(140,'IA-05','11.5.2'),(141,'IA-05','11.5.3'),(142,'IA-06','11.5.1'),(143,'IR-01','10.4.1'),(144,'IR-01','13.1'),(145,'IR-01','13.2.1'),(146,'IR-01','15.1.1'),(147,'IR-02','13.1.1'),(148,'IR-03','14.1.5'),(149,'IR-04','6.1.6'),(150,'IR-04','13.2.1'),(151,'IR-04','13.2.2'),(152,'IR-06','6.1.6'),(153,'IR-06','6.2.2'),(154,'IR-06','6.2.3'),(155,'IR-06','13.1.1'),(156,'IR-06','13.1.2'),(157,'IR-07','14.1.3'),(158,'MA-01','10.1.1'),(159,'MA-01','15.1.1'),(160,'MA-02','9.2.4'),(161,'MA-04','11.4.4'),(162,'MA-05','6.2.3'),(163,'MA-05','9.2.4'),(164,'MP-01','10.1.1'),(165,'MP-01','10.7'),(166,'MP-01','15.1.1'),(167,'MP-01','15.1.3'),(168,'MP-02','10.7.3'),(169,'MP-03','7.2.2'),(170,'MP-03','10.7.3'),(171,'MP-03','10.8.2'),(172,'MP-03','15.1.3'),(173,'MP-04','10.7.1'),(174,'MP-04','10.7.2'),(175,'MP-04','10.7.3'),(176,'MP-04','10.7.4'),(177,'MP-04','15.1.3'),(178,'MP-05','10.8.3'),(179,'MP-06','9.2.6'),(180,'MP-06','10.7.1'),(181,'MP-06','10.7.2'),(182,'PE-01','15.1.1'),(183,'PE-02','9.1.2'),(184,'PE-02','9.1.6'),(185,'PE-03','9.1.1'),(186,'PE-03','9.1.2'),(187,'PE-03','9.1.5'),(188,'PE-03','9.1.6'),(189,'PE-03','10.5.1'),(190,'PE-04','9.2.3'),(191,'PE-05','9.1.2'),(192,'PE-05','11.3.3'),(193,'PE-06','9.1.2'),(194,'PE-07','9.1.2'),(195,'PE-08','9.1.2'),(196,'PE-09','9.2.2'),(197,'PE-09','9.2.3'),(198,'PE-10','9.2.2'),(199,'PE-11','9.2.2'),(200,'PE-12','9.2.2'),(201,'PE-13','9.1.4'),(202,'PE-13','9.2.1'),(203,'PE-14','9.2.1'),(204,'PE-14','10.5.1'),(205,'PE-14','10.7.1'),(206,'PE-15','9.1.4'),(207,'PE-15','9.2.1'),(208,'PE-16','9.1.6'),(209,'PE-16','9.2.7'),(210,'PE-16','10.7.1'),(211,'PE-17','11.7.2'),(212,'PE-18','9.2.1'),(213,'PL-01','6.1'),(214,'PL-01','15.1.1'),(215,'PL-02','6.1'),(216,'PL-03','6.1'),(217,'PL-04','7.1.3'),(218,'PL-04','8.1.3'),(219,'PL-04','15.1.5'),(220,'PL-05','15.1.4'),(221,'PL-06','15.3.1'),(222,'PS-01','8.1.1'),(223,'PS-01','15.1.1'),(224,'PS-02','8.1.2'),(225,'PS-03','8.1.2'),(226,'PS-04','8.1.3'),(227,'PS-04','8.3'),(228,'PS-04','11.2.1'),(229,'PS-05','8.3.1'),(230,'PS-05','8.3.3'),(231,'PS-05','11.2.1'),(232,'PS-06','6.1.5'),(233,'PS-06','8.1.3'),(234,'PS-07','6.2.1'),(235,'PS-07','6.2.3'),(236,'PS-07','8.1.1'),(237,'PS-07','8.1.2'),(238,'PS-07','8.1.3'),(239,'PS-07','8.2.1'),(240,'PS-07','8.2.2'),(241,'PS-07','11.2.1'),(242,'PS-08','8.2.3'),(243,'PS-08','11.2.1'),(244,'RA-01','4.1'),(245,'RA-01','15.1.1'),(246,'RA-02','7.2.1'),(247,'RA-03','4.0'),(248,'RA-03','4.1'),(249,'RA-03','4.2'),(250,'RA-03','6.2.1'),(251,'RA-03','10.10.2'),(252,'RA-03','10.10.5'),(253,'RA-03','12.5.1'),(254,'RA-03','12.6.1'),(255,'RA-03','14.1.1'),(256,'RA-03','14.1.2'),(257,'RA-04','4.1'),(258,'RA-05','12.6.1'),(259,'SA-01','12.1'),(260,'SA-01','15.1.1'),(261,'SA-02','10.3.1'),(262,'SA-04','12.1.1'),(263,'SA-05','10.7.4'),(264,'SA-06','15.1.2'),(265,'SA-07','15.1.2'),(266,'SA-08','12.1'),(267,'SA-09','6.2.1'),(268,'SA-09','6.2.3'),(269,'SA-09','10.2.1'),(270,'SA-09','10.2.2'),(271,'SA-09','10.6.2'),(272,'SA-10','12.5.1'),(273,'SA-10','12.5.2'),(274,'SA-11','12.5.1'),(275,'SA-11','12.5.2'),(276,'SC-01','10.8.1'),(277,'SC-01','15.1.1'),(278,'SC-02','11.4.5'),(279,'SC-03','11.4.5'),(280,'SC-04','10.8.1'),(281,'SC-05','10.8.4'),(282,'SC-05','13.2.1'),(283,'SC-07','11.4.6'),(284,'SC-08','10.6.1'),(285,'SC-08','10.8.1'),(286,'SC-08','10.9.1'),(287,'SC-09','10.6.1'),(288,'SC-09','10.8.1'),(289,'SC-09','10.9.1'),(290,'SC-10','11.5.6'),(291,'SC-11','10.9.2'),(292,'SC-12','12.3.1'),(293,'SC-12','12.3.2'),(294,'SC-14','10.7.4'),(295,'SC-14','10.9.3'),(296,'SC-16','7.2.2'),(297,'SC-16','10.8.2'),(298,'SC-16','10.9.2'),(299,'SC-17','12.3.2'),(300,'SC-18','10.4.1'),(301,'SC-18','10.4.2'),(302,'SI-01','15.1.1'),(303,'SI-02','10.10.5'),(304,'SI-02','12.4.1'),(305,'SI-02','12.5.1'),(306,'SI-02','12.5.2'),(307,'SI-02','12.6.1'),(308,'SI-03','10.4.1'),(309,'SI-04','10.6.2'),(310,'SI-04','10.10.1'),(311,'SI-04','10.10.2'),(312,'SI-04','10.10.4'),(313,'SI-05','6.1.7'),(314,'SI-05','10.4.1'),(315,'SI-07','12.2.1'),(316,'SI-07','12.2.2'),(317,'SI-07','12.2.4'),(318,'SI-09','12.2.1'),(319,'SI-09','12.2.2'),(320,'SI-10','10.7.3'),(321,'SI-10','12.2.1'),(322,'SI-10','12.2.2'),(323,'SI-11','12.2.1'),(324,'SI-11','12.2.2'),(325,'SI-11','12.2.3'),(326,'SI-11','12.2.4'),(327,'SI-12','10.7.3'),(328,'SI-12','12.2.4');

--
-- Table structure for table `pci2`
--

CREATE TABLE `pci2` (
  `pci_id` smallint(5) unsigned NOT NULL AUTO_INCREMENT,
  `c_id` char(5) DEFAULT NULL,
  `pci2` varchar(10) DEFAULT NULL,
  PRIMARY KEY (`pci_id`)
) ENGINE=InnoDB AUTO_INCREMENT=182 DEFAULT CHARSET=latin1;

--
-- Dumping data for table `pci2`
--

INSERT INTO `pci2` VALUES (1,'AC-01','12.3.2'),(2,'AC-01','7.1'),(3,'AC-01','12.5.1'),(4,'AC-02','7.1.3'),(5,'AC-03','7.1.4'),(6,'AC-04','4.1'),(7,'AC-05','7.1.2'),(8,'AC-06','7.1.1'),(9,'AC-07','8.5.13'),(10,'AC-08','8.5.7'),(11,'AC-11','8.5.14'),(12,'AC-12','8.5.15'),(13,'AC-13','8.5.1'),(14,'AC-17','8.3'),(15,'AC-17','8.5.6'),(16,'AC-18','2.1.1'),(17,'AC-19','1.4'),(18,'AC-19','12.3.10'),(19,'AT-01','12.6'),(20,'AT-02','12.6.1a'),(21,'AT-03','12.6.1b'),(22,'AT-03','12.9.4'),(23,'AT-04','12.6.2'),(24,'AU-01','10.1'),(25,'AU-01','12.5.1'),(26,'AU-02','10.2'),(27,'AU-03','10.3'),(28,'AU-04','10.7'),(29,'AU-05','10.6'),(30,'AU-05','12.9'),(31,'AU-06','10.6'),(32,'AU-06','12.5.2'),(33,'AU-06','12.9.5'),(34,'AU-08','10.4'),(35,'AU-09','10.5'),(36,'AU-10','10.5'),(37,'AU-10','10.5.5'),(38,'AU-11','10.7'),(39,'CA-01','12.5.1'),(40,'CA-02','11.1'),(41,'CA-02','11.2'),(42,'CA-03','1.1.5'),(43,'CA-03','1.1.6'),(44,'CA-04','11.3'),(45,'CA-07','12.5.2'),(46,'CA-07','12.9.5'),(47,'CM-01','2.2a'),(48,'CM-02','2.2'),(49,'CM-02','2.1.1'),(50,'CM-03','6.4'),(51,'CM-04','11.5'),(52,'CM-05','2.2'),(53,'CM-06','2.2'),(54,'CM-06','2.2.3'),(55,'CM-07','2.2.2'),(56,'CM-07','2.2.4'),(57,'CM-08','12.3.3'),(58,'CM-08','12.3.4'),(59,'CP-01','12.9'),(60,'CP-01','12.9.1'),(61,'CP-02','12.9.1'),(62,'CP-02','12.9.2'),(63,'CP-03','12.9.4'),(64,'CP-04','12.9.2'),(65,'CP-05','12.9.6'),(66,'CP-09','12.9.1a'),(67,'IA-01','12.3.2'),(68,'IA-01','8.5.7'),(69,'IA-02','8.1'),(70,'IA-02','8.2'),(71,'IA-04','8.5'),(72,'IA-04','8.5.1'),(73,'IA-04','8.5.5'),(74,'IA-05','8.5'),(75,'IA-07','3.5'),(76,'IR-01','12.9'),(77,'IR-02','12.9.4'),(78,'IR-03','12.9.2'),(79,'IR-04','12.9'),(80,'IR-04','12.9.1'),(81,'IR-04','12.9.6'),(82,'IR-05','12.9.5'),(83,'IR-06','12.9.1'),(84,'IR-07','12.9.3'),(85,'MA-02','9.8'),(86,'MA-04','8.5.6'),(87,'MA-05','8.5.6'),(88,'MP-01','12.5.1'),(89,'MP-02','9.6'),(90,'MP-02','9.8'),(91,'MP-02','9.9'),(92,'MP-03','9.7'),(93,'MP-03','12.3.4'),(94,'MP-04','9.5'),(95,'MP-04','9.6'),(96,'MP-05','9.7.2'),(97,'MP-06','9.10'),(98,'MP-06','9.10.1'),(99,'MP-06','9.10.2'),(100,'PE-01','12.5.1'),(101,'PE-02','9.1'),(102,'PE-03','9.1'),(103,'PE-04','9.1.2'),(104,'PE-04','9.1.3'),(105,'PE-06','9.1.1'),(106,'PE-07','9.2'),(107,'PE-07','9.3.x'),(108,'PE-08','9.4'),(109,'PL-01','12.5.1'),(110,'PL-02','12.1'),(111,'PL-03','12.1'),(112,'PL-04','12.6.2'),(113,'PL-05','3.1.1'),(114,'PS-01','12.5.1'),(115,'PS-02','12.7'),(116,'PS-03','12.7'),(117,'PS-04','8.5.4'),(118,'PS-05','7.1.1'),(119,'PS-06','7.1.3'),(120,'PS-07','8.5.6'),(121,'PS-07','7.2.2'),(122,'RA-01','12.5.1'),(123,'RA-01','12.1'),(124,'RA-02','12.1.2'),(125,'RA-03','12.1.2'),(126,'RA-04','12.1.3'),(127,'RA-05','11.1'),(128,'RA-05','11.2'),(129,'RA-05','11.2.1'),(130,'RA-05','11.2.2'),(131,'RA-05','11.2.3'),(132,'RA-05','11.3'),(133,'SA-01','12.5.1'),(134,'SA-03','6.3'),(135,'SA-07','12.3.7'),(136,'SA-08','6.3'),(137,'SA-09','12.8.2'),(138,'SA-10','6.4.5'),(139,'SA-11','6.4.5.3'),(140,'SC-01','12.5.1'),(141,'SC-02','2.2.1'),(142,'SC-02','1.3.7'),(143,'SC-03','2.2.1'),(144,'SC-07','1.2'),(145,'SC-07','1.2.1'),(146,'SC-07','1.3.1'),(147,'SC-07','1.3.2'),(148,'SC-07','1.3.3'),(149,'SC-07','1.3.4'),(150,'SC-09','4.1'),(151,'SC-09','4.1.1'),(152,'SC-10','12.3.8'),(153,'SC-12','3.5'),(154,'SC-12','3.6'),(155,'SC-12','3.6.1'),(156,'SC-12','3.6.2'),(157,'SC-12','3.6.3'),(158,'SC-12','3.6.4'),(159,'SC-12','3.6.5'),(160,'SC-12','3.6.6'),(161,'SC-12','3.6.7'),(162,'SC-12','3.6.8'),(163,'SC-13','3.6'),(164,'SC-13','4.1.c'),(165,'SC-15','4.2'),(166,'SC-22','2.2.1'),(167,'SI-01','12.5.1'),(168,'SI-02','6.1'),(169,'SI-02','6.2'),(170,'SI-02','11.2'),(171,'SI-02','11.3'),(172,'SI-03','5.1'),(173,'SI-03','5.1.1'),(174,'SI-03','5.2'),(175,'SI-04','11.4'),(176,'SI-04','11.5'),(177,'SI-04','10.5.5'),(178,'SI-04','11.1'),(179,'SI-05','12.9.6'),(180,'SI-07','11.5'),(181,'SI-12','3.1.1');


