What must be deleted for a tenant to be removed from Deep Security Manager?

For a tenant to be successfully removed from Deep Security Manager, all jobs and messages associated with that tenant must be deleted. This requirement ensures that any operational data, configurations, or ongoing processes related to that specific tenant do not persist after the tenant's account is removed.

In a multi-tenant environment like Deep Security Manager, each tenant may have scheduling jobs and messages that include alerts, logs, and reports tied to their specific settings and activities. Without clearing these, it could lead to confusion, data integrity issues, or orphaned processes remaining in the system.

This process of clearing jobs and messages not only maintains the cleanliness of the system but also ensures that upon removal, there’s no residual data that could impact reporting or future operations related to other tenants.

Clearing user associations or dealing with the tenant account itself does not directly relate to the requirement for deleting operational jobs and messages. Similarly, the notion of needing to delete an entire database for the tenant is not necessary and would be impractical in a well-structured tenant management system.