What is not supported with virtual services?

SecureConnect is not supported with virtual services because it typically relies on establishing direct, secure connections between endpoints and services in a physical or hybrid environment. Virtual services often involve dynamic, ephemeral instances that may not adhere to the same security protocols or architectures as traditional services, thereby limiting the application of SecureConnect in these contexts.

In contrast, policy generation, monitoring tools, and traffic analysis are generally compatible with virtual services. Policy generation can still create and enforce security policies for virtualized environments, while monitoring tools can track performance, compliance, and security metrics. Traffic analysis, similarly, can be applied to analyze flows within virtual networks, allowing for insights into vulnerabilities and behaviors that might require attention. Understanding these distinctions helps clarify the challenges and capabilities specific to managing policies for virtual services in a cloud-oriented or virtualized landscape.