vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Information system entry and exit points include, for example, firewalls, electronic mail servers, web servers, proxy servers, remote-access servers, workstations, notebook computers, and mobile devices. Malicious code includes, for example, viruses, worms, Trojan horses, and spyware. Malicious code can also be encoded in various formats (e.g., UUENCODE, Unicode), contained within compressed or hidden files, or hidden in files using steganography. Malicious code can be transported by different means including, for example, web accesses, electronic mail, electronic mail attachments, and portable storage devices. Malicious code insertions occur through the exploitation of information system vulnerabilities. Malicious code protection mechanisms include, for example, anti-virus signature definitions and reputation-based technologies. A variety of technologies and methods exist to limit or eliminate the effects of malicious code. Pervasive configuration management and comprehensive software integrity controls may be effective in preventing execution of unauthorized code. In addition to commercial off-the-shelf software, malicious code may also be present in custom-built software. This could include, for example, logic bombs, back doors, and other types of cyber attacks that could affect organizational missions/business functions. Traditional malicious code protection mechanisms cannot always detect such code. In these situations, organizations rely instead on other safeguards including, for example, secure coding practices, configuration management and control, trusted procurement processes, and monitoring practices to help ensure that software does not perform functions other than the functions intended. Organizations may determine that in response to the detection of malicious code, different actions may be warranted. For example, organizations can define actions in response to malicious code detection during periodic scans, actions in response to detection of malicious downloads, and/or actions in response to detection of maliciousness when attempting to open or execute files.
ibmcloud cis alert-policy glb-healthcheck-alert-update a2633e68-1a64-2512-a321-b64a17c7db7a --name test1 --emails test1@cn.ibm.com --enabled true --pools all --include-future-pools true -i "cis-demo"
<-- </section "id="section-update-glb-healthcheck-alert-examples" "> --><-- </section "id="section-update-glb-healthcheck-alert" "> --><-- <section "id="section-delete-alert-policy" "> --> ibmcloud cis alert-policy delete Delete an alert policy. cis alert-policy delete POLICY_ID -i, --instance INSTANCE] -f, --force] ! ! ! ! ! ! ! !
<-- <section "id="section-delete-alert-policy-options" "> --> Command options POLICY_ID: The ID of alert policy. Required.-i, --instance: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.-f, --force: Attempt to delete policy without prompting for confirmation.<-- </section "id="section-delete-alert-policy-options" "> --><-- <section "id="section-delete-alert-policy-examples" "> --> Examples delete an alert policy a2633e68-1a64-2512-a321-b64a17c7db7a. ibmcloud cis alert-policy delete a2633e68-1a64-2512-a321-b64a17c7db7a -f -i "cis-demo"
ibmcloud cis firewall-create -t ua-rules -d 31984fea73a15b45779fa0df4ef62f9b --json '{"mode": "block", "configuration": {"target": "ua", "value": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/603.2.4 (KHTML, like Gecko) Version/10.1.1 Safari/603.2.4"}}' -i "cis-demo"
ibmcloud cis firewall-create -t lockdowns -d 31984fea73a15b45779fa0df4ef62f9b --json '{"urls": ["api.mysite.com/some/endpoint"], "configurations": [{"target": "ip", "value": "127.0.0.1"}, {"target": "ip_range", "value": "2.2.2.0/24"}]}' -i "cis-demo"







 ibmcloud cis firewall-update 

Update a firewall rule.

ibmcloud cis firewall-update FIREWALL_RULE_ID (-t, --type Type) (--json @JSON_FILE | JSON_STRING) [-d, --domain DNS_DOMAIN_ID] [-i, --instance INSTANCE] [--output FORMAT]
[Deprecated] ibmcloud cis firewall-update FIREWALL_RULE_ID (-t, --type Type) (-s, --json-str JSON_STR | -j, --json-file JSON_FILE) [-d, --domain DNS_DOMAIN_ID] [-i, --instance INSTANCE] [--output FORMAT]



 Command options 



* FIREWALL_RULE_ID: The ID of firewall rule. Required.



