vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Compliance 

Compliance is a set of requirements necessary to meet the minimum controls established by either a regulatory agency or industry best practices. Regularity compliance frameworks are usually broad frameworks that provide guidance on a broad range of technology, whereas industry best practices from vendors are typically technology specific to address technological risks.

For your vCenter Server® instance, it is recommended that security is managed by using a dedicated team post-deployment. This separation of duties augments and monitors the security posture of your instance. Entrust CloudControl™ can assist your teams with role-based separation.

Entrust DataControl® and KeyControl™ can assist you in delivering workload protection such as at-rest encryption and geo-fencing. You might be interested in deploying the Caveonix RiskForesight™ service to assist you in, not only your compliance requirements but also cyber-risk and forensic management.

The VMware Security Hardening Guides provide prescriptive guidance on how to deploy and operate VMware products in a secure manner. Guides for vSphere are provided in an easy to use spreadsheet format, with rich metadata to allow for guideline classification and risk assessment. They also include script examples for enabling security automation. Comparison documents are provided if the list changes in guidance in successive versions of the guide.

Many of the controls that are documented in the VMware® Security Hardening Guides are incorporated in the IBM Cloud® for VMware Solutions reference architecture and therefore, automatically deployed, ensure that you tailor the security posture of the platform to your own needs and enterprise policy. The VMware Security Hardening Guides provide the technology-specific controls that are required for you to complete this review. Caveonix RiskForesight automates this compliance task and provides additional regulatory agency guidance.

