csa-ccm 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 2f015ba679cc1669e74b71615b94a3b12b5a4984bea3ff34c7eb0c72c188f2d8
+  data.tar.gz: c7c87ae9c35b0cf5f9c90d292004f2ab21fa741cc21db7fcf7aeb1ed5ae5a5c8
+SHA512:
+  metadata.gz: 7d6f1ced0dabe541e671ecf7af29c9312fcde4015371be06b6f703fe8c25b56506e2dada0b513665199c118afccfa592937d11793af63cc1d280b5501548a985
+  data.tar.gz: 1f037e41b049059fc5435daf90cf746b27f6e80e565065e9f31c9d82ff440a380d554868a0c5ae3c4a664a6aa3b2e25764d6c3767c46710e8c4de12d3b963888

data/3.0.1.yaml

@@ -0,0 +1,1517 @@
+---
+ccm:
+  metadata:
+    version: 3.0.1
+    title: CONSENSUS ASSESSMENTS INITIATIVE QUESTIONNAIRE v3.0.1
+    source-file: csa-caiq-v3.0.1-12-05-2016.xlsx
+  control-domains:
+  - id: AIS
+    name: Application & Interface Security
+    controls:
+    - id: AIS-01
+      name: Application Security
+      specification: Applications and programming interfaces (APIs) shall be designed, developed, deployed, and tested in accordance with leading industry standards (e.g., OWASP for web applications) and adhere to applicable legal, statutory, or regulatory compliance obligations.
+      questions:
+      - id: AIS-01.1
+        content: Do you use industry standards (Build Security in Maturity Model [BSIMM] benchmarks, Open Group ACS Trusted Technology Provider Framework, NIST, etc.) to build in security for your Systems/Software Development Lifecycle (SDLC)?
+      - id: AIS-01.2
+        content: Do you use an automated source code analysis tool to detect security defects in code prior to production?
+      - id: AIS-01.3
+        content: Do you use manual source-code analysis to detect security defects in code prior to production?
+      - id: AIS-01.4
+        content: Do you verify that all of your software suppliers adhere to industry standards for Systems/Software Development Lifecycle (SDLC) security?
+      - id: AIS-01.5
+        content: "(SaaS only) Do you review your applications for security vulnerabilities and address any issues prior to deployment to production?"
+    - id: AIS-02
+      name: Customer Access Requirements
+      specification: 'Prior to granting customers access to data, assets, and information systems, identified security, contractual, and regulatory requirements for customer access shall be addressed. '
+      questions:
+      - id: AIS-02.1
+        content: Are all identified security, contractual, and regulatory requirements for customer access contractually addressed and remediated prior to granting customers access to data, assets, and information systems?
+      - id: AIS- 02.2
+        content: Are all requirements and trust levels for customers’ access defined and documented?
+    - id: AIS-03
+      name: Data Integrity
+      specification: Data input and output integrity routines (i.e., reconciliation and edit checks) shall be implemented for application interfaces and databases to prevent manual or systematic processing errors, corruption of data, or misuse.
+      questions:
+      - id: AIS-03.1
+        content: Are data input and output integrity routines (i.e., reconciliation and edit checks) implemented for application interfaces and databases to prevent manual or systematic processing errors or corruption of data?
+    - id: AIS-04
+      name: Data Security / Integrity
+      specification: Policies and procedures shall be established and maintained in support of data security to include (confidentiality, integrity, and availability) across multiple system interfaces, jurisdictions, and business functions to prevent improper disclosure, alternation, or destruction.
+      questions:
+      - id: AIS-04.1
+        content: Is your Data Security Architecture designed using an industry standard (e.g., CDSA, MULITSAFE, CSA Trusted Cloud Architectural Standard, FedRAMP, CAESARS)?
+  - id: AAC
+    name: Audit Assurance & Compliance
+    controls:
+    - id: AAC-01
+      name: Audit Planning
+      specification: Audit plans shall be developed and maintained to address business process disruptions. Auditing plans shall focus on reviewing the effectiveness of the implementation of security operations. All audit activities must be agreed upon prior to executing any audits.
+      questions:
+      - id: AAC-01.1
+        content: Do you produce audit assertions using a structured, industry accepted format (e.g., CloudAudit/A6 URI Ontology, CloudTrust, SCAP/CYBEX, GRC XML, ISACA's Cloud Computing Management Audit/Assurance Program, etc.)?
+    - id: AAC-02
+      name: Independent Audits
+      specification: Independent reviews and assessments shall be performed at least annually to ensure that the organization addresses nonconformities of established policies, standards, procedures, and compliance obligations.
+      questions:
+      - id: AAC-02.1
+        content: Do you allow tenants to view your SOC2/ISO 27001 or similar third-party audit or certification reports?
+    - id: AAC-03
+      name: Information System Regulatory Mapping
+      specification: Organizations shall create and maintain a control framework which captures standards, regulatory, legal, and statutory requirements relevant for their business needs. The control framework shall be reviewed at least annually to ensure changes that could affect the business processes are reflected.
+      questions:
+      - id: AAC-03.1
+        content: Do you have the ability to logically segment or encrypt customer data such that data may be produced for a single tenant only, without inadvertently accessing another tenant's data?
+  - id: CO
+    name: Audit Assurance & Compliance
+    controls:
+    - id: CO-02
+      name: Independent Audits
+      specification: Independent reviews and assessments shall be performed at least annually to ensure that the organization addresses nonconformities of established policies, standards, procedures, and compliance obligations.
+      questions:
+      - id: AAC-02.2
+        content: Do you conduct network penetration tests of your cloud service infrastructure regularly as prescribed by industry best practices and guidance?
+      - id: AAC-02.3
+        content: Do you conduct application penetration tests of your cloud infrastructure regularly as prescribed by industry best practices and guidance?
+      - id: AAC-02.4
+        content: Do you conduct internal audits regularly as prescribed by industry best practices and guidance?
+      - id: AAC-02.5
+        content: Do you conduct external audits regularly as prescribed by industry best practices and guidance?
+      - id: AAC-02.6
+        content: Are the results of the penetration tests available to tenants at their request?
+      - id: AAC-02.7
+        content: Are the results of internal and external audits available to tenants at their request?
+      - id: AAC-02.8
+        content: Do you have an internal audit program that allows for cross-functional audit of assessments?
+    - id: CO-05
+      name: Information System Regulatory Mapping
+      specification: Organizations shall create and maintain a control framework which captures standards, regulatory, legal, and statutory requirements relevant for their business needs. The control framework shall be reviewed at least annually to ensure changes that could affect the business processes are reflected.
+      questions:
+      - id: AAC-03.2
+        content: Do you have the capability to recover data for a specific customer in the case of a failure or data loss?
+      - id: AAC-03.3
+        content: Do you have the capability to restrict the storage of customer data to specific countries or geographic locations?
+      - id: AAC-03.4
+        content: Do you have a program in place that includes the ability to monitor changes to the regulatory requirements in relevant jurisdictions, adjust your security program for changes to legal requirements, and ensure compliance with relevant regulatory requirements?
+  - id: BCR
+    name: Business Continuity Management & Operational Resilience
+    controls:
+    - id: BCR-01
+      name: Business Continuity Planning
+      specification: |-
+        A consistent unified framework for business continuity planning and plan development shall be established, documented, and adopted to ensure all business continuity plans are consistent in addressing priorities for testing, maintenance, and information security requirements. Requirements for business continuity plans include the following:
+         • Defined purpose and scope, aligned with relevant dependencies
+         • Accessible to and understood by those who will use them
+         • Owned by a named person(s) who is responsible for their review, update, and approval
+         • Defined lines of communication, roles, and responsibilities
+         • Detailed recovery procedures, manual work-around, and reference information
+         • Method for plan invocation
+      questions:
+      - id: BCR-01.1
+        content: Do you provide tenants with geographically resilient hosting options?
+    - id: BCR-02
+      name: Business Continuity Testing
+      specification: Business continuity and security incident response plans shall be subject to testing at planned intervals or upon significant organizational or environmental changes. Incident response plans shall involve impacted customers (tenant) and other business relationships that represent critical intra-supply chain business process dependencies.
+      questions:
+      - id: BCR-02.1
+        content: Are business continuity plans subject to testing at planned intervals or upon significant organizational or environmental changes to ensure continuing effectiveness?
+    - id: BCR-03
+      name: Power / Telecommunications
+      specification: Data center utilities services and environmental conditions (e.g., water, power, temperature and humidity controls, telecommunications, and internet connectivity) shall be secured, monitored, maintained, and tested for continual effectiveness at planned intervals to ensure protection from unauthorized interception or damage, and designed with automated fail-over or other redundancies in the event of planned or unplanned disruptions.
+      questions:
+      - id: BCR-03.1
+        content: Do you provide tenants with documentation showing the transport route of their data between your systems?
+    - id: BCR-04
+      name: Documentation
+      specification: |-
+        Information system documentation (e.g., administrator and user guides, and architecture diagrams) shall be made available to authorized personnel to ensure the following:
+         • Configuring, installing, and operating the information system
+         • Effectively using the system’s security features
+      questions:
+      - id: BCR-04.1
+        content: Are information system documents (e.g., administrator and user guides, architecture diagrams, etc.) made available to authorized personnel to ensure configuration, installation and operation of the information system?
+    - id: BCR-05
+      name: Environmental Risks
+      specification: Physical protection against damage from natural causes and disasters, as well as deliberate attacks, including fire, flood, atmospheric electrical discharge, solar induced geomagnetic storm, wind, earthquake, tsunami, explosion, nuclear accident, volcanic activity, biological hazard, civil unrest, mudslide, tectonic activity, and other forms of natural or man-made disaster shall be anticipated, designed, and have countermeasures applied.
+      questions:
+      - id: BCR-05.1
+        content: Is physical protection against damage (e.g., natural causes, natural disasters, deliberate attacks) anticipated and designed with countermeasures applied?
+    - id: BCR-06
+      name: Equipment Location
+      specification: To reduce the risks from environmental threats, hazards, and opportunities for unauthorized access, equipment shall be kept away from locations subject to high probability environmental risks and supplemented by redundant equipment located at a reasonable distance.
+      questions:
+      - id: BCR-06.1
+        content: Are any of your data centers located in places that have a high probability/occurrence of high-impact environmental risks (floods, tornadoes, earthquakes, hurricanes, etc.)?
+    - id: BCR-07
+      name: Equipment Maintenance
+      specification: Policies and procedures shall be established, and supporting business processes and technical measures implemented, for equipment maintenance ensuring continuity and availability of operations and support personnel.
+      questions:
+      - id: BCR-07.1
+        content: If using virtual infrastructure, does your cloud solution include independent hardware restore and recovery capabilities?
+    - id: BCR-08
+      name: Equipment Power Failures
+      specification: Protection measures shall be put into place to react to natural and man-made threats based upon a geographically-specific business impact assessment.
+      questions:
+      - id: BCR-08.1
+        content: Are security mechanisms and redundancies implemented to protect equipment from utility service outages (e.g., power failures, network disruptions, etc.)?
+    - id: BCR-09
+      name: Impact Analysis
+      specification: |-
+        There shall be a defined and documented method for determining the impact of any disruption to the organization (cloud provider, cloud consumer) that must incorporate the following:
+         • Identify critical products and services
+         • Identify all dependencies, including processes, applications, business partners, and third party service providers
+         • Understand threats to critical products and services
+         • Determine impacts resulting from planned or unplanned disruptions and how these vary over time
+         • Establish the maximum tolerable period for disruption
+         • Establish priorities for recovery
+         • Establish recovery time objectives for resumption of critical products and services within their maximum tolerable period of disruption
+         • Estimate the resources required for resumption
+      questions:
+      - id: BCR-09.1
+        content: Do you provide tenants with ongoing visibility and reporting of your operational Service Level Agreement (SLA) performance?
+    - id: BCR-10
+      name: Policy
+      specification: Policies and procedures shall be established, and supporting business processes and technical measures implemented, for appropriate IT governance and service management to ensure appropriate planning, delivery and support of the organization's IT capabilities supporting business functions, workforce, and/or customers based on industry acceptable standards (i.e., ITIL v4 and COBIT 5). Additionally, policies and procedures shall include defined roles and responsibilities supported by regular workforce training.
+      questions:
+      - id: BCR-10.1
+        content: Are policies and procedures established and made available for all personnel to adequately support services operations’ roles?
+    - id: BCR-11
+      name: Retention Policy
+      specification: Policies and procedures shall be established, and supporting business processes and technical measures implemented, for defining and adhering to the retention period of any critical asset as per established policies and procedures, as well as applicable legal, statutory, or regulatory compliance obligations. Backup and recovery measures shall be incorporated as part of business continuity planning and tested accordingly for effectiveness.
+      questions:
+      - id: BCR-11.1
+        content: Do you have technical control capabilities to enforce tenant data retention policies?
+  - id: RS
+    name: Business Continuity Management & Operational Resilience
+    controls:
+    - id: RS-03
+      name: Business Continuity Planning
+      specification: |-
+        A consistent unified framework for business continuity planning and plan development shall be established, documented, and adopted to ensure all business continuity plans are consistent in addressing priorities for testing, maintenance, and information security requirements. Requirements for business continuity plans include the following:
+         • Defined purpose and scope, aligned with relevant dependencies
+         • Accessible to and understood by those who will use them
+         • Owned by a named person(s) who is responsible for their review, update, and approval
+         • Defined lines of communication, roles, and responsibilities
+         • Detailed recovery procedures, manual work-around, and reference information
+         • Method for plan invocation
+      questions:
+      - id: BCR-01.2
+        content: Do you provide tenants with infrastructure service failover capability to other providers?
+    - id: RS-08
+      name: Power / Telecommunications
+      specification: Data center utilities services and environmental conditions (e.g., water, power, temperature and humidity controls, telecommunications, and internet connectivity) shall be secured, monitored, maintained, and tested for continual effectiveness at planned intervals to ensure protection from unauthorized interception or damage, and designed with automated fail-over or other redundancies in the event of planned or unplanned disruptions.
+      questions:
+      - id: BCR-03.2
+        content: Can tenants define how their data is transported and through which legal jurisdictions?
+    - id: RS-02
+      name: Impact Analysis
+      specification: |-
+        There shall be a defined and documented method for determining the impact of any disruption to the organization (cloud provider, cloud consumer) that must incorporate the following:
+         • Identify critical products and services
+         • Identify all dependencies, including processes, applications, business partners, and third party service providers
+         • Understand threats to critical products and services
+         • Determine impacts resulting from planned or unplanned disruptions and how these vary over time
+         • Establish the maximum tolerable period for disruption
+         • Establish priorities for recovery
+         • Establish recovery time objectives for resumption of critical products and services within their maximum tolerable period of disruption
+         • Estimate the resources required for resumption
+      questions:
+      - id: BCR-09.2
+        content: Do you make standards-based information security metrics (CSA, CAMM, etc.) available to your tenants?
+      - id: BCR-09.3
+        content: Do you provide customers with ongoing visibility and reporting of your SLA performance?
+  - id: OP
+    name: Business Continuity Management & Operational Resilience
+    controls:
+    - id: OP-04
+      name: Equipment Maintenance
+      specification: Policies and procedures shall be established, and supporting business processes and technical measures implemented, for equipment maintenance ensuring continuity and availability of operations and support personnel.
+      questions:
+      - id: BCR-07.2
+        content: If using virtual infrastructure, do you provide tenants with a capability to restore a Virtual Machine to a previous state in time?
+      - id: BCR-07.3
+        content: If using virtual infrastructure, do you allow virtual machine images to be downloaded and ported to a new cloud provider?
+      - id: BCR-07.4
+        content: If using virtual infrastructure, are machine images made available to the customer in a way that would allow the customer to replicate those images in their own off-site storage location?
+      - id: BCR-07.5
+        content: Does your cloud solution include software/provider independent restore and recovery capabilities?
+    - id: OP-03
+      name: Capacity / Resource Planning
+      specification: The availability, quality, and adequate capacity and resources shall be planned, prepared, and measured to deliver the required system performance in accordance with legal, statutory, and regulatory compliance obligations. Projections of future capacity requirements shall be made to mitigate the risk of system overload.
+      questions:
+      - id: IVS-04.2
+        content: Do you restrict use of the memory oversubscription capabilities present in the hypervisor?
+      - id: IVS-04.3
+        content: Do your system capacity requirements take into account current, projected, and anticipated capacity needs for all systems used to provide services to the tenants?
+      - id: IVS-04.4
+        content: Is system performance monitored and tuned in order to continuously meet regulatory, contractual, and business requirements for all the systems used to provide services to the tenants?
+  - id: DG
+    name: Business Continuity Management & Operational Resilience
+    controls:
+    - id: DG-04
+      name: Retention Policy
+      specification: Policies and procedures shall be established, and supporting business processes and technical measures implemented, for defining and adhering to the retention period of any critical asset as per established policies and procedures, as well as applicable legal, statutory, or regulatory compliance obligations. Backup and recovery measures shall be incorporated as part of business continuity planning and tested accordingly for effectiveness.
+      questions:
+      - id: BCR-11.2
+        content: Do you have a documented procedure for responding to requests for tenant data from governments or third parties?
+      - id: BCR-11.4
+        content: Have you implemented backup or redundancy mechanisms to ensure compliance with regulatory, statutory, contractual or business requirements?
+      - id: BCR-11.5
+        content: Do you test your backup or redundancy mechanisms at least annually?
+    - id: DG-02
+      name: Classification
+      specification: Data and objects containing data shall be assigned a classification by the data owner based on data type, value, sensitivity, and criticality to the organization.
+      questions:
+      - id: DSI-01.2
+        content: Do you provide a capability to identify hardware via policy tags/metadata/hardware tags (e.g., TXT/TPM, VN-Tag, etc.)?
+      - id: DSI-01.3
+        content: Do you have a capability to use system geographic location as an authentication factor?
+      - id: DSI-01.4
+        content: Can you provide the physical location/geography of storage of a tenant’s data upon request?
+      - id: DSI-01.5
+        content: Can you provide the physical location/geography of storage of a tenant's data in advance?
+      - id: DSI-01.6
+        content: Do you follow a structured data-labeling standard (e.g., ISO 15489, Oasis XML Catalog Specification, CSA data type guidance)?
+      - id: DSI-01.7
+        content: Do you allow tenants to define acceptable geographical locations for data routing or resource instantiation?
+    - id: DG-03
+      name: Handling / Labeling / Security Policy
+      specification: Policies and procedures shall be established for labeling, handling, and the security of data and objects which contain data. Mechanisms for label inheritance shall be implemented for objects that act as aggregate containers for data.
+      questions:
+      - id: DSI-04.2
+        content: Are mechanisms for label inheritance implemented for objects that act as aggregate containers for data?
+    - id: DG-05
+      name: Secure Disposal
+      specification: Policies and procedures shall be established with supporting business processes and technical measures implemented for the secure disposal and complete removal of data from all storage media, ensuring data is not recoverable by any computer forensic means.
+      questions:
+      - id: DSI-07.2
+        content: Can you provide a published procedure for exiting the service arrangement, including assurance to sanitize all computing resources of tenant data once a customer has exited your environment or has vacated a resource?
+  - id: CCC
+    name: Change Control & Configuration Management
+    controls:
+    - id: CCC-01
+      name: New Development / Acquisition
+      specification: Policies and procedures shall be established, and supporting business processes and technical measures implemented, to ensure the development and/or acquisition of new data, physical or virtual applications, infrastructure network and systems components, or any corporate, operations and/or data center facilities have been pre-authorized by the organization's business leadership or other accountable business role or function.
+      questions:
+      - id: CCC-01.1
+        content: Are policies and procedures established for management authorization for development or acquisition of new applications, systems, databases, infrastructure, services, operations and facilities?
+      - id: CCC-01.2
+        content: Is documentation available that describes the installation, configuration, and use of products/services/features?
+    - id: CCC-02
+      name: Outsourced Development
+      specification: External business partners shall adhere to the same policies and procedures for change management, release, and testing as internal developers within the organization (e.g., ITIL service management processes).
+      questions:
+      - id: CCC-02.1
+        content: Do you have controls in place to ensure that standards of quality are being met for all software development?
+    - id: CCC-03
+      name: Quality Testing
+      specification: Organizations shall follow a defined quality change control and testing process (e.g., ITIL Service Management) with established baselines, testing, and release standards which focus on system availability, confidentiality, and integrity of systems and services.
+      questions:
+      - id: CCC-03.1
+        content: Do you provide your tenants with documentation that describes your quality assurance process?
+      - id: CCC-03.2
+        content: Is documentation describing known issues with certain products/services available?
+      - id: CCC-03.3
+        content: Are there policies and procedures in place to triage and remedy reported bugs and security vulnerabilities for product and service offerings?
+      - id: CCC-03.4
+        content: Are mechanisms in place to ensure that all debugging and test code elements are removed from released software versions?
+    - id: CCC-04
+      name: Unauthorized Software Installations
+      specification: Policies and procedures shall be established, and supporting business processes and technical measures implemented, to restrict the installation of unauthorized software on organizationally-owned or managed user end-point devices (e.g., issued workstations, laptops, and mobile devices) and IT infrastructure network and systems components.
+      questions:
+      - id: CCC-04.1
+        content: Do you have controls in place to restrict and monitor the installation of unauthorized software onto your systems?
+    - id: CCC-05
+      name: Production Changes
+      specification: |-
+        Policies and procedures shall be established for managing the risks associated with applying changes to:
+         • Business-critical or customer (tenant)-impacting (physical and virtual) applications and system-system interface (API) designs and configurations.
+         • Infrastructure network and systems components.
+        Technical measures shall be implemented to provide assurance that all changes directly correspond to a registered change request, business-critical or customer (tenant), and/or authorization by, the customer (tenant) as per agreement (SLA) prior to deployment.
+      questions:
+      - id: CCC-05.1
+        content: Do you provide tenants with documentation that describes your production change management procedures and their roles/rights/responsibilities within it?
+  - id: RM
+    name: Change Control & Configuration Management
+    controls:
+    - id: RM-04
+      name: Outsourced Development
+      specification: External business partners shall adhere to the same policies and procedures for change management, release, and testing as internal developers within the organization (e.g., ITIL service management processes).
+      questions:
+      - id: CCC-02.2
+        content: Do you have controls in place to detect source code security defects for any outsourced software development activities?
+  - id: DSI
+    name: Data Security & Information Lifecycle Management
+    controls:
+    - id: DSI-01
+      name: Classification
+      specification: Data and objects containing data shall be assigned a classification by the data owner based on data type, value, sensitivity, and criticality to the organization.
+      questions:
+      - id: DSI-01.1
+        content: Do you provide a capability to identify virtual machines via policy tags/metadata (e.g., tags can be used to limit guest operating systems from booting/instantiating/transporting data in the wrong country)?
+    - id: DSI-02
+      name: Data Inventory / Flows
+      specification: Policies and procedures shall be established, and supporting business processes and technical measures implemented, to inventory, document, and maintain data flows for data that is resident (permanently or temporarily) within the service's geographically distributed (physical and virtual) applications and infrastructure network and systems components and/or shared with other third parties to ascertain any regulatory, statutory, or supply chain agreement (SLA) compliance impact, and to address any other business risks associated with the data. Upon request, provider shall inform customer (tenant) of compliance impact and risk, especially if customer data is used as part of the services.
+      questions:
+      - id: DSI-02.1
+        content: Do you inventory, document, and maintain data flows for data that is resident (permanent or temporary) within the services' applications and infrastructure network and systems?
+      - id: DSI-02.2
+        content: Can you ensure that data does not migrate beyond a defined geographical residency?
+    - id: DSI-03
+      name: E-commerce Transactions
+      specification: Data related to electronic commerce (e-commerce) that traverses public networks shall be appropriately classified and protected from fraudulent activity, unauthorized disclosure, or modification in such a manner to prevent contract dispute and compromise of data.
+      questions:
+      - id: DSI-03.1
+        content: Do you provide open encryption methodologies (3.4ES, AES, etc.) to tenants in order for them to protect their data if it is required to move through public networks (e.g., the Internet)?
+    - id: DSI-04
+      name: Handling / Labeling / Security Policy
+      specification: Policies and procedures shall be established for labeling, handling, and the security of data and objects which contain data. Mechanisms for label inheritance shall be implemented for objects that act as aggregate containers for data.
+      questions:
+      - id: DSI-04.1
+        content: Are policies and procedures established for labeling, handling and the security of data and objects that contain data?
+    - id: DSI-05
+      name: Nonproduction Data
+      specification: Production data shall not be replicated or used in non-production environments. Any use of customer data in non-production environments requires explicit, documented approval from all customers whose data is affected, and must comply with all legal and regulatory requirements for scrubbing of sensitive data elements.
+      questions:
+      - id: DSI-05.1
+        content: Do you have procedures in place to ensure production data shall not be replicated or used in non-production environments?
+    - id: DSI-06
+      name: Ownership / Stewardship
+      specification: All data shall be designated with stewardship, with assigned responsibilities defined, documented, and communicated.
+      questions:
+      - id: DSI-06.1
+        content: Are the responsibilities regarding data stewardship defined, assigned, documented, and communicated?
+    - id: DSI-07
+      name: Secure Disposal
+      specification: Policies and procedures shall be established with supporting business processes and technical measures implemented for the secure disposal and complete removal of data from all storage media, ensuring data is not recoverable by any computer forensic means.
+      questions:
+      - id: DSI-07.1
+        content: Do you support secure deletion (e.g., degaussing/cryptographic wiping) of archived and backed-up data as determined by the tenant?
+  - id: IS
+    name: Data Security & Information Lifecycle Management
+    controls:
+    - id: IS-28
+      name: E-commerce Transactions
+      specification: Data related to electronic commerce (e-commerce) that traverses public networks shall be appropriately classified and protected from fraudulent activity, unauthorized disclosure, or modification in such a manner to prevent contract dispute and compromise of data.
+      questions:
+      - id: DSI-03.2
+        content: Do you utilize open encryption methodologies any time your infrastructure components need to communicate with each other via public networks (e.g., Internet-based replication of data from one environment to another)?
+    - id: IS-19
+      name: Key Generation
+      specification: Policies and procedures shall be established for the management of cryptographic keys in the service's cryptosystem (e.g., lifecycle management from key generation to revocation and replacement, public key infrastructure, cryptographic protocol design and algorithms used, access controls in place for secure key generation, and exchange and storage including segregation of keys used for encrypted data or sessions). Upon request, provider shall inform the customer (tenant) of changes within the cryptosystem, especially if the customer (tenant) data is used as part of the service, and/or the customer (tenant) has some shared responsibility over implementation of the control.
+      questions:
+      - id: EKM-02.2
+        content: Do you have a capability to manage encryption keys on behalf of tenants?
+      - id: EKM-02.3
+        content: Do you maintain key management procedures?
+      - id: EKM-02.4
+        content: Do you have documented ownership for each stage of the lifecycle of encryption keys?
+      - id: EKM-02.5
+        content: Do you utilize any third party/open source/proprietary frameworks to manage encryption keys?
+    - id: IS-18
+      name: Encryption
+      specification: Policies and procedures shall be established, and supporting business processes and technical measures implemented, for the use of encryption protocols for protection of sensitive data in storage (e.g., file servers, databases, and end-user workstations) and data in transmission (e.g., system interfaces, over public networks, and electronic messaging) as per applicable legal, statutory, and regulatory compliance obligations.
+      questions:
+      - id: EKM-03.2
+        content: Do you leverage encryption to protect data and virtual machine images during transport across and between networks and hypervisor instances?
+      - id: EKM-03.3
+        content: Do you support tenant-generated encryption keys or permit tenants to encrypt data to an identity without access to a public key certificate (e.g., identity-based encryption)?
+      - id: EKM-03.4
+        content: Do you have documentation establishing and defining your encryption management policies, procedures, and guidelines?
+    - id: IS-04
+      name: Baseline Requirements
+      specification: Baseline security requirements shall be established for developed or acquired, organizationally-owned or managed, physical or virtual, applications and infrastructure system, and network components that comply with applicable legal, statutory, and regulatory compliance obligations. Deviations from standard baseline configurations must be authorized following change management policies and procedures prior to deployment, provisioning, or use. Compliance with security baseline requirements must be reassessed at least annually unless an alternate frequency has been established and authorized based on business needs.
+      questions:
+      - id: GRM-01.2
+        content: Do you have the capability to continuously monitor and report the compliance of your infrastructure against your information security baselines?
+      - id: GRM-01.3
+        content: Do you allow your clients to provide their own trusted virtual machine image to ensure conformance to their own internal standards?
+    - id: IS-06
+      name: Policy Enforcement
+      specification: A formal disciplinary or sanction policy shall be established for employees who have violated security policies and procedures. Employees shall be made aware of what action might be taken in the event of a violation, and disciplinary measures must be stated in the policies and procedures.
+      questions:
+      - id: GRM-07.2
+        content: Are employees made aware of what actions could be taken in the event of a violation via their policies and procedures?
+    - id: IS-27
+      name: Asset Returns
+      specification: Upon termination of workforce personnel and/or expiration of external business relationships, all organizationally-owned assets shall be returned within an established period.
+      questions:
+      - id: HRS-01.2
+        content: Is your Privacy Policy aligned with industry standards?
+    - id: IS-26
+      name: Acceptable Use
+      specification: Policies and procedures shall be established, and supporting business processes and technical measures implemented, for defining allowances and conditions for permitting usage of organizationally-owned or managed user end-point devices (e.g., issued workstations, laptops, and mobile devices) and IT infrastructure network and systems components. Additionally, defining allowances and conditions to permit usage of personal mobile devices and associated applications with access to corporate resources (i.e., BYOD) shall be considered and incorporated as appropriate.
+      questions:
+      - id: HRS-08.2
+        content: Do you collect or create metadata about tenant data usage through inspection technologies (e.g., search engines, etc.)?
+      - id: HRS-08.3
+        content: Do you allow tenants to opt out of having their data/metadata accessed via inspection technologies?
+    - id: IS-11
+      name: Training / Awareness
+      specification: A security awareness training program shall be established for all contractors, third-party users, and employees of the organization and mandated when appropriate. All individuals with access to organizational data shall receive appropriate awareness training and regular updates in organizational procedures, processes, and policies relating to their professional function relative to the organization.
+      questions:
+      - id: HRS-09.2
+        content: Are administrators and data stewards properly educated on their legal responsibilities with regard to security and data integrity?
+    - id: IS-16
+      name: User Responsibility
+      specification: |-
+        All personnel shall be made aware of their roles and responsibilities for:
+         • Maintaining awareness and compliance with established policies and procedures and applicable legal, statutory, or regulatory compliance obligations.
+         • Maintaining a safe and secure working environment
+      questions:
+      - id: HRS-10.2
+        content: Are users made aware of their responsibilities for maintaining a safe and secure working environment?
+      - id: HRS-10.3
+        content: Are users made aware of their responsibilities for leaving unattended equipment in a secure manner?
+      - id: HRS-11.2
+        content: Do your data management policies and procedures include a tamper audit or software integrity function for unauthorized access to tenant data?
+      - id: HRS-11.3
+        content: Does the virtual machine management infrastructure include a tamper audit or software integrity function to detect changes to the build/configuration of the virtual machine?
+    - id: IS-07
+      name: User Access Policy
+      specification: |-
+        User access policies and procedures shall be established, and supporting business processes and technical measures implemented, for ensuring appropriate identity, entitlement, and access management for all internal corporate and customer (tenant) users with access to data and organizationally-owned or managed (physical and virtual) application interfaces and infrastructure network and systems components. These policies, procedures, processes, and measures must incorporate the following:
+         • Procedures, supporting roles, and responsibilities for provisioning and de-provisioning user account entitlements following the rule of least privilege based on job function (e.g., internal employee and contingent staff personnel changes, customer-controlled access, suppliers' business relationships, or other third-party business relationships)
+         • Business case considerations for higher levels of assurance and multi-factor authentication secrets (e.g., management interfaces, key generation, remote access, segregation of duties, emergency access, large-scale provisioning or geographically-distributed deployments, and personnel redundancy for critical systems)
+         • Access segmentation to sessions and data in multi-tenant architectures by any third party (e.g., provider and/or other customer (tenant))
+         • Identity trust verification and service-to-service application (API) and information processing interoperability (e.g., SSO and federation)
+         • Account credential lifecycle management from instantiation through revocation
+         • Account credential and/or identity store minimization or re-use when feasible
+         • Authentication, authorization, and accounting (AAA) rules for access to data and sessions (e.g., encryption and strong/multi-factor, expireable, non-shared authentication secrets)
+         • Permissions and supporting capabilities for customer (tenant) controls over authentication, authorization, and accounting (AAA) rules for access to data and sessions
+         • Adherence to applicable legal, statutory, or regulatory compliance requirements
+      questions:
+      - id: IAM-02.2
+        content: Do you provide metrics to track the speed with which you are able to remove systems access that is no longer required for business purposes?
+    - id: IS-33
+      name: Source Code Access Restriction
+      specification: Access to the organization's own developed applications, program, or object source code, or any other form of intellectual property (IP), and use of proprietary software shall be appropriately restricted following the rule of least privilege based on job function as per established user access policies and procedures.
+      questions:
+      - id: IAM-06.2
+        content: Are controls in place to prevent unauthorized access to tenant application, program, or object source code, and assure it is restricted to authorized personnel only?
+    - id: IS-08
+      name: User Access Restriction / Authorization
+      specification: Policies and procedures are established for permissible storage and access of identities used for authentication to ensure identities are only accessible based on rules of least privilege and replication limitation only to users explicitly defined as business necessary.
+      questions:
+      - id: IAM-08.2
+        content: Do you have a method of aligning provider and tenant data classification methodologies for access control purposes?
+    - id: IS-10
+      name: User Access Reviews
+      specification: User access shall be authorized and revalidated for entitlement appropriateness, at planned intervals, by the organization's business leadership or other accountable business role or function supported by evidence to demonstrate the organization is adhering to the rule of least privilege based on job function. For identified access violations, remediation must follow established user access policies and procedures.
+      questions:
+      - id: IAM-10.2
+        content: If users are found to have inappropriate entitlements, are all remediation and certification actions recorded?
+      - id: IAM-10.3
+        content: Will you share user entitlement remediation and certification reports with your tenants, if inappropriate access may have been allowed to tenant data?
+    - id: IS-09
+      name: User Access Revocation
+      specification: Timely de-provisioning (revocation or modification) of user access to data and organizationally-owned or managed (physical and virtual) applications, infrastructure systems, and network components, shall be implemented as per established policies and procedures and based on user's change in status (e.g., termination of employment or other business relationship, job change, or transfer). Upon request, provider shall inform customer (tenant) of these changes, especially if customer (tenant) data is used as part the service and/or customer (tenant) has some shared responsibility over implementation of control.
+      questions:
+      - id: IAM-11.2
+        content: Is any change in user access status intended to include termination of employment, contract or agreement, change of employment or transfer within the organization?
+    - id: IS-34
+      name: Utility Programs Access
+      specification: Utility programs capable of potentially overriding system, object, network, virtual machine, and application controls shall be restricted.
+      questions:
+      - id: IAM-13.2
+        content: Do you have the capability to detect attacks that target the virtual infrastructure directly (e.g., shimming, Blue Pill, Hyper jumping, etc.)?
+      - id: IAM-13.3
+        content: Are attacks that target the virtual infrastructure prevented with technical controls?
+    - id: IS-22
+      name: Incident Management
+      specification: Policies and procedures shall be established, and supporting business processes and technical measures implemented, to triage security-related events and ensure timely and thorough incident management, as per established IT service management policies and procedures.
+      questions:
+      - id: SEF-02.2
+        content: Do you integrate customized tenant requirements into your security incident response plans?
+      - id: SEF-02.3
+        content: Do you publish a roles and responsibilities document specifying what you vs. your tenants are responsible for during security incidents?
+      - id: SEF-02.4
+        content: Have you tested your security incident response plans in the last year?
+    - id: IS-23
+      name: Incident Reporting
+      specification: Workforce personnel and external business relationships shall be informed of their responsibility and, if required, shall consent and/or contractually agree to report all information security events in a timely manner. Information security events shall be reported through predefined communications channels in a timely manner adhering to applicable legal, statutory, or regulatory compliance obligations.
+      questions:
+      - id: SEF-03.2
+        content: Does your logging and monitoring framework allow isolation of an incident to specific tenants?
+    - id: IS-24
+      name: Incident Response Legal Preparation
+      specification: Proper forensic procedures, including chain of custody, are required for the presentation of evidence to support potential legal action subject to the relevant jurisdiction after an information security incident. Upon notification, customers and/or other external business partners impacted by a security breach shall be given the opportunity to participate as is legally permissible in the forensic investigation.
+      questions:
+      - id: SEF-04.2
+        content: Does your incident response capability include the use of legally admissible forensic data collection and analysis techniques?
+      - id: SEF-04.3
+        content: Are you capable of supporting litigation holds (freeze of data from a specific point in time) for a specific tenant without freezing other tenant data?
+      - id: SEF-04.4
+        content: Do you enforce and attest to tenant data separation when producing data in response to legal subpoenas?
+    - id: IS-25
+      name: Incident Response Metrics
+      specification: Mechanisms shall be put in place to monitor and quantify the types, volumes, and costs of information security incidents.
+      questions:
+      - id: SEF-05.2
+        content: Will you share statistical information for security incident data with your tenants upon request?
+    - id: IS-31
+      name: Network / Infrastructure Services
+      specification: Business-critical or customer (tenant) impacting (physical and virtual) application and system-system interface (API) designs and configurations, and infrastructure network and systems components, shall be designed, developed, and deployed in accordance with mutually agreed-upon service and capacity-level expectations, as well as IT governance and service management policies and procedures.
+      questions:
+      - id: STA-03.2
+        content: Do you provide tenants with capacity planning and use reports?
+    - id: IS-21
+      name: Antivirus / Malicious Software
+      specification: Policies and procedures shall be established, and supporting business processes and technical measures implemented, to prevent the execution of malware on organizationally-owned or managed user end-point devices (i.e., issued workstations, laptops, and mobile devices) and IT infrastructure network and systems components.
+      questions:
+      - id: TVM-01.2
+        content: Do you ensure that security threat detection systems using signatures, lists, or behavioral patterns are updated across all infrastructure components within industry accepted time frames?
+    - id: IS-20
+      name: Vulnerability / Patch Management
+      specification: Policies and procedures shall be established, and supporting processes and technical measures implemented, for timely detection of vulnerabilities within organizationally-owned or managed applications, infrastructure network and system components (e.g., network vulnerability assessment, penetration testing) to ensure the efficiency of implemented security controls. A risk-based model for prioritizing remediation of identified vulnerabilities shall be used. Changes shall be managed through a change management process for all vendor-supplied patches, configuration changes, or changes to the organization's internally developed software. Upon request, the provider informs customer (tenant) of policies and procedures and identified weaknesses especially if customer (tenant) data is used as part the service and/or customer (tenant) has some shared responsibility over implementation of control.
+      questions:
+      - id: TVM-02.2
+        content: Do you conduct application-layer vulnerability scans regularly as prescribed by industry best practices?
+      - id: TVM-02.3
+        content: Do you conduct local operating system-layer vulnerability scans regularly as prescribed by industry best practices?
+      - id: TVM-02.4
+        content: Will you make the results of vulnerability scans available to tenants at their request?
+      - id: TVM-02.5
+        content: Do you have a capability to rapidly patch vulnerabilities across all of your computing devices, applications, and systems?
+      - id: TVM-02.6
+        content: Will you provide your risk-based systems patching time frames to your tenants upon request?
+  - id: DCS
+    name: Datacenter Security
+    controls:
+    - id: DCS-01
+      name: Asset Management
+      specification: Assets must be classified in terms of business criticality, service-level expectations, and operational continuity requirements. A complete inventory of business-critical assets located at all sites and/or geographical locations and their usage over time shall be maintained and updated regularly, and assigned ownership by defined roles and responsibilities.
+      questions:
+      - id: DCS-01.1
+        content: Do you maintain a complete inventory of all of your critical assets that includes ownership of the asset?
+    - id: DCS-02
+      name: Controlled Access Points
+      specification: Physical security perimeters (e.g., fences, walls, barriers, guards, gates, electronic surveillance, physical authentication mechanisms, reception desks, and security patrols) shall be implemented to safeguard sensitive data and information systems.
+      questions:
+      - id: DCS-02.1
+        content: Are physical security perimeters (e.g., fences, walls, barriers, guards, gates, electronic surveillance, physical authentication mechanisms, reception desks, and security patrols) implemented?
+    - id: DCS-03
+      name: Equipment Identification
+      specification: Automated equipment identification shall be used as a method of connection authentication. Location-aware technologies may be used to validate connection authentication integrity based on known equipment location.
+      questions:
+      - id: DCS-03.1
+        content: Is automated equipment identification used as a method to validate connection authentication integrity based on known equipment location?
+    - id: DCS-04
+      name: Offsite Authorization
+      specification: Authorization must be obtained prior to relocation or transfer of hardware, software, or data to an offsite premises.
+      questions:
+      - id: DCS-04.1
+        content: Do you provide tenants with documentation that describes scenarios in which data may be moved from one physical location to another (e.g., offsite backups, business continuity failovers, replication)?
+    - id: DCS-05
+      name: Offsite Equipment
+      specification: Policies and procedures shall be established for the secure disposal of equipment (by asset type) used outside the organization's premise. This shall include a wiping solution or destruction process that renders recovery of information impossible. The erasure shall consist of a full write of the drive to ensure that the erased drive is released to inventory for reuse and deployment or securely stored until it can be destroyed.
+      questions:
+      - id: DCS-05.1
+        content: Can you provide tenants with evidence documenting your policies and procedures governing asset management and repurposing of equipment?
+    - id: DCS-06
+      name: Policy
+      specification: Policies and procedures shall be established, and supporting business processes implemented, for maintaining a safe and secure working environment in offices, rooms, facilities, and secure areas storing sensitive information.
+      questions:
+      - id: DCS-06.1
+        content: Can you provide evidence that policies, standards, and procedures have been established for maintaining a safe and secure working environment in offices, rooms, facilities, and secure areas?
+      - id: DCS-06.2
+        content: Can you provide evidence that your personnel and involved third parties have been trained regarding your documented policies, standards, and procedures?
+    - id: DCS-07
+      name: Secure Area Authorization
+      specification: Ingress and egress to secure areas shall be constrained and monitored by physical access control mechanisms to ensure that only authorized personnel are allowed access.
+      questions:
+      - id: DCS-07.1
+        content: Do you allow tenants to specify which of your geographic locations their data is allowed to move into/out of (to address legal jurisdictional considerations based on where data is stored vs. accessed)?
+    - id: DCS-08
+      name: Unauthorized Persons Entry
+      specification: Ingress and egress points such as service areas and other points where unauthorized personnel may enter the premises shall be monitored, controlled and, if possible, isolated from data storage and processing facilities to prevent unauthorized data corruption, compromise, and loss.
+      questions:
+      - id: DCS-08.1
+        content: Are ingress and egress points, such as service areas and other points where unauthorized personnel may enter the premises, monitored, controlled and isolated from data storage and process?
+    - id: DCS-09
+      name: User Access
+      specification: Physical access to information assets and functions by users and support personnel shall be restricted.
+      questions:
+      - id: DCS-09.1
+        content: Do you restrict physical access to information assets and functions by users and support personnel?
+  - id: FS
+    name: Datacenter Security
+    controls:
+    - id: FS-08
+      name: Asset Management
+      specification: Assets must be classified in terms of business criticality, service-level expectations, and operational continuity requirements. A complete inventory of business-critical assets located at all sites and/or geographical locations and their usage over time shall be maintained and updated regularly, and assigned ownership by defined roles and responsibilities.
+      questions:
+      - id: DCS-01.2
+        content: Do you maintain a complete inventory of all of your critical supplier relationships?
+  - id: EKM
+    name: Encryption & Key Management
+    controls:
+    - id: EKM-01
+      name: Entitlement
+      specification: Keys must have identifiable owners (binding keys to identities) and there shall be key management policies.
+      questions:
+      - id: EKM-01.1
+        content: Do you have key management policies binding keys to identifiable owners?
+    - id: EKM-02
+      name: Key Generation
+      specification: Policies and procedures shall be established for the management of cryptographic keys in the service's cryptosystem (e.g., lifecycle management from key generation to revocation and replacement, public key infrastructure, cryptographic protocol design and algorithms used, access controls in place for secure key generation, and exchange and storage including segregation of keys used for encrypted data or sessions). Upon request, provider shall inform the customer (tenant) of changes within the cryptosystem, especially if the customer (tenant) data is used as part of the service, and/or the customer (tenant) has some shared responsibility over implementation of the control.
+      questions:
+      - id: EKM-02.1
+        content: Do you have a capability to allow creation of unique encryption keys per tenant?
+    - id: EKM-03
+      name: Encryption
+      specification: Policies and procedures shall be established, and supporting business processes and technical measures implemented, for the use of encryption protocols for protection of sensitive data in storage (e.g., file servers, databases, and end-user workstations) and data in transmission (e.g., system interfaces, over public networks, and electronic messaging) as per applicable legal, statutory, and regulatory compliance obligations.
+      questions:
+      - id: EKM-03.1
+        content: Do you encrypt tenant data at rest (on disk/storage) within your environment?
+    - id: EKM-04
+      name: Storage and Access
+      specification: Platform and data appropriate encryption (e.g., AES-256) in open/validated formats and standard algorithms shall be required. Keys shall not be stored in the cloud (i.e. at the cloud provider in question), but maintained by the cloud consumer or trusted key management provider. Key management and key usage shall be separated duties.
+      questions:
+      - id: EKM-04.1
+        content: Do you have platform and data appropriate encryption that uses open/validated formats and standard algorithms?
+      - id: EKM-04.2
+        content: Are your encryption keys maintained by the cloud consumer or a trusted key management provider?
+      - id: EKM-04.3
+        content: Do you store encryption keys in the cloud?
+      - id: EKM-04.4
+        content: Do you have separate key management and key usage duties?
+  - id: GRM
+    name: Governance and Risk Management
+    controls:
+    - id: GRM-01
+      name: Baseline Requirements
+      specification: Baseline security requirements shall be established for developed or acquired, organizationally-owned or managed, physical or virtual, applications and infrastructure system, and network components that comply with applicable legal, statutory, and regulatory compliance obligations. Deviations from standard baseline configurations must be authorized following change management policies and procedures prior to deployment, provisioning, or use. Compliance with security baseline requirements must be reassessed at least annually unless an alternate frequency has been established and authorized based on business needs.
+      questions:
+      - id: GRM-01.1
+        content: Do you have documented information security baselines for every component of your infrastructure (e.g., hypervisors, operating systems, routers, DNS servers, etc.)?
+    - id: GRM-02
+      name: Risk Assessments
+      specification: |-
+        Risk assessments associated with data governance requirements shall be conducted at planned intervals and shall consider the following:
+         • Awareness of where sensitive data is stored and transmitted across applications, databases, servers, and network infrastructure
+         • Compliance with defined retention periods and end-of-life disposal requirements
+         • Data classification and protection from unauthorized use, access, loss, destruction, and falsification
+      questions:
+      - id: GRM-02.1
+        content: Do you provide security control health data in order to allow tenants to implement industry standard Continuous Monitoring (which allows continual tenant validation of your physical and logical control status)?
+      - id: GRM-02.2
+        content: Do you conduct risk assessments associated with data governance requirements at least once a year?
+    - id: GRM-03
+      name: Management Oversight
+      specification: Managers are responsible for maintaining awareness of, and complying with, security policies, procedures, and standards that are relevant to their area of responsibility.
+      questions:
+      - id: GRM-03.1
+        content: Are your technical, business, and executive managers responsible for maintaining awareness of and compliance with security policies, procedures, and standards for both themselves and their employees as they pertain to the manager and employees' area of responsibility?
+    - id: GRM-04
+      name: Management Program
+      specification: |-
+        An Information Security Management Program (ISMP) shall be developed, documented, approved, and implemented that includes administrative, technical, and physical safeguards to protect assets and data from loss, misuse, unauthorized access, disclosure, alteration, and destruction. The security program shall include, but not be limited to, the following areas insofar as they relate to the characteristics of the business:
+         • Risk management
+         • Security policy
+         • Organization of information security
+         • Asset management
+         • Human resources security
+         • Physical and environmental security
+         • Communications and operations management
+         • Access control
+         • Information systems acquisition, development, and maintenance
+      questions:
+      - id: GRM-04.1
+        content: Do you provide tenants with documentation describing your Information Security Management Program (ISMP)?
+      - id: GRM-04.2
+        content: Do you review your Information Security Management Program (ISMP) at least once a year?
+    - id: GRM-05
+      name: Management Support / Involvement
+      specification: Executive and line management shall take formal action to support information security through clearly-documented direction and commitment, and shall ensure the action has been assigned.
+      questions:
+      - id: GRM-05.1
+        content: Do you ensure your providers adhere to your information security and privacy policies?
+    - id: GRM-06
+      name: Policy
+      specification: Information security policies and procedures shall be established and made readily available for review by all impacted personnel and external business relationships. Information security policies must be authorized by the organization's business leadership (or other accountable business role or function) and supported by a strategic business plan and an information security management program inclusive of defined information security roles and responsibilities for business leadership.
+      questions:
+      - id: GRM-06.1
+        content: Do your information security and privacy policies align with industry standards (ISO-27001, ISO-22307, CoBIT, etc.)?
+      - id: GRM-06.2
+        content: Do you have agreements to ensure your providers adhere to your information security and privacy policies?
+      - id: GRM-06.3
+        content: Can you provide evidence of due diligence mapping of your controls, architecture, and processes to regulations and/or standards?
+      - id: GRM-06.4
+        content: Do you disclose which controls, standards, certifications, and/or regulations you comply with?
+    - id: GRM-07
+      name: Policy Enforcement
+      specification: A formal disciplinary or sanction policy shall be established for employees who have violated security policies and procedures. Employees shall be made aware of what action might be taken in the event of a violation, and disciplinary measures must be stated in the policies and procedures.
+      questions:
+      - id: GRM-07.1
+        content: Is a formal disciplinary or sanction policy established for employees who have violated security policies and procedures?
+    - id: GRM-08
+      name: Business / Policy Change Impacts
+      specification: Risk assessment results shall include updates to security policies, procedures, standards, and controls to ensure that they remain relevant and effective.
+      questions:
+      - id: GRM-08.1
+        content: Do risk assessment results include updates to security policies, procedures, standards, and controls to ensure they remain relevant and effective?
+    - id: GRM-09
+      name: Policy Reviews
+      specification: The organization's business leadership (or other accountable business role or function) shall review the information security policy at planned intervals or as a result of changes to the organization to ensure its continuing alignment with the security strategy, effectiveness, accuracy, relevance, and applicability to legal, statutory, or regulatory compliance obligations.
+      questions:
+      - id: GRM-09.1
+        content: Do you notify your tenants when you make material changes to your information security and/or privacy policies?
+      - id: GRM-09.2
+        content: Do you perform, at minimum, annual reviews to your privacy and security policies?
+    - id: GRM-10
+      name: Assessments
+      specification: Aligned with the enterprise-wide framework, formal risk assessments shall be performed at least annually or at planned intervals, (and in conjunction with any changes to information systems) to determine the likelihood and impact of all identified risks using qualitative and quantitative methods. The likelihood and impact associated with inherent and residual risk shall be determined independently, considering all risk categories (e.g., audit results, threat and vulnerability analysis, and regulatory compliance).
+      questions:
+      - id: GRM-10.1
+        content: Are formal risk assessments aligned with the enterprise-wide framework and performed at least annually, or at planned intervals, determining the likelihood and impact of all identified risks, using qualitative and quantitative methods?
+    - id: GRM-11
+      name: Program
+      specification: Risks shall be mitigated to an acceptable level. Acceptance levels based on risk criteria shall be established and documented in accordance with reasonable resolution time frames and stakeholder approval.
+      questions:
+      - id: GRM-11.1
+        content: Do you have a documented, organization-wide program in place to manage risk?
+  - id: RI
+    name: Governance and Risk Management
+    controls:
+    - id: RI-02
+      name: Assessments
+      specification: Aligned with the enterprise-wide framework, formal risk assessments shall be performed at least annually or at planned intervals, (and in conjunction with any changes to information systems) to determine the likelihood and impact of all identified risks using qualitative and quantitative methods. The likelihood and impact associated with inherent and residual risk shall be determined independently, considering all risk categories (e.g., audit results, threat and vulnerability analysis, and regulatory compliance).
+      questions:
+      - id: GRM-10.2
+        content: Is the likelihood and impact associated with inherent and residual risk determined independently, considering all risk categories (e.g., audit results, threat and vulnerability analysis, and regulatory compliance)?
+    - id: RI-01
+      name: Program
+      specification: Risks shall be mitigated to an acceptable level. Acceptance levels based on risk criteria shall be established and documented in accordance with reasonable resolution time frames and stakeholder approval.
+      questions:
+      - id: GRM-11.2
+        content: Do you make available documentation of your organization-wide risk management program?
+    - id: RI-05
+      name: Third Party Access
+      specification: The identification, assessment, and prioritization of risks posed by business processes requiring third-party access to the organization's information systems and data shall be followed by coordinated application of resources to minimize, monitor, and measure likelihood and impact of unauthorized or inappropriate access. Compensating controls derived from the risk analysis shall be implemented prior to provisioning access.
+      questions:
+      - id: IAM-07.2
+        content: Do you monitor service continuity with upstream providers in the event of provider failure?
+      - id: IAM-07.3
+        content: Do you have more than one provider for each service you depend on?
+      - id: IAM-07.4
+        content: Do you provide access to operational redundancy and continuity summaries, including the services you depend on?
+      - id: IAM-07.5
+        content: Do you provide the tenant the ability to declare a disaster?
+      - id: IAM-07.6
+        content: Do you provide a tenant-triggered failover option?
+      - id: IAM-07.7
+        content: Do you share your business continuity and redundancy plans with your tenants?
+  - id: HRS
+    name: Human Resources
+    controls:
+    - id: HRS-01
+      name: Asset Returns
+      specification: Upon termination of workforce personnel and/or expiration of external business relationships, all organizationally-owned assets shall be returned within an established period.
+      questions:
+      - id: HRS-01.1
+        content: Are systems in place to monitor for privacy breaches and notify tenants expeditiously if a privacy event may have impacted their data?
+    - id: HRS-02
+      name: Background Screening
+      specification: Pursuant to local laws, regulations, ethics, and contractual constraints, all employment candidates, contractors, and third parties shall be subject to background verification proportional to the data classification to be accessed, the business requirements, and acceptable risk.
+      questions:
+      - id: HRS-02.1
+        content: Pursuant to local laws, regulations, ethics, and contractual constraints, are all employment candidates, contractors, and involved third parties subject to background verification?
+    - id: HRS-03
+      name: Employment Agreements
+      specification: Employment agreements shall incorporate provisions and/or terms for adherence to established information governance and security policies and must be signed by newly hired or on-boarded workforce personnel (e.g., full or part-time employee or contingent staff) prior to granting workforce personnel user access to corporate facilities, resources, and assets.
+      questions:
+      - id: HRS-03.1
+        content: Do you specifically train your employees regarding their specific role and the information security controls they must fulfill?
+    - id: HRS-04
+      name: Employment Termination
+      specification: Roles and responsibilities for performing employment termination or change in employment procedures shall be assigned, documented, and communicated.
+      questions:
+      - id: HRS-04.1
+        content: Are documented policies, procedures, and guidelines in place to govern change in employment and/or termination?
+      - id: HRS-04.2
+        content: Do the above procedures and guidelines account for timely revocation of access and return of assets?
+    - id: HRS-05
+      name: Portable / Mobile Devices
+      specification: Policies and procedures shall be established, and supporting business processes and technical measures implemented, to manage business risks associated with permitting mobile device access to corporate resources and may require the implementation of higher assurance compensating controls and acceptable-use policies and procedures (e.g., mandated security training, stronger identity, entitlement and access controls, and device monitoring).
+      questions:
+      - id: HRS-05.1
+        content: Are policies and procedures established and measures implemented to strictly limit access to your sensitive data and tenant data from portable and mobile devices (e.g., laptops, cell phones, and personal digital assistants (PDAs)), which are generally higher-risk than non-portable devices (e.g., desktop computers at the provider organization’s facilities)?
+    - id: HRS-06
+      name: Non-Disclosure Agreements
+      specification: Requirements for non-disclosure or confidentiality agreements reflecting the organization's needs for the protection of data and operational details shall be identified, documented, and reviewed at planned intervals.
+      questions:
+      - id: HRS-06.1
+        content: Are requirements for non-disclosure or confidentiality agreements reflecting the organization's needs for the protection of data and operational details identified, documented, and reviewed at planned intervals?
+    - id: HRS-07
+      name: Roles / Responsibilities
+      specification: Roles and responsibilities of contractors, employees, and third-party users shall be documented as they relate to information assets and security.
+      questions:
+      - id: HRS-07.1
+        content: Do you provide tenants with a role definition document clarifying your administrative responsibilities versus those of the tenant?
+    - id: HRS-08
+      name: Acceptable Use
+      specification: Policies and procedures shall be established, and supporting business processes and technical measures implemented, for defining allowances and conditions for permitting usage of organizationally-owned or managed user end-point devices (e.g., issued workstations, laptops, and mobile devices) and IT infrastructure network and systems components. Additionally, defining allowances and conditions to permit usage of personal mobile devices and associated applications with access to corporate resources (i.e., BYOD) shall be considered and incorporated as appropriate.
+      questions:
+      - id: HRS-08.1
+        content: Do you provide documentation regarding how you may access tenant data and metadata?
+    - id: HRS-09
+      name: Training / Awareness
+      specification: A security awareness training program shall be established for all contractors, third-party users, and employees of the organization and mandated when appropriate. All individuals with access to organizational data shall receive appropriate awareness training and regular updates in organizational procedures, processes, and policies relating to their professional function relative to the organization.
+      questions:
+      - id: HRS-09.1
+        content: Do you provide a formal, role-based, security awareness training program for cloud-related access and data management issues (e.g., multi-tenancy, nationality, cloud delivery model, segregation of duties implications, and conflicts of interest) for all persons with access to tenant data?
+    - id: HRS-10
+      name: User Responsibility
+      specification: |-
+        All personnel shall be made aware of their roles and responsibilities for:
+         • Maintaining awareness and compliance with established policies and procedures and applicable legal, statutory, or regulatory compliance obligations.
+         • Maintaining a safe and secure working environment
+      questions:
+      - id: HRS-10.1
+        content: Are users made aware of their responsibilities for maintaining awareness and compliance with published security policies, procedures, standards, and applicable regulatory requirements?
+    - id: HRS-11
+      name: Workspace
+      specification: Policies and procedures shall be established to require that unattended workspaces do not have openly visible (e.g., on a desktop) sensitive documents and user computing sessions had been disabled after an established period of inactivity.
+      questions:
+      - id: HRS-11.1
+        content: Do your data management policies and procedures address tenant and service level conflicts of interests?
+  - id: HR
+    name: Human Resources
+    controls:
+    - id: HR-02
+      name: Employment Agreements
+      specification: Employment agreements shall incorporate provisions and/or terms for adherence to established information governance and security policies and must be signed by newly hired or on-boarded workforce personnel (e.g., full or part-time employee or contingent staff) prior to granting workforce personnel user access to corporate facilities, resources, and assets.
+      questions:
+      - id: HRS-03.2
+        content: Do you document employee acknowledgment of training they have completed?
+      - id: HRS-03.3
+        content: Are all personnel required to sign NDA or Confidentiality Agreements as a condition of employment to protect customer/tenant information?
+      - id: HRS-03.4
+        content: Is successful and timed completion of the training program considered a prerequisite for acquiring and maintaining access to sensitive systems?
+      - id: HRS-03.5
+        content: Are personnel trained and provided with awareness programs at least once a year?
+  - id: IAM
+    name: Identity & Access Management
+    controls:
+    - id: IAM-01
+      name: Audit Tools Access
+      specification: Access to, and use of, audit tools that interact with the organization's information systems shall be appropriately segmented and restricted to prevent compromise and misuse of log data.
+      questions:
+      - id: IAM-01.1
+        content: Do you restrict, log, and monitor access to your information security management systems (e.g., hypervisors, firewalls, vulnerability scanners, network sniffers, APIs, etc.)?
+      - id: IAM-01.2
+        content: Do you monitor and log privileged access (e.g., administrator level) to information security management systems?
+    - id: IAM-02
+      name: User Access Policy
+      specification: |-
+        User access policies and procedures shall be established, and supporting business processes and technical measures implemented, for ensuring appropriate identity, entitlement, and access management for all internal corporate and customer (tenant) users with access to data and organizationally-owned or managed (physical and virtual) application interfaces and infrastructure network and systems components. These policies, procedures, processes, and measures must incorporate the following:
+         • Procedures, supporting roles, and responsibilities for provisioning and de-provisioning user account entitlements following the rule of least privilege based on job function (e.g., internal employee and contingent staff personnel changes, customer-controlled access, suppliers' business relationships, or other third-party business relationships)
+         • Business case considerations for higher levels of assurance and multi-factor authentication secrets (e.g., management interfaces, key generation, remote access, segregation of duties, emergency access, large-scale provisioning or geographically-distributed deployments, and personnel redundancy for critical systems)
+         • Access segmentation to sessions and data in multi-tenant architectures by any third party (e.g., provider and/or other customer (tenant))
+         • Identity trust verification and service-to-service application (API) and information processing interoperability (e.g., SSO and federation)
+         • Account credential lifecycle management from instantiation through revocation
+         • Account credential and/or identity store minimization or re-use when feasible
+         • Authentication, authorization, and accounting (AAA) rules for access to data and sessions (e.g., encryption and strong/multi-factor, expireable, non-shared authentication secrets)
+         • Permissions and supporting capabilities for customer (tenant) controls over authentication, authorization, and accounting (AAA) rules for access to data and sessions
+         • Adherence to applicable legal, statutory, or regulatory compliance requirements
+      questions:
+      - id: IAM-02.1
+        content: Do you have controls in place ensuring timely removal of systems access that is no longer required for business purposes?
+    - id: IAM-03
+      name: Diagnostic / Configuration Ports Access
+      specification: User access to diagnostic and configuration ports shall be restricted to authorized individuals and applications.
+      questions:
+      - id: IAM-03.1
+        content: Do you use dedicated secure networks to provide management access to your cloud service infrastructure?
+    - id: IAM-04
+      name: Policies and Procedures
+      specification: Policies and procedures shall be established to store and manage identity information about every person who accesses IT infrastructure and to determine their level of access. Policies shall also be developed to control access to network resources based on user identity.
+      questions:
+      - id: IAM-04.1
+        content: Do you manage and store the identity of all personnel who have access to the IT infrastructure, including their level of access?
+      - id: IAM-04.2
+        content: Do you manage and store the user identity of all personnel who have network access, including their level of access?
+    - id: IAM-05
+      name: Segregation of Duties
+      specification: User access policies and procedures shall be established, and supporting business processes and technical measures implemented, for restricting user access as per defined segregation of duties to address business risks associated with a user-role conflict of interest.
+      questions:
+      - id: IAM-05.1
+        content: Do you provide tenants with documentation on how you maintain segregation of duties within your cloud service offering?
+    - id: IAM-06
+      name: Source Code Access Restriction
+      specification: Access to the organization's own developed applications, program, or object source code, or any other form of intellectual property (IP), and use of proprietary software shall be appropriately restricted following the rule of least privilege based on job function as per established user access policies and procedures.
+      questions:
+      - id: IAM-06.1
+        content: Are controls in place to prevent unauthorized access to your application, program, or object source code, and assure it is restricted to authorized personnel only?
+    - id: IAM-07
+      name: Third Party Access
+      specification: The identification, assessment, and prioritization of risks posed by business processes requiring third-party access to the organization's information systems and data shall be followed by coordinated application of resources to minimize, monitor, and measure likelihood and impact of unauthorized or inappropriate access. Compensating controls derived from the risk analysis shall be implemented prior to provisioning access.
+      questions:
+      - id: IAM-07.1
+        content: Do you provide multi-failure disaster recovery capability?
+    - id: IAM-08
+      name: User Access Restriction / Authorization
+      specification: Policies and procedures are established for permissible storage and access of identities used for authentication to ensure identities are only accessible based on rules of least privilege and replication limitation only to users explicitly defined as business necessary.
+      questions:
+      - id: IAM-08.1
+        content: Do you document how you grant and approve access to tenant data?
+    - id: IAM-09
+      name: User Access Authorization
+      specification: Provisioning user access (e.g., employees, contractors, customers (tenants), business partners and/or supplier relationships) to data and organizationally-owned or managed (physical and virtual) applications, infrastructure systems, and network components shall be authorized by the organization's management prior to access being granted and appropriately restricted as per established policies and procedures. Upon request, provider shall inform customer (tenant) of this user access, especially if customer (tenant) data is used as part of the service and/or customer (tenant) has some shared responsibility over implementation of control.
+      questions:
+      - id: IAM-09.1
+        content: Does your management provision the authorization and restrictions for user access (e.g., employees, contractors, customers (tenants), business partners, and/or suppliers) prior to their access to data and any owned or managed (physical and virtual) applications, infrastructure systems, and network components?
+      - id: IAM-09.2
+        content: Do you provide upon request user access (e.g., employees, contractors, customers (tenants), business partners and/or suppliers) to data and any owned or managed (physical and virtual) applications, infrastructure systems and network components?
+    - id: IAM-10
+      name: User Access Reviews
+      specification: User access shall be authorized and revalidated for entitlement appropriateness, at planned intervals, by the organization's business leadership or other accountable business role or function supported by evidence to demonstrate the organization is adhering to the rule of least privilege based on job function. For identified access violations, remediation must follow established user access policies and procedures.
+      questions:
+      - id: IAM-10.1
+        content: Do you require at least annual certification of entitlements for all system users and administrators (exclusive of users maintained by your tenants)?
+    - id: IAM-11
+      name: User Access Revocation
+      specification: Timely de-provisioning (revocation or modification) of user access to data and organizationally-owned or managed (physical and virtual) applications, infrastructure systems, and network components, shall be implemented as per established policies and procedures and based on user's change in status (e.g., termination of employment or other business relationship, job change, or transfer). Upon request, provider shall inform customer (tenant) of these changes, especially if customer (tenant) data is used as part the service and/or customer (tenant) has some shared responsibility over implementation of control.
+      questions:
+      - id: IAM-11.1
+        content: Is timely deprovisioning, revocation, or modification of user access to the organizations systems, information assets, and data implemented upon any change in status of employees, contractors, customers, business partners, or involved third parties?
+    - id: IAM-12
+      name: User ID Credentials
+      specification: |-
+        Internal corporate or customer (tenant) user account credentials shall be restricted as per the following, ensuring appropriate identity, entitlement, and access management and in accordance with established policies and procedures:
+         • Identity trust verification and service-to-service application (API) and information processing interoperability (e.g., SSO and Federation)
+         • Account credential lifecycle management from instantiation through revocation
+         • Account credential and/or identity store minimization or re-use when feasible
+         • Adherence to industry acceptable and/or regulatory compliant authentication, authorization, and accounting (AAA) rules (e.g., strong/multi-factor, expireable, non-shared authentication secrets)
+      questions:
+      - id: IAM-12.1
+        content: Do you support use of, or integration with, existing customer-based Single Sign On (SSO) solutions to your service?
+    - id: IAM-13
+      name: Utility Programs Access
+      specification: Utility programs capable of potentially overriding system, object, network, virtual machine, and application controls shall be restricted.
+      questions:
+      - id: IAM-13.1
+        content: Are utilities that can significantly manage virtualized partitions (e.g., shutdown, clone, etc.) appropriately restricted and monitored?
+  - id: SA
+    name: Identity & Access Management
+    controls:
+    - id: SA-02
+      name: User ID Credentials
+      specification: |-
+        Internal corporate or customer (tenant) user account credentials shall be restricted as per the following, ensuring appropriate identity, entitlement, and access management and in accordance with established policies and procedures:
+         • Identity trust verification and service-to-service application (API) and information processing interoperability (e.g., SSO and Federation)
+         • Account credential lifecycle management from instantiation through revocation
+         • Account credential and/or identity store minimization or re-use when feasible
+         • Adherence to industry acceptable and/or regulatory compliant authentication, authorization, and accounting (AAA) rules (e.g., strong/multi-factor, expireable, non-shared authentication secrets)
+      questions:
+      - id: IAM-12.2
+        content: Do you use open standards to delegate authentication capabilities to your tenants?
+      - id: IAM-12.3
+        content: Do you support identity federation standards (e.g., SAML, SPML, WS-Federation, etc.) as a means of authenticating/authorizing users?
+      - id: IAM-12.4
+        content: Do you have a Policy Enforcement Point capability (e.g., XACML) to enforce regional legal and policy constraints on user access?
+      - id: IAM-12.5
+        content: Do you have an identity management system (enabling classification of data for a tenant) in place to enable both role-based and context-based entitlement to data?
+      - id: IAM-12.6
+        content: Do you provide tenants with strong (multifactor) authentication options (e.g., digital certs, tokens, biometrics, etc.) for user access?
+      - id: IAM-12.7
+        content: Do you allow tenants to use third-party identity assurance services?
+      - id: IAM-12.8
+        content: Do you support password (e.g., minimum length, age, history, complexity) and account lockout (e.g., lockout threshold, lockout duration) policy enforcement?
+      - id: IAM-12.9
+        content: Do you allow tenants/customers to define password and account lockout policies for their accounts?
+      - id: IAM-12.10
+        content: Do you support the ability to force password changes upon first logon?
+      - id: IAM-12.11
+        content: Do you have mechanisms in place for unlocking accounts that have been locked out (e.g., self-service via email, defined challenge questions, manual unlock)?
+    - id: SA-14
+      name: Audit Logging / Intrusion Detection
+      specification: Higher levels of assurance are required for protection, retention, and lifecycle management of audit logs, adhering to applicable legal, statutory, or regulatory compliance obligations and providing unique user access accountability to detect potentially suspicious network behaviors and/or file integrity anomalies, and to support forensic investigative capabilities in the event of a security breach.
+      questions:
+      - id: IVS-01.2
+        content: Is physical and logical user access to audit logs restricted to authorized personnel?
+      - id: IVS-01.3
+        content: Can you provide evidence that due diligence mapping of regulations and standards to your controls/architecture/processes has been done?
+      - id: IVS-01.4
+        content: Are audit logs centrally stored and retained?
+      - id: IVS-01.5
+        content: Are audit logs reviewed on a regular basis for security events (e.g., with automated tools)?
+    - id: SA-06
+      name: Production / Non-Production Environments
+      specification: 'Production and non-production environments shall be separated to prevent unauthorized access or changes to information assets. Separation of the environments may include: stateful inspection firewalls, domain/realm authentication sources, and clear segregation of duties for personnel accessing these environments as part of their job duties.'
+      questions:
+      - id: IVS-08.2
+        content: For your IaaS offering, do you provide tenants with guidance on how to create suitable production and test environments?
+      - id: IVS-08.3
+        content: Do you logically and physically segregate production and non-production environments?
+    - id: SA-09
+      name: Segmentation
+      specification: |-
+        Multi-tenant organizationally-owned or managed (physical and virtual) applications, and infrastructure system and network components, shall be designed, developed, deployed, and configured such that provider and customer (tenant) user access is appropriately segmented from other tenant users, based on the following considerations:
+         • Established policies and procedures
+         • Isolation of business critical assets and/or sensitive user data and sessions that mandate stronger internal controls and high levels of assurance
+         • Compliance with legal, statutory, and regulatory compliance obligations
+      questions:
+      - id: IVS-09.2
+        content: Are system and network environments protected by a firewall or virtual firewall to ensure compliance with legislative, regulatory, and contractual requirements?
+      - id: IVS-09.3
+        content: Are system and network environments protected by a firewall or virtual firewall to ensure separation of production and non-production environments?
+      - id: IVS-09.4
+        content: Are system and network environments protected by a firewall or virtual firewall to ensure protection and isolation of sensitive data?
+    - id: SA-10
+      name: Wireless Security
+      specification: |-
+        Policies and procedures shall be established, and supporting business processes and technical measures implemented, to protect wireless network environments, including the following:
+         • Perimeter firewalls implemented and configured to restrict unauthorized traffic
+         • Security settings enabled with strong encryption for authentication and transmission, replacing vendor default settings (e.g., encryption keys, passwords, and SNMP community strings)
+         • User access to wireless network devices restricted to authorized personnel
+         • The capability to detect the presence of unauthorized (rogue) wireless network devices for a timely disconnect from the network
+      questions:
+      - id: IVS-12.2
+        content: Are policies and procedures established and mechanisms implemented to ensure wireless security settings are enabled with strong encryption for authentication and transmission, replacing vendor default settings (e.g., encryption keys, passwords, SNMP community strings)?
+      - id: IVS-12.3
+        content: Are policies and procedures established and mechanisms implemented to protect wireless network environments and detect the presence of unauthorized (rogue) network devices for a timely disconnect from the network?
+    - id: SA-15
+      name: Mobile Code
+      specification: Policies and procedures shall be established, and supporting business processes and technical measures implemented, to prevent the execution of unauthorized mobile code, defined as software transferred between systems over a trusted or untrusted network and executed on a local system without explicit installation or execution by the recipient, on organizationally-owned or managed user end-point devices (e.g., issued workstations, laptops, and mobile devices) and IT infrastructure network and systems components.
+      questions:
+      - id: TVM-03.2
+        content: Is all unauthorized mobile code prevented from executing?
+  - id: IVS
+    name: Infrastructure & Virtualization Security
+    controls:
+    - id: IVS-01
+      name: Audit Logging / Intrusion Detection
+      specification: Higher levels of assurance are required for protection, retention, and lifecycle management of audit logs, adhering to applicable legal, statutory, or regulatory compliance obligations and providing unique user access accountability to detect potentially suspicious network behaviors and/or file integrity anomalies, and to support forensic investigative capabilities in the event of a security breach.
+      questions:
+      - id: IVS-01.1
+        content: Are file integrity (host) and network intrusion detection (IDS) tools implemented to help facilitate timely detection, investigation by root cause analysis, and response to incidents?
+    - id: IVS-02
+      name: Change Detection
+      specification: The provider shall ensure the integrity of all virtual machine images at all times. Any changes made to virtual machine images must be logged and an alert raised regardless of their running state (e.g., dormant, off, or running). The results of a change or move of an image and the subsequent validation of the image's integrity must be immediately available to customers through electronic methods (e.g., portals or alerts).
+      questions:
+      - id: IVS-02.1
+        content: Do you log and alert any changes made to virtual machine images regardless of their running state (e.g., dormant, off or running)?
+      - id: IVS-02.2
+        content: Are changes made to virtual machines, or moving of an image and subsequent validation of the image's integrity, made immediately available to customers through electronic methods (e.g., portals or alerts)?
+    - id: IVS-03
+      name: Clock Synchronization
+      specification: A reliable and mutually agreed upon external time source shall be used to synchronize the system clocks of all relevant information processing systems to facilitate tracing and reconstitution of activity timelines.
+      questions:
+      - id: IVS-03.1
+        content: Do you use a synchronized time-service protocol (e.g., NTP) to ensure all systems have a common time reference?
+    - id: IVS-04
+      name: Capacity / Resource Planning
+      specification: The availability, quality, and adequate capacity and resources shall be planned, prepared, and measured to deliver the required system performance in accordance with legal, statutory, and regulatory compliance obligations. Projections of future capacity requirements shall be made to mitigate the risk of system overload.
+      questions:
+      - id: IVS-04.1
+        content: Do you provide documentation regarding what levels of system (e.g., network, storage, memory, I/O, etc.) oversubscription you maintain and under what circumstances/scenarios?
+    - id: IVS-05
+      name: Management - Vulnerability Management
+      specification: Implementers shall ensure that the security vulnerability assessment tools or services accommodate the virtualization technologies used (e.g., virtualization aware).
+      questions:
+      - id: IVS-05.1
+        content: Do security vulnerability assessment tools or services accommodate the virtualization technologies being used (e.g., virtualization aware)?
+    - id: IVS-06
+      name: Network Security
+      specification: Network environments and virtual instances shall be designed and configured to restrict and monitor traffic between trusted and untrusted connections. These configurations shall be reviewed at least annually, and supported by a documented justification for use for all allowed services, protocols, ports, and compensating controls.
+      questions:
+      - id: IVS-06.1
+        content: For your IaaS offering, do you provide customers with guidance on how to create a layered security architecture equivalence using your virtualized solution?
+      - id: IVS-06.2
+        content: Do you regularly update network architecture diagrams that include data flows between security domains/zones?
+      - id: IVS-06.3
+        content: Do you regularly review for appropriateness the allowed access/connectivity (e.g., firewall rules) between security domains/zones within the network?
+      - id: IVS-06.4
+        content: Are all firewall access control lists documented with business justification?
+    - id: IVS-07
+      name: OS Hardening and Base Controls
+      specification: 'Each operating system shall be hardened to provide only necessary ports, protocols, and services to meet business needs and have in place supporting technical controls such as: antivirus, file integrity monitoring, and logging as part of their baseline operating build standard or template.'
+      questions:
+      - id: IVS-07.1
+        content: Are operating systems hardened to provide only the necessary ports, protocols, and services to meet business needs using technical controls (e.g., antivirus, file integrity monitoring, and logging) as part of their baseline build standard or template?
+    - id: IVS-08
+      name: Production / Non-Production Environments
+      specification: 'Production and non-production environments shall be separated to prevent unauthorized access or changes to information assets. Separation of the environments may include: stateful inspection firewalls, domain/realm authentication sources, and clear segregation of duties for personnel accessing these environments as part of their job duties.'
+      questions:
+      - id: IVS-08.1
+        content: For your SaaS or PaaS offering, do you provide tenants with separate environments for production and test processes?
+    - id: IVS-09
+      name: Segmentation
+      specification: |-
+        Multi-tenant organizationally-owned or managed (physical and virtual) applications, and infrastructure system and network components, shall be designed, developed, deployed, and configured such that provider and customer (tenant) user access is appropriately segmented from other tenant users, based on the following considerations:
+         • Established policies and procedures
+         • Isolation of business critical assets and/or sensitive user data and sessions that mandate stronger internal controls and high levels of assurance
+         • Compliance with legal, statutory, and regulatory compliance obligations
+      questions:
+      - id: IVS-09.1
+        content: Are system and network environments protected by a firewall or virtual firewall to ensure business and customer security requirements?
+    - id: IVS-10
+      name: VM Security - Data Protection
+      specification: Secured and encrypted communication channels shall be used when migrating physical servers, applications, or data to virtualized servers and, where possible, shall use a network segregated from production-level networks for such migrations.
+      questions:
+      - id: IVS-10.1
+        content: Are secured and encrypted communication channels used when migrating physical servers, applications, or data to virtual servers?
+      - id: IVS-10.2
+        content: Do you use a network segregated from production-level networks when migrating physical servers, applications, or data to virtual servers?
+    - id: IVS-11
+      name: VMM Security - Hypervisor Hardening
+      specification: Access to all hypervisor management functions or administrative consoles for systems hosting virtualized systems shall be restricted to personnel based upon the principle of least privilege and supported through technical controls (e.g., two-factor authentication, audit trails, IP address filtering, firewalls, and TLS encapsulated communications to the administrative consoles).
+      questions:
+      - id: IVS-11.1
+        content: Do you restrict personnel access to all hypervisor management functions or administrative consoles for systems hosting virtualized systems based on the principle of least privilege and supported through technical controls (e.g., two-factor authentication, audit trails, IP address filtering, firewalls and TLS-encapsulated communications to the administrative consoles)?
+    - id: IVS-12
+      name: Wireless Security
+      specification: |-
+        Policies and procedures shall be established, and supporting business processes and technical measures implemented, to protect wireless network environments, including the following:
+         • Perimeter firewalls implemented and configured to restrict unauthorized traffic
+         • Security settings enabled with strong encryption for authentication and transmission, replacing vendor default settings (e.g., encryption keys, passwords, and SNMP community strings)
+         • User access to wireless network devices restricted to authorized personnel
+         • The capability to detect the presence of unauthorized (rogue) wireless network devices for a timely disconnect from the network
+      questions:
+      - id: IVS-12.1
+        content: Are policies and procedures established and mechanisms configured and implemented to protect the wireless network environment perimeter and to restrict unauthorized wireless traffic?
+    - id: IVS-13
+      name: Network Architecture
+      specification: Network architecture diagrams shall clearly identify high-risk environments and data flows that may have legal compliance impacts. Technical measures shall be implemented and shall apply defense-in-depth techniques (e.g., deep packet analysis, traffic throttling, and black-holing) for detection and timely response to network-based attacks associated with anomalous ingress or egress traffic patterns (e.g., MAC spoofing and ARP poisoning attacks) and/or distributed denial-of-service (DDoS) attacks.
+      questions:
+      - id: IVS-13.1
+        content: Do your network architecture diagrams clearly identify high-risk environments and data flows that may have legal compliance impacts?
+      - id: IVS-13.2
+        content: Do you implement technical measures and apply defense-in-depth techniques (e.g., deep packet analysis, traffic throttling and black-holing) for detection and timely response to network-based attacks associated with anomalous ingress or egress traffic patterns (e.g., MAC spoofing and ARP poisoning attacks) and/or distributed denial-of-service (DDoS) attacks?
+  - id: IPY
+    name: Interoperability & Portability
+    controls:
+    - id: IPY-01
+      name: APIs
+      specification: The provider shall use open and published APIs to ensure support for interoperability between components and to facilitate migrating applications.
+      questions:
+      - id: IPY-01.1
+        content: Do you publish a list of all APIs available in the service and indicate which are standard and which are customized?
+    - id: IPY-02
+      name: Data Request
+      specification: All structured and unstructured data shall be available to the customer and provided to them upon request in an industry-standard format (e.g., .doc, .xls, .pdf, logs, and flat files).
+      questions:
+      - id: IPY-02.1
+        content: Is unstructured customer data available on request in an industry-standard format (e.g., .doc, .xls, or .pdf)?
+    - id: IPY-03
+      name: Policy & Legal
+      specification: Policies, procedures, and mutually-agreed upon provisions and/or terms shall be established to satisfy customer (tenant) requirements for service-to-service application (API) and information processing interoperability, and portability for application development and information exchange, usage, and integrity persistence.
+      questions:
+      - id: IPY-03.1
+        content: Do you provide policies and procedures (i.e. service level agreements) governing the use of APIs for interoperability between your service and third-party applications?
+      - id: IPY-03.2
+        content: Do you provide policies and procedures (i.e. service level agreements) governing the migration of application data to and from your service?
+    - id: IPY-04
+      name: Standardized Network Protocols
+      specification: The provider shall use secure (e.g., non-clear text and authenticated) standardized network protocols for the import and export of data and to manage the service, and shall make available a document to consumers (tenants) detailing the relevant interoperability and portability standards that are involved.
+      questions:
+      - id: IPY-04.1
+        content: Can data import, data export, and service management be conducted over secure (e.g., non-clear text and authenticated), industry accepted standardized network protocols?
+      - id: IPY-04.2
+        content: Do you provide consumers (tenants) with documentation detailing the relevant interoperability and portability network protocol standards that are involved?
+    - id: IPY-05
+      name: Virtualization
+      specification: The provider shall use an industry-recognized virtualization platform and standard virtualization formats (e.g., OVF) to help ensure interoperability, and shall have documented custom changes made to any hypervisor in use, and all solution-specific virtualization hooks, available for customer review.
+      questions:
+      - id: IPY-05.1
+        content: Do you use an industry-recognized virtualization platform and standard virtualization formats (e.g., OVF) to help ensure interoperability?
+      - id: IPY-05.2
+        content: Do you have documented custom changes made to any hypervisor in use, and all solution-specific virtualization hooks available for customer review?
+  - id: MOS
+    name: Mobile Security
+    controls:
+    - id: MOS-01
+      name: Anti-Malware
+      specification: Anti-malware awareness training, specific to mobile devices, shall be included in the provider's information security awareness training.
+      questions:
+      - id: MOS-01.1
+        content: Do you provide anti-malware training specific to mobile devices as part of your information security awareness training?
+    - id: MOS-02
+      name: Application Stores
+      specification: A documented list of approved application stores has been communicated as acceptable for mobile devices accessing or storing provider managed data.
+      questions:
+      - id: MOS-02.1
+        content: Do you document and make available lists of approved application stores for mobile devices accessing or storing company data and/or company systems?
+    - id: MOS-03
+      name: Approved Applications
+      specification: The company shall have a documented policy prohibiting the installation of non-approved applications or approved applications not obtained through a pre-identified application store.
+      questions:
+      - id: MOS-03.1
+        content: Do you have a policy enforcement capability (e.g., XACML) to ensure that only approved applications and those from approved application stores can be loaded onto a mobile device?
+    - id: MOS-04
+      name: Approved Software for BYOD
+      specification: The BYOD policy and supporting awareness training clearly states the approved applications, application stores, and application extensions and plugins that may be used for BYOD usage.
+      questions:
+      - id: MOS-04.1
+        content: Does your BYOD policy and training clearly state which applications and applications stores are approved for use on BYOD devices?
+    - id: MOS-05
+      name: Awareness and Training
+      specification: The provider shall have a documented mobile device policy that includes a documented definition for mobile devices and the acceptable usage and requirements for all mobile devices. The provider shall post and communicate the policy and requirements through the company's security awareness and training program.
+      questions:
+      - id: MOS-05.1
+        content: Do you have a documented mobile device policy in your employee training that clearly defines mobile devices and the accepted usage and requirements for mobile devices?
+    - id: MOS-06
+      name: Cloud Based Services
+      specification: All cloud-based services used by the company's mobile devices or BYOD shall be pre-approved for usage and the storage of company business data.
+      questions:
+      - id: MOS-06.1
+        content: Do you have a documented list of pre-approved cloud based services that are allowed to be used for use and storage of company business data via a mobile device?
+    - id: MOS-07
+      name: Compatibility
+      specification: The company shall have a documented application validation process to test for mobile device, operating system, and application compatibility issues.
+      questions:
+      - id: MOS-07.1
+        content: Do you have a documented application validation process for testing device, operating system, and application compatibility issues?
+    - id: MOS-08
+      name: Device Eligibility
+      specification: The BYOD policy shall define the device and eligibility requirements to allow for BYOD usage.
+      questions:
+      - id: MOS-08.1
+        content: Do you have a BYOD policy that defines the device(s) and eligibility requirements allowed for BYOD usage?
+    - id: MOS-09
+      name: Device Inventory
+      specification: An inventory of all mobile devices used to store and access company data shall be kept and maintained. All changes to the status of these devices, (i.e., operating system and patch levels, lost or decommissioned status, and to whom the device is assigned or approved for usage (BYOD)), will be included for each device in the inventory.
+      questions:
+      - id: MOS-09.1
+        content: Do you maintain an inventory of all mobile devices storing and accessing company data which includes device status (e.g., operating system and patch levels, lost or decommissioned, device assignee)?
+    - id: MOS-10
+      name: Device Management
+      specification: A centralized, mobile device management solution shall be deployed to all mobile devices permitted to store, transmit, or process customer data.
+      questions:
+      - id: MOS-10.1
+        content: Do you have a centralized mobile device management solution deployed to all mobile devices that are permitted to store, transmit, or process company data?
+    - id: MOS-11
+      name: Encryption
+      specification: The mobile device policy shall require the use of encryption either for the entire device or for data identified as sensitive on all mobile devices and shall be enforced through technology controls.
+      questions:
+      - id: MOS-11.1
+        content: Does your mobile device policy require the use of encryption for either the entire device or for data identified as sensitive enforceable through technology controls for all mobile devices?
+    - id: MOS-12
+      name: Jailbreaking and Rooting
+      specification: The mobile device policy shall prohibit the circumvention of built-in security controls on mobile devices (e.g., jailbreaking or rooting) and is enforced through detective and preventative controls on the device or through a centralized device management system (e.g., mobile device management).
+      questions:
+      - id: MOS-12.1
+        content: Does your mobile device policy prohibit the circumvention of built-in security controls on mobile devices (e.g., jailbreaking or rooting)?
+      - id: MOS-12.2
+        content: Do you have detective and preventative controls on the device or via a centralized device management system which prohibit the circumvention of built-in security controls?
+    - id: MOS-13
+      name: Legal
+      specification: The BYOD policy includes clarifying language for the expectation of privacy, requirements for litigation, e-discovery, and legal holds. The BYOD policy shall clearly state the expectations over the loss of non-company data in the case that a wipe of the device is required.
+      questions:
+      - id: MOS-13.1
+        content: Does your BYOD policy clearly define the expectation of privacy, requirements for litigation, e-discovery, and legal holds?
+      - id: MOS-13.2
+        content: Do you have detective and preventative controls on the device or via a centralized device management system which prohibit the circumvention of built-in security controls?
+    - id: MOS-14
+      name: Lockout Screen
+      specification: BYOD and/or company owned devices are configured to require an automatic lockout screen, and the requirement shall be enforced through technical controls.
+      questions:
+      - id: MOS-14.1
+        content: Do you require and enforce via technical controls an automatic lockout screen for BYOD and company owned devices?
+    - id: MOS-15
+      name: Operating Systems
+      specification: Changes to mobile device operating systems, patch levels, and/or applications shall be managed through the company's change management processes.
+      questions:
+      - id: MOS-15.1
+        content: Do you manage all changes to mobile device operating systems, patch levels, and applications via your company's change management processes?
+    - id: MOS-16
+      name: Passwords
+      specification: Password policies, applicable to mobile devices, shall be documented and enforced through technical controls on all company devices or devices approved for BYOD usage, and shall prohibit the changing of password/PIN lengths and authentication requirements.
+      questions:
+      - id: MOS-16.1
+        content: Do you have password policies for enterprise issued mobile devices and/or BYOD mobile devices?
+      - id: MOS-16.2
+        content: Are your password policies enforced through technical controls (i.e. MDM)?
+      - id: MOS-16.3
+        content: Do your password policies prohibit the changing of authentication requirements (i.e. password/PIN length) via a mobile device?
+    - id: MOS-17
+      name: Policy
+      specification: The mobile device policy shall require the BYOD user to perform backups of data, prohibit the usage of unapproved application stores, and require the use of anti-malware software (where supported).
+      questions:
+      - id: MOS-17.1
+        content: Do you have a policy that requires BYOD users to perform backups of specified corporate data?
+      - id: MOS-17.2
+        content: Do you have a policy that requires BYOD users to prohibit the usage of unapproved application stores?
+      - id: MOS-17.3
+        content: Do you have a policy that requires BYOD users to use anti-malware software (where supported)?
+    - id: MOS-18
+      name: Remote Wipe
+      specification: All mobile devices permitted for use through the company BYOD program or a company-assigned mobile device shall allow for remote wipe by the company's corporate IT or shall have all company-provided data wiped by the company's corporate IT.
+      questions:
+      - id: MOS-18.1
+        content: Does your IT provide remote wipe or corporate data wipe for all company-accepted BYOD devices?
+      - id: MOS-18.2
+        content: Does your IT provide remote wipe or corporate data wipe for all company-assigned mobile devices?
+    - id: MOS-19
+      name: Security Patches
+      specification: Mobile devices connecting to corporate networks or storing and accessing company information shall allow for remote software version/patch validation. All mobile devices shall have the latest available security-related patches installed upon general release by the device manufacturer or carrier and authorized IT personnel shall be able to perform these updates remotely.
+      questions:
+      - id: MOS-19.1
+        content: Do your mobile devices have the latest available security-related patches installed upon general release by the device manufacturer or carrier?
+      - id: MOS-19.2
+        content: Do your mobile devices allow for remote validation to download the latest security patches by company IT personnel?
+    - id: MOS-20
+      name: Users
+      specification: The BYOD policy shall clarify the systems and servers allowed for use or access on a BYOD-enabled device.
+      questions:
+      - id: MOS-20.1
+        content: Does your BYOD policy clarify the systems and servers allowed for use or access on the BYOD-enabled device?
+      - id: MOS-20.2
+        content: Does your BYOD policy specify the user roles that are allowed access via a BYOD-enabled device?
+  - id: SEF
+    name: Security Incident Management, E-Discovery, & Cloud Forensics
+    controls:
+    - id: SEF-01
+      name: Contact / Authority Maintenance
+      specification: Points of contact for applicable regulation authorities, national and local law enforcement, and other legal jurisdictional authorities shall be maintained and regularly updated (e.g., change in impacted-scope and/or a change in any compliance obligation) to ensure direct compliance liaisons have been established and to be prepared for a forensic investigation requiring rapid engagement with law enforcement.
+      questions:
+      - id: SEF-01.1
+        content: Do you maintain liaisons and points of contact with local authorities in accordance with contracts and appropriate regulations?
+    - id: SEF-02
+      name: Incident Management
+      specification: Policies and procedures shall be established, and supporting business processes and technical measures implemented, to triage security-related events and ensure timely and thorough incident management, as per established IT service management policies and procedures.
+      questions:
+      - id: SEF-02.1
+        content: Do you have a documented security incident response plan?
+    - id: SEF-03
+      name: Incident Reporting
+      specification: Workforce personnel and external business relationships shall be informed of their responsibility and, if required, shall consent and/or contractually agree to report all information security events in a timely manner. Information security events shall be reported through predefined communications channels in a timely manner adhering to applicable legal, statutory, or regulatory compliance obligations.
+      questions:
+      - id: SEF-03.1
+        content: Does your security information and event management (SIEM) system merge data sources (e.g., app logs, firewall logs, IDS logs, physical access logs, etc.) for granular analysis and alerting?
+    - id: SEF-04
+      name: Incident Response Legal Preparation
+      specification: Proper forensic procedures, including chain of custody, are required for the presentation of evidence to support potential legal action subject to the relevant jurisdiction after an information security incident. Upon notification, customers and/or other external business partners impacted by a security breach shall be given the opportunity to participate as is legally permissible in the forensic investigation.
+      questions:
+      - id: SEF-04.1
+        content: Does your incident response plan comply with industry standards for legally admissible chain-of-custody management processes and controls?
+    - id: SEF-05
+      name: Incident Response Metrics
+      specification: Mechanisms shall be put in place to monitor and quantify the types, volumes, and costs of information security incidents.
+      questions:
+      - id: SEF-05.1
+        content: Do you monitor and quantify the types, volumes, and impacts on all information security incidents?
+  - id: STA
+    name: Supply Chain Management, Transparency, and Accountability
+    controls:
+    - id: STA-01
+      name: Data Quality and Integrity
+      specification: Providers shall inspect, account for, and work with their cloud supply-chain partners to correct data quality errors and associated risks. Providers shall design and implement controls to mitigate and contain data security risks through proper separation of duties, role-based access, and least-privilege access for all personnel within their supply chain.
+      questions:
+      - id: STA-01.1
+        content: Do you inspect and account for data quality errors and associated risks, and work with your cloud supply-chain partners to correct them?
+      - id: STA-01.2
+        content: Do you design and implement controls to mitigate and contain data security risks through proper separation of duties, role-based access, and least-privileged access for all personnel within your supply chain?
+    - id: STA-02
+      name: Incident Reporting
+      specification: The provider shall make security incident information available to all affected customers and providers periodically through electronic methods (e.g., portals).
+      questions:
+      - id: STA-02.1
+        content: Do you make security incident information available to all affected customers and providers periodically through electronic methods (e.g., portals)?
+    - id: STA-03
+      name: Network / Infrastructure Services
+      specification: Business-critical or customer (tenant) impacting (physical and virtual) application and system-system interface (API) designs and configurations, and infrastructure network and systems components, shall be designed, developed, and deployed in accordance with mutually agreed-upon service and capacity-level expectations, as well as IT governance and service management policies and procedures.
+      questions:
+      - id: STA-03.1
+        content: Do you collect capacity and use data for all relevant components of your cloud service offering?
+    - id: STA-04
+      name: Provider Internal Assessments
+      specification: The provider shall perform annual internal assessments of conformance and effectiveness of its policies, procedures, and supporting measures and metrics.
+      questions:
+      - id: STA-04.1
+        content: Do you perform annual internal assessments of conformance and effectiveness of your policies, procedures, and supporting measures and metrics?
+    - id: STA-05
+      name: Third Party Agreements
+      specification: |-
+        Supply chain agreements (e.g., SLAs) between providers and customers (tenants) shall incorporate at least the following mutually-agreed upon provisions and/or terms:
+         • Scope of business relationship and services offered (e.g., customer (tenant) data acquisition, exchange and usage, feature sets and functionality, personnel and infrastructure network and systems components for service delivery and support, roles and responsibilities of provider and customer (tenant) and any subcontracted or outsourced business relationships, physical geographical location of hosted services, and any known regulatory compliance considerations)
+         • Information security requirements, provider and customer (tenant) primary points of contact for the duration of the business relationship, and references to detailed supporting and relevant business processes and technical measures implemented to enable effectively governance, risk management, assurance and legal, statutory and regulatory compliance obligations by all impacted business relationships
+         • Notification and/or pre-authorization of any changes controlled by the provider with customer (tenant) impacts
+         • Timely notification of a security incident (or confirmed breach) to all customers (tenants) and other business relationships impacted (i.e., up- and down-stream impacted supply chain)
+         • Assessment and independent verification of compliance with agreement provisions and/or terms (e.g., industry-acceptable certification, attestation audit report, or equivalent forms of assurance) without posing an unacceptable business risk of exposure to the organization being assessed
+         • Expiration of the business relationship and treatment of customer (tenant) data impacted
+         • Customer (tenant) service-to-service application (API) and data interoperability and portability requirements for application development and information exchange, usage, and integrity persistence
+      questions:
+      - id: STA-05.1
+        content: Do you select and monitor outsourced providers in compliance with laws in the country where the data is processed, stored, and transmitted?
+    - id: STA-06
+      name: Supply Chain Governance Reviews
+      specification: Providers shall review the risk management and governance processes of their partners so that practices are consistent and aligned to account for risks inherited from other members of that partner's cloud supply chain.
+      questions:
+      - id: STA-06.1
+        content: Do you review the risk management and governanced processes of partners to account for risks inherited from other members of that partner's supply chain?
+    - id: STA-07
+      name: Supply Chain Metrics
+      specification: Policies and procedures shall be implemented to ensure the consistent review of service agreements (e.g., SLAs) between providers and customers (tenants) across the relevant supply chain (upstream/downstream). Reviews shall be performed at least annually and identify non-conformance to established agreements. The reviews should result in actions to address service-level conflicts or inconsistencies resulting from disparate supplier relationships.
+      questions:
+      - id: STA-07.1
+        content: Are policies and procedures established, and supporting business processes and technical measures implemented, for maintaining complete, accurate, and relevant agreements (e.g., SLAs) between providers and customers (tenants)?
+      - id: STA-07.2
+        content: Do you have the ability to measure and address non-conformance of provisions and/or terms across the entire supply chain (upstream/downstream)?
+      - id: STA-07.3
+        content: Can you manage service-level conflicts or inconsistencies resulting from disparate supplier relationships?
+      - id: STA-07.4
+        content: Do you review all agreements, policies, and processes at least annually?
+    - id: STA-08
+      name: Third Party Assessment
+      specification: Providers shall assure reasonable information security across their information supply chain by performing an annual review. The review shall include all partners/third party providers upon which their information supply chain depends on.
+      questions:
+      - id: STA-08.1
+        content: Do you assure reasonable information security across your information supply chain by performing an annual review?
+      - id: STA-08.2
+        content: Does your annual review include all partners/third-party providers upon which your information supply chain depends?
+    - id: STA-09
+      name: Third Party Audits
+      specification: Third-party service providers shall demonstrate compliance with information security and confidentiality, access control, service definitions, and delivery level agreements included in third-party contracts. Third-party reports, records, and services shall undergo audit and review at least annually to govern and maintain compliance with the service delivery agreements.
+      questions:
+      - id: STA-09.1
+        content: Do you permit tenants to perform independent vulnerability assessments?
+      - id: STA-09.2
+        content: Do you have external third party services conduct vulnerability scans and periodic penetration tests on your applications and networks?
+  - id: LG
+    name: Supply Chain Management, Transparency, and Accountability
+    controls:
+    - id: LG-02
+      name: Third Party Agreements
+      specification: |-
+        Supply chain agreements (e.g., SLAs) between providers and customers (tenants) shall incorporate at least the following mutually-agreed upon provisions and/or terms:
+         • Scope of business relationship and services offered (e.g., customer (tenant) data acquisition, exchange and usage, feature sets and functionality, personnel and infrastructure network and systems components for service delivery and support, roles and responsibilities of provider and customer (tenant) and any subcontracted or outsourced business relationships, physical geographical location of hosted services, and any known regulatory compliance considerations)
+         • Information security requirements, provider and customer (tenant) primary points of contact for the duration of the business relationship, and references to detailed supporting and relevant business processes and technical measures implemented to enable effectively governance, risk management, assurance and legal, statutory and regulatory compliance obligations by all impacted business relationships
+         • Notification and/or pre-authorization of any changes controlled by the provider with customer (tenant) impacts
+         • Timely notification of a security incident (or confirmed breach) to all customers (tenants) and other business relationships impacted (i.e., up- and down-stream impacted supply chain)
+         • Assessment and independent verification of compliance with agreement provisions and/or terms (e.g., industry-acceptable certification, attestation audit report, or equivalent forms of assurance) without posing an unacceptable business risk of exposure to the organization being assessed
+         • Expiration of the business relationship and treatment of customer (tenant) data impacted
+         • Customer (tenant) service-to-service application (API) and data interoperability and portability requirements for application development and information exchange, usage, and integrity persistence
+      questions:
+      - id: STA-05.2
+        content: Do you select and monitor outsourced providers in compliance with laws in the country where the data originates?
+      - id: STA-05.3
+        content: Does legal counsel review all third-party agreements?
+      - id: STA-05.4
+        content: Do third-party agreements include provision for the security and protection of information and assets?
+      - id: STA-05.5
+        content: Do you provide the client with a list and copies of all subprocessing agreements and keep this updated?
+  - id: TVM
+    name: Threat and Vulnerability Management
+    controls:
+    - id: TVM-01
+      name: Antivirus / Malicious Software
+      specification: Policies and procedures shall be established, and supporting business processes and technical measures implemented, to prevent the execution of malware on organizationally-owned or managed user end-point devices (i.e., issued workstations, laptops, and mobile devices) and IT infrastructure network and systems components.
+      questions:
+      - id: TVM-01.1
+        content: Do you have anti-malware programs that support or connect to your cloud service offerings installed on all of your systems?
+    - id: TVM-02
+      name: Vulnerability / Patch Management
+      specification: Policies and procedures shall be established, and supporting processes and technical measures implemented, for timely detection of vulnerabilities within organizationally-owned or managed applications, infrastructure network and system components (e.g., network vulnerability assessment, penetration testing) to ensure the efficiency of implemented security controls. A risk-based model for prioritizing remediation of identified vulnerabilities shall be used. Changes shall be managed through a change management process for all vendor-supplied patches, configuration changes, or changes to the organization's internally developed software. Upon request, the provider informs customer (tenant) of policies and procedures and identified weaknesses especially if customer (tenant) data is used as part the service and/or customer (tenant) has some shared responsibility over implementation of control.
+      questions:
+      - id: TVM-02.1
+        content: Do you conduct network-layer vulnerability scans regularly as prescribed by industry best practices?
+    - id: TVM-03
+      name: Mobile Code
+      specification: Policies and procedures shall be established, and supporting business processes and technical measures implemented, to prevent the execution of unauthorized mobile code, defined as software transferred between systems over a trusted or untrusted network and executed on a local system without explicit installation or execution by the recipient, on organizationally-owned or managed user end-point devices (e.g., issued workstations, laptops, and mobile devices) and IT infrastructure network and systems components.
+      questions:
+      - id: TVM-03.1
+        content: Is mobile code authorized before its installation and use, and the code configuration checked, to ensure that the authorized mobile code operates according to a clearly defined security policy?