-t, --type
: Type of firewall rule to create.
<-- </section "id="section-display-routing-analytics-examples" "> --><-- </section "id="section-display-routing-analytics" "> --><-- </section "id="section-routing" "> --><-- <section "id="section-security-events" "> --> Security events (Deprecated) Security events will be deprecated on October 26, 2020. Use ibmcloud cis firewall-event-analytics]ibmcloud cis firewall-event-analytics] ! instead. Manage how the Security Events performs using the following security-events command:<-- <section "id="section-list-security-event" "> --> ibmcloud cis security-events The security-events command is replacing the firewall-events command. It can pull up to 30 days of security events which may be triggered from a wider variety of sources (other than firewall) such as rate-limiting, L7 DDoS, and browser-integrity-check. With the new security-events command, you are able to list only firewall events by specifying the --source options.Retrieve a full log of security events include Firewall Rules, Rate Limiting, Security Level, Access Rules, WAF, User Agent Blocking, Zone Lockdown and Advanced DDoS Protection. ibmcloud cis security-events DNS_DOMAIN_ID --ip-class IP_CLASS] --method METHOD] --scheme SCHEME] --ip IP_ADDR] --host HOSTNAME] --protocol PROTOCOL] --uri URI] --ua USER_AGENT] --colo COLO] --ray-id RAY_ID] --kind KIND] --action ACTION] --cursor CURSOR] --country COUNTRY] --since START_DATE] --until END_DATE] --source SOURCE] --limit LIMIT] --rule_id RULE_ID] -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! ! ! !
* PHP[4] - Enable this rule set if PHP is used for this domain.
* Plone[5] - Enable this rule set only if the Plone CMS is used for this domain.
* Specials - Contains a number of rules that were created to deal with specific attack types.
* WHMCS[6] - Enable this rule set only if WHMCS is used for this domain.
* Wordpress - Enable this rule set only if the WordPress CMS is used for this domain.



The Specials rule set contains a number of rules appropriate for virtually all applications and websites on the internet. This rule set is the core of the security that our WAF offers, with rules that target common attacks like SQLi, XSS, and LFI. It is recommended that you always enable Specials.

Enable only the rule sets that correspond to your technology stack. For instance, if you use Wordpress, but no other technologies, enable only the Specials and Wordpress rule sets. Avoid enabling rule sets that are not relevant to your tech stack.

Select any of the specific rule sets to see further details about each of the rules included.

Use the CIS rule set to perform the following actions on each rule:



* Disable turns off the rule.
* Simulate logs the event, and does not block or challenge the visitor. You can still decide to set to Block or Challenge after you review the logs.
* Block blocks the request entirely, with no option to bypass it for that request.
* Challenge displays a challenge (CAPTCHA) page that must be completed before the request in question is allowed access.



You might notice that the names of the rules don't reveal exactly how they work and that they are mostly a general summary of their function. This is deliberate. For security purposes, CIS does not reveal the code (or other exact information) used to filter traffic. Doing so prevents malicious actors from reverse engineering it to bypass our defenses.





 OWASP rule set 

The OWASP rule set for WAF contains generic attack detection rules. The OWASP rules protect against many common attack categories, including SQL injection, cross-site scripting, and local file inclusion. CIS provides, but does not curate these rules.
CIS does not write or curate OWASP rules. Click on a ruleset name under Group to reveal the rule descriptions. Unlike the CIS Managed Ruleset, specific OWASP rules are either turned On or Off.

To manage OWASP thresholds, set the Sensitivity to Low, Medium, or High in the Package: OWASP ModSecurity Core Rule Set section. Setting the Sensitivity to Off disables the entire OWASP package, including all its rules. Determining the appropriate Sensitivity depends on your business industry and operations. For instance, a Low setting is appropriate for large file uploads.

With a High Sensitivity, large file uploads trigger the WAF.

The Activity log displays Rule ID 981176 when a request is blocked by OWASP. Also, some OWASP rules listed in the Activity log do not appear in the list of rules under Package: OWASP ModSecurity Core Rule Set because disabling those rules is not recommended.
"api.mysite.com/some/endpoint"
],
"configurations": [
{
"target": "ip",
"value": "127.0.0.1"
},
{
"target": "ip_range",
"value": " 2.2.2.0/24"
}
]
}

-s, --json-str
: Deprecated. The JSON data describing a firewall rule.

-j, --json-file
: Deprecated. A file contains input JSON data.

-i, --instance
: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.

--output
: Specify output format, only JSON is supported.





 Examples 

Create firewall rules.

ibmcloud cis firewall-create -t access-rules --json '{"mode": "block", "notes": "This rule is added because of event X that occurred on date xyz", "configuration": {"target": "ip", "value": "127.0.0.1"}}' -i "cis-demo"
ibmcloud cis firewall-create -t ua-rules -d 31984fea73a15b45779fa0df4ef62f9b --json '{"mode": "block", "configuration": {"target": "ua", "value": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/603.2.4 (KHTML, like Gecko) Version/10.1.1 Safari/603.2.4"}}' -i "cis-demo"
* [Overview of potential points of failure in IBM Blockchain Platform](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-haibp-console-ha-points-of-failure-overview)



* [Peer considerations](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-haibp-console-ha-peers)
* [Ordering service considerations](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-haibp-console-ha-ordering-service)
* [Certificate Authority (CA) considerations](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-haibp-console-ha-ca)



* [HA Checklist](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-haibp-console-ha-checklist)
* [Potential points of failure](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-haibp-console-ha-points-of-failure)