VMware Aria® Operations™ Manager provides monitoring of VMware objects for violations against the compliance rules in the vSphere Security Configuration Guide. The compliance alerts trigger on the vCenter Server instance, hosts, virtual machines, distributed port groups, or distributed switches, allowing the investigation of the compliance violation.
For more information see, [Alerts](https://cloud.ibm.com/docs/monitoring?topic=monitoring-monitoring).

When a storage volume is down, your app pods that are using storage have a low file system I/O, have network errors, or crash which causes the replica count to go down. You can set up alerts in IBM Cloud Monitoring to get notified if the file system operations for your app drop under a specific threshold, if network errors occur, or if your app pods don't reach a Ready state.



1. From the [Kubernetes clusters console](https://cloud.ibm.com/kubernetes/clusters), select the cluster where you want to set up alerts for your storage volumes.
2. In the Monitoring section, click Connect to connect an existing IBM Cloud Monitoring instance to your cluster. If you don't have an instance, click Create an instance to create one. For more information about how to set up an IBM Cloud Monitoring instance, see [Provisioning an instance](https://cloud.ibm.com/docs/monitoring?topic=monitoring-provision).
3. Click the Launch button to open the IBM Cloud Monitoring dashboard.
4. Create file system utilization alerts for an app that runs in your cluster.



1. From the IBM Cloud Monitoring console, click Overview > Workloads.
2. Select the Namespace where your app is deployed. Find your app, click the arrow icon on your app, and select Kubernetes Pod overview.
3. In the File System Utilization section, review the File I/O Bandwidth by Pod tile.
4. Review the file I/O bandwidth from the last day or week time window to determine the average bandwidth. You can use the average bandwidth as a threshold to set an alert for when the file I/O bandwidth is less than the average for a certain amount of time. For example, if the average file I/O bandwidth for your app is 300B/s, you can create an alert for when the network utilization remains less than 300B/s for a certain amount of time.
5.
The CA is now ready to be used to register and enroll identities.

As with the peer, we need to register two identities, one for the ordering service admin and one for the ordering service nodes.

First up will be the ordering service admin. We'll give it an enroll id of OSadmin and a secret of OSadminpw. This is an admin so we use the admin type, not the peer, orderer, or client type. As before, use the default affiliations and ignore the enrollments and attributes.

Now we can register the identity of our ordering node. In this tutorial, we’ll create a single node Raft ordering service. This configuration is not considered ideal for production because it is not highly available, but it is sufficient to get started. We’ll use an enroll id of OS1 and a secret of OS1pw. As this is an ordering node, use the orderer type, and once again use the default affiliations and attributes.

Now that we have the CA and have used it to register identities we can create the definition of the ordering service organization, which we do by clicking the Organizations tab and then create MSP definition. The display name for this msp will be called Ordering Service MSP, while the MSP ID will be osmsp. Our CA here is the ordering service CA, not the Org1 CA. Then give the enroll id and secret of the admin of your ordering service organization, OSadmin and OSadminpw. Do not use any default value that might be here. Then give this identity the name Ordering Service MSP Admin. Then click generate. That will create the identity. And then export it to your machine. Then click create the MSP definition. You should see the Ordering Service MSP. And if you look in your wallet you should now see the Ordering Service MSP Admin identity we just created.

Now that we have the msp and the identities that we need we can go back and create our ordering service. Click the add orderer tile and specify that you’re creating an ordering service. On the next panel, give this ordering service the name Ordering Service.
Download Location /home/ibmuser/Downloads
CRN 8f275e7b-c076-49e2-b9c5-f985704cf678
AccessKeyID 9eib1eejar6HaezaohveV5hikei4aNg2ooV0qu
SecretAccessKey 
Authentication Method IAM
URL Style VHost



 IAM Authentication 

If you are using IAM authentication, then you then you must configure your client with an instance ID to use some of the commands. To retrieve the instance ID you can type ibmcloud resource service-instance <INSTANCE_NAME> --id, replace <INSTANCE_NAME> with the unique alias that you assigned to your service instance. In the below examples, the 8f275e7b-c076-49e2-b9c5-f985704cf678 value is an example instance ID.

First, retrieve the CRN and id with the name of your instance. Be sure to use quotes (') on your instance name and that you are logged in to IBM Cloud. Only the last piece of the CRN is needed, the part after ::.

$ ibmcloud resource service-instance 'My Awesome Cloud Object Storage' --id
Retrieving service instance My Awesome Cloud Object Storage in all resource groups under account IBM as ibmuser@us.ibm.com...
crn:v1:bluemix:public:cloud-object-storage:global:a/94400e98c553415c9599db39b9be9219:3b7d66c8-9fdf-4f81-b7e6-08d187f07288:: 8f275e7b-c076-49e2-b9c5-f985704cf678

Set the CRN with the ibmcloud cos config crn command. It may warn you about overwriting. If you don't want to provide the CRN interactively, you can provide it on the same command with the --crn flag.
Become an MQ expert and prove your knowledge with the [official IBM MQ developer badge](https://developer.ibm.com/components/ibm-mq/series/badge-ibm-mq-developer-essentials), you will be able to work your way through some tutorials and learn all MQ fundamentals as well as some more in depth knowledge of creating applications that can utilise MQ to communicate.





 Administering an MQ on Cloud queue manager 

MQ on Cloud allows you to use all of the traditional MQ administration tools, including a web based version of the MQ Console. You can find instructions on how to use the console [here](https://cloud.ibm.com/docs/mqcloud?topic=mqcloud-mqoc_admin_mqweb)

MQ on Cloud can be administered via locally installed tools too. MQ Explorer is a locally installed Eclipse-based tool for administering IBM MQ which you can install on a machine of your choosing, it connects to MQ on Cloud using a client connection and is supported on both Windows and Linux based environments.

You can also use the runmqsc Command Line Interface to administer MQ on Cloud queue managers. The CLI enables the ability to create scripts containing groups of MQ commands so that many different tasks can be carried out at the same time. It can be installed as part of the MQ clients bundle and is available on Windows and Linux. You can learn more about using MQ Explorer or the CLI to administer your queue manager [here](https://cloud.ibm.com/docs/mqcloud?topic=mqcloud-mqoc_admin_mqcliexp)
Events for is.share.target.create, is.share.target.list, is.share.target.read, is.share.target.delete, and is.share.target.update are deprecated and will be removed in a future API release per the VPC beta API [versioning policy](https://cloud.ibm.com/apidocs/vpc-betaapi-versioning-beta).





 19 May 2023 

Removal of weak VPN for VPC ciphers
: Effective 18 May 2023, the following VPN IKE and IPsec ciphers are now removed:



* Authentication algorithms md5 and sha1
* Encryption algorithm triple_des
* Diffie–Hellman groups 2 and 5



After this date, you cannot create an IKE/IPsec policy or connection that includes a weak cipher, but you can still [upgrade weak cipher suites](https://cloud.ibm.com/docs/vpc?topic=vpc-upgrading-weak-ciphers&interface=ui) on an existing policy or connection. Starting 10 July 2023, any existing connections with customized IKE or IPsec policies that contain weak ciphers will be disabled, and any connections with auto IKE or IPsec policies that were created before September 20, 2022 will be forced to upgrade to the [enhanced auto-negotiation policy](https://cloud.ibm.com/docs/vpc?topic=vpc-using-vpnpolicy-negotiation).





 11 May 2023 

IBM Hyper Protect Container Runtime image ibm-hyper-protect-container-runtime-1-0-s390x-10
: For the IBM Hyper Protect Container Runtime image version ibm-hyper-protect-container-runtime-1-0-s390x-10, new certificates are available.



* [Attestation certificate](https://cloud.ibm.com/media/docs/downloads/hyper-protect-container-runtime/ibm-hyper-protect-container-runtime-1-0-s390x-10-attestation.crt)
Managing data 

To ensure that you can securely manage your data when you use IBM Cloud Monitoring, it is important to know exactly what data is stored and encrypted, and how you can delete any stored personal data.



 How your data is collected in IBM Cloud Monitoring 

When you configure a monitoring agent to collect and forward data to an IBM Cloud Monitoring instance, data is automatically collected and available for analysis through the web UI. You can configure the monitoring agent to connect to the monitoring instance via the public network or the private network.

To connect to resources in your account over the IBM Cloud public network, you can configure an agent to send metrics by using a public endpoint. The environment where the agent is running requires internet access to use the public endpoint.

You can enable virtual routing and forwarding (VRF) to move IP routing for your account and all of its resources into a separate routing table. If VRF is enabled, you can then enable IBM Cloud service endpoints to connect directly to resources without using the public network. To configure an agent to send metrics by using a private endpoint, you must [enable virtual routing and forwarding (VRF)](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpoint) for your account. Once the account is VRF enabled, the monitoring agent can be configured to use the private network by using the [Private Endpoint](https://cloud.ibm.com/docs/monitoring?topic=monitoring-endpointsendpoints_ingestion) as the ingestion URL.



* Private endpoints are not accessible from the public internet.
* All traffic is routed to the IBM Cloud private network.



monitoring agent data is collected at 10-seconds frequency. Data that is published by platform metrics is collected on a 1-minute frequency.



 Captures 

In IBM Cloud Monitoring, you can also enable captures when you configure a monitoring agent. A capture is a trace file that you can use to analyze what happens in a host during a time frame.



* Captures contain system calls, and other OS events.
To ensure your clients will work reliably in the future, check that the new instance_groups_supported property on the [load balancer](https://cloud.ibm.com/apidocs/vpcget-load-balancer) is true before specifying that load balancer or one of its pools.







 13 June 2023 



 For all version dates 

VPC routing table authorizations. You can use the new VPC routing table authorizations to allow users to administer VPC routing tables but not allow them to administer the broader VPC. The VPC API methods that operate on routing tables have been updated to check for these new authorizations, instead of the broader VPC authorizations. The VPC Administrator, Editor, Operator, and Viewer IAM access roles have been updated so that users with those roles will function as before. However, custom roles that require access to routing tables must be updated. For more information, see [IAM actions for VPC routing tables](https://cloud.ibm.com/docs/vpc?topic=vpc-iam-actions-vpc-routing-tables).







 23 May 2023 



 For all version dates 

Removal of weak VPN for VPC ciphers. Effective 18 May 2023, the following VPN IKE and IPsec ciphers are removed:



* Authentication algorithms md5 and sha1
* Encryption algorithm triple_des
* Diffie–Hellman groups 2 and 5



As a result, you will no longer be able to create an IKE/IPsec policy or VPN connection that includes a weak cipher, but you can still [upgrade weak cipher suites](https://cloud.ibm.com/docs/vpc?topic=vpc-upgrading-weak-ciphers&interface=ui) on an existing policy or connection. For more information, see [Upgrading weak cipher suites on a VPN gateway](https://cloud.ibm.com/docs/vpc?topic=vpc-upgrading-weak-ciphers&interface=api).







 2 May 2023 



 For all version dates 

Exporting custom images.
You can use the IBM Activity Tracker Event Routing Overview predefined dashboard template to monitor Activity Tracker Event Routing in IBM Cloud.

To open the predefined Activity Tracker Event Routing template, complete the following steps from the Monitoring UI:



1. In the Monitoring UI, go to Dashboards > Dashboard templates > IBM.
2. Select IBM Activity Tracker Event Routing Overview.



You cannot modify a dashboard template. However, you can copy the template and create a custom dashboard that you can then configure.

Next, choose any of the following tasks to learn more about how to manage and work with platform metrics:

[![Working with platform metrics](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/atracker/images/platform_metrics_task_1.svg)](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_working)[![Controlling what data is visible](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/atracker/images/platform_metrics_task_2.svg)](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_workingcontrolling-what-data-is-visible)[![Monitoring metrics through dashboards](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/atracker/images/platform_metrics_task_3.svg
<br>You can create a rule to specify which image versions can be used. 
 [Define a policy](https://cloud.ibm.com/docs/docs/workload-protection?topic=workload-protection-manage_policies) You can configure a policy on a resource and define what to do when 1 or more rules that are included in the policy are noncompliant. <br>Secure includes a number of pre-defined policies that you can use. 
 [Configure a benchmark task](https://docs.sysdig.com/en/docs/sysdig-secure/posture/compliance/legacy-versions/benchmarks-legacy/configure-benchmark-tasks/) You can use [Compliance dashboards and metrics](https://docs.sysdig.com/en/docs/sysdig-secure/home/secure-dashboards/) to monitor the status of your sources based on the benchmark task that you configure.
Understanding latency 

IBM Cloud® offers data centers with Direct Link capabilities around the globe. Therefore, you can count on minimal latency when you use Direct Link to create your Hybrid cloud solution by linking your IBM Cloud to your existing infrastructure.

Whether you have an online store, run big data solutions, or have your employees set up on a network with access to files around the world, you never want to hear that slow page loading, or slow data transfer, is keeping you from a sale. Slowdowns can be caused by network latency, which is the measurement of how quickly data travels between two connected points on the internet. You can think of it as the amount of time it takes for one packet of data to get from one place to another.

Globally, the internet’s overall latency can vary significantly, depending on how far the data must travel physically, how many times the data must hop between service providers, how much bandwidth is available along the way, what other data is traveling across the same path, in addition to other variables. IBM Cloud Direct Link offers deterministic latency with greater security, relative to the internet for predictable performance.



 Understanding network latency 

As a best practice, every network provider wants to offer the lowest network latency to the greatest number of customers, and every customer wants to obtain the lowest possible latency. It’s a desirable, shared outcome.

Theoretically, data can travel at the speed of light across optical fiber network cables, but for all the reasons that are given, data typically travels much more slowly. For example, if a particular network connection reached its bandwidth capacity, data packets might temporarily queue up to wait for their turn to travel across that pathway. As another example, if a particular service provider’s network selects a network route that is not optimal, data packets can be sent hundreds or thousands of miles away from their destination while getting to their destination! These kinds of delays and detours are the causes of higher network latency—and slower data transfers.

We express network latency in milliseconds (that’s 1,000 milliseconds per second). A few thousandths of a second might not mean much to us as we’re living our daily lives, but milliseconds often become a deciding factor in our web browsing or in our business transactions.
check the VPN connection status to be changed to up
terraform state show ibm_is_vpn_gateway_connection.is_vpn_gateway_connection



For more information, see the [Terraform registry](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_vpn_gateway_connection).







 Upgrading a VPN from a custom IKE or IPsec policy 

Complete the following procedure to upgrade a VPN from a custom IKE or IPsec policy.



 Before you begin 

On 20 September 2022, VPN for VPC IKE and IPsec weak ciphers were deprecated. To upgrade a VPN connection that was created using a custom IKE or IPsec policy that contains weak ciphers, complete the following steps.

You will experience a network outage during the upgrade. The duration of the outage depends on the time that it takes to update the weak ciphers and to reestablish the VPN connection. It is recommended that you plan a maintenance window for this upgrade.

Before you begin, it is a good idea to first configure your on-prem VPN gateway peer to contain both the weak and secure ciphers for Phase 1 and Phase 2 negotiation. Then, change the IBM VPN gateway to remove the use of the weak ciphers by following these steps. Afterward, remove the weak ciphers from the on-prem VPN gateway. This step might also reduce the outage time.





 Upgrading a VPN from a custom IKE policy in the UI 

To upgrade the IKE policy by using the UI, follow these steps:



1. From the VPNs for VPC page, select Site-to-site gateways > IKE policies.
2. Select the IKE policy configured in the VPN connection that you want to upgrade.
3. Highlight the row of the IKE policy in the table, then click Edit from the Actions menu !
To open the predefined Activity Tracker Event Routing template, complete the following steps from the Monitoring UI:



1. In the Monitoring UI, go to Dashboards > Dashboard templates > IBM.
2. Select IBM Activity Tracker Event Routing Overview.



You cannot modify a dashboard template. However, you can copy the template and create a custom dashboard that you can then configure.

Next, choose any of the following tasks to learn more about how to manage and work with platform metrics:

[![Working with platform metrics](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/atracker/images/platform_metrics_task_1.svg)](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_working)[![Controlling what data is visible](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/atracker/images/platform_metrics_task_2.svg)](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_workingcontrolling-what-data-is-visible)[![Monitoring metrics through dashboards](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/atracker/images/platform_metrics_task_3.svg
IBM Cloud services that generate metrics that are managed through IBM Cloud Metrics Routing 

List of IBM Cloud® services that generate metrics that you can manage through IBM Cloud Metrics Routing.

There are 2 ways that services send metrics:



* As platform metrics

You monitor these metrics through the monitoring instance that is configured to receive platform metrics. [Learn more about enabling platform metrics](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_enabling).
* By configuring a Monitoring agent

You configure the agent to send metrics to the Monitoring instance that you choose. You monitor these metrics through that instance.



IBM Cloud Metrics Routing routes platform metrics based on the location, service-name, service-instance, resource, and resource-type that is specified in the CRN labels included with each metric. You can define a target, the resource where metrics are routed to, in any IBM Cloud Metrics Routing supported region. However, the target resource can be located in any region where that type of target is supported, in the same account or in a different account. You can define rules to determine where metrics are to be routed by configuring 1 or more routes in the account. You can define rules for managing routing of metrics that are generated in regions where IBM Cloud Metrics Routing is supported.



 Container services 



Table 1. List of IBM Cloud container services

 Service CRN service name Metrics 

 [IBM Cloud Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-getting-started) container-registry [Platform metrics](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_monitor) 







 Database services 



Table 2. List of database services

 Service CRN service name Metrics 

 [IBM Cloud® Data Engine](https://cloud.ibm.com/docs/services/sql-query?topic=sql-query-gettingstarted) sql-query [Platform metrics](https://cloud.ibm.com/docs/services/sql-query?topic=sql-query-metrics) 







 Developer tools