Portal Licensing and Downloads¶
The customer portal provides entitled downloads, licence state, update visibility, and support access. Licence issuance and artifact delivery are separate operations. See Editions and Licensing for edition-specific terms, capability ceilings and allocation rules.
Downloads¶
Customer-visible downloads should be delivered from the portal with entitlement checks, checksums, and short-lived access where enabled.
Download types¶
| Type | Purpose |
|---|---|
| Host packages | .deb and .rpm packages for Linux hosts. |
| Container archives | OCI archive delivery for container deployments. |
| Client tools | CLI and desktop/admin tooling. |
| Checksums | Integrity validation. |
Best practices¶
- Verify checksums before installing.
- Keep downloaded artifacts in an internal repository where required by customer policy.
- Do not publish private registry paths or customer tokens in tickets or documentation.
- Use the portal for support and entitlement visibility.
GEO Database Licensing¶
VNetArmor licensing controls access to VNetArmor product capabilities and supported modules. GEO country lookup data is separate.
If a deployment uses GEO location filtering, the customer must provide a compatible GEO database or trusted upstream GEO metadata. Commercial GEO databases are not supplied as part of the VNetArmor software license unless specifically stated in a written agreement.
Customers are responsible for:
- Selecting an approved GEO data provider.
- Purchasing and maintaining any required third-party GEO database license.
- Complying with the provider's download, update, usage, and redistribution terms.
- Keeping GEO data updated according to operational and security requirements.
See GEO Location Filtering and Database Licensing for deployment and operations guidance.