The vCenter server must enable the OVF security policy for content libraries.

In the vSphere Client, you can create a local or a subscribed content library. By using content libraries, you can store and manage content in one vCenter Server instance. Alternatively, you can distribute content across vCenter Server instances to increase consistency and facilitate the deployment workloads at scale.

You can protect the OVF items by applying default OVF security policy to a content library. The OVF security policy enforces strict validation on OVF items when you deploy or update the item, import items, or synchronize OVF and OVA templates. To make sure that the OVF and OVA templates are signed by a trusted certificate, you can add the OVF signing certificate from a trusted CA.

Note: If Content Libraries are not used, this is not applicable.

From the vSphere Client, go to Content Libraries.

Review the "Security Policy" column.

If a content library does not have the "OVF default policy" enabled, this is a finding.

From the vSphere Client, go to Content Libraries.

Select the target content library.

Select "Actions" then "Edit Settings".

Click the checkbox to "Apply Security Policy". Click "OK".

Note: If you disable the security policy of a content library, you cannot reuse the existing OVF items.