Exhibit S, HHSC Security Control Standards Catalog.xlsx

XLSX spreadsheet 77 KB Posted

Attached to
Eligibility Support Services
Solicitation number
HHS0017117
Issued by
Hockley County, Arlington City, Texas

About this file

This document is the HHSC Security Control Standards Catalog, a comprehensive security and access control framework developed by the Texas Health and Human Services Commission (HHSC) in conjunction with CMS standards. The catalog establishes detailed security and privacy control requirements organized into multiple control families including Access Control (AC), Awareness and Training (AT), Audit and Accountability (AU), Assessment, Authorization, and Monitoring (CA), Configuration Management (CM), Contingency Planning (CP), Identification and Authentication (IA), Incident Response (IR), Maintenance (MA), Media Protection (MP), Physical and Environmental Protection (PE), and Planning (PL). Each control includes specific implementation requirements, frequency schedules, and compliance criteria that systems must follow to protect organizational information, personally identifiable information (PII), and protected health information (PHI). The framework requires annual policy reviews, regular assessments, continuous monitoring, and incident response capabilities aligned with NIST standards and federal regulations.

The control standards mandate numerous operational and technical safeguards including multi-factor authentication for privileged and non-privileged accounts, automated account management and audit logging, encryption for sensitive data transmission and storage using FIPS 140-compliant standards, physical access controls with six-month authorization reviews, regular penetration testing, backup maintenance with three generations of files, configuration baselines with quarterly review of software authorization lists, and incident response planning with breach notification procedures. Training requirements specify initial security literacy training within one year of hire, role-based training before system access, and annual refresher training with lessons learned incorporated. The framework establishes audit record retention for ninety days with ten-year archival, requires weekly audit log review, mandates device locks after fifteen minutes of inactivity, enforces five-attempt login limits with thirty-minute lockouts, and specifies one concurrent session per user account. The control implementation version is ARC-AMPE-1.03, indicating this is an established standard for HHSC systems handling sensitive state and federal health information.

View the file

Other files

File Type Posted
Exhibit L, Deliverables.pdf PDF
Exhibit M, Certification Regarding Lobbying.pdf PDF
Exhibit Q, Subcontracting Plan.pdf PDF
Exhibit J, Evaluation Tool.pdf PDF
Exhibit C, Additional Provisions v1.0.pdf.pdf PDF
Official Correspondence Volume 2023.xlsx XLSX spreadsheet
Exhibit F, Cost Proposal.xlsx XLSX spreadsheet
Annual Incidents Follow Ups Numbers.xlsx XLSX spreadsheet
Athens Floor Plan.pdf PDF
Quantities - Historical Contract Year 2024 and 2023.xlsx XLSX spreadsheet
Exhibit B, Health and Human Services (HHS) Uniform Terms and Conditions (UTC) - Vendor Version 3.4.pdf PDF
ESBD_564512_1794352902211_RFP HHS0017117_Eligibility Support Services.pdf PDF
Edinburg Floor Plan.pdf PDF
Exhibit G, Exceptions Form.docx DOCX document
Complaint Volumes.xlsx XLSX spreadsheet
HHSC 2024 Laptop and Headset Inventory .xlsx XLSX spreadsheet
Exhibit A, Health and Human Services (HHS) Solicitation Affirmations, Version 2.10.pdf PDF
Exhibit E, Scope of Work (SOW).pdf PDF
HHSC Asset Management Guide.pdf PDF
TIERS Print Job Inventory.xlsx XLSX spreadsheet
Exhibit T, Oral Presentation Consensus Scoring Rubric.pdf PDF
Outbound Quantities by Letter Type.xlsx XLSX spreadsheet
San Antonio Floor Plan.pdf PDF
Call Center Software Application Support Functions.xlsx XLSX spreadsheet
HHSC SMS Email Mapping 05092024 - APPENDIX G v 1.7.xlsx XLSX spreadsheet
Exhibit I, Online Bid Room Information, v 1.40.pdf PDF
Exhibit O, Federal Funding Accountability and Transparency Act (FFATA) Certification.pdf PDF
Exhibit K, Key Performance Requirements.pdf PDF
Exhibit P, Insurance Requirements.pdf PDF
Exhibit R, Breach Disclosure History.pdf PDF
Exhibit D-1, Attachment 2 to the DUA, Secuirity and Privacy (SPI), Version 2.1.pdf PDF
Exhibit N, Assurances Non-Construction Programs.pdf PDF
Exhibit D, Health and Human Services (HHS) Data Use Agreement (DUA) Version 8.5.pdf PDF
Show all 33

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Archer Search Report

