New in the Deep Security 12 Feature Release API

The following changes have been made since the release of the Deep Security 12.0 API. Also see What’s New in the Deep Security Help Center for information about general product changes.

New features

Container control

The Container Control module controls whether a container can run on a Docker host that is protected by a Deep Security Agent, based on parameters that you configure. You can block privileged containers from running, or allow them to run but log an event. If you have Deep Security Smart Check running in your environment, you can also block containers where Smart Check has found malware or vulnerabilities.

Use the CRUD operations of the /api/registryscanners endpoint to automate your Container Control tasks. For more information see the Configure Container Control and Connect Smart Check and Manager guides.

Google Cloud Platform integration

Google Cloud Platform (GCP) has been integrated with Deep Security. You can now view new GCP instances that come online or are removed, and which instances have protection. If you are using multiple clouds on-premise and in your data center, Deep Security can provide visibility for all of your environments.

Use the /api/gcpconnectors endpoint to automate your GCP-releated tasks. For more information, see the Google Cloud Platform (GCP) Connector guide.


  • The response time has been greatly reduced when calling
  • The response to /api/administrators operations now includes the lastPasswordChange field
  • You can now search on the hostGUID field when searching computers
  • The AzureVirtualMachineSummary property of the Computers API now includes the Azure Subscription ID. See the sample for a 200 response for the Describe a Computer operation in the API Reference.
  • Improved the error message when locked-out API keys are used
  • Added an error message to /api/computers for attempts to delete a cloud-connected computer
  • Improved the error message that is returned when you use an invalid computer group ID as an argument for the operations of /api/computers and /api/computergroups

New and updated content

Resolved issues

  • Fixed an issue where /api accepted requests to enable SAP on computers that do not support SAP
  • Fixed an issue with the API key wizard where the wizard immediately saved the API key when the user specified the role ID
  • Fixed an issue where GET /api/tenants (i.e. list all tenants) would not return a response if a tenant was in a state of suspension due to a database lock
  • Fixed an issue with the /api/systemsettings/ endpoint that caused a 4xx error response
  • Fixed an issue with /api/systemsettings and the platformSettingAgentInitiatedActivationEnabled setting where setting values sometimes didn’t match the value that was displayed in the Deep Security Manager GUI
  • The SOAP API can no longer be used to delete Deep Security Rule Updates that are currently applied
  • Fixed an issue in the antiMalwareEventRetrieve endpoint of the legacy SOAP API