* [Single region HA](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-haibp-console-ha-single-region)
* [Multizone HA](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-haibp-console-ha-multi-zone)
* [Multi-region HA](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-haibp-console-ha-multi-region)



* [Disaster recovery (DR)](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-haibp-console-ha-dr)
ibmcloud cis ratelimit-rule-update 31984fea73a15b45779fa0df4ef62f9b 372e67954025e0ba6aaa6d586b9e0b59 --json '{"disabled":false,"description":"Prevent multiple login failures to mitigate brute force attacks","match":{"request":{"methods":"GET","POST"],"schemes":"HTTP","HTTPS"],"url":".example.org/path"},"response":{"status": 403, 401],"headers":{"name":"Cf-Cache-Status","op":"ne","value":"HIT"}]}},"bypass":{"name":"url","value":"api.example.com/"}] ! ! ! ,"threshold":60,"period":900,"action":{"mode":"challenge","timeout":86400,"response":{"content_type":"text/xml","body":"<error>This request has been rate-limited.</error>"}}}' -i "cis-demo"
<-- </section "id="section-update-ratelimit-examples" "> --><-- </section "id="section-update-ratelimit" "> --><-- <section "id="section-list-ratelimit-rules" "> --> ibmcloud cis ratelimit-rules List rate limiting rules of a given DNS domain. ibmcloud cis ratelimit-rules DNS_DOMAIN_ID -i, --instance INSTANCE] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-list-ratelimit-rules-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain.
A member can be dynamically added to the network by a user with registrar privilege. Members are also assigned roles and attributes, which control their access and authority on the network. Neither roles nor attributes can be assigned dynamically though. Hyperledger Fabric supports the addition or removal of members, peers, and ordering service nodes, without compromising the operations of the overall network. Dynamic membership is critical when business relationships adjust and entities need to be added or removed for various reasons.





 Endorsement 

The process by which transactions are validated. Endorsement rules are implemented by specifying endorsement policies, which define the organizations that must approve of a transaction.





 Endorsement policy 

Defines the peer nodes on a channel that must execute transactions that are attached to a specific application, and the required combination of responses (endorsements). A policy could require that a transaction be endorsed by a minimum number of endorsing peers, a minimum percentage of endorsing peers, or by all endorsing peers that are assigned to a specific application. Policies can be curated based on the application and the desired level of resilience against misbehavior, whether deliberate or not, by the endorsing peers. A submitted transaction must satisfy the endorsement policy before it is marked as valid by committing peers. A distinct endorsement policy to deploy transactions is also required.





 Genesis block 

The configuration block that initializes a blockchain network or channel, and also serves as the first block on a chain.





 Gossip 

Hyperledger Fabric allows peers to gather important network information from each other without having to rely on the ordering service. The [gossip data dissemination protocol](https://hyperledger-fabric.readthedocs.io/en/release-2.2/gossip.html) provides a secure, reliable, and scalable way for peers to exchange messages between each other. For example, if peers miss some blocks because of delays, network outages, or other reasons, they can sync up to the current ledger state by using gossip messaging to contact other peers in possession of these missing blocks.





 HSM 

Hardware Security Module. Provides on-demand encryption, key management, and key storage as a managed service.
Actions



Table 121. Platform roles - NeuralSeek
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As an administrator, you can perform all platform actions based on the resource this role is being assigned, including assigning access policies to other users. 
 Editor As an editor, you can perform all platform actions except for managing the account and assigning access policies. 
 Operator As an operator, you can perform platform actions required to configure and operate service instances, such as viewing a service's dashboard. 
 Viewer As a viewer, you can view service instances, but you can't modify them. 







 Partner Center 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use partner-portal for the service name.

Platform roles

Actions



Table 122. Platform roles - Partner Center
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As an administrator, you can perform all platform actions based on the resource this role is being assigned, including assigning access policies to other users. 
 Editor As an editor, you can perform all platform actions except for managing the account and assigning access policies. 
 Viewer As a viewer, you can view service instances, but you can't modify them. 







 Personality Insights 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use personality-insights for the service name.

Platform roles

Service roles

Actions



Table 123. Platform roles - Personality Insights
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator null
Managing access for CIS 

Access to IBM Cloud® Internet Services service instances for users in your account is controlled by IBM Cloud Identity and Access Management (IAM). Every user that accesses the (CIS) service in your account must be assigned an access policy with an IAM role defined. The policy determines what actions a user can perform within the context of the service or instance that you select. The allowable actions are customized and defined by the IBM Cloud service as operations that are allowed to be performed on the service. The actions are then mapped to IAM user roles.

Policies enable access to be granted at different levels. Some of the options include the following:



*  Access across all instances of the service in your account
*  Access to an individual service instance in your account



After you define the scope of the access policy, you assign a role, which determines the user's level of access.

Review the following table that outlines what actions each role allows within the (CIS) service. The platform and service roles for CIS are listed under "Internet Services". If you're using the CLI or API to assign access, use internet-svcs for the service name.

Platform management roles enable users to perform tasks on service resources at the platform level, for example, assign user access for the service and create or delete instances.

For more information about IAM roles, see [Getting Started with IAM](https://cloud.ibm.com/docs/vpc?topic=vpc-iam-getting-started).



Table 1. IAM user roles and actions

 Platform management role      Description of actions                                     

 Manager                       Create and delete instances, domains, and configurations.  
 Reader                        View information about instances and domains.              
 Service Configuration Reader  Read services configuration for Governance management.     
 Writer                        Change existing configurations.                            



For information about assigning user roles in the console, see [Managing access to resources](https://cloud.ibm.com/docs/account?topic=account-assign-access-resourcesassign-access-resources).
What do I do if I’m under a DDoS attack? 

  Why it’s happening 

Your site is under DDoS attack.

  How to fix it 

To help resolve a DDoS attack, take the following steps:



1.  Turn on "Defense Mode" from your dashboard.
2.  Set your DNS records for maximum security.
3.  Do not rate-limit or throttle requests from CIS.



During "Defense Mode", each new visitor is met with a "Captcha" security challenge, which they must pass before being given a cookie for unchallenged access. That way, botnet traffic is blocked until the "Defense Mode" is turned off. Visitors that do not meet the security challenge are added to the (bad) IP Reputation database.
* [What are computer networking solutions](https://www.ibm.com/cloud/learn/networking-a-complete-guidetoc-computer-n-9C7jokVu)



* How to



* [Managing your CIS deployment](https://cloud.ibm.com/docs/cis?topic=cis-manage-your-cis-deployment)
* [Managing origin certificates](https://cloud.ibm.com/docs/cis?topic=cis-cis-origin-certificates)
* [Getting CIS running with a new subdomain](https://cloud.ibm.com/docs/cis?topic=cis-get-started-new-subdomain)
* [Adding domains to your CIS instance](https://cloud.ibm.com/docs/cis?topic=cis-multi-domain-support)
* [Setting up your Domain Name System for CIS](https://cloud.ibm.com/docs/cis?topic=cis-set-up-your-dns-for-cis)
* [CIS DNS zone CNAME (partial) setup](https://cloud.ibm.com/docs/cis?topic=cis-cname-setup)
* [Configuring rate limiting](https://cloud.ibm.com/docs/cis?topic=cis-cis-rate-limiting)
* Working with Range applications



* [Protecting TCP traffic (Range)](https://cloud.ibm.com/docs/cis?topic=cis-cis-range)
* [Enabling Proxy protocol](https://cloud.ibm.com/docs/cis?topic=cis-enable-proxy-protocol)



* [Using service endpoints to privately connect to CIS](https://cloud.ibm.com/docs/cis?topic=cis-service-endpoints)
* Working with TLS



* [Setting Transport Layer Security (TLS) options](https://cloud.ibm.com/docs/cis?topic=cis-cis-tls-options)
For more information, view [Managing your CIS deployment for optimal reliability](https://cloud.ibm.com/docs/cis?topic=cis-manage-your-ibm-cloud-internet-services-deployment-for-optimal-reliability). 
 Origin Cache Control Determines what content is cached from the origin and how often the content is updated. For more information, view [Managing your CIS deployment for optimal reliability](https://cloud.ibm.com/docs/cis?topic=cis-manage-your-ibm-cloud-internet-services-deployment-for-optimal-reliability). 
 Forwarding URL URL to use in case the website is unavailable. Using this setting disables all other setting configurations because you are forwarding the request somewhere else. For more information, view [Managing your CIS deployment for optimal reliability](https://cloud.ibm.com/docs/cis?topic=cis-manage-your-ibm-cloud-internet-services-deployment-for-optimal-reliability). 
 Host Header Override Replaces the host header for the URI matching the page rule to the value specified. This is commonly used for content that is hosted in an S3 bucket. 
 Disable Apps Turns off all CIS apps. Enterprise only 
 Origin Error Page Pass-through Disables CIS error pages that would trigger for issues that are sent from the origin server, and instead displays the error pages set at the origin. Enterprise only 







 Performance 



Table 3. Performance rules

 Setting Behavior Considerations 

 Browser Cache TTL Controls how long resources that are cached by client browsers remain valid. 
 Bypass Cache on Cookie Serves a cached object unless a cookie of a specific name is seen; for example, serve a cached version of the home page unless we see a SessionID cookie indicating that the customer is logged in and should be presented personalized content.