What should be done after configuring DSAs according to Connected Threat Defense steps?

After configuring Deep Security Agents (DSAs) as part of connected threat defense steps, it's crucial to gather and submit suspicious objects to the Deep Security Manager. This action is integral to maintaining the security posture of the environment. By submitting suspicious objects to the Deep Security Manager, the system can analyze the data, identify potential threats, and enhance its overall threat detection capabilities. This collaborative approach helps in building a more robust defense against emerging threats while allowing the management server to apply the latest defense strategies based on the collected data.

Submitting these objects allows for a proactive response to potential threats, ensuring that all detected items are appropriately categorized and dealt with, reducing the risk of a successful attack. It also ensures that the security environment remains up-to-date with threat intelligence, allowing for timely updates and refined security policies.

Other actions, such as submitting a quarterly report for compliance, forwarding suspicious object lists to external partners, or disabling unnecessary services, may be part of broader operational best practices but do not specifically address the immediate step following DSA configuration in the context of connected threat defense. These actions may occur at different stages or as ongoing practices, but they don't directly enhance the immediate operational capacity of the DSAs in gathering and processing threat information.