vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Contingency Planning (CP) [CP-2 (3) Contingency Plan | Resume Essential Missions / Business Functions](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-cp-2.3) <br>[CP-6 Alternate Storage Site](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-cp-6) <br>[CP-7 Alternate Processing Site](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-cp-7) <br>[CP-10 Information System Recovery and Reconstitution](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-cp-10) 
 System and Information Integrity (SI) [SI-11 Error Handling](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-si-11) 







 Next steps 



* [Compliance monitoring](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-monitoring-compliance)
<artifactId>spring-boot-maven-plugin</artifactId>
</plugin>







 Initializing OAuth2 



1. Add the following annotations to your Java file.

@SpringBootApplication
@EnableOAuth2Sso
2. Extend the class with WebSecurityConfigurerAdapter.
3. Override any security configuration and register your protected endpoint.

@Override
protected void configure(HttpSecurity http) throws Exception {
http.authorizeRequests()
.antMatchers("/protected_Resource").authenticated()
.and().logout().logoutSuccessUrl("/").permitAll();
}







 Adding credentials 



1. Obtain your credentials in one of the following ways.



* By navigating to the Applications tab of the App ID dashboard. If you don't already have one, you can click Add application to create a new one.
* By making a POST request to the [/management/v4/<tenantID>/applications endpoint](https://us-south.appid.cloud.ibm.com/swagger-ui/!/Applications/registerApplication).

Request format:

curl -X POST https://us-south.appid.cloud.ibm.com/management/v4/39a37f57-a227-4bfe-a044-93b6e6060b61/applications/ -H 'Content-Type: application/json' -H 'Authorization: Bearer <IAMToken>' -d '{"name": "ApplicationName"}'

Example response:

{
"clientId": "111c22c3-38ea-4de8-b5d4-338744d83b0f",
"tenantId": "39a37f57-a227-4bfe-a044-93b6e6060b61",
Must be different than the one assigned to Brocade vRouter (Vyatta 1)
set interfaces bonding bond0 vif 1101 vrrp vrrp-group 2 advertise-interval '1'
set interfaces bonding bond0 vif 1101 vrrp vrrp-group 2 preempt 'false'
set interfaces bonding bond0 vif 1101 vrrp vrrp-group 2 priority '253'
set interfaces bonding bond0 vif 1101 vrrp vrrp-group 2 'rfc3768-compatibility'
set interfaces bonding bond0 vif 1101 vrrp vrrp-group 2 sync-group 'vgroup1'
set interfaces bonding bond0 vif 1101 vrrp vrrp-group 2 virtual-address ‘<GATEWAY ADDRESS/MASK of Primary Private VLAN Bound to 1101/Management>’
set interfaces bonding bond0 vif 1101 vrrp vrrp-group 2 virtual-address ‘<GATEWAY ADDRESS/MASK of Portable Private VLAN Bound to 1101/Management VMs>’
set interfaces bonding bond0 vif 1102 vrrp vrrp-group 3 advertise-interval '1'
set interfaces bonding bond0 vif 1102 vrrp vrrp-group 3 preempt 'false'
set interfaces bonding bond0 vif 1102 vrrp vrrp-group 3 priority '253'
set interfaces bonding bond0 vif 1102 vrrp vrrp-group 3 'rfc3768-compatibility'
set interfaces bonding bond0 vif 1102 vrrp vrrp-group 3 sync-group 'vgroup1'
set interfaces bonding bond0 vif 1102 vrrp vrrp-group 3 virtual-address ‘<GATEWAY ADDRESS/MASK of Primary Private VLAN Bound to 1102/Storage>’
set interfaces bonding bond0 vif 1102 vrrp vrrp-group 3 virtual-address ‘<GATEWAY ADDRESS/MASK of Portable Private VLAN Bound to 1102/Storage Path A>’
set interfaces bonding bond0 vif 1102 vrrp vrrp-group 3 virtual-address ‘<GATEWAY ADDRESS/MASK of Portable Private VLAN Bound to 1102/Storage Path B>’
set interfaces bonding bond0 vif 1103 vrrp vrrp-group 4 advertise-interval '1'
To modify the way the ALB matches the request URI against the app path, use the following Kubernetes Ingress resource [annotation](https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/use-regex).

nginx.ingress.kubernetes.io/use-regex: "true"

For more info, see [this blog](https://kubernetes.github.io/ingress-nginx/user-guide/ingress-path-matching/ingress-path-matching).





 Adding custom location block configurations 

To add a custom location block configuration for a service, use the following Kubernetes Ingress resource [annotation](https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/configuration-snippet).

nginx.ingress.kubernetes.io/configuration-snippet: 
more_set_headers "Request-Id: $req_id";





 Configuring mutual authentication 

To configure mutual authentication for the ALB, use the following Kubernetes Ingress resource [annotations](https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/client-certificate-authentication). Note that mutual authentication can't be applied to custom ports and must be applied to the HTTPS port.

nginx.ingress.kubernetes.io/auth-tls-verify-client: "on"
nginx.ingress.kubernetes.io/auth-tls-secret: "default/ca-secret"
nginx.ingress.kubernetes.io/auth-tls-verify-depth: "1"
"logging": {
"datapath": {
"active": false
}
},
"profile": {
"href": "https://us-east.iaas.cloud.ibm.com/v1/load_balancer/profiles/dynamic",
"name": "dynamic",
"family": "Application"
},
"security_groups": [
{
"id": "r014-b739c959-fb3c-44cc-9ec5-41c45b4d637e",
"href": "https://us-east.iaas.cloud.ibm.com/v1/security_groups/r014-b739c959-fb3c-44cc-9ec5-41c45b4d637e",
"crn": "crn:v1:bluemix:public:is:us-east:a/be636a7a6e4d4b6296bedf669ce8f757::security-group:r014-b739c959-fb3c-44cc-9ec5-41c45b4d637e",
"name": "astonish-backing-shadiness-frostlike-cosmos-hunk"
}
],
"security_group_supported": true,
"route_mode": false,
"udp_supported": false,
"dns": {
"instance": {
"crn": "crn:v1:bluemix:public:dns-svcs:global:a/be636a7a6e4d4b6296bedf669ce8f757:c7295f57-4d25-4832-9d7e-a032de0c278c::"
},
"zone": {
mongo/cli connection information

 Field Name Index Description 

 Bin The recommended binary to create a connection; in this case it is mongo. 
 Composed A formatted command to establish a connection to your deployment. The command combines the Bin executable, Environment variable settings, and uses 
 Environment A list of key/values you set as environment variables. 
 Arguments 0... The information that is passed as arguments to the command shown in the Bin field. 
 Certificate Base64 A self-signed certificate that is used to confirm that an application is connecting to the appropriate server. It is base64 encoded. 
 Certificate Name The allocated name for the self-signed certificate. 
 Type The type of package that uses this connection information; in this case cli. 





* 0... indicates that there might be one or more of these entries in an array.







 mongo example 

mongo -u admin -p $PASSWORD --ssl --sslCAFile c5f07836-d94c-11e8-a2e9-62ec2ed68f84 --authenticationDatabase admin --host replset/bd574ce4-7b36-4274-9976-96db98a3ac10-0.b8a5e798d2d04f2e860e54e5d042c915.databases.appdomain.cloud:30484,bd574ce4-7b36-4274-9976-96db98a3ac10-1.b8a5e798d2d04f2e860e54e5d042c915.databases.appdomain.cloud:30484



* mongo - The command itself.
* --ssl --sslCAFile - The path and name of the self-signed certificate for your deployment.
* -u - The parameter for the username.
* -p - The parameter for the password.
* --authenticationDatabase - The database where the user and its credentials are created and stored.
* [IBM Cloud for Financial Services profile](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-si-4scc-fs-cloud-profile)
* [NIST supplemental guidance](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-si-4nist-supplemental-guidance)



[SI-4 (1) - System-wide Intrusion Detection System](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-si-4.1si-4.1)



* [Control requirements](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-si-4.1control-requirements)



[SI-4 (2) - Automated Tools for Real-time Analysis](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-si-4.2si-4.2)



* [Control requirements](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-si-4.2control-requirements)
* [NIST supplemental guidance](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-si-4.2nist-supplemental-guidance)



[SI-4 (4) - Inbound and Outbound Communications Traffic](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-si-4.4si-4.4)



* [Control requirements](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-si-4.4control-requirements)
You don't need to perform the VerifyUpdate and VerifyFinal suboperations for a single-part verification. Before you call this function, make sure to run VerifyInit first.

Enterprise PKCS #11 over gRPC

Enterprise PKCS #11

PKCS #11





 Description Binds to EP11 m_Verify, which is an implementation of PKCS #11 C_Verify. 
 Parameters message VerifyRequest { bytes State = 1; bytes Data = 2; bytes Signature = 3; } message VerifyResponse { } 
 Return values Wraps EP11 error into message Grep11Error. 



Code snippets



* Golang code snippet

VerifyRequest := &pb.VerifyRequest {
State: VerifyInitResponse.State,
Data: msgHash[:],
Signature: SignResponse.Signature,
}

VerifyResponse, err := cryptoClient.Verify(context.Background(), VerifyRequest)
* JavaScript code snippet

client.Verify({
State: state,
Data: dataToSign,
Signature: signature
}, (err, data={}) => {
cb(err, signature);
});







 VerifyUpdate 

The VerifyUpdate function continues a multiple-part verification operation. Before you call this function, make sure to run VerifyInit first.

Enterprise PKCS #11 over gRPC

Enterprise PKCS #11

PKCS #11





 Description Binds to EP11 m_VerifyUpdate, which is an implementation of PKCS #11 C_VerifyUpdate. 
 Parameters message VerifyUpdateRequest { bytes State = 1; bytes Data = 2; } message VerifyUpdateResponse { bytes State = 1; } 
 Return values Wraps EP11 error into message Grep11Error. 



Code snippets



* Golang code snippet

// Use VerifyUpdate if you would like to breakup
// the verify operation into multiple suboperations
VerifyUpdateRequest1 := &pb.VerifyUpdateRequest {
* [Setting a maximum number of upstream keepalive requests](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsupstream-keepalive-requests)
* [Setting the maximum upstream keepalive timeout](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsupstream-keepalive-timeout)
* [Customizing the ALB deployment](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationscomm-customize-deploy)



* [Creating a ConfigMap to customize the Ingress deployment](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationscreate-ingress-configmap-custom)



* [Customizing the Ingress class](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotations-custom-ingress-class)
* [Adding App ID authentication to apps](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsapp-id-auth)



* [Upgrading ALB OAuth Proxy add-on](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsupgrading-alb-oauth-proxy-add-on)



* [Preserving the source IP address](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationspreserve_source_ip)



* [Enabling the PROXY protocol in VPC clusters](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationspreserve_source_ip_vpc)
[FortiGate connection peer IP of the primary tunnel](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc/images/vpn-fortigate-configure-peer-ip.png)

Figure 2: FortiGate connection eer IP of primary tunnel
3. To configure an IKE proposal, use the matched IKE version and proposals.

Zoom

![FortiGate connection IKE proposal](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc/images/vpn-fortigate-configure-ike-proposal.png)

Figure 3: FortiGate connection IKE proposal
4. To configure an IPsec proposal, use the matched IPsec proposals.

Zoom

![FortiGate connection IPsec proposal](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc/images/vpn-fortigate-configure-ipsec-proposal.png)

Figure 4: FortiGate connection IPsec proposal





 Configuring a secondary tunnel 

To configure a secondary tunnel, follow these steps:



1. Repeat the preceding steps to create the secondary tunnel. Use the large public IP address of the IBM route-based VPN gateway as the remote gateway IP address.

Zoom

![FortiGate connection secondary tunnel creation](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc/images/vpn-fortigate-configure-secondary.png)
This data includes the asset details and the incident URL.



Non-remediated pull/merge request incidents impact the deployment readiness of the change request. If any pull/merge request incidents are found, they are considered vulnerabilities and the [change request](https://cloud.ibm.com/docs/devsecops?topic=devsecops-cd-devsecops-approve-cr) must be reviewed and approved manually.

Zoom

![Change request content](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/devsecops/images/devsecops-pr-incident-change-request-content.png)

Figure 3. Change request content





 Pull request incident remediation 

Pull request incidents are considered vulnerabilities because they indicate that unchecked code is contained in the released artifacts. To remediate these incidents, complete the following steps:



1. Retroactively review the merged change.
2. Create an issue about how to fix any existing problems with the code.
3. Add the exempt label or close the pull/merge request incident issue.



The author of the pull/merge request and the person who closes the pull/merge request incident issue cannot be the same person.





 Known issues 



* Peer review compliance is reliant on the inclusion of inventory entry in the release step following each iteration of the Continuous Integration (CI) pipeline. Skipping to include the inventory entry for any failed CI pipeline run might result in the peer review evidence for that specific CI pipeline run being disregarded in your Continuous Delivery (CD) pipeline.
DevSecOps PR Pipeline Successful



1. Navigate back to the merge request.
2. Merge the request so that your changes are copied to the master branch of your application repository: the CI pipeline is automatically triggered.



Simplified flow of tasks in the pipeline: (Utility tasks are omitted. For example, status-check update on GitHub, credential fetching, and so on).

Zoom

![DevSecOps PR Tasks](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/devsecops/images/devsecops-ci-pr-tasks.png)

Figure 23. DevSecOps PR Tasks

In the DevSecOps world, shift left is a practice that prevents and finds issues like defects, security vulnerabilities. Shift left also performs compliance checks early in the software delivery process.



* Checks that can be run on the code/repository and do not need the built image should be run as early as possible to prevent noncompliant code from being merged to master branch of repository. Evidence is not collected from the PR pipeline. The pipeline's goal is to shift compliance checks, as far left as possible.
* All checks are done every pipeline run, even if a previous check fails, the pipeline progresses to the next one. To evaluate if you have any failures in your run, you need to check the final step of your pipeline, which has a pipeline evaluator.
* If you are trying to merge an emergency fix, and want to bypass compliance checks, add a label to your merge request to indicate this. The same label must be provided when running the CD pipeline.





 Run PR Pipeline 



* To start the PR pipeline, create a pull request in your application repository.
* The corresponding Merge Request in your application repository is in "Pending" state until all the stages of PR Pipeline finishes successfully.







 Run CI Pipeline 

There are two ways to start a CI pipeline:



* Automatically: after a successful PR pipeline, by approving and merging the PR to the master branch.
* PR: triggers when a new PR is submitted in the app repository
* CI: manually run or triggers when a PR is merged to master in the app repository







 Run the PR-CI Pipeline 

To start the PR pipeline, you should create a merge request in your application repository. To achieve this, do the following:



1. On the CI toolchain page, click the application repository tile. By default, it gets created with a name compliance-app-<timestamp>.
2. Create a branch from master.
3. Update some code like in app or readme file and save changes.
4. Submit merge request.
5. Back on the CI toolchain page, click the pr-pipeline tile. The PR pipeline is initiated.



The corresponding Merge Request in your application repository is in "Pending" state until all the stages of PR Pipeline finish successfully.

After the PR Pipeline run is successful, you can click it to explore numerous steps completed.

Zoom

![DevSecOps PR Pipeline Successful](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/devsecops/images/devsecops-ci-explore-pr-pipeline-success.png)

Figure 22. DevSecOps PR Pipeline Successful



1. Navigate back to the merge request.
2. Merge the request so that your changes are copied to the master branch of your application repository: the CI pipeline is automatically triggered.



Simplified flow of tasks in the pipeline: (Utility tasks are omitted. For example, status-check update on GitHub, credential fetching, and so on).

Zoom

!
dest: /etc/ssh/sshd_config
regexp: "^X11Forwarding yes"
line: "X11Forwarding yes"
state: present

- name: Limit max authentication attempts to 3
lineinfile:
dest: /etc/ssh/sshd_config
regexp: "MaxAuthTries 6"
line: "MaxAuthTries 3"
state: present
notify: Restart ssh

- name: Restart ssh
service:
name: sshd
state: restarted
Show more

If you are creating the cyber-recovery immutable backup solution architecture, then the tasks are completed. For creating the cyber-recovery isolated recovery environment solution architecture, see [Creating the airgap by using Juniper vSRX](https://cloud.ibm.com/docs/vmwaresolutions/?topic=vmwaresolutions-veeam-cr-sag-vsrx).





 Related links 



* [Cyber recovery with Veeam architecture overview](https://cloud.ibm.com/docs/vmwaresolutions/?topic=vmwaresolutions-veeam-cr-sa-overview)
Action Method IAM ACTION AT ACTION 

 Get global load balancers GET /v1/{crn}/zones/{domain_id}/load_balancers internet-svcs.reliability.read internet-svcs.load-balancers.read 
 Create a global load balancer POST /v1/{crn}/zones/{domain_id}/load_balancers internet-svcs.reliability.manage internet-svcs.load-balancers.create 
 Update a global load balancer PUT /v1/{crn}/zones/{domain_id}/load_balancers/{glb_id} internet-svcs.reliability.update internet-svcs.load-balancers.update 
 Delete a global load balancer DELETE /v1/{crn}/zones/{domain_id}/load_balancers/{glb_id} internet-svcs.reliability.manage internet-svcs.load-balancers.delete 
 Get health monitors GET /v1/{crn}/load_balancers/monitors internet-svcs.zones.read internet-svcs.load-balancer-monitors.read 
 Create a health monitor POST /v1/{crn}/load_balancers/monitors internet-svcs.zones.manage internet-svcs.load-balancer-monitors.create 
 Update a health monitor PUT /v1/{crn}/load_balancers/monitors/{monitor_id} internet-svcs.zones.update internet-svcs.load-balancer-monitors.update 
 Delete a health monitor DELETE /v1/{crn}/load_balancers/monitors/{monitor_id} internet-svcs.zones.manage internet-svcs.load-balancer-monitors.delete 
 Get load balancer pools GET /v1/{crn}/load_balancers/pools internet-svcs.zones.read internet-svcs.load-balancer-pools.read 
 Create a load balancer pool POST /v1/{crn}/load_balancers/pools internet-svcs.zones.manage internet-svcs.load-balancer-pools.create
Get HTTP requests analytics by colocations GET /v1/{crn}/zones/{domain_id}/analytics/colos internet-svcs.reliability.read internet-svcs.colos-analytics.read 
 Get DNS analytics GET /v1/{crn}/zones/{domain_id}/dns_analytics/report internet-svcs.reliability.read internet-svcs.dns-analytics.read 







 WAF 



Table 6. WAF

 Action Method IAM ACTION AT ACTION 

 Get WAF packages GET /v1/{crn}/zones/{domain_id}/firewall/waf/packages internet-svcs.security.read internet-svcs.waf-packages.read 
 Change the sensitivity and action mode of a WAF package PATCH /v1/{crn}/zones/{domain_id}/firewall/waf/packages/{package_id} internet-svcs.security.update internet-svcs.waf-packages.update 
 Get WAF groups GET /v1/{crn}/zones/{domain_id}/firewall/waf/packages/{package_id}/groups internet-svcs.security.read internet-svcs.waf-groups.read 
 Enable / disable a WAF group PATCH /v1/{crn}/zones/{domain_id}/firewall/waf/packages/{package_id}/groups/{group_id} internet-svcs.security.update internet-svcs.waf-groups.update 
 Get WAF rules GET /v1/{crn}/zones/{domain_id}/firewall/waf/packages/{package_id}/rules internet-svcs.security.read internet-svcs.waf-rules.read 
 Change the action mode of a WAF rule PATCH /v1/{crn}/zones/{domain_id}/firewall/waf/packages/{package_id}/rules/{rule_id} internet-svcs.security.update internet-svcs.waf-rules.update 







 IP Firewall 



Table 7. IP Firewall

 Action Method IAM ACTION AT ACTION
"href": "https://us-south.iaas.cloud.ibm.com/v1/images/9aaf3bcb-dcd7-4de7-bb60-24e39ff9d366",
"id": "9aaf3bcb-dcd7-4de7-bb60-24e39ff9d366",
"name": "my-image"
},
"memory": 8,
"name": "my-instance",
"network_interfaces": [
{
"href": "https://us-south.iaas.cloud.ibm.com/v1/instances/e402fa1b-96f6-4aa2-a8d7-703aac843651/network_interfaces/7ca88dfb-8962-469d-b1de-1dd56f4c3275",
"id": "7ca88dfb-8962-469d-b1de-1dd56f4c3275",
"name": "my-network-interface",
"primary_ipv4_address": "10.0.0.32",
"resource_type": "network_interface",
"subnet": {
"crn": "crn:...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/subnets/7389-bea6a632-5e13-42a4-b4b8-31dc877abfe4",
"id": "bea6a632-5e13-42a4-b4b8-31dc877abfe4",
"name": "my-subnet"
}
}
],
"placement_target": {
"crn": "crn:[...]",
Action Method IAM ACTION AT ACTION 

 Get rate limiting rules GET /v1/{crn}/zones/{domain_id}/rate_limits internet-svcs.security.read internet-svcs.rate-limits.read 
 Create a rate limiting rule POST /v1/{crn}/zones/{domain_id}/rate_limits internet-svcs.security.manage internet-svcs.rate-limits.create 
 Update a rate limiting rule PUT /v1/{crn}/zones/{domain_id}/rate_limits/{ratelimit_id} internet-svcs.security.update internet-svcs.rate-limits.update 
 Delete a rate limiting rule DELETE /v1/{crn}/zones/{domain_id}/rate_limits/{ratelimit_id} internet-svcs.security.manage internet-svcs.rate-limits.delete 
 Get rate limiting analytics GET /v1/{crn}/zones/{domain_id}/rate_limit_analytics internet-svcs.security.read internet-svcs.rate-limit-analytics.read 







 Caching 



Table 11. Caching

 Action Method IAM ACTION AT ACTION 

 Purge all cached assets of a domain from edge server PUT /v1/{crn}/zones/{domain_id}/purge_cache/purge_all internet-svcs.performance.update internet-svcs.purge-cache-all.update 
 Purge cached assets by URLs from edge server PUT /v1/{crn}/zones/{domain_id}/purge_cache/purge_by_urls internet-svcs.performance.update internet-svcs.purge-cache-by-urls.update 
 Purge cached assets by cache tags from edge server PUT /v1/{crn}/zones/{domain_id}/purge_cache/purge_by_cache_tags internet-svcs.performance.update internet-svcs.purge-cache-by-cache-tags.update