Deploying Tenable.io Container Security is straightforward, and we completed it in under two days, including the time we spent setting up the prerequisites. You can complete it in less time if you have the prerequisites in place already. You have to create an instance on the cloud within EC2 or wherever you plan to host the container, whether AWS or a private cloud.

We deployed it with a little guidance and coordination from the Tenable team. It's a cloud-based solution, so they need to make changes on their side and set up a tenant for the customer. Tenable products are mature and user-friendly, so you can deploy them quickly if you're familiar with the vendor. 

The best part about Tenable.io Container Security is that they have well-prepared guidebooks for their deployment. Initially, we had queries and questions about deployment, but after we completed it for one or two clients, it was easier for us.

The amount of people needed for deployment depends on the engagement and the number of applications. It is usually a consultant on one application, but an entire application security team is involved. On average, deployment takes around one or two weeks. No maintenance is required, but we need to ensure connectivity with the Tenable Portal. This ensures it updates whenever there are new updates or patches from the back end. Tenable.io Container Security is suitable for all companies.

I rate Tenable.io Container Security's deployment a seven out of ten. You need two people to manage its deployment. The tool updates automatically after every 24 hours. 

The initial setup of Tenable.io Container Security is a little bit complex.

If you have a bigger cluster or container environment, then the solution's deployment phase may take more than three months since you won't directly go for the solution's block mode. To start things in the solution, you will have to deploy it in SIEM mode, while the detection mode will provide you with visibility in accordance with which you need to take actions for production, which needs time. Regarding the time taken for deployment, for detection, it may not take more than a week, but in production, it may take at least three months to be completed.

For the deployment process, there are some scripts available along with some YAML files that you need to run on the cluster, specifically considering the cluster you want to focus more on before creating Tenable Cloud Security Console. After creating Tenable Cloud Security Console, you can proceed with the onboarding process.

It's a straightforward implementation. Once you receive the key, you need to enter the PIN number and, through the internet, it automatically detects the version and internet. It downloads packages seamlessly. One point to note here is that once the license is over, you can only access the completed files but you cannot initiate new scans.