Update vsatctl to upgrade security of existing VSatellite connections
Table of Contents
Expand all | Collapse all
-
- Activate Next-Generation Trust Security
-
-
- Configure AWS connection
- Configure Azure Key Vault connection
-
- Workload Identity Federation authentication
- Workload Identity Federation - Azure Identity Provider authentication
- Next-Gen Trust Security Generated Key authentication
- User permissions
- Workload Identity Federation authentication
- Next-Gen Trust Security Generated Key authentication
- User permissions
- Supported OIDC claims
-
-
-
-
- Create an F5 BIG-IP LTM machine
- Create a Microsoft Azure Private Key Vault machine
- Create a Microsoft IIS machine
- Create a Microsoft Windows (PowerShell) machine
- Create a Microsoft SQL Server machine
- Create a Common KeyStore machine
- Create a Citrix ADC machine
- Create an Imperva WAF machine
- Create a VMware NSX Advanced Load Balancer (AVI) machine
- Create an A10 Thunder ADC machine
- Create a Cloudflare machine
- Create Kemp Virtual LoadMaster machine
- Create a Palo Alto Panorama machine
-
- Provision to an F5 BIG-IP LTM
- Provision to a Microsoft Azure Private Key Vault
- Provision to Microsoft IIS
- Provision to Microsoft Windows (PowerShell)
- Provision to Microsoft SQL Server
- Provision to a Common KeyStore
- Provision to a Citrix ADC
- Provision to an Imperva WAF
- Provision to VMware NSX Advanced Load Balancer (AVI)
- Provision to an A10 Thunder ADC
- Provision to Cloudflare
- Provision to a Kemp Virtual LoadMaster
- Provision to Palo Alto Panorama
-
-
- 47-Day Validity Readiness TLS Certificates dashboard
- About the Certificate Inventory
- Managing certificate lifecycle settings
- Reissuing certificates in Next-Gen Trust Security
- Downloading certificates, certificate chains, and keystores
- Retiring, recovering, and deleting certificates
- Finding certificates in the certificate inventory
- Importing certificates from a CA using EJBCA
- Notification Center overview
- Domain-based validation for external emails
- Managing user accounts
- Troubleshooting
Update vsatctl to upgrade security of existing VSatellite connections
Updated 11 February 2025
VSatellite has been updated to improve security by enabling TLS certificate validation when k3s connects to the Venafi registry. Previously, k3s did not validate TLS certificates, which could allow insecure connections. This security update is automatically applied to new VSatellite installations, but if you have existing VSatellite servers, you must manually update them.
To upgrade a VSatellite server
- Download the latest version of vsatctl:curl -O https://dl.venafi.cloud/vsatctlMake the file executable and run the security update:chmod +x ./vsatctl && ./vsatctl update securityIf your registries.yaml file is in a non-default location, specify the path:sudo ./vsatctl update security --registries-file /path/to/registries.yaml
Important considerations
- If you have custom configurations in registries.yaml, they will be overwritten when you run the security update.To preserve custom configurations, back up the file before updating:cp /etc/rancher/k3s/registries.yaml /etc/rancher/k3s/registries.yaml.bakAfter updating, manually reapply your custom configurations.Alternatively, you can skip running the security update and manually edit the registries.yaml file:
- Open the file in a text editor:nano /etc/rancher/k3s/registries.yamlLocate the insecure_skip_verify setting and change it to false:mirrors: your-registry: endpoint: - "https://your-registry-url" tls: insecure_skip_verify: falseSave and exit the file.Restart k3s to apply the changes:sudo systemctl restart k3s
How will I know if my server needs this update?
If your vsatctl is older than version 2.0.32, you should apply this update as a best practice to align with the latest security standards.Where can I get support?
For additional guidance or troubleshooting, contact CyberArk support or visit our Customer Support site.