vSphere Integrated Containers Security Reference

The Security Reference provides information to allow you to secure your vSphere Integrated Containers implementation.

• Service Accounts, Privileges, and User Authentication
• Network Security
• External Interfaces, Ports, and Services
• Apply Security Updates and Patches
• Security Related Log Messages
• Sensitive Data

Service Accounts, Privileges, and User Authentication

vSphere Integrated Containers does not create service accounts and does not assign any vSphere privileges. The vSphere Integrated Containers appliance uses vCenter Single Sign-On user accounts to manage user authentication. You can optionally create example Single Sign-On user accounts for vSphere Integrated Containers Management Portal when you deploy the appliance. For information about the example user accounts, see User Authentication and Deploy the vSphere Integrated Containers Appliance.

VCH Authentication with vSphere

Using vic-machine to deploy and manage virtual container hosts (VCHs) requires a user account with vSphere administrator privileges. The vic-machine create --ops-user and --ops-password options allow a VCH to operate with less-privileged credentials than those that are required to deploy a new VCH. For information about the --ops-user option and the permissions that it requires, see Create the Operations User Account.

When deploying VCHs, you must provide the certificate thumbprint of the vCenter Server or ESXi host on which you are deploying the VCH. For information about how to obtain and verify vSphere certificate thumbprints, see Obtain vSphere Certificate Thumbprints. Be aware that it is possible to use the --force option to run vic-machine commands that bypass vSphere certificate verification. For information about the --force option, see --force in the topic on running vic-machine commands.

Docker Client Authentication with VCHs

VCHs authenticate Docker API clients by using client certificates. For information about VCHs and client authentication, see Virtual Container Host Security. Be aware that it is possible to use the --no-tlsverify and --no-tls options to deploy VCHs that do not authenticate client connections. For information about the --no-tlsverify and --no-tls options, see Disable Certificate Authentication.

Network Security

All connections to vSphere Integrated Containers Management Portal and Registry are encrypted and secured by HTTPS.

VMware highly recommends using a secure network for the VCH management network. For more information about connections to VCHs in general and the management network in particular, see Virtual Container Host Networks and Configure the Management Network.

External Interfaces, Ports, and Services

The following ports must be open on the vSphere Integrated Containers appliance, VCH endpoint VMs, and container VMs:

ESXi Hosts

ESXi hosts must have the following firewall configuration for VCH deployment:

• Allow outbound TCP traffic to port 2377 on the endpoint VM, for use by the interactive container shell.
• Allow inbound HTTPS/TCP traffic on port 443, for uploading to and downloading from datastores.

For information about how to open ports on ESXi hosts, see Open the Required Ports on ESXi Hosts.

vSphere Integrated Containers Appliance

The vSphere Integrated Containers appliance makes the core vSphere Integrated Containers services available.

VCH Endpoint VM

The different network interfaces on a VCH expose different services on different ports. For an overview of the different network interfaces on a VCH, see Virtual Container Host Networks.

Public Interface

Container developers can forward any VCH port that is not used elsewhere to a container VM. For more information about the VCH public interface, see Configure the Public Network.

Bridge Interface

For information about the VCH bridge interface, see Configure Bridge Networks.

Client Interface

For information about the VCH client interface, see Configure the Client Network.

For information about VCH TLS options, see Virtual Container Host Security. For information about how debugging VCHs affects VCH behavior, see , see Debug in the topic on configuring general VCH settings and Debug Running Virtual Container Hosts.

Management Interface

For information about the VCH management interface, see Configure the Management Network.

Container VMs

If container developers do not explicitly expose ports, container VMs do not expose any ports if they are not running in debug mode.

Security Updates and Patches

Download a new version of vSphere Integrated Containers and upgrade your existing appliances, the vSphere Client plug-in, and your VCHs. For information about installing security patches, see Upgrading vSphere Integrated Containers.

Security Related Log Messages

Security-related information for vSphere Integrated Containers Engine appears in docker-personality.log and vicadmin.log, that you can access from the VCH Admin portal for a VCH. For information about accessing VCH logs, see Access Virtual Container Host Log Bundles.

There are no specific security-related logs for the vSphere Integrated Containers appliance. To access logs for the appliance, see Access vSphere Integrated Containers Appliance Logs.

Sensitive Data

The VMX file of the VCH endpoint VM stores vSphere Integrated Containers Engine configuration information, which allows most of the configuration to be read-only by the guest. The container VMs might hold sensitive application data, such as environment variables for processes, command arguments, and so on.

vSphere Integrated Containers Management Portal securely stores the credentials for access to VCHs, Docker hosts, and registries. Any private elements of those credentials, such as passwords or private keys, are kept encrypted in the vSphere Integrated Containers Management Portal data store.