DDoS Protection Service Outage Response

When a DDoS Protection service outage occurs, follow the steps below to address and respond to the issue.

Service outage detection

• The service owner will become aware of a failed service URL health check or a response error.
• The security monitoring center will encounter SECaaS service disruptions and cause the registered Origin Healthcheck to fail.

Remediation

• After identifying the cause of the failure, if it is determined to be a SECaaS service outage, you must change the registered CNAME/A Record values to the original service’s Origin IP/address for redirection (reversion) and apply them. Since DNS values need to be changed, the user must handle it directly.
• When an urgent bypass (restoration) is required.
  • SECaaS(DDoS Protection) → Server(Origin) Open the segment firewall to any.
  • You can achieve the same effect by asking the SECaaS administrator to request DNS bypass processing in the SECaaS settings. (It is applied based on the DNS TTL value and takes about five minutes.)
  • Websites that have DNS applied via an A Record value, such as a root (naked) domain, cannot be used.

SECaaS reapplication

After the outage is resolved, reapply the modified CNAME/A Record values to the SECaaS CNAME/A Record address.