Control UniqueControl NumberControl NameControlImplemented ByControl Set Version Number
AC-01-CMS-ARC-AMPE-1.03AC-01Policy and ProceduresDevelop, document, and disseminate to applicable personnel and roles: Organization-level access control policy that: Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and Is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines; and Procedures that are defined within the applicable control implementation statements of the associated access controls; Designate an organization-defined official to manage the development, documentation, and dissemination of the access control policy and procedures; and Review and update the current access control: Policy at least every one (1) year and following organization-defined events; and Procedures at least every one (1) year and following organization-defined events.ARC-AMPE-1.03
AC-02-CMS-ARC-AMPE-1.03AC-02Account ManagementDefine and document the type of accounts allowed and specifically prohibited for use within the system; Assign account managers; Require organization-defined prerequisites and criteria for group and role membership; Specify: Authorized users of the system; Group and role membership; and Access authorizations (i.e., privileges) and organization-defined attributes (as required) for each account; Require approvals by organization-defined personnel or roles for requests to create accounts; Create, enable, modify, disable, and remove accounts in accordance with organization-defined policy, procedures, prerequisites, and criteria; Monitor the use of accounts; Notify account managers and organization-defined personnel or roles within: Twenty-four (24) hours when accounts are no longer required; Eight (8) hours when users are terminated or transferred; and Eight (8) hours when system usage or need-to-know changes for an individual; Authorizes access to the system based on: A valid access authorization; Intended system usage; and Other attributes as required by the organization or associated missions/business functions; Review accounts for compliance with account management requirements at least every ninety (90) days for all systems; and Establish and implement a process for changing shared or group account authenticators (if deployed) when individuals are removed from the group; and Align account management processes with personnel termination and transfer processes.ARC-AMPE-1.03
AC-02(01)-CMS-ARC-AMPE-1.03AC-02(01)Automated System Account ManagementSupport the management of system accounts using organization-defined automated mechanisms.ARC-AMPE-1.03
AC-02(02)-CMS-ARC-AMPE-1.03AC-02(02)Automated Temporary and Emergency Account ManagementAutomatically disable temporary and emergency accounts after no more than ninety-six (96) hours from last use.ARC-AMPE-1.03
AC-02(03)-CMS-ARC-AMPE-1.03AC-02(03)Disable AccountsDisable accounts within twenty-four (24) hours when the accounts: Have expired; Are no longer associated with a user or individual; Are in violation of organizational policy; or Have been inactive for: sixty (60) days for all non-consumer accounts, or, fifteen (15) months for ACA consumer accountsARC-AMPE-1.03
AC-02(04)-CMS-ARC-AMPE-1.03AC-02(04)Automated Audit ActionsAutomatically audit system account creation, modification, enabling, disabling, and removal actions.ARC-AMPE-1.03
AC-02(05)-CMS-ARC-AMPE-1.03AC-02(05)Inactivity LogoutRequire that users log out when the time-period of inactivity will exceed twenty-four (24) hours.ARC-AMPE-1.03
AC-02(07)-CMS-ARC-AMPE-1.03AC-02(07)Privileged User AccountsEstablish and administer privileged user accounts in accordance with a role-based access scheme; Monitor privileged role or attribute assignments; Monitor changes to roles or attributes; and Revoke access when privileged role or attribute assignments are no longer appropriate.ARC-AMPE-1.03
AC-02(09)-CMS-ARC-AMPE-1.03AC-02(09)Restrictions on Use of Shared and Groups AccountsOnly permit the use of shared and group accounts that meet the following conditions: A business need can be documented and approved, in advance, by the Authorizing Official (AO); and The applicable system security plan must: Describe how the accounts are used; and Include compensating processes and procedures implemented to provide the ability to uniquely attribute account user activities.ARC-AMPE-1.03
AC-02(12)-CMS-ARC-AMPE-1.03AC-02(12)Account Monitoring for Atypical UsageMonitor system accounts for atypical use; and Report atypical usage of system accounts to organization-defined personnel or roles, and if necessary, any applicable incident response team .ARC-AMPE-1.03
AC-02(13)-CMS-ARC-AMPE-1.03AC-02(13)Disable Accounts for High-Risk IndividualsDisable accounts of individuals within one (1) hour of discovery of individual posing as a significant risk.ARC-AMPE-1.03
AC-03-CMS-ARC-AMPE-1.03AC-03Access EnforcementEnforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.ARC-AMPE-1.03
AC-03(08)-CMS-ARC-AMPE-1.03AC-03(08)Revocation of Access AuthorizationsEnforce the revocation of access authorizations resulting from changes to the security attributes of subjects and objects based on organization-defined rules governing the timing of revocations of access authorizations.ARC-AMPE-1.03
AC-03(09)-CMS-ARC-AMPE-1.03AC-03(09)Controlled ReleaseRelease information outside of the system only if: The receiving external organization provides information security and privacy safeguards commensurate with those implemented by the organization; and Organization-defined controls are used to validate the appropriateness of the information designated for release.ARC-AMPE-1.03
AC-03(14)-CMS-ARC-AMPE-1.03AC-03(14)Individual AccessProvide organization-defined mechanisms to enable individuals to have access to the following elements of their Personally Identifiable Information (PII): PII / Protected Health Information (PHI) elements defined in applicable security/privacy plans.ARC-AMPE-1.03
AC-04-CMS-ARC-AMPE-1.03AC-04Information Flow EnforcementEnforce approved authorizations for controlling the flow of information within the system and between connected systems based on organization-defined information flow control policies.ARC-AMPE-1.03
AC-05-CMS-ARC-AMPE-1.03AC-05Separation of DutiesIdentify and document organization-defined duties of individuals requiring separation; and Define system access authorizations to support separation of duties.ARC-AMPE-1.03
AC-06-CMS-ARC-AMPE-1.03AC-06Least PrivilegeEmploy the principle of least privilege, allowing only authorized accesses for users (or processes acting on behalf of users) that are necessary to accomplish assigned organizational tasks.ARC-AMPE-1.03
AC-06(01)-CMS-ARC-AMPE-1.03AC-06(01)Authorize Access to Security FunctionsAuthorize access for organization-defined individuals or roles to: Organization-defined security functions (deployed in hardware, software, and firmware); and Organization-defined security-relevant information, including but not limited to: Setting/modifying audit logs and auditing behavior; Setting/modifying boundary protection system rules; Configuring/modifying access authorizations (i.e., permissions, privileges); Setting/modifying authentication parameters; and Setting/modifying system configurations and parameters.ARC-AMPE-1.03
AC-06(02)-CMS-ARC-AMPE-1.03AC-06(02)Non-privileged Access for Nonsecurity FunctionsRequire that users of system accounts (or roles) with access to organization-defined security functions or security-relevant information use non-privileged accounts (or roles) when accessing nonsecurity functions.ARC-AMPE-1.03
AC-06(05)-CMS-ARC-AMPE-1.03AC-06(05)Privileged AccountsThe organization restricts privileged accounts on the information system to defined organization-personnel or roles.ARC-AMPE-1.03
AC-06(07)-CMS-ARC-AMPE-1.03AC-06(07)Review of User PrivilegesReview no less often than every ninety (90) days the privileges assigned to all users with privileges to validate the need for such privileges; and Reassign or remove privileges, if necessary, to correctly reflect organizational mission and business needs.ARC-AMPE-1.03
AC-06(09)-CMS-ARC-AMPE-1.03AC-06(09)Log Use of Privileged FunctionsLog the execution of privileged functions.ARC-AMPE-1.03
AC-06(10)-CMS-ARC-AMPE-1.03AC-06(10)Prohibit Non-privileged Users from Executing Privileged FunctionsPrevent non-privileged users from executing privileged functions.ARC-AMPE-1.03
AC-07-CMS-ARC-AMPE-1.03AC-07Unsuccessful Logon AttemptsEnforce a limit of five (5) consecutive invalid logon attempts by a user during a fifteen (15) minute time period; and Automatically lock the account or node for a minimum of thirty (30) minutes or lock the account or node until released by an administrator or delay next logon prompt consistent with a delay algorithm or notify system administrator or take other action as determined by the organization when the maximum number of unsuccessful attempts is exceeded.ARC-AMPE-1.03
AC-07(02)-CMS-ARC-AMPE-1.03AC-07(02)Purge or Wipe Mobile DevicePurge or wipe information from organization-defined mobile devices based on organization-defined purging or wiping requirements and techniques after ten (10) consecutive, unsuccessful device logon attempts.ARC-AMPE-1.03
AC-08-CMS-ARC-AMPE-1.03AC-08System Use NotificationDisplay organization-defined system use notification message or banner to users before granting access to the system that provides privacy and security notices consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines and state that: Users are accessing a system that contains U.S. Government information; System usage may be monitored, recorded, and subject to audit; Unauthorized use of the system is prohibited and subject to criminal and civil penalties; and Use of the system indicates consent to monitoring and recording; Retain the notification message or banner on the screen until users acknowledge the usage conditions and take explicit actions to log on to or further access the system; and For publicly accessible systems: Display system use information organization-defined conditions before granting further access to the publicly accessible system; Display references, if any, to monitoring, recording, or auditing that are consistent with privacy accommodations for such systems that generally prohibit those activities; and Include a description of the authorized uses of the system.ARC-AMPE-1.03
AC-10-CMS-ARC-AMPE-1.03AC-10Concurrent Session ControlLimit the number of concurrent sessions for each account and/or account types to one (1) session.ARC-AMPE-1.03
AC-11-CMS-ARC-AMPE-1.03AC-11Device LockPrevent further access to the system by: initiating a device lock after fifteen (15) minutes of inactivity; requiring the user to initiate a device lock before leaving the system unattended; and, retaining the device lock until the user reestablishes access using established identification and authentication procedures.ARC-AMPE-1.03
AC-12-CMS-ARC-AMPE-1.03AC-12Session TerminationAutomatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.ARC-AMPE-1.03
AC-12(01)-CMS-ARC-AMPE-1.03AC-12(01)User-Initiated LogoutsProvide a logout capability for user-initiated communications sessions whenever authentication is used to gain access to organization-defined information resources.ARC-AMPE-1.03
AC-12(02)-CMS-ARC-AMPE-1.03AC-12(02)Termination MessageDisplay an explicit logout message to users indicating the termination of authenticated communications sessions.ARC-AMPE-1.03
AC-12(03)-CMS-ARC-AMPE-1.03AC-12(03)Timeout Warning MessageDisplay an explicit message to users indicating that the session will end in an organization-defined time until end of session.ARC-AMPE-1.03
AC-14-CMS-ARC-AMPE-1.03AC-14Permitted Actions Without Identification or AuthenticationIdentify organization-defined user actions that can be performed on the system without identification or authentication consistent with organizational mission and business functions; and Document and provide supporting rationale in the security plan for the system, user actions not requiring identification or authentication.ARC-AMPE-1.03
AC-17-CMS-ARC-AMPE-1.03AC-17Remote AccessEstablish and document usage restrictions, configuration/connection requirements, and implementation guidance for each type of remote access allowed; and Authorize each type of remote access to the system prior to allowing such connections.ARC-AMPE-1.03
AC-17(01)-CMS-ARC-AMPE-1.03AC-17(01)Monitoring and ControlEmploy automated mechanisms to monitor and control remote access methods.ARC-AMPE-1.03
AC-17(02)-CMS-ARC-AMPE-1.03AC-17(02)Protection of Confidentiality and Integrity Using EncryptionImplement cryptographic mechanisms to protect the confidentiality and integrity of remote access sessions.ARC-AMPE-1.03
AC-17(03)-CMS-ARC-AMPE-1.03AC-17(03)Managed Access Control PointsRoute remote accesses through authorized and managed network access control points.ARC-AMPE-1.03
AC-17(04)-CMS-ARC-AMPE-1.03AC-17(04)Privileged Commands and AccessAuthorize the execution of privileged commands and access to security-relevant information via remote access only in a format that provides assessable evidence and for compelling operational needs; and Document the rationale for remote access in the security plan for the system.ARC-AMPE-1.03
AC-17(09)-CMS-ARC-AMPE-1.03AC-17(09)Disconnect or Disable AccessProvide the capability to disconnect or disable remote access to the system within one (1) hour.ARC-AMPE-1.03
AC-18-CMS-ARC-AMPE-1.03AC-18Wireless AccessEstablish configuration requirements, connection requirements, and implementation guidance for each type of wireless access; and Authorize each type of wireless access to the system prior to allowing such connections.ARC-AMPE-1.03
AC-18(01)-CMS-ARC-AMPE-1.03AC-18(01)Authentication and EncryptionProtect wireless access to the system using authentication of users, devices, and encryption.ARC-AMPE-1.03
AC-18(03)-CMS-ARC-AMPE-1.03AC-18(03)Disable Wireless NetworkingDisable, when not intended for use, wireless networking capabilities embedded within system components prior to issuance and deployment.ARC-AMPE-1.03
AC-19-CMS-ARC-AMPE-1.03AC-19Access Control for Mobile DevicesEstablish configuration requirements, connection requirements, and implementation guidance for organization-controlled mobile devices, to include when such devices are outside of controlled areas; and Authorize the connection of mobile devices to organizational systems.ARC-AMPE-1.03
AC-19(05)-CMS-ARC-AMPE-1.03AC-19(05)Full Device and Container-based EncryptionEmploy full device encryption or container encryption using the latest published FIPS 140-compliant encryption standards to protect the confidentiality and integrity of information on approved mobile devices.ARC-AMPE-1.03
AC-20-CMS-ARC-AMPE-1.03AC-20Use of External SystemsEstablish organization-defined terms and conditions and identify organization-defined controls asserted to be implemented on external systems, consistent with the trust relationships established with other organizations owning, operating, and/or maintaining external systems, allowing authorized individuals to: Access the system from external systems; and Process, store, or transmit organization-controlled information using external systems; or Prohibit the use of organizationally defined types of external systems.ARC-AMPE-1.03
AC-20(01)-CMS-ARC-AMPE-1.03AC-20(01)Limits on Authorized UsePermit authorized individuals to use an external system to access the system or to process, store, or transmit organization-controlled information only after: Verification of the implementation of controls on the external system as specified in the organization’s security and privacy policies and security and privacy plans; or Retention of approved system connection or processing agreements with the organizational entity hosting the external system.ARC-AMPE-1.03
AC-20(02)-CMS-ARC-AMPE-1.03AC-20(02)Portable Storage Devices — Restricted UseRestrict the use of organization-controlled portable storage devices by authorized individuals on external systems using organization-defined restrictions.ARC-AMPE-1.03
AC-20(03)-CMS-ARC-AMPE-1.03AC-20(03)Non-organizationally Owned Systems — Restricted UseRestrict the use of non-organizationally owned systems or system components to process, store, or transmit organization information unless: The use of contractor-owned devices are: Documented within the contract and appropriate security and privacy plans; and Explicitly authorized, in writing, by the Authorizing Official (AO) or his/her designated representative; and The use of personally owned devices must comply with organizational policies and directives on use of personally-owned systems and components; and Security and privacy safeguards are employed that are appropriate for the sensitivity of the data; and Implements either full-device or virtual container encryption to reduce the vulnerability to sensitive information processed, stored, or transmitted by non-organizationally owned systems or system components (devices).ARC-AMPE-1.03
AC-21-CMS-ARC-AMPE-1.03AC-21Information SharingEnable authorized users to determine whether access authorizations assigned to a sharing partner match the information’s access and use restrictions for organization-defined information-sharing circumstances where user discretion is required; and Employ organization-defined automated mechanisms or manual processes to assist users in making information-sharing and collaboration decisions.ARC-AMPE-1.03
AC-22-CMS-ARC-AMPE-1.03AC-22Publicly Accessible ContentDesignate individuals authorized to make information publicly accessible; Train authorized individuals to ensure that publicly accessible information does not contain nonpublic information; Review the proposed content of information prior to posting onto the publicly accessible system to ensure that nonpublic information is not included; and Review the content on the publicly accessible system for nonpublic information bi-weekly (no less often than fourteen [14] days) and remove such information, if discovered.ARC-AMPE-1.03
AT-01-CMS-ARC-AMPE-1.03AT-01Policy and ProceduresDevelop, document, and disseminate to applicable personnel or roles: Organization-level awareness and training policy that: Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and Is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines; and Procedures to facilitate the implementation of the awareness and training policy and the associated awareness and training controls; Designate an organization-defined official to manage the development, documentation, and dissemination of the awareness and training policy and procedures; and Review and update the current awareness and training: Policy at least every one (1) year and following organization-defined events; and Procedures at least every one (1) year and following organization-defined events.ARC-AMPE-1.03
AT-02-CMS-ARC-AMPE-1.03AT-02Literacy Training and AwarenessProvide security and privacy literacy training to system users (including managers, senior executives, and contractors): As part of initial training for new users and within at least every one (1) year thereafter; and When required by system changes or following organization-defined events; Employ the following techniques to increase the security and privacy awareness of system users: phishing email tests and other organization-defined techniques. Update literacy training and awareness content at least once every one (1) year and following organization-defined events; and Incorporate lessons learned from internal or external security incidents or breaches into literacy training and awareness techniques.ARC-AMPE-1.03
AT-02(02)-CMS-ARC-AMPE-1.03AT-02(02)Insider ThreatProvide literacy training on recognizing and reporting potential indicators of insider threat.ARC-AMPE-1.03
AT-02(03)-CMS-ARC-AMPE-1.03AT-02(03)Social Engineering and MiningProvide literacy training on recognizing and reporting potential and actual instances of social engineering and social mining.ARC-AMPE-1.03
AT-02(04)-CMS-ARC-AMPE-1.03AT-02(04)Suspicious Communications and Anomalous System BehaviorProvide literacy training on recognizing suspicious communications and anomalous behavior in organizational systems using organization-defined indicators of malicious code.ARC-AMPE-1.03
AT-02(05)-CMS-ARC-AMPE-1.03AT-02(05)Advanced Persistent ThreatProvide literacy training on the advanced persistent threat (APT).ARC-AMPE-1.03
AT-03-CMS-ARC-AMPE-1.03AT-03Role-Based TrainingProvide role-based security and privacy training to personnel with the following significant information security and privacy roles and responsibilities: Before authorizing access to the system, information, or performing assigned duties, and at least every one (1) year thereafter; and When required by system changes; Update role-based training (RBT) content at least every one (1) year and following significant changes to the system or the system environment changes; and Incorporate lessons learned from internal or external security incidents or breaches into role-based training.ARC-AMPE-1.03
AT-03(05)-CMS-ARC-AMPE-1.03AT-03(05)Processing Personally Identifiable InformationProvide organizational-personnel (to include vendors, contractors, and employees) with initial, and at least every one (1) year thereafter, training in the employment and operation of Personally Identifiable Information (PII) processing and transparency controls.ARC-AMPE-1.03
AT-04-CMS-ARC-AMPE-1.03AT-04Training RecordsDocument and monitor information security and privacy training activities, including security and privacy awareness training and specific role-based security and privacy training; and Retain individual training records for a minimum of five (5) years after completing a specific training course.ARC-AMPE-1.03
AU-01-CMS-ARC-AMPE-1.03AU-01Policy and ProceduresDevelop, document, and disseminate to organization-defined personnel and roles: Organization-level audit and accountability policy that: Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and Is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines; and Procedures to facilitate the implementation of the audit and accountability policy and the associated audit and accountability controls; Designate an organization-defined official to manage the development, documentation, and dissemination of the audit and accountability policy and procedures; and Review and update the current audit and accountability: Policy at least every one (1) year and following organization-defined events; and Procedures at least every one (1) year and following organization-defined events.ARC-AMPE-1.03
AU-02-CMS-ARC-AMPE-1.03AU-02Event LoggingIdentify the types of events that the system is capable of logging in support of the audit function: organization-defined event types based on a risk assessment of organization defined mission/business needs; Coordinate the event logging function with other organizational entities requiring audit-related information to guide and inform the selection criteria for events to be logged; Specify the following event types for logging within the system: organization-defined event types along with organization-defined frequency or situation for each identified event type; Provide a rationale for why the event types selected for logging are deemed to be adequate to support after-the-fact investigations of incidents; and Review and update the event types selected for logging at least every one (1) year and whenever there is a significant system modification or change in the system environment.ARC-AMPE-1.03
AU-03-CMS-ARC-AMPE-1.03AU-03Content of Audit RecordsEnsure that audit records contain information that establishes the following: What type of event occurred; When the event occurred; Where the event occurred; Source of the event; Outcome of the event; and Identity of any individuals, subjects, or objects/entities associated with the event.ARC-AMPE-1.03
AU-03(01)-CMS-ARC-AMPE-1.03AU-03(01)Additional Audit InformationGenerate audit records containing the following additional information and event details explicitly needed for audit requirements: Session, connection, transaction, or activity duration; For client-server transactions, the number of bytes received and bytes sent; Additional informational messages to diagnose or identify the event; Characteristics that describe or identify the object or resource being acted upon; Individual identities of group account users; and Full-text of privileged commands.ARC-AMPE-1.03
AU-03(03)-CMS-ARC-AMPE-1.03AU-03(03)Limit Personally Identifiable Information ElementsLimit Personally Identifiable Information (PII) contained in audit records to the defined elements identified in the privacy risk assessment: system-defined elements in the Privacy Impact Assessment (PIA).ARC-AMPE-1.03
AU-04-CMS-ARC-AMPE-1.03AU-04Audit Log Storage CapacityAllocate audit log storage capacity to accommodate, at a minimum, storage capacity of ninety (90) days and any other organization-defined audit log retention requirements.ARC-AMPE-1.03
AU-05-CMS-ARC-AMPE-1.03AU-05Response to Audit Logging Processing FailuresAlert organization-defined personnel or roles within near real-time in the event of an audit logging process failure; and Take the following additional actions: - Shut down the system or halt processing immediately; or - Shut down systems that do not support automatic shutdown within one (1) hour of the audit processing failure.ARC-AMPE-1.03
AU-06-CMS-ARC-AMPE-1.03AU-06Audit Record Review, Analysis, and ReportingReview and analyze system audit records no less often than weekly (every seven [7] days) for indications of organization-defined inappropriate or unusual activity and the potential impact of the inappropriate or unusual activity; Report findings to organization-defined personnel or roles; and Adjust the level of audit record review, analysis, and reporting within the system when there is a change in risk based on law enforcement information, intelligence information, or other credible sources of information.ARC-AMPE-1.03
AU-06(01)-CMS-ARC-AMPE-1.03AU-06(01)Automated Process IntegrationIntegrate audit record review, analysis, and reporting processes using automated mechanisms to the fullest extent possible.ARC-AMPE-1.03
AU-06(03)-CMS-ARC-AMPE-1.03AU-06(03)Correlate Audit Record RepositoriesAnalyze and correlate audit records across different repositories to gain organization-wide situational awareness.ARC-AMPE-1.03
AU-07-CMS-ARC-AMPE-1.03AU-07Audit Record Reduction and Report GenerationProvide and implement an audit record reduction and report generation capability that: Supports on-demand audit record review, analysis, and reporting requirements and after-the-fact investigations of incidents; and Does not alter the original content or time ordering of audit records.ARC-AMPE-1.03
AU-07(01)-CMS-ARC-AMPE-1.03AU-07(01)Automatic ProcessingProvide and implement the capability to process, sort, and search audit records for events of interest based on the following content: organization-defined selectable event criteria and fields within audit records.ARC-AMPE-1.03
AU-08-CMS-ARC-AMPE-1.03AU-08Time StampsUse internal system clocks to generate time stamps for audit records; and Record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT) and are accurate to within one hundred (100) milliseconds.ARC-AMPE-1.03
AU-09-CMS-ARC-AMPE-1.03AU-09Protection of Audit InformationProtect audit information and audit logging tools from unauthorized access, modification, and deletion; and Alert organization-defined personnel or roles upon detection of unauthorized access, modification, or deletion of audit information.ARC-AMPE-1.03
AU-09(04)-CMS-ARC-AMPE-1.03AU-09(04)Access by Subset of Privileged UsersAuthorize access to management of audit logging functionality to only an organization-defined subset of privileged users or roles.ARC-AMPE-1.03
AU-10-CMS-ARC-AMPE-1.03AU-10Non-RepudiationProvide irrefutable evidence that an individual (or process acting on behalf of an individual) has performed organization-defined actions to be covered by non-repudiation.ARC-AMPE-1.03
AU-11-CMS-ARC-AMPE-1.03AU-11Audit Record RetentionRetain audit records for ninety (90) days and archive old records for ten (10) years consistent with records retention policy to provide support for after-the-fact investigations of incidents and to meet regulatory and organizational information retention requirements.ARC-AMPE-1.03
AU-11(01)-CMS-ARC-AMPE-1.03AU-11(01)Long-Term Retrieval CapabilityEmploy organization-defined measures to ensure that long-term audit records generated by the system can be retrieved.ARC-AMPE-1.03
AU-12-CMS-ARC-AMPE-1.03AU-12Audit Record GenerationProvide audit record generation capability for the event types the system is capable of auditing as defined in AU-2a on all systems and network components where audit capability is deployed/available; Allow organization-defined personnel or roles to select the event types that are to be logged by specific components of the system; and Generate audit records for the event types defined in AU-2c that include the audit record content defined in AU-3.ARC-AMPE-1.03
CA-01-CMS-ARC-AMPE-1.03CA-01Policies and ProceduresDevelop, document, and disseminate to organization-defined personnel and roles: Organization-level assessment, authorization, and monitoring policy that: Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and Is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines; and Procedures to facilitate the implementation of the assessment, authorization, and monitoring policy and the associated assessment, authorization, and monitoring controls; Designate an organization-defined official to manage the development, documentation, and dissemination of the assessment, authorization, and monitoring policy and procedures; and Review and update the current assessment, authorization, and monitoring: Policy at least every one (1) year and following organization-defined events; and Procedures at least every one (1) year and following organization-defined events.ARC-AMPE-1.03
CA-02-CMS-ARC-AMPE-1.03CA-02Control AssessmentsSelect the appropriate assessor or assessment team for the type of assessment to be conducted; Develop a control assessment plan that describes the scope of the assessment, including: Controls and control enhancements under assessment; Assessment procedures to be used to determine control effectiveness; and Assessment environment, assessment team, and assessment roles and responsibilities; Ensure the control assessment plan is reviewed and approved by the Authorizing Official or designated representative prior to conducting the assessment; Assess the controls in the system and its environment of operation as specified in the supplemental control requirements & guidance to determine the extent to which the controls are implemented correctly, operating as intended, and producing the desired outcome with respect to meeting established security and privacy requirements; Produce a control assessment report that documents the results of the assessment; and Provide the results of the control assessment to the Business Owner responsible for the system and personnel responsible for reviewing the assessment documentation, and updating security and privacy documentation where necessary to reflect any changes to the system within thirty (30) days after its completion in writing.ARC-AMPE-1.03
CA-02(01)-CMS-ARC-AMPE-1.03CA-02(01)Independent AssessorsEmploy independent assessors or assessment teams to conduct control assessments.ARC-AMPE-1.03
CA-03-CMS-ARC-AMPE-1.03CA-03Information ExchangeApprove and manage the exchange of information between the system and other systems using interconnection security agreements (ISA), information exchange security agreements, memoranda of understanding or agreement (MOU/MOA), service level agreements (SLA), user agreements, nondisclosure agreements (NDA), or other exchange agreements; Document, as part of each exchange agreement, the interface characteristics, security and privacy requirements, controls, and responsibilities for each system, and the impact level of the information communicated; and Review and update the agreements at least every one (1) year.ARC-AMPE-1.03
CA-05-CMS-ARC-AMPE-1.03CA-05Plan of Action and MilestonesDevelop a plan of action and milestones (POA&M) for the system to document the planned remediation actions of the organization to correct weaknesses or deficiencies noted during the assessment of the controls and to reduce or eliminate known vulnerabilities in the system; and Update existing POA&M in accordance with the frequency documented in the organization's Information Security Continuous Monitoring (ISCM) strategy based on the findings from control assessments, independent audits or reviews, and continuous monitoring activities.ARC-AMPE-1.03
CA-06-CMS-ARC-AMPE-1.03CA-06AuthorizationAssign a senior official as the Authorizing Official (AO) for the system; Assign a senior official as the AO for common controls available for inheritance by organizational systems; Ensure that, before commencing operations, the AO for the system: Accepts the use of common controls inherited by the system; and Authorizes the system to operate; Ensure that the AO for common controls authorizes the use of those controls for inheritance by organizational systems; and Update the authorizations consistent with the frequency identified in the supplemental control requirements and guidance.ARC-AMPE-1.03
CA-07-CMS-ARC-AMPE-1.03CA-07Continuous MonitoringDevelop a system-level continuous monitoring strategy and implement continuous monitoring in accordance with the organization-level continuous monitoring strategy that includes: Establishing the following system-level metrics to be monitored based on the organization security and privacy goals and in accordance with organization's Information Security Continuous Monitoring (ISCM) strategy; Establishing at least once a month scans for operating system, databases, and web applications for monitoring and no less than at least every one (1) year for assessment of control effectiveness; Ongoing control assessments in accordance with the continuous monitoring strategy; Ongoing monitoring of system and organization-defined metrics in accordance with the continuous monitoring strategy; Correlation and analysis of information generated by control assessments and monitoring; Response actions to address results of the analysis of control assessment and monitoring information; and Reporting the security and privacy status of the system to organization-defined personnel or roles at least every thirty (30) days (monthly).ARC-AMPE-1.03
CA-07(01)-CMS-ARC-AMPE-1.03CA-07(01)Independent AssessmentEmploy independent assessors or assessment teams to monitor the controls in the system on an ongoing basis.ARC-AMPE-1.03
CA-07(04)-CMS-ARC-AMPE-1.03CA-07(04)Risk MonitoringEnsure risk monitoring is an integral part of the continuous monitoring strategy that includes the following: Effectiveness monitoring; Compliance monitoring; and Change monitoring.ARC-AMPE-1.03
CA-08-CMS-ARC-AMPE-1.03CA-08Penetration TestingConduct penetration testing at least every one (1) year on organization-defined systems or system components as agreed with the penetration testers in the Rules of Engagement.ARC-AMPE-1.03
CA-08(01)-CMS-ARC-AMPE-1.03CA-08(01)Independent Penetration Testing Agent or TeamEmploy an independent penetration testing agent or team to perform penetration testing on the system or system components.ARC-AMPE-1.03
CA-09-CMS-ARC-AMPE-1.03CA-09Internal System ConnectionsAuthorize internal connections of organization-defined system components or classes of components to the system; Document, for each internal connection, the interface characteristics, security and privacy requirements, and the nature of the information communicated; Terminate internal system connections after issuance of an order by the organization's Chief Information Officer (CIO), Chief Information Security Officer (CISO), or senior privacy official and when such internal system connections no longer support the organization's missions or business functions; and Review at least every one (1) year the continued need for each internal connection.ARC-AMPE-1.03
CM-01-CMS-ARC-AMPE-1.03CM-01Policy and ProceduresDevelop, document, and disseminate to organization-defined personnel and roles: Organization-level configuration management policy that: Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and Is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines; and Procedures to facilitate the implementation of the configuration management policy and the associated configuration management procedures; Designate an organization-defined officials to manage the development, documentation, and dissemination of the configuration management policy and procedures; and Review and update the current configuration management: Policy at least every one (1) year and following organization-defined events; and Procedures at least every one (1) year and following organization-defined events.ARC-AMPE-1.03
CM-02-CMS-ARC-AMPE-1.03CM-02Baseline ConfigurationDevelop, document, and maintain under configuration control, a current baseline configuration of the system; and Review and update the baseline configuration of the system: At least every one (1) year. When required due to major system changes/upgrades, critical security patches, and/or emergency changes; and When system components are installed or upgraded.ARC-AMPE-1.03
CM-02(02)-CMS-ARC-AMPE-1.03CM-02(02)Automation Support for Accuracy and CurrencyMaintain the currency, completeness, accuracy, and availability of the baseline configuration of the system using automated mechanisms.ARC-AMPE-1.03
CM-02(03)-CMS-ARC-AMPE-1.03CM-02(03)Retention of Previous ConfigurationsRetain at least one (1) of the previous versions of baseline configurations of the system to support rollback.ARC-AMPE-1.03
CM-02(06)-CMS-ARC-AMPE-1.03CM-02(06)Development and Test EnvironmentsMaintain a baseline configuration for system development and test environments that is managed separately from the operational baseline configuration.ARC-AMPE-1.03
CM-02(07)-CMS-ARC-AMPE-1.03CM-02(07)Configure Systems and Components for High-Risk AreasIssue systems, system components, or devices to individuals traveling to locations that the organization deems to be of significant risk; and Apply the following controls to the systems or components when the individuals return from travel: organization-defined security safeguards to systems, system components, or devices.ARC-AMPE-1.03
CM-03-CMS-ARC-AMPE-1.03CM-03Configuration Change ControlDetermine and document the types of changes to the system that are configuration-controlled; Review proposed configuration-controlled changes to the system and approve or disapprove such changes with explicit consideration for security and privacy impact analyses; Document configuration change decisions associated with the system; Implement approved configuration-controlled changes to the system; Retain records of configuration-controlled changes to the system for no less than one (1) year after the change; Monitor and review activities associated with configuration-controlled changes to the system; and Coordinate and provide oversight for configuration change control activities through (1) change request forms that must be approved by an organizational configuration change control board that convenes sufficiently frequently to accommodate proposed change requests, and (2) requirements of other appropriate organization officials when configuration change control activities occur.ARC-AMPE-1.03
CM-03(02)-CMS-ARC-AMPE-1.03CM-03(02)Testing, Validation, and Documentation of ChangesTest, validate, and document changes to the system before finalizing the implementation of the changes.ARC-AMPE-1.03
CM-03(04)-CMS-ARC-AMPE-1.03CM-03(04)Security and Privacy RepresentativesRequire security and privacy representatives to be members of the organizational configuration change control board.ARC-AMPE-1.03
CM-04-CMS-ARC-AMPE-1.03CM-04Impact AnalysesAnalyze changes to the system to determine potential security and privacy impacts prior to change implementation.ARC-AMPE-1.03
CM-04(01)-CMS-ARC-AMPE-1.03CM-04(01)Separate Test EnvironmentsAnalyze changes to the system in a separate test environment before implementation in an operational environment. Focus on security and privacy impacts due to flaws, weaknesses, incompatibility, or intentional malice.ARC-AMPE-1.03
CM-04(02)-CMS-ARC-AMPE-1.03CM-04(02)Verification of ControlsAfter system changes, verify that the impacted controls are implemented correctly, operating as intended, and producing the desired outcome with regard to meeting the security and privacy requirements for the system.ARC-AMPE-1.03
CM-05-CMS-ARC-AMPE-1.03CM-05Access Restrictions for ChangeDefine, document, approve, and enforce physical and logical access restrictions associated with changes to the system.ARC-AMPE-1.03
CM-05(01)-CMS-ARC-AMPE-1.03CM-05(01)Automated Access Enforcement and Audit RecordsEnforce access restrictions using automated mechanisms to the fullest extent possible; and Automatically generate audit records of the enforcement actions.ARC-AMPE-1.03
CM-05(05)-CMS-ARC-AMPE-1.03CM-05(05)Privilege Limitation for Production and OperationLimit privileges to change system components and system-related information within a production or operational environment; and Review and reevaluate privileges at least quarterly.ARC-AMPE-1.03
CM-06-CMS-ARC-AMPE-1.03CM-06Configuration SettingsEstablish and document configuration settings for components employed within the system that reflect the most restrictive mode consistent with operational requirements using the most current security configuration guidelines listed in the Supplemental Control Requirements & Guidance; Implement the configuration settings; Identify, document, and approve any deviations from established configuration settings for all configurable system components based on explicit operational requirements; and Monitor and control changes to the configuration settings in accordance with organizational policies and procedures.ARC-AMPE-1.03
CM-06(01)-CMS-ARC-AMPE-1.03CM-06(01)Automated Management, Application, and VerificationManage, apply, and verify configuration settings for Information Technology products and organization-defined system components using automated mechanisms.ARC-AMPE-1.03
CM-07-CMS-ARC-AMPE-1.03CM-07Least FunctionalityConfigure the system to provide only essential capabilities; and Prohibit or restrict the use of the following functions, ports protocols, software, and/or services: high-risk system services, functions, ports, network protocols, and capabilities across network boundaries that are not explicitly required for system or application functionality or are identified to be unnecessary and/or nonsecure.ARC-AMPE-1.03
CM-07(01)-CMS-ARC-AMPE-1.03CM-07(01)Periodic ReviewReview the system upon encountering a significant risk, as incidents occur, major system/software updates, or at least every one (1) year, to identify unnecessary and/or nonsecure functions, ports, protocols, software, and services; and Disable or remove functions, ports, protocols, software, and services within the system deemed to be unnecessary and/or nonsecure.ARC-AMPE-1.03
CM-07(02)-CMS-ARC-AMPE-1.03CM-07(02)Prevent Program ExecutionPrevent program execution in accordance with organizational-defined policies, rules of behavior, and rules authorizing the terms and conditions of software program usage.ARC-AMPE-1.03
CM-07(05)-CMS-ARC-AMPE-1.03CM-07(05)Authorized Software - Allow by ExceptionIdentify software programs authorized to execute on the system; Employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs on the system; and Review and update the list of authorized software programs at least quarterly or when there is a change.ARC-AMPE-1.03
CM-07(09)-CMS-ARC-AMPE-1.03CM-07(09)Prohibiting the Use of Unauthorized HardwareIdentify hardware components authorized for system use; Prohibit the use or connection of unauthorized hardware components; and Review and update the list of authorized hardware components at least every one (1) year or when there is a change.ARC-AMPE-1.03
CM-08-CMS-ARC-AMPE-1.03CM-08System Component InventoryDevelop and document an inventory of system components that: Accurately reflects the system; Includes all components within the system; Does not include duplicate accounting of components or components assigned to any other system; Is at the level of granularity deemed necessary for tracking and reporting; and Includes the following information to achieve proper system component accountability: - Each component's unique identifier and/or serial number; - Type of information system component (e.g., server, desktop, and application); - Manufacturer/model information; - Operating system type and version/service pack level; - Presence of virtual machines; - Application software version/license information; - Physical location (e.g., building/room number); - Logical location (e.g., Internet Protocol [IP] address, position with the information system [IS]); - Media access control (MAC) address; - System/component owner; - Operational status; and - Information system/component administrators. Review and update the system component inventory at least every six (6) months.ARC-AMPE-1.03
CM-08(01)-CMS-ARC-AMPE-1.03CM-08(01)Updates During Installation and RemovalUpdate the inventory of system components as part of component installations, removals, and system updates.ARC-AMPE-1.03
CM-08(03)-CMS-ARC-AMPE-1.03CM-08(03)Automated Unauthorized Component DetectionDetect the presence of unauthorized hardware, software, and firmware components within the system using automated mechanisms continuously, using automated mechanisms with a maximum five (5) minute delay in detection; and Take the following actions when unauthorized components and/or provisioned configurations are detected: - Disable network access by such components; - Isolate the component; and - Notify responsible personnel or role.ARC-AMPE-1.03
CM-09-CMS-ARC-AMPE-1.03CM-09Configuration Management PlanDevelop, document, and implement a configuration management plan for the system that: Addresses roles, responsibilities, and configuration management processes and procedures; Establishes a process for identifying configuration items throughout the system development life cycle and for managing the configuration of the configuration items; Defines the configuration items for the system and places the configuration items under configuration management; Is reviewed and approved by organization-defined personnel or roles (e.g., Business Owner and System Owner); and Protects the configuration management plan from unauthorized disclosure and modification.ARC-AMPE-1.03
CM-10-CMS-ARC-AMPE-1.03CM-10Software Usage RestrictionsUse software and associated documentation in accordance with contract agreements and copyright laws; Track the use of software and associated documentation protected by quantity licenses to control copying and distribution; and Control and document the use of 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.ARC-AMPE-1.03
CM-11-CMS-ARC-AMPE-1.03CM-11User-Installed SoftwareEstablish organization-defined policies governing the installation of software by users; Enforce software installation policies through the organization-defined applicable System Security and Privacy Plan (SSPP); and Monitor policy compliance continuously.ARC-AMPE-1.03
CM-12-CMS-ARC-AMPE-1.03CM-12Information LocationIdentify and document the location of organization-defined information and the specific system components on which the information is processed and stored; Identify and document the users who have access to the system and system components where the information is processed and stored; and Document changes to the location (i.e., system or system components) where the information is processed and stored.ARC-AMPE-1.03

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .