Skip to main content

Start using CloudConnexa

The key steps to get started and customize your WPC to meet your needs are shown below:

  1. Sign up for a CloudConnexa account.

  2. Do you want remote access to an application or service on your private network? Add your application server (a remote desktop server, network-attached storage, or a file server) as a Host. Connect your server to CloudConnexa using a Host Connector.

  3. Do you want connectivity to a private network for remote access, site-to-site networking, using it as an internet gateway, or access to private and internet applications? Add a Network. CloudConnexa has a configuration wizard that makes it easy. Connect your network to a CloudConnexa Region using an OpenVPN compatible router, an IPsec compatible router (feature in closed beta testing), or one or more Network Connectors.

    1. Do you know the IP subnets of the networks you are connecting? You need not add the private network with IP subnet routes. Just configure Applications, and CloudConnexa will take care of the routing.

    2. Do you know if another network you want to add has the same IP address ranges as the one already connected? Use Application Domain-Based Routing and add networks (even those with conflicting or overlapping IP subnets) just using Applications.

  4. Test out the connectivity with your device.

  5. Do you want to categorize your users by role or department? If you have users with common characteristics you want to group together and use later for access control, create User Groups.

  6. How will you authenticate your users? Choose SAML or LDAP as one of the authentication methods if you do not want to provision your users directly in CloudConnexa using username/password. Enable 2FA if not using SAML, and don't forget about User Group mapping if using SAML or LDAP.

  7. Is it access policy time? Yes, it is. First, set the global access policy to default deny and then configure Access Groups to allow access only to authorized applications, following the least privilege paradigm.

  8. Let us not forget to take device identity and location into context while making access decisions.

  9. With access policies set, monitor who is accessing your applications and whether access controls work as expected.

  10. How about controlling user access to the internet? you can manage the internet access configuration for Users, Networks, and Hosts all in one place.

  11. Can CloudConnexa protect users from cyber threats even if you are not sending internet traffic to CloudConnexa? yes, Cyber Shield uses DNS-based content filtering to block access to malicious content and other content categories while allowing you to route internet traffic as desired.

  12. What about traffic transiting CloudConnexa? Are there any protections in place? CloudConnexa has a built-in IDS/IPS that can monitor for and block malicious traffic and attacks on traffic passing through it with Cyber Shield Traffic Filtering.

  13. Is it time to upgrade? Did a network go offline? rest easy by turning on notifications for various events of interest.

  14. Can you do all this configuration with Terraform or an API? Yes, automate with the CloudConnexa API or the Terraform CloudConnexa Provider.

  15. Do you need another WPC? Using the same account, you can create another completely isolated virtual overlay network and dedicate it to IoT devices, another department, etc. Learn more.

  16. Using AppHub, you can share a private application with another WPC you own or with a trusted third party. Replace extranet with CloudConnexa.

  17. Finally, log streaming lets you get all the CloudConnexa logs to your SIEM or XDR, enabling you to maintain a unified view of your IT environment.