vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If you included the resource metadata in your source repository, the information is parsed during validation and pulled into a starting cost per hour (USD) summary table. The table is displayed in the catalog for customers to compare across variations of a deployable architecture or to get a general idea of what a base configuration of your deployable architecture might cost.

The summary table lists the resources that your product uses and their estimated costs. Starting cost is an estimate based on available data. It does not include all resources, usage, license, fees, discounts, or taxes.





 Managing compliance 

You can add controls to your deployable architecture to prove that it meets security and compliance requirements.

Before you can add controls to your product, you must choose a predefined profile or add your controls to a custom IBM Cloud® Security and Compliance Center profile. Then, scan the resources in your account that match those the deployable architecture creates to verify. For more information, see [What is a profile?](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-profiles)

Only controls that are supported by the Security and Compliance Center and validated by Security and Compliance Center scans appear in the catalog.



 Adding compliance controls by using the console 

You must include compliance information in your catalog manifest JSON file to add profiles and controls to your product. For more information, see [Specifying product metadata for onboarding a product to a private catalog](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-manifest).





 Adding compliance controls by using the CLI 

You must include compliance information in your catalog manifest JSON file to add profiles and controls to your product. To see the steps, see [Adding compliance controls by using the console](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-onboard-custom&interface=uicustom-tf-add-controls-ui).





 Applying Security and Compliance Center scans by using the console 

Add the scans that you previously ran in the Security and Compliance Center. Security and Compliance Center scans determine adherence to regulatory controls.
Managing security groups 

You can manage security groups by using the Security page or your device details page in the IBM Cloud® console.

For more information about managing security groups, see [Managing security groups](https://cloud.ibm.com/docs/security-groups?topic=security-groups-managing-sgmanaging-sg).
If you have an app that runs with root permissions, you must modify your deployment to work with the [security context constraints](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_scc) that are set for your Red Hat OpenShift cluster. For example, you might set up your project with a service account to control privileged access, and then modify your deployment to use this service account.

Before you begin: [Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).



1. As a cluster administrator, create a project.

oc adm new-project <project_name>
2. Target the project so that the subsequent resources that you create are in the project namespace.

oc project <project_name>
3. Create a service account for the project.

oc create serviceaccount <sa_name>
4. Add a privileged security context constraint to the service account for the project. If you want to check what policies are in the privileged SCC, run oc describe scc privileged. For more information about SCCs, see the [Red Hat OpenShift documentation](https://docs.openshift.com/container-platform/4.11/authentication/managing-security-context-constraints.html).

oc adm policy add-scc-to-user privileged -n <project_name> -z <sa_name>
5. In your deployment configuration file, refer to the privileged service account and set the security context to privileged.



* In spec.template.spec, add serviceAccount: <sa_name>.
* In spec.template.spec.containers, add securityContext: privileged: true.



Example

apiVersion: apps/v1
kind: Deployment
metadata:
name: myapp_deployment
labels:
app: myapp
spec:
...
template:
...
spec:
serviceAccount: <sa_name>
containers:
Provisioning Citrix DaaS for IBM Cloud on Virtual Private Cloud 

Use this task to provision your Citrix DaaS for IBM Cloud® solution on IBM® Virtual Private Cloud. This task corresponds to the provisioning form that you see when you select the VPC tile from the Citrix DaaS for IBM Cloud page. Provisioning uses Schematics to provision your resources. For more information about Schematics, see [Schematics, IBM Cloud’s deployment manager](https://cloud.ibm.com/schematics/overview).



 What is provisioned 

When you provision Citrix DaaS for IBM Cloud on VPC, you receive the following components in each zone:



 Size Lite Standard Enterprise 

 VPC 1 1 1 
 Subnet (256 IP addresses) 1 x /24 1 x /24 1 x /24 
 Public Gateway 1 1 1 
 Floating IP 1 1 1 
 Active Directory VSI 1 1 1 
 Cloud Connector VSIs 1 <br><br>[1] 2 3 
 Master Image VSI <br><br>[2] 1 1 1 
 VDA VSI 1 1 1 
 Custom Image VSI (optional) 1 1 1 
 Security Groups<br><br><br><br> * Active Directory Security Group<br> * Cloud Connector Security Group<br> * VDAs Security Group<br> * Master Image Security Group (VSI deployed during Citrix Machine Catalog creation)<br> * Custom Image Security Group (optional)<br><br><br> 4 (5 if Custom Image VSI deployed) 4 (5 if Custom Image VSI deployed) 4 (5 if Custom Image VSI deployed) 
 Volume Worker n/a n/a <br><br> * 1 IBM Cloud Databases for Redis with 2G RAM 4G of storage<br> * IBM Cloud Functions instance<br> * 1 Cloud Object Storage bucket<br><br><br> 



Lite is for testing and proof of concept, not production.

Citrix DaaS for IBM Cloud solutions on VPC do not require extra configuration for monitoring, storage, networking, or high availability.

All of the servers and virtual desktops are provisioned in the IBM® private network.
23 June 2021 

Review the release notes for 23 June 2021.

CLI version 1.10.0 released.
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).

Updated app and app revision quotas for projects.
: The quota is revised to 20 apps per project and 60 revisions for all apps per project. See [Limits and quotas for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limitsproject_quotas).

Added basic troubleshooting information.
: See [Troubleshooting overview](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshooting_over).

IBM Cloud and third-party integrations
: Find out what IBM Cloud and third-party integrations are supported by Code Engine. See [Supported IBM Cloud and third-party integrations](https://cloud.ibm.com/docs/codeengine?topic=codeengine-supported-integrations).

Added information about security and Code Engine.
: See [Code Engine and security](https://cloud.ibm.com/docs/codeengine?topic=codeengine-secure).

Updated versions for buildpacks.
: See [Choosing a build strategy](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-strategy).





 16 June 2021 

Review the release notes for 16 June 2021.

CLI version 1.9.0 released.
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).

Build size
: Updated the size for xlarge builds to 4 CPU and 16 GB. See [Determine the size of the build](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-size).
* For more information see [What's new in MQ 9.1.2](https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.1.0/com.ibm.mq.pro.doc/q132380_.htm)









 9.1.1 r2 



 Available from 5th February 2019 to 22nd April 2019 



* Required security and vulnerability fixes.
* Reduced queue manager deploy time.
* Improved resilience and performance when authenticating clients.









 9.1.1 r1 



 Available from 2nd January 2019 to 5th March 2019 



* Update to MQ version 9.1.1
* For more information see [What's new in MQ 9.1.1](https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.1.0/com.ibm.mq.pro.doc/q132240_.htm)









 9.1.0 r2 



 Available from 9th August 2018 to 6th February 2019 



* Required security and vulnerability fixes.
* Enable the ability to set up certificates on queue managers so that TLS and AMS can be configured.









 9.1.0 r1 



 Available from 20th July 2018 to 11th September 2018 



* Update to MQ version 9.1.0
* For more information see [What's new in MQ 9.1](https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.1.0/com.ibm.mq.pro.doc/q113110_.htm)
* Note on the release model for IBM MQ on Cloud:



* The MQ on Cloud service follows the "Continuous Delivery" (CD) model which means that all queue managers (including those deployed on MQ v9.1.0) will be upgraded to the next CD version within a defined period of time after the next CD version becomes available.
* In particular the MQ on Cloud service treats MQ v9.1.0 as a CD version and not a "Long Term Support" (LTS) version.











 9.0.5 r2
If you would like to retain a long-term record of activity within your App Configuration instance, either for audit purposes or for post-processing and data analysis, including application of machine learning models, create an instance of IBM Cloud Activity Tracker from the [Observability](https://cloud.ibm.com/observe) section of the IBM Cloud console. Then archive events from an IBM Cloud Activity Tracker instance into a bucket in an IBM Cloud Object Storage (COS) instance. [Learn more](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-archiving).
* In what regions is App Configuration available?

To see a list of IBM Cloud regions where you can provision instances of App Configuration, see the [App Configuration About](https://cloud.ibm.com/catalog/services/app-configurationabout) page in the IBM Cloud catalog.
* Is App Configuration a highly available service?

Yes. App Configuration is designed as a high availability service designed for enterprise workloads, and conforming to the [App Configuration Service Description](https://www.ibm.com/support/customer/csol/terms/?id=i126-8986detail-documentand) and the [IBM Cloud Service Level Agreement](https://cloud.ibm.com/docs/overview?topic=overview-slas) for availability. Within a single region, App Configuration is deployed across a multi-zone cluster.
* Is App Configuration secure?

Yes. While App Configuration is not designed as a vault for secrets (use IBM Cloud Secrets Manager instead), the service itself adheres to strict security guidelines in the development process and in securing and protecting your data. The development process includes things like vulnerability scanning and remediation, periodic penetration testing, and frequent security reviews by world-class security experts. The data in App Configuration is encrypted by default both in transit and at rest. (See the App Configuration Data Processing and Protection data sheet to learn more). Additionally, you secure access to your own instances of App Configuration by using IBM Cloud Identity and Access Management (IAM). You can use IBM Cloud Security and Compliance Center for ongoing security monitoring and alerts for your App Configuration instances.
What if the Persistent Volume Claim (PVC) goes into pending state after installing Data Security Broker Manager? 

After you install Data Security Broker Manager, sometimes the PVC goes into pending state as shown below:

NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE dsb-manager-pvc Pending ibmc-block-bronze 3m30s dsb-mongodb-pvc Pending ibmc-block-bronze 3m29s



*  Create a YAML file and deploy the YAML file in the Kubernetes cluster, where you have installed the Data Security Broker Manager.



Example:

A sample YAML for PVC of Data Security Broker Manager:

apiVersion: v1
kind: PersistentVolume
metadata:
name: pvc-dsb-manager
spec:
accessModes:
- ReadWriteOnce
capacity:
storage: 20Gi
flexVolume:
driver: ibm/ibmc-block
fsType: ext4
persistentVolumeReclaimPolicy: Delete
storageClassName: ibmc-block-bronze
volumeMode: Filesystem

A sample YAML for PVC of Data Security Broker MangoDB:

apiVersion: v1
kind: PersistentVolume
metadata:
name: pvc-dsb-mongo
spec:
accessModes:
- ReadWriteOnce
capacity:
storage: 20Gi
flexVolume:
driver: ibm/ibmc-block
fsType: ext4
persistentVolumeReclaimPolicy: Delete
storageClassName: ibmc-block-bronze
volumeMode: Filesystem
[Using Hyper Protect Crypto Services as PKCS #11 HSMs](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-uko-use-casesuko-pkcs11_hsm)

[Using Hyper Protect Crypto Services as Enterprise PKCS #11 HSMs](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-uko-use-casesuko-ep11-hsm)
* [What's next](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-uko-use-casesuko-use-case-next)



[Security and compliance - Unified Key Orchestrator Plan](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-uko-security-and-complianceuko-security-and-compliance)



* [Security readiness](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-uko-security-and-complianceuko-security-ready)
* [Compliance readiness](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-uko-security-and-complianceuko-compliance-ready)



[Components and concepts - Unified Key Orchestrator Plan](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-uko-understand-conceptsuko-understand-concepts)



* [Key management service](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-uko-understand-conceptsuko-key-management-concepts)
* [Cloud hardware security module](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-uko-understand-conceptsuko-cloud-hsm-concepts)
"expirationDate": "2019-04-08T17:18:29Z",
"maxAllowedRetrievals": 1,
"remainingRetrievals": 0,
"payload": "Rm91ciBzY29yZSBhbmQgc2V2ZW4geWVhcnMgYWdv",
"nonce": "8zJE9pKVdXVe/nLb"
}

The response body also contains the public encryption key that you can use to [encrypt a root key](https://cloud.ibm.com/docs/key-protect?topic=key-protect-importing-keysusing-import-tokens) before you upload the key material to a Key Protect instance.

In the example, the payload value represents the public key that is associated with the import token. This value is base64 encoded. For extra security, Key Protect also provides a nonce value that is used to verify the originality of a key import request to the service. To learn more about how to use these values, check out [Tutorial: Creating and importing encryption keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-tutorial-import-keys).





 What's next 



* To find out more about using an import token to securely bring encryption keys to IBM Cloud, check out [Importing root keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-import-root-keys).
* For a guided tutorial on using import tokens in Key Protect, see [Tutorial: Creating and importing encryption keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-tutorial-import-keys).
* Tutorial: [Apply end to end security to a cloud application](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-cloud-e2e-security)
* Tutorial: [Best practices for organizing users, teams, applications](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-users-teams-applications)
* Blog: [Cloud App Security: What Makes a Secure App?](https://www.ibm.com/cloud/blog/cloud-app-security)
* Blog: [Onboarding Cloud Projects: Security and Resource Considerations](https://www.ibm.com/cloud/blog/onboarding-cloud-projects-security-and-resource-considerations)
* Blog: [Use Your FIDO2 Key for 2FA on IBM Cloud Apps](https://www.ibm.com/cloud/blog/use-your-fido2-key-for-2fa-on-ibm-cloud-apps)
* Blog: [Going Passwordless on IBM Cloud Thanks to FIDO2](https://www.ibm.com/cloud/blog/going-passwordless-on-ibm-cloud-thanks-to-fido2)
* Blog: [IBM Cloud Security Hands-On: Share Your Chatbot Project](https://www.ibm.com/cloud/blog/share-your-chatbot-project)
* Blog: [Increase Information Security for Db2 on IBM Cloud](https://www.ibm.com/cloud/blog/increase-information-security-for-db2-on-ibm-cloud)
* IBM Architecture Center: [Security to safeguard and monitor your cloud apps](https://www.ibm.com/cloud/architecture/architectures/securityArchitecture)
* [IBM Cloud platform service CLIs and APIs](https://cloud.ibm.com/docs/overview?topic=overview-platform-svc-cli-api)
* [IBM Cloud Compliance Programs](https://www.ibm.com/cloud/compliance)
For more information about managing tags for your account, see [Working with tags](https://cloud.ibm.com/docs/account?topic=account-tag&interface=ui).







 Managing security and compliance 

Block Storage for VPC is integrated with the Security and Compliance Center to help you manage security and compliance for your organization. You can set up goals that check whether volumes are encrypted by using customer-managed keys. By using the Security and Compliance Center to validate the Block Storage for VPC configurations in your account against a profile, you can identify potential issues as they arise.

For more information about monitoring security and compliance for VPC, see [Monitoring security and compliance posture with VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-manage-security-compliancemonitor-vpc). For more information about creating security and compliance goals, see [Defining rules](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-rules-define&interface=ui) in the Security and Compliance documentation.





 Cancelling your Block Storage for VPC 

If you no longer need a volume, you can cancel it at any time. IBM [wipes all data](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storageblock-storage-data-eradication) before the storage is reused. If you have extra compliance requirements such as NIST 800-88 Guidelines for Media Sanitization, you must perform data sanitation procedures before you delete your volumes. For more information, see [Sanitize your data before you delete a volume](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-block-storageblock-storage-sanitization).





 Next steps 

Create your Block Storage for VPC volumes.



* For more information about creating a volume during instance provisioning, see [Create and attach a Block Storage for VPC volume when you create an instance](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-block-storagecreate-from-vsi).
In a connected world, security is more important than ever, and we've built it right into the platform [Click Menu icon > Security and Compliance]. With the IBM Cloud Security and Compliance Center [Click Dashboard], you can set up a unified dashboard to monitor security and compliance, govern configuration, and gain insights into threats.

If you prefer to work from the command line [Click IBM Cloud Shell menu item], you can manage your IBM Cloud account and resources from your browser with IBM Cloud Shell. Just open Cloud Shell to start using the IBM Cloud CLI and tons of other plug-ins, tools, and runtimes with no installation needed.

If you run into any questions as you're working in IBM Cloud, visit the Support Center [Click Support menu option], where you'll find FAQs and common tasks that can help you to resolve your issue quickly without even having to contact IBM Cloud. However, if you do need to get in touch with us or open a support case, those options are also available to you.

For in-depth information about how to get up and running in IBM Cloud, visit the docs [Click Docs menu item > Develop tab]. Explore key topics by use case or browse through our library of tutorials that range from quick start guides to advanced solution tutorials [Click Deploy tab > Tutorials tab].

For more guidance, check out the full product docs [Click All product docs tab] or API & SDK reference libraries [Click API & SDK reference tab]. Or, browse our FAQ library to get answers to common questions about IBM Cloud's products and services [Click FAQs tab, and expand the What is Master Data Management? entry].

Now that you know how to navigate through the IBM Cloud user interface to get your account set up, create resources from the catalog, and find help through support and docs, it's time get coding or building your infrastructure!







 Using the console 

When you log in to IBM Cloud, your dashboard is displayed, which shows widgets that summarize the status of your account. If you're interested in customizing your dashboard, see [Working with scoped dashboards](https://cloud.ibm.com/docs/account?topic=account-custom-dashboard).
IBM Cloud Activity Tracker Event Routing 

Use IBM Cloud Activity Tracker Event Routing to configure how to route auditing events, both global and location-based event data, in your IBM Cloud account. Audit events are critical data for security operations and a key element for meeting compliance requirements. Control of the storage location is critical to building enterprise-grade solutions.

 Developer tools 

[API & SDK reference](https://cloud.ibm.com/apidocs/atracker)[CLI reference](https://cloud.ibm.com/docs/atracker-cli-plugin?topic=atracker-cli-plugin-atracker-cli-overview)[Terraform reference](https://cloud.ibm.com/docs/atracker?topic=atracker-atracker-tf-config)

 Recommended content 

[Understanding IBM Cloud Activity Tracker Event Routing Learn about how to manage auditing events by using IBM Cloud Activity Tracker](https://cloud.ibm.com/docs/atracker?topic=atracker-about)[Getting started with Activity Tracker Event Routing Use the Activity Tracker CLI to configure your account to manage auditing events.](https://cloud.ibm.com/docs/atracker?topic=atracker-getting-started)[Planning your environment Plan how to configure the account to manage auditing events.](https://cloud.ibm.com/docs/atracker?topic=atracker-planning)[See what's new Read about the latest changes to IBM Cloud Activity Tracker Event Routing. ](https://cloud.ibm.com/docs/atracker?topic=atracker-activity-tracker-release-notes)[Find out which IBM Cloud services are onboarded Learn about the IBM Cloud services that you can monitor in your account and the actions that they report on.](https://cloud.ibm.com/docs/atracker?topic=atracker-cloud_services_atracker&interface=cli)[Looking for compliance with Financial Services (FS)?
Security compliances 

IBM® Db2® Warehouse on Cloud is provided on secure IBM Cloud® and Amazon Web Services platforms. Db2 managed services comply with the specific security standards and auditing processes that are listed here and do not automatically inherit general IBM Cloud security compliances that are documented for IaaS, PaaS, and SaaS cloud offerings.

For details about each of the security compliances, see [Details about security compliance](https://www.ibm.com/support/knowledgecenter/SS6NHC/com.ibm.swg.im.dashdb.security.doc/doc/compliances.html).



Table 1. Summary of security compliances for the Flex service offering plans

 IBM® Db2® Warehouse on Cloud Flex offering plans HIPAA ISO SOC 2 Type 2 GDPR Privacy shield 

 Flex One on IBM Cloud ![checkmark](https://cloud.ibm.com/docs-content/v1/content/68e10678b2f8b8694884ecb5442c326c9b60a3fb/Db2whc/images/checkmark.png) ![checkmark](https://cloud.ibm.com/docs-content/v1/content/68e10678b2f8b8694884ecb5442c326c9b60a3fb/Db2whc/images/checkmark.png) ![checkmark](https://cloud.ibm.com/docs-content/v1/content/68e10678b2f8b8694884ecb5442c326c9b60a3fb/Db2whc/images/checkmark.png) ![checkmark](https://cloud.ibm.com/docs-content/v1/content/68e10678b2f8b8694884ecb5442c326c9b60a3fb/Db2whc/images/checkmark.png) !