vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Changes of any type should be communicated to the customer as they arise.
* Each change request must be properly documented to ITIL v3 - Request for Change (RFC) Standards: Each RFC must have the following fields:
* Unique ID :
* Date of submission :
* Change Owner :
* Initiator of the RFC :
* Proposed Change priority :
* Low
* Normal
* High
* Very High (Emergency Change)
* Reference to Change Proposal
* Description of the Change being applied for :
* Summary description :
* Business case :
* Reason for the Change to be implemented :
* Costs :
* Benefits :
* Consequences if the Change is not implemented :
* References (e.g. to a Problem Record triggering this RFC) :
* Business areas on the client-side affected by the Change :
* Services affected by the Change :
* IT infrastructure components (CIs) affected by the Change :
* Technology aspects (is a new technology being introduced?) :
* Risks : (Risks during the implementation of the Change)
* Identified risks :
* Counter-measures :
* Back-out strategy for the case of a failed Change implementation :
* Time schedule :
* Estimate of resources for the implementation :
* Required personnel resources :
* Estimated work effort for the required personnel resources :
* Cost estimate :
* Budget :
* Additional supporting documents :
* Approval or rejection :
* Date :
* Person/ body in charge of the approval :
* Change reviewers :
* Priority assigned by Change Management :
* Restrictions :
* If applicable, reasons for rejecting the RFC :.







 IBM Cloud for Financial Services profile 

The rules related to this control that follow are part of the IBM Cloud for Financial Services v1.2.0 profile in [IBM Cloud® Security and Compliance Center](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-getting-started).



Rules for CM-3 in IBM Cloud for Financial Services v1.2.0 profile

 Requirement ID Rules
* Goal ID's: 3000901 - 3000907







 5 April 2021 

Initial Posture Management API support
: As part of this release, the Posture Management component of the service provides three external APIs that you can use as part of your security and compliance automation. For more information, see the [Posture Management API docs](https://cloud.ibm.com/apidocs/security-compliance/posture).

Proxy support for discovery and fact collection
: With this release, you can configure your collector to use a proxy to access the public endpoints to enhance the security of your scans.

New goal mapping
: The goal 3000045 is now mapped to CM-2 NIST 800 and were added to an additional profile.

IBM Cloud for Financial Services profile
: Released today, the IBM Cloud for Financial Services profile is a collection of curated goals. These goals can help organizations make a large jump on the path to meeting the NIST 800-53 security controls that are required for financial institutions. By validating your resources against the IBM Cloud for Financial Services profile, you can be more confident that your IBM Cloud resources are following best practices for security and compliance.

Important: The IBM Cloud for Financial Services profile are constantly expanding and is not an exhaustive list of all the controls that might be required for every organization. Users can validate the available goals and determine where a need to supplement their workloads with other security measures exists.





 23 March 2021 

Manage the location in which your data is stored
: Have specific regulations around where your data is stored and processed? With Security and Compliance Center, you can now choose the location in which the data that is generated by the service is managed. To set your location preferences, you can go to the Menu icon![Menu icon](https://cloud.ibm.com/docs-content/v1/content/a6478671e8f845a84102d9cf49bf28ee7f4f3227/icons/icon_hamburger.svg)> Security and Compliance > Data Settings.
0.0.0.0/0 Deliver 10.10.1.5 Dallas DC 1 





 Objective: public load balancer 

Hosting web applications using a client-defined application or network load balancer.

Utilizing VPC custom routes with per-subnet egress routing, you can create a table to override the system-implicit routing with the VPC network without updating routing information on each instance. In this example, the source IP from the internet users to the web layer is preserved. The web-to-app and app-to-db layers communicate using implicit VPC routing and continue to use the public gateway for internet egress.

Route delegation is required for internal/private networks within the VPC and IBM service networks over the private backbone. To avoid the need for delegation, web layer servers can be attached to the app layer subnet, and routing changed on the web instances to use the app subnet gateway as the next hop for the internal VPC and cloud service networks.





 Functions used in public load balancers 

This use case uses the following functions of public load balancers:



* Disabling the IP spoofing check on 10.10.0.5 and 10.10.1.5 interfaces to enable source address preservation. This action requires elevated IAM permissions on the instance.
* A public gateway for outbound flows for resources that are not directed through the NFV proxy.
* The floating IP attached to the 10.10.0.5 interface to enable inbound and outbound public flows directly to the NFV load balancer.
* Adding stateful security groups and network access control lists (ACLs) to the instances interfaces and VPC subnets, respectively, to provide additional isolation resources within the VPC.









 Use case 3: VPN 

To have a VPN gateway as the next hop in a VPC routing table, the gateway is created in a dedicated subnet. This subnet is used only for the VPN gateway, and associated with the VPN gateway subnet with a different routing table when there is a route 0.0.0.0/0 and the next hop is a VPN connection.

For example:



* Subnet A is used to host the virtual servers and is associated with the default routing table.
Part 2: Create a GitHub issue when your certificates are about to expire 

This tutorial is part 2 of a 3-part tutorial series that guides you through setting up alerts for your expiring secrets.

In part 1 of this tutorial series, you learned how to set up IBM Cloud® Secrets Manager and Event Notifications to route events to a test webhook URL. Part 2 shows you how to replace your test webhook with a Cloud Functions webhook URL so that you can open a GitHub issue that contains your Secrets Manager notification content.

Zoom

![The diagram shows the basic flow between the Secrets Manager, Event Notifications, and Cloud Functions services to create a GitHub issue.](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/secrets-manager/images/notifications-github.svg)

Figure 1. Notifications flow



 Before you begin 

Be sure that you've completed [Part 1: Enabling notifications for Secrets Manager](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-tutorial-expiring-secrets-part-1). Before you get started with part 2, you also need the following prerequisites:



* An IBM Cloud API key with Manager service access on the Event Notifications service.
* A [GitHub personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) with repo access.







 Step 1: Create a webhook with Cloud Functions 

Let's start by creating a [Cloud Functions](https://cloud.ibm.com/docs/openwhisk) action. A Cloud Functions action is a piece of code that can be run in response to a trigger, such as an incoming notification from the Event Notifications service.
Using the Enterprise Resource Planning (ERP) business application, for example, an SAP System hosting the Production instance that uses the SAP System Tiering approach using High Availability of SAP NetWeaver and SAP HANA:



* SAP NetWeaver, there are at least four hosts instead of 1:



* Central Services (ASCS)
* Primary Application Server (PAS), also known as Central Instance (CI)
* Enqueue Replication Server Instance (ERS)
* Additional Application Server (AAS)



* SAP HANA, there are at least 2 hosts (possibly 3) instead of 1:



* SAP HANA primary node (using SAP HANA System Replication)
* SAP HANA secondary failover node (using SAP HANA System Replication)
* SAP HANA tertiary disaster recovery failover node (using SAP HANA System Replication)



This describes 1 SAP System within the SAP Landscape. An SAP Landscape might use:



* One Track, 5 SAP Systems (Sandbox > Development > Testing > Staging > Production)
* Dual Track, 5 SAP Systems (Sandbox > New Feature Development + Maintenance Development > New feature testing + Maintenance testing > Staging > Production)





Therefore for an SAP Landscape potentially 30 to 50 instances of SAP, spread across 10-50 host servers (physical or virtualized) might be required. This is before more business applications are added for specific business operations, industry, or geographic functions.

The size of the SAP Landscapes have a direct impact on the Network Topology.

Typically, although this varies from case to case, the following networks are required to meet the scenarios and performance that is required by the business that uses SAP Business Applications:



* Internal network for communication between multiple instances in an SAP Landscape with different SAP System Tiering approaches
* Network for the management and storage transfers of database systems
* Network that is used in production



However, in the simplest scenario there might be one private network for all purposes. It depends on business requirements.



 Additional management systems to enable SAP systems 

Depending on your operating system, SAP workload, and network connectivity, you might need to configure access to many more SAP and non-SAP systems. The following is a list of various management systems that your SAP workloads might require to operate:
The release removes support for the strongpm App Management handler as announced in [IBM Cloud Node.js Buildpack v3.3 – FIPS mode and more](https://www.ibm.com/blogs/cloud-archive/2016/05/node-buildpack-update-fips-mode/).

Note that there is a known issue when using Node.js 6.x and Development Mode. As a work around you will need to restage your app after enabling Development Mode before you can begin using it.





 22 July 2016 

Updated Liberty buildpack v3.1-20160717-2254
: The [App Management](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-app_management) functionality was updated to support federated authentication. Also, the Node.js runtime that is used by the devconsole and shell utilities was updated to the latest 0.12.15 version.



* The buildpack adds support for the [Dynatrace Ruxit](https://www.dynatrace.com/solutions/cloud-native-application-monitoring/) app monitoring agent.
* The buildpack provides an updated data collector for the Monitoring and Analytics service.
* The buildpack also provides an updated version of the agent for the Auto-Scaling service.
* The monthly Liberty runtime version was updated to the [2016.7.0.0](https://developer.ibm.com/wasdev/blog/2016/06/30/beta-websphere-liberty-and-tools-july-2016/) release.



Updated Node.js buildpack v3.6-20160715-0749
: This release of the buildpack supports IBM SDK for Node.js runtime versions: 0.10.45, 0.10.46, 0.12.14, 0.12.15, 4.4.6, 4.4.7, 6.2.1, and 6.2.2. The default is now 4.4.7.

This release includes an updated App Management proxy that supports federated logins.

Included are fixes for the following security vulnerabilities:
Sample apps 

IBM is announcing the deprecation of the IBM Watson® Language Translator service for IBM Cloud® in all regions. As of 10 June 2023, the Language Translator tile will be removed from the IBM Cloud Platform for new customers; only existing customers will be able to access the product. As of 10 June 2024, the service will reach its End of Support date. As of 10 December 2024, the service will be withdrawn entirely and will no longer be available to any customers.

Check out the following sample applications to see what you can build with Language Translator.

These systems are for demonstration purposes only and are not intended to process Personal Data. No Personal Data is to be entered into these systems as they may not have the necessary controls in place to meet the requirements of the General Data Protection Regulation (EU) 2016/679.



 Snap and translate text in images (Node.js) 

This sample app explains how to create a hybrid mobile app that uses Watson Language Translator and Tesseract OCR. With this sample app you can capture an image, extract the text, and translate that text.



* [Read the blog](https://developer.ibm.com/announcements/snap-translate-using-tesseract-ocr-watson-language-translator/)
* [Code Pattern](https://developer.ibm.com/patterns/snap-translate-using-tesseract-ocr-watson-language-translator/)
* [View on GitHub](https://github.com/IBM/snap-and-translate)







 Multilingual Chatbot (Node.js, Python) 

This chatbot that is built with Watson Assistant and Cloud Functions adds support for multiple languages with Language Translator.



* [View on GitHub](https://github.com/with-watson/multilingual-chatbot)
* [Try the demo](https://multilingual-chatbot.mybluemix.net/)
* [Read more](https://medium.com/ibm-watson/build-multilingual-chatbots-with-watson-language-translator-watson-assistant-8c38247e8af1)
* Dallas as of June 15, 2018
* Frankfurt as of June 15, 2018
* London
* Seoul
* Sydney as of June 12, 2018
* Tokyo
* Washington, DC as of June 12, 2018



IBM Cloud is migrating to token-based Identity and Access Management (IAM) authentication. With some service instances, you authenticate to the API by using IAM.

IBM Cloud IAM available for service instances
: IBM Cloud Identity and Access Management (IAM) is available for new and existing service instances as follows:



* For new service instances created in the locations indicated previously, you use IAM for authentication. You can pass either a bearer token or an API key. Tokens support authenticated requests without embedding service credentials in every call. API keys use basic authentication.

When you use any of the Watson SDKs, you can pass the API key and let the SDK manage the lifecycle of the tokens. For more information and examples, see [Authentication](https://cloud.ibm.com/apidocs/language-translatorauthentication) in the API & SDK reference.
* For existing service instances that you created before the indicated date, you continue to authenticate by providing the username and password for the service instance. Eventually, you will need to migrate these service instances to IAM authentication. Updates will be provided about migration process and dates. For more information about migration, see [Migrating Watson services from Cloud Foundry](https://cloud.ibm.com/docs/language-translator?topic=watson-migrate).



To find out which authentication to use, view the service credentials by clicking the service instance on the [IBM Cloud resources page](https://cloud.ibm.com/resources).
IR-8 - Incident Response Plan 



  Control requirements 

The organization:

IR-8 (a)
:   Develops an incident response plan that:



1.  Provides the organization with a roadmap for implementing its incident response capability;
2.  Describes the structure and organization of the incident response capability;
3.  Provides a high-level approach for how the incident response capability fits into the overall organization;
4.  Meets the unique requirements of the organization, which relate to mission, size, structure, and functions;
5.  Defines reportable incidents;
6.  Provides metrics for measuring the incident response capability within the organization;
7.  Defines the resources and management support needed to effectively maintain and mature an incident response capability; and
8.  Is reviewed and approved by [Assignment: organization-defined personnel or roles];



IR-8 (b)
:   Distributes copies of the incident response plan to [Assignment: organization-defined incident response personnel (identified by name and/or by role) and organizational elements];

IR-8 (c)
:   Reviews the incident response plan [IBM Assignment: at least annually];

IR-8 (d)
:   Updates the incident response plan to address system/organizational changes or problems encountered during plan implementation, execution, or testing;

IR-8 (e)
:   Communicates incident response plan changes to [Assignment: organization-defined incident response personnel (identified by name and/or by role) and organizational elements]; and

IR-8 (f)
:   Protects the incident response plan from unauthorized disclosure and modification.





  Additional IBM Cloud for Financial Services specifications 



*  Documentation includes plan and playbook(s).







  NIST supplemental guidance 

It is important that organizations develop and implement a coordinated approach to incident response. Organizational missions, business functions, strategies, goals, and objectives for incident response help to determine the structure of incident response capabilities. As part of a comprehensive incident response capability, organizations consider the coordination and sharing of information with external organizations, including, for example, external service providers and organizations involved in the supply chain for organizational information systems.
* More Information - Additional information available from IBM® or VMware to help with the resolution of these alarms when triggered.



If you have a vSAN cluster, the additional preconfigured alarms in the following table apply.



Table 2. Preconfigured alarms - vSAN

 Alarm name Guidance Details 

 Host flash capacity exceeds the licensed limit for vSAN Not considered essential for notification. Alarm that is reviewed as part of proactive daily checks. No additional information 
 Expired vSAN license Not considered essential for notification. Alarm that is reviewed as part of proactive daily checks. [Troubleshooting licensing](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-3C4E8BF7-B0A9-46F0-BA50-D69F950AB958.html) 
 Errors occurred on the disks of a vSAN host Configure to send email one time when a permanent error is on a vSAN disk. [vSAN device encounters a permanent error when devices are not readable or writeable (2071075)](https://kb.vmware.com/s/article/2071075) 
 Errors occurred on the disks of a vSAN host Configure to send email one time when the Virtual SAN device is under permanent failure critical event occurs. [vSAN device encounters a permanent error when devices are not readable or writeable (2071075)](https://kb.vmware.com/s/article/2071075) 
 Expired vSAN license Not considered essential for notification. Alarm that is reviewed as part of proactive daily checks. [Considerations about the vSAN license](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vsan-planning.doc/GUID-20731F2A-B001-4A05-AB4D-30C5B0044EC5.html) 
 Expired vSAN time-limited license Not considered essential for notification.
Part 3: Send your notifications to a Slack channel 

This tutorial is part 3 of a 3-part tutorial series that guides you through setting up alerts for your expiring secrets.

In part 2 of this tutorial series, you learned how to create a GitHub issue from an event notification that originated in your IBM Cloud® Secrets Manager service instance. Part 3 shows you how to create another Cloud Functions action that uses an incoming Secrets Manager event to post a notification to Slack.

As of 31 May 2022, the Event Notifications service supports a built-in Slack integration! Instead of using a Cloud Functions action to forward your events to Slack, you can now select Slack as an Event Notifications destination. To learn more about this feature, check out the [Event Notifications documentation](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-destination).

Zoom

![The diagram shows the basic flow between the Secrets Manager, Event Notifications, and Cloud Functions that sends a notification to Slack.](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/secrets-manager/images/notifications-slack.svg)

Figure 1. Posting a notification to Slack



 Before you begin 

Be sure that you've completed [Part 2: Enabling notifications for Secrets Manager](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-tutorial-expiring-secrets-part-2). Before you get started with part 3, you also need the following prerequisites:



* A Slack app with an [incoming webhook URL](https://api.slack.com/messaging/webhooks) enabled.
* A Slack channel to post your incoming notifications.

The Slack app must be added to your channel so that incoming messages are displayed.
For a more condensed comparison, see [IBM Power Systems CPW performance data comparison](https://www.itechsol.com/wp-content/uploads/2018/07/IBM-Power-Systems-CPW-Performance-Data-Comparison-P7-vs-P8-vs-P9-rev3-July-2018.pdf).



 Constructs for provisioning IBM Power Virtual Servers 

As the IBM Power Virtual Server is a complementary offering from IBM Power Systems, it is accessed as an additional offering from the IBM Cloud catalog. To begin using IBM Power Virtual Servers, an instantiation of an IBM Power Virtual Server resource group must first be made.

The below sections explain this in more detail.



 Resource versus Resource Group 

A resource in the context of IBM Power Systems Virtual Servers is not a user, it's anything that you can create from the catalog, for example, an IBM Power Systems Virtual Server. A resource group contains multiple resources, for example, a set of servers used strictly for development activities. For more information, see [Creating resources](https://cloud.ibm.com/docs/account?topic=account-manage_resource).





 Service versus instance 

There is difference between an IBM Power Systems Virtual Server service and an IBM Power Systems Virtual Server instance. Think of the IBM Power Systems Virtual Server service as a container for all IBM Power Systems Virtual Server instances at a specific geographic location. The IBM Power Systems Virtual Server service is available from the Resource list in the IBM Cloud® UI. The service can contain multiple IBM Power Systems Virtual Server instances.

For example, you can have two IBM Power Systems Virtual Server services, one in Dallas and another in Washington DC. Each service can contain multiple IBM Power Systems Virtual Server instances. For more information, see [Getting started with IBM Cloud IBM Power Systems Virtual Server](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-getting-started).

All instances of an SAP system must run in the same service. Multiple systems can be distributed through different services, in which case IT operations teams must ensure that latency is acceptable for their scenarios.







 IBM Power CPU type - dedicated or shared