code
stringlengths 4
16
| description
stringlengths 7
4k
|
|---|---|
PS-CS-3 | "Identified vulnerabilities are tracked and remediated in accordance with the assigned risk ranking and as defined by SLAs in the Standard." |
PS-CS-4 | "A minimum of two-factor authentication is required at Tier 1 facility area entrances." |
PS-CS-4 | "ACS tracks and responds to physical access events by date, location and time of event." |
PS-CS-5 | "All physical access entitlements are requested, approved, and provisioned in accordance with the Standards." |
PS-CS-5 | "The Company supervisors request physical access based on work need and location." |
PS-CS-5 | "All physical access badge holders are in [INSERT TOOL]." |
PS-CS-6 | "General Area Access (GAA) reviews are performed as part of the entitlement review [INSERT TIME FRAME] by the badge holder's manager or sponsor." |
PS-CS-6 | "Internally Secure Area (ISA) reviews are performed [INSERT TIME FRAME] by the designated ISA area owner or sponsor." |
PS-CS-6 | "Physical access reviews are performed in accordance with the Access Management Team Review Process." |
PS-CS-7 | "All physical access entitlements are deprovisioned in accordance with the Standards." |
PS-CS-8 | "Visitor logs are retained per The Company Records Retention Schedule." |
PS-CS-8 | "All Users who do not possess The Company issued badge, and are seeking entrance to The Company facility, complete the visitor registration process and obtain a visitor ID badge which is displayed prominently at all times." |
PS-CS-8 | "At locations where no visitor reception area exists, a designated staff member(s) manages the visitor sign-in process." |
PS-CS-9 | "Video surveillance is placed at perimeter access points, including entrances, exits, and loading docks." |
PS-CS-9 | "Video surveillance is placed inside or outside the facility as long as the door is in view and permits view of the access point." |
PS-CS-9 | "Video recordings are stored on-site in a secure location." |
PS-CS-9 | "Video recordings will be retained for a minimum of [INSERT TIME FRAME] for Tier 2-4 facilities and [INSERT TIME FRAME] for Tier 1 facilities." |
PM-CS-1 | "The Company shall have a Patch Management Group (PMG) that includes persons with appropriate experience and qualifications, and is responsible for:" |
PM-CS-1 | "The Company shall appoint a Patch Supervisor who is responsible for overseeing the PMG. The Patch Supervisor shall report to the CTO and have appropriate experience and qualifications." |
PM-CS-2 | "The Company shall have a Patch Management Group (PMG) that includes persons with appropriate experience and qualifications, and is responsible for:" |
PM-CS-3 | "The PMG shall perform a biannual internal assessment of its management and implementation of security updates and patches. This assessment shall identify all known vulnerabilities to The Company technology assets and the security updates or security patches applied to address each vulnerability. The assessment shall be formally identified, documented, and reviewed by the PMG, Senior Technology, and Senior Security Leadership." |
PM-CS-4 | "Technology Owners must identify, assess, and document available patches for each assigned technology. Documentation for each patch should include:" |
PM-CS-4 | "The Company shall use the IT asset inventory to assist in identifying assets for purposes of applying security updates/patches." |
PM-CS-4 | "Patches are assigned Patch Severity Ratings based on the Initial Severity Rating (ISR), Asset Inherent Risk Rating (IRR), and other risk measures" |
PM-CS-4 | "Modification of patch severity ratings must be approved by the [INSERT TEAM OR NAME]" |
PM-CS-4 | "Where the severity rating of a patch that is applicable to externally-facing applications is reduced from the vendor or in the NVD supplied rating, or if the Alliance Owner requests a modification to the severity rating, the following information is documented within [INSERT TIME FRAME] of modifying the rating:" |
PM-CS-4 | "Site Reliability Engineers coordinate patch activities between infrastructure and application teams." |
PM-CS-4 | "Asset Owners must onboard all assets to use the automated mechanisms prescribed for identification and assessment of software patches. Where automated mechanisms do not exist, Asset Owners must subscribe to vendor patch notification services, document all available patches, and track the installation of the patch." |
PM-CS-5 | "Patches must be remediated according to the Patch Remediation Timeline provided in the following table:" |
PM-CS-5 | "Application and System Owners must document a deployment plan that addresses patch coordination, scheduling, testing, verification, and rollback." |
PM-CS-5 | "Patch deployments must be approved in accordance with the requirements of the [INSERT POLICY NAME] Policy and Standards prior to implementation." |
PM-CS-5 | "Application and System Owners must initiate and deploy patches in accordance with the Patch Remediation Timeframe requirements." |
PM-CS-5 | "The Company shall appoint Patch Champions for each Alliance. Patch Champions are responsible for:" |
PM-CS-5 | "Site Reliability Engineers coordinate patch activities between infrastructure and application teams." |
PM-CS-5 | "Patch deployment is prioritized, initiated, completed, and documented per patch remediation timeframe requirements." |
PM-CS-6 | "Application and System Owners must update The Company change management system once a patch has been installed and verified, or rescheduled due to patch failure. Required documentation tasks include:" |
PM-CS-6 | "For each security update or security patch rated as critical, The Company shall maintain records (Critical Patch Management Records") identifying:"" |
PM-CS-6 | "Critical Patch Management Records shall be reviewed [INSERT TIME FRAME] by the PMG." |
PM-CS-6 | "The PMG must ensure that security patches are tracked and reported throughout the patch lifecycle. Reporting must include:" |
PM-CS-6 | "The PMG must have a dashboard or otherwise report on the success, failure, or other status of any security update or security patch including listing of outstanding and applied available patches." |
PM-CS-6 | "The Company shall have the capability to generate a listing of each security update and security patch applied or installed during the [INSERT TIME FRAME] period for each asset in the Asset Inventory." |
PM-CS-6 | "The Company shall appoint Patch Champions for each Alliance. Patch Champions are responsible for:" |
PM-CS-7 | "Process Owners shall ensure standard images or baseline build configurations are updated to include available vendor-supplied patches in accordance with the patch severity identified in alignment with security recommendations." |
PM-CS-7 | "Standard images and baseline build configurations used in The Company's FedRAMP boundaries are reviewed and updated: a) at least [INSERT TIME FRAME] b) as a part of system component installations and upgrades (e.g. patch deployment, configuration change) In addition, for The Company systems deployed in its FedRAMP boundaries, The Company will evaluate and as appropriate, incorporate FedRAMP Program Management Office directives in its baselines." |
PM-CS-8 | "The Company must have a patch management solution or solutions that are used to automate patch distribution to assets wherever technically feasible. Patch management solutions must:" |
PM-CS-8 | "Application Owners must use an approved patch management solution and document the solution used for each asset." |
PM-CS-8 | "The PMG shall report on compliance with the use of approved patch management tools." |
PM-CS-8 | "Asset Owners must onboard all assets to use the automated mechanisms prescribed for identification and assessment of software patches. Where automated mechanisms do not exist, Asset Owners must subscribe to vendor patch notification services, document all available patches, and track the installation of the patch." |
PM-CS-9 | "Application and System Owners must test software patches, including firmware updates, in non-production environments and verify that there are no adverse effects before they are deployed to production environments." |
PM-CS-9 | "Application and System Owners must verify that patches are successfully deployed." |
PM-CS-9 | "The Company shall appoint Patch Champions for each Alliance. Patch Champions are responsible for:" |
PM-CS-9 | "The Company shall define a Technology Owner for software and applications used in the environment." |
PP-CS-1 | "The Company develops, documents, and maintains an information security strategy. The information security strategy is reviewed and refreshed [INSERT TIME FRAME] and communicated to senior executives." |
PP-CS-10 | "The Company develops, documents, and deploys a formal Information Security budget, Privacy budget, and technology budget." |
PP-CS-2 | "The Company develops, documents, and deploys a formal Information Security budget, Privacy budget, and technology budget." |
PP-CS-3 | "The Company documents, implements and communicates a System Development Life Cycle (SDLC) which incorporates privacy requirements, security requirements, security tools, and security activities in phases of system development." |
PP-CS-3 | "For The Company systems deployed in its FedRAMP boundaries, controls are in place: - To prevent unauthorized and unintended information transfer via shared system resources, - To prohibit remote activation of collaborative computing devices - To separate execution domains for each executing process" |
PP-CS-3 | "For The Company systems deployed in its FedRAMP boundaries, The Company establishes restrictions on the use of open source software." |
PP-CS-3 | "For The Company systems deployed in its FedRAMP boundaries, The Company generates error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries. Error messages are revealed only to users of the System." |
PP-CS-3 | "For The Company systems deployed in its FedRAMP boundaries, an information security architecture is established, maintained, and updated on a periodic basis. The information security architecture: - Describes the overall philosophy, requirements, and approach to be taken with regard to protecting the confidentiality, integrity, and availability of organizational information; - Describes how the information security architecture is integrated into and supports the enterprise architecture; and - Describes any information security assumptions about, and dependencies on, external services; - Reviews and updates the information security architecture at least annually or when a significant change occurs to reflect updates in the enterprise architecture; and - Ensures that planned information security architecture changes are reflected in the system security plan" |
PP-CS-4 | "The Company defines the roles and responsibilities for development, information security, and change management." |
PP-CS-5 | "The Company documents, implements and communicates a System Development Life Cycle (SDLC) which incorporates privacy requirements, security requirements, security tools, and security activities in phases of system development." |
PP-CS-5 | "For The Company systems deployed in its FedRAMP boundaries, software and firmware components are digitally signed using an approved certificate and verification occurs prior to component installation to production. If digital signatures/certificates are unavailable, alternative cryptographic integrity checks (hashes, self-signed certs, etc.) can be utilized to perform the verification." |
PP-CS-6 | "The following security controls are implemented in any environment." |
PP-CS-6 | "In addition to security controls in PP-TR-600, the following security controls are implemented in non-production environment:" |
PP-CS-6 | "In addition to security controls in PP-TR-600, the following security controls are implemented in production environment" |
PP-CS-6 | "The Company does not use production data in non-production environments. Production data can be used in UAT (User Acceptance Test) environment provided UAT environment is configured and operated as Production and business justification is documented, reviewed, and approved." |
PP-CS-7 | "The Company logically separates non-production environments from the production environment." |
PP-CS-8 | "The Company documents, implements and communicates a System Development Life Cycle (SDLC) which incorporates privacy requirements, security requirements, security tools, and security activities in phases of system development." |
PP-CS-8 | "For The Company systems deployed in its FedRAMP boundaries, The Company builds data flow diagrams for applications which include interface characteristics, security requirements, and nature of the information communicated. Data flow diagrams are reviewed and updated at least [INSERT TIME FRAME] and upon significant change." |
PP-CS-9 | "The Company develops, documents, and maintains an Privacy strategy. The Privacy strategy is reviewed and refreshed [INSERT TIME FRAME] and communicated to senior executives." |
RM-CS-1 | "Organizational risk target/goals is presented to the Board of Directors on at least an annual basis, or as significant changes to the company's risk exposure occur." |
RM-CS-1 | "The Board of Directors, or relevant committee thereof, reviews and approves the Organizational risk target/goals on at least an [INSERT TIME FRAME] basis." |
RM-CS-2 | "The Board of Directors, or relevant committee thereof, reviews and approves the Core Security Risk Assessment on at least an [INSERT TIME FRAME] basis." |
RM-CS-3 | "The Enterprise Security Risk Assessment includes an assessment of internal and external risks to the security, confidentiality, or integrity of personal information that could result in unauthorized disclosure, misuse, loss, alteration, destruction, or other compromise." |
RM-CS-3 | "The Enterprise Security Risk Assessment is maintained by the Chief Information Security Officer or his or her designee." |
RM-CS-4 | "The SVP, Security Risk reviews and approves the Enterprise Threat Vector Assessment on at least an [INSERT TIME FRAME] basis, or as significant changes to the assessment are made." |
RM-CS-4 | "The Enterprise Threat Vector Assessment includes an analysis of enterprise threat vectors which are both internal and external to The Company." |
RM-CS-5 | "Asset risk assessment lifecycle steps are risk identification, analysis, evaluation, and treatment." |
RM-CS-5 | "The Inherent Risk Rating (IRR), Control Assessment Rating (CAR), and Residual Risk Rating (RRR) for technology assets is defined in the Asset Criticality Risk Methodology." |
RM-CS-6 | "The criteria used to calculate the IRR and prioritize technology assets is based on the asset's data classification, data volume, data availability, and whether the asset is internet-facing." |
RM-CS-7 | "Security Risk Assessments (SRAs) are performed for applicable applications and platforms as defined in the Asset Security Risk Methodology." |
RM-CS-7 | "Based on the results of the Control Self-Assessment (CSA) process and the technology asset's Inherent Risk Rating (IRR), the Residual Risk Rating (RRR) is calculated. " |
RM-CS-8 | "The Company identifies and communicates risk(s) to the issues management team in accordance with the Issues and Deviations process." |
RM-CS-9 | "The Company designs, implements, maintains, and documents safeguards that mitigate the material internal and external risks The Company identifies to the security, confidentiality, or integrity of personal information." |
RM-CS-9 | "The Company's security controls are designed to reduce the risk to personal information based on the volume, sensitivity, and likelihood, given the existence of other safeguards, that the risk could be realized and result in the unauthorized access, collection, use, alteration, destruction, or disclosure of the personal information." |
ST-CS-1 | "The Company security awareness curriculum is developed and updated based on current threats, industry best practices, and significant information system changes." |
ST-CS-1 | "Information Spillage or Unauthorized Access Notification UAN" is included within Security Training."" |
ST-CS-1 | "The Company documents and monitors individual information system security training activities including basic security awareness training and specific information system security training; and retains individual training records in accordance to The Company Records Retention Policy." |
ST-CS-1 | "The prescribed timeline for remedial and disciplinary actions for non-complete New Hire Security Training is outlined in the Mandatory Training policy. Remedial actions pursuant to this policy include but is not limited to:" |
ST-CS-2 | "The Company security awareness curriculum is developed and updated based on current threats, industry best practices, and significant information system changes." |
ST-CS-2 | "The prescribed timeline for remedial and disciplinary actions for non-complete New Hire Security Training is outlined in the Mandatory Training policy. Remedial actions pursuant to this policy include but is not limited to:" |
ST-CS-2 | "Information Spillage or Unauthorized Access Notification UAN" is included within Security Training."" |
ST-CS-2 | "The Company documents and monitors individual information system security training activities including basic security awareness training and specific information system security training; and retains individual training records in accordance to The Company Records Retention Policy." |
ST-CS-3 | "The Company security awareness curriculum is developed and updated based on current threats, industry best practices, and significant information system changes." |
ST-CS-3 | "The prescribed timeline for remedial and disciplinary actions for non-complete New Hire Security Training is outlined in the Mandatory Training policy. Remedial actions pursuant to this policy include but is not limited to:" |
ST-CS-3 | "Information Spillage or Unauthorized Access Notification UAN" is included within Security Training."" |
ST-CS-3 | "In the event of an information system change to the FedRAMP boundary that triggers a Security Training content update, for example, the creation or significant update of Information Security policies or technologies, The Company will provide remedial Security Training to all employees and contractors. " |
ST-CS-3 | "The prescribed timeline for remedial and disciplinary actions for non-complete Annual Refresher Security Training is outlined in the Mandatory Training policy. Remedial actions pursuant to this policy include but is not limited to:" |
ST-CS-3 | "The Company documents and monitors individual information system security training activities including basic security awareness training and specific information system security training; and retains individual training records in accordance to The Company Records Retention Policy." |