WilliamLam.com

After successfully deploying vDefend Security Services Platform (SSP) 5.2 in my VCF 9.1.1 environment, I came to learn that SSP requires at least 1,000 unique flows before it can generate a security assessment of your environment.

Similarly, SSP also requires a minimum of three days of collected flow data before it can generate a flow capacity assessment.

If you have a small lab environment like myself, generating 1,000 unique flows can be difficult, and having to wait several days to demonstrate certain SSP capabilities may not be ideal, especially for proof-of-concept deployments. Here is how you can work around these default requirements when deploying SSP in a lab environment.

Disclaimer: This is not officially supported by Broadcom, please use only in a non-production environment for lab and learning purposes.

[Read more...]

After recently sharing my automation for deploying the vDefend Security Services Platform (SSP) 5.2 Installer, the next logical step was automating the configuration of the SSP Installer and deployment of an SSP Instance. To make this easy and reusable, I have created a new PowerShell Module for vDefend SSP that automates these workflows from end to end.

[Read more...]

After successfully deploying the vDefend Security Services Platform (SSP) 5.2 Installer, which I recently built some automation for, the next step is to deploy an SSP Instance. I was surprised to see there was a fairly hefty minimum storage pre-check of a little over 3.5TB, something I certainly hope my lab never gets close to consuming! Since thin provisioning is already used by default, ideally the minimum storage requirement should simply reflect what is needed for the selected form factor.

😅Fortunately, there is a workaround to skip the minimum storage pre-check and allow us to proceed with the SSP Instance deployment.

Disclaimer: This is not officially supported by Broadcom, please use only in a non-production environment for lab and learning purposes.

[Read more...]