In a world of accelerating safety threats, IBM Cloud provides quite a lot of options to help you in safety and compliance. We now have integrated a number of IBM Cloud providers into our Citrix-DaaS resolution, enabling you to simply rise up a safe deployment out of the field. In managing your menace vectors, it’s a good suggestion to have a single level of entry into your VPC. Moreover, having zero publicity to the web and encryption helps forestall attackers from compromising your deployments. Centralized logging helps you observe down points in your surroundings shortly and successfully.
If you happen to require stricter safety and compliance requirements inside your Citrix DaaS deployment on IBM Cloud, you should utilize these IBM Cloud sources and options to customise your workload safety:
- Bastion host: Supplies a safe technique to entry distant situations inside a Digital Non-public Cloud (VPC).
- Consumer-to-site VPN: Supplies client-to-site connectivity, which permits distant units to securely hook up with the VPC community by utilizing an OpenVPN software program consumer.
- Buyer-managed encryption: Protects information whereas in transit from block storage to the host/hypervisor and whereas at relaxation in volumes.
- Entry management listing (ACLs): Used with safety teams to limit entry to NIC port ranges.
- Log evaluation: Makes use of IBM Log Evaluation to supply logs multi function place.
Provision a bastion host
A bastion host is an occasion that’s provisioned with a public IP handle and will be accessed through SSH. After setup, the bastion host acts as a bounce server, permitting safe connection to situations provisioned and not using a public IP handle.
Earlier than you start, it is advisable create or configure these sources in your IBM cloud account:
- IAM permissions
- VPC Subnet
- SSH Key
To cut back the publicity of servers inside the VPC, create and use a bastion host. Administrative duties on the person servers are carried out by utilizing SSH, proxied by way of the bastion. Entry to the servers and common web entry from the servers (e.g., software program set up) are allowed solely with a particular upkeep safety group that’s hooked up to these servers.
For extra data, see Securely access remote instances with a bastion host.
If you wish to arrange a bastion host that makes use of teleport, see Setting up a bastion host that uses teleport.
Create a client-to-site VPN for safety
The VPN server is deployed in a particular multi-zone area (MZR) and VPC. All digital server situations are accessible from the VPN consumer within the single VPC:
You may create your VPN server in the identical area and VPC the place your DaaS deployment resides.
Relying on the consumer authentication you chose throughout VPN server provisioning, customers can hook up with the VPN server by utilizing a consumer certificates, consumer ID with passcode or each.
Now you possibly can hook up with your DaaS VSIs out of your native machine(s) by utilizing personal IP solely.
Use customer-managed encryption to encrypt your information end-to-end
By default, VPC volumes are encrypted at relaxation with IBM provider-managed encryption. There isn’t a further value for this service. For end-to-end encryption in IBM Cloud, you may as well use customer-managed encryption the place you possibly can handle your individual encryption. Your information is protected whereas in transit from block storage to the host/hypervisor and whereas at relaxation in volumes.
Buyer-managed encryption is offered in VPC by utilizing IBM Key Protect for IBM Cloud or IBM Hyper Protect Crypto Services (HPCS). The Key Shield or HPCS occasion should be created and configured earlier than the order circulation inside Citrix-DaaS. The Identification quantity encryption choice on the Citrix-DaaS order UI is then used to encrypt every identification disk related along with your machine catalog inside Citrix Machine Creation Companies (MCS).
Use entry management lists to limit port ranges
By default, Citrix-DaaS deployments create a number of safety teams (SGs) designed to isolate entry between NICs. For extra data on SGs, see About security teams. There isn’t a inbound entry from the web by default until you select to assign floating IPs (FIP). We advocate organising VPN as described on this article over utilizing FIPs. Safety teams include a limitation of 5 SGs per community interface card (NIC), which leaves some pointless port ranges open that may be additional restricted by utilizing entry management lists (ACLs).
Use IBM Log Evaluation to observe logs for compliance and safety
For many Citrix-DaaS deployments, centralized logging is necessary. With out centralized logging, you might be pressured to seek out logs for every particular person part throughout a number of sources. For instance, some logs are on the Cloud Connector VSIs (Connector Logs and Plug-in) and Area Controller logs are on the Lively Listing Server. If you’re utilizing Quantity Employee, logs are cut up between IBM Cloud Capabilities and the employee VSIs that full the roles. A few of these logs are ephemeral and aren’t accessible if not being recorded by centralized logging.
Centralized logging is offered by utilizing an IBM Log Analysis occasion and might present logs multi function place. IBM Log Evaluation can both be provisioned with the Citrix-DaaS deployment or an ingestion key for an current occasion offered by way of a Terraform variable. As a result of centralized logging is extraordinarily necessary for this product, it’s enabled by default; optionally (with a Terraform variable), it may be disabled.
A number of IBM Cloud providers are integrated into the Citrix DaaS resolution, so you possibly can simply rise up a safe deployment out of the field. You may configure stricter safety inside your deployment on IBM Cloud. Based mostly on the enterprise wants, you possibly can customise the safety precautions that you just require to combine along with your deployment.