ENTERPRISE & PORTALS

Reliable access, from your website to your customer portal

Configure HTTPS, content acceleration and application protection for the company's official website, customer portal and public business entrance, taking into account daily releases and important business submissions.

THE CHALLENGE

Start with the workload

The official website is responsible for brand display, product inquiry and customer consultation, and the management backend and portal also involve login status and business information. Pages have different public scopes and cannot use the same set of caching and access rules.

  • Business and brand websites
  • Customer Service Portal
  • Enterprise external business system
BUILT AROUND YOUR WORKLOAD

Protect each critical path

01

Distribute display content nearby

Include product images, promotional materials, and page static resources in the cache, and establish a refresh process for page updates.

02

Configure forms and admin paths

The consultation form, customer inquiry and management portal are protected according to the path; responses involving personal data and login status are kept dynamically returned to the source.

03

Unify HTTPS and portal management

Check the main site, subdomains, redirects and certificate coverage. After integration, verify which origin endpoints remain publicly reachable.

Suggested integration path Confirm the protocol and delivery scope
  1. 01Visitor/Customer
  2. 02HTTPS / SCDN / WAF
  3. 03Official website origin server/portal and form
FROM PLAN TO PRODUCTION

Integration, step by step

  1. 01

    Inventory public-facing endpoints

    List the main site, subsites, portals, forms, and management addresses used for operation and maintenance.

  2. 02

    Configure policies by entry

    Access SCDN and certificates to distinguish public pages and restricted business paths.

  3. 03

    Check access and submission

    Verify redirection, consultation submission, file download and background login, and then arrange domain name switching.

Verify before launch

  • Check the main domain name, subdomain names and certificate coverage.
  • Verify form submissions, file uploads, and third-party notifications.
  • Check the background permissions, origin server entrance and domain name fallback method.
Monitor after launch

Pay attention to core page availability, form submission results, certificate validity and background abnormal access records.

QUESTIONS & ANSWERS

Frequently asked questions

Is the Personal or Basic suitable for corporate official websites?

You can choose based on traffic, domain name and protocol requirements; if you need WAF application protection, all three types of lines should choose the Standard or higher. The Personal and Basic do not include WAF.

Do I still need to log in to the management backend after accessing?

Needed. Account permissions, multi-factor authentication and business auditing are still maintained by enterprise applications. SCDN and WAF provide acceleration and application layer protection for external access.

Have other questions?Contact a technical advisor

BUILD WITH CONFIDENCE

Make every connection safer.

From personal projects to corporate operations, find the protection solution that's right for you.

Contact us