The deployment is straightforward; I rate it nine out of ten for ease of setup. The time the solution takes to set up depends upon the deployment's scale and complexity, as well as the use case.

The deployment process was long. It took about two months for the last implementation I did.

The initial setup of Trend Micro Deep Security was easy. The setup process is GUI-based and straightforward. With just a few clicks, it can be installed on a virtual machine, and network access is then required. After installation, users can access the web application interface and proceed from there.

The deployment took approximately 10 to fifteen days if I exclude the network accesses.

The solution's initial setup process was straightforward. For deployment, we have more than a thousand servers. So, it took a month to roll out. One of the steps in the deployment process is leading the team involved in the technical part. We are deploying using Microsoft SAP. So through that, we push the agents to all the servers, and sometimes it requires a restart in some of the agent updates, and sometimes it doesn't require a restart. So, coordination is required during deployment.

For deployment and maintenance, four to five engineers are required.

The initial setup for Trend Micro Deep Security Version 20 was comfortable for me.

The solution is deployed on-premises.

Our company has multiple customers. Some customers have on-boarded the tool on-premises, while others have opted for SaaS models. With the SaaS deployment model, it takes only 20 to 30 mins to complete the setup phase if the license is already activated. For new users of the tool, once the license is activated, it initially needs some build-up for the entire deployment of the tool on the SaaS model, which then takes around a week because after a server gets ready, we have to coordinate with multiple teams.

I have seven years of experience with the setup phase of the tool.

The setup phase is carried out with the help of application control, web reputation, and integrity monitoring.

I would rate the easiness of the initial setup as a seven out of ten. Setting up Trend Micro Deep Security was not entirely straightforward. While there is a comprehensive solution, the complexity arises from the diverse components in our environment. Unlike a single-box setup, we manage multiple components, which requires careful configuration for effective deployment. It took three months to deploy the solution.

We find the solution very easy to set up, even for enterprises. We can set it up on primary and secondary servers.

Based on the requirements of the customer, we'll deploy the solution to match their needs.

We can install and implement the solution within one to two hours. It can be set up in 20 minutes; however, testing the use cases takes one to two hours on top of that. 

We always recommend a check of the servers before beginning. Whether it is Windows or Linux, we make sure we implement the latest security measures. 

We give the clients a checklist and go through everything once we begin the installation. Then we deal with the dependencies and the connectivity. 

The initial setup of the product was straightforward. All you need to do is install the firmware, ensure the firewall connections are open, and you are done. 

The initial setup is straightforward and only a matter of a couple of clicks. Once you have a design in place, deployment is not a challenge. In terms of time– one part goes into solution deployment and the other into solution adaptation. Solution deployment does not take much time; solution adaptation does.

The solution's initial setup was straightforward. It's not kind of a cumbersome one.

The deployment process did not take more than two months post-order placement for the solution. So, Trend Micro Deep Security and SOC are two separate parts. For SOC's deployment, we took around six to nine months. Trend Micro Deep Security is a type of endpoint security solution which, post procurement, takes around four to six weeks to configure.

Regarding the solution's deployment model, the managing, monitoring and diagnostics part of the solution is on the cloud, while all of our clients have chosen an on-premises deployment model. Basically, the clients are installed on physical devices.

Previously we had support for a deployment and maintenance procedure from the service provider. Currently, the solution is managed by our team as it is deployed on-premises.

The product offers a simple, straightforward setup. I'm not sure how long the deployment itself took. It was implemented three years ago, and I do not recall the exact strategy we used during implementation. 

I'm not sure how many people were involved in the initial deployment. 

The tool's setup is easy. The tool doesn't take more than five to eight minutes on average to deploy at an endpoint. 

We deployed the solution to about 3,000 servers. We had is implemented in lesss than three months. 

Once we get used to the product, it is easy to use.

The initial setup for Trend Micro Deep Security was very easy.

It's easy to deploy. I've deployed it for more than 12,000 devices, which includes endpoints and servers. It's easy to deploy and easy to manage. You can do it automatically through the script. The ease of implementation and ease of management are there, but there are a few challenges. Linux compatibility has some issues because it's a kernel-based rollout. Especially with CentOS, I face challenges. CentOS is now Red Hat, so if we are running CentOS, we have to deploy Red Hat agents and not CentOS agents. It's not that easy to manage on Linux. If it's a stable, standard Linux version, it works, but with beta versions, there are some challenges.

It can be complex to implement depending on what features you enable because Deep Security is such a comprehensive product. However, if we just enabled everything out of the box, then it's quite easy. Your choice of how many layers of security you want makes a difference.

The initial setup process is very simple. 

The deployment took one to two days. Within one day it was mostly deployed.

The solution was straightforward to install. There is a default version that is ready to use as soon as it is installed and anything specific that the company desires can then be set.

We have about six to eight people with access to management.

The solution is difficult to set up, maintain, and manage. There are a lot of options, a lot of buttons, a lot for new items. It's not very user-friendly. You need a lot of training to be able to manage and implement the solution correctly.

We have two system admins that manage servers. You need two people to manage and maintain the solution.

The initial setup was easy.

The integration and configuration of this product in our AWS environment was good. We haven't had any problems at all.

The implementation is straightforward. I rate the process a nine out of ten. We require a team of five executives for troubleshooting.

Setting up Deep Security isn't that complicated. The entire process takes 90 days, including a proof of concept to demo the product in the customer's environment and show them what it can do. Typically, it takes about 90 days to close a deal. We have 15 members on our team.

The initial setup was pretty straightforward. We were novices to the cloud anyways, so we were struggling with some of the ideas. But I think that if you're acclimated with AWS, it's pretty straightforward. We were struggling to learn cloud concepts and we couldn't understand how to ping horizontal scaling versus vertical scaling.

The solution is not too difficult and not exactly straightforward. It was a moderate setup. Anyone with a little bit of knowledge of installing antiviruses can actually handle the process. 

I'd rate the ease of setup a two or three out of five. 

The initial setup is complex.

The time for deployment depends on the size. You have different installations for different sizes.

The integration and configuration in our AWS is user-friendly. When you work with enterprise, you have a multi-cloud strategy. We can deploy it in AWS and use it in other clouds as well. So, it is pretty robust.

The solution provides proper documentation for setting it up. It's pretty easy. We can follow the steps in the video tutorials. It’s simple to configure. We installed Trend Micro Deep Security Manager on Windows Server and connected all the agents to it. The deployment took around five to seven minutes on each server. It depends on the network speed.

Deep Security is very easy to install. Installation didn't take much time, but after installing the center console, we needed to apply some kinds of policies, for which we needed some experience. It took some time to decide which policies we needed to apply and which rules we didn't want to apply, and for those things, we needed help from more experienced people—either Trend Micro support or their authorized partner's support. You can handle the installation on your own, with the help of some technical team. The implementation is not a very long-term process. 

The installation is the same as in Symantec. We have not installed the cloud-based version of Trend Micro. We have installed the on-premises version and it is easy to do.

To deploy the server, it will take 15 minutes and only five minutes to deploy each client.

The initial setup for this solution is straightforward.

For the deployment, we are using three cybersecurity engineers and three network security engineers.

The integration and configuration of this product in our AWS environment was very easy.

Installation is not an issue. They offer good support for installation. It is the run time of the program that is very critical for us. During run time, when there is an attack, the program should be able to identify it. If the program does not have a proper system to identify the attack, it will destabilize our entire security platform.

The solution is deployed on a private cloud in our organization. We have our own cloud partner. We don't use Azure or Google.

It does not take much time to deploy the solution. All the time taken for deployment and support comes under one particular point. The primary question is if a tool can neutralize the attacks. The function of an antivirus or security product is to make sure it neutralizes its situation or at least identifies the situation. If a tool does not neutralize attacks, it's a major drawback or unsuitable for an enterprise-grade business.

You can just run a script and deploy it in NAS. The deployment process is not an issue.

One engineer is fine to deploy it if he understands the script. He can deploy it using automation on all the systems, be it 1,000 or 20,000 systems.

Trend Micro Deep Security does not require maintenance. The tool has an auto-run feature, so all updates are automatic and we do not need to maintain it.

The complexity of the initial setup depends on the customer's environment. There are different methods of deployment. If it is an agentless deployment then there are prerequisites for that. The agent-based version is a bit easier to set up than the agentless version.

They have to go through setting up policies, which will take time to implement and fine tune. They have to make sure that the solution is communicating with the management server, and that there are no conflicts with other applications that are running. If there is anything that is broken or should not be running, then that is fixed. Once the initial application is perfectly up and running without any issues, and the policies have been fine-tuned, there should not be an issue.

Depending on the customer's environment, the deployment time varies. We have deployed some solutions in one day, while others have taken months to complete the fine-tuning. 

Generally, for any implementation, we will not use more than two staff. For cases with more than one hundred machines, this can be a challenge during deployment. 

Configuration in our AWS environment is straightforward and policy-based with inheritance, e.g., making it easy to align with Active Directory. Event-based triggers can automate the correct policy implementation.

The initial setup was easy. I rate the ease of setup a ten out of ten. The deployment took three days.

Deployment took a week or two because we didn't know what we were doing. But once we got it up, it's not like I had to install it multiple times. But if I did, it wouldn't be that bad. Deep Security is pretty low maintenance. It patches itself then downloads all the new buyer signatures, the common vulnerabilities, and everything like that. So it pretty much takes care of itself. However, when we're patching everything else, it could knock one of the agents offline. So we have to deal with that aspect a little bit.

The implementation process is not very complex. If the initial setup is just replacing a competitor antivirus with Trend Micro, it's very easy. The only thing you have to be sure of is that you are setting up the right functionality. Trend Micro Deep Security, has a lot of functions. If you want a classic antivirus, there are very few functions to set up. However, if you want a specific functionality, there may be more steps. There will be more fine-tuning that is required to make sure you are well-protected.

When you have start Deep Security on something that was not equipped with an antivirus, or equipped with, let's say, Bitdefender or Windows Defender, you have very few protections. If you don't take care of covering all these safety functions, you'll be vulnerable. That said, you need to be careful of which functions you activate. You need to make sure it makes sense in terms of the rest of your setup.

The initial setup process is straightforward. It requires two to three executives for implementation and takes five minutes to complete.

The tool's deployment is straightforward. 

Its installation is pretty easy. You can do the installation remotely because it is on the cloud, so you have access from anywhere.

Installation duration depends on how many servers you have, but it normally takes about four to five days. It is not just the installation. After installing it, you also have to do testing and other stuff.

The initial setup and deployment are not complex. The infrastructure is very good to operate. 

The deployment of the agent is very lightweight. It takes about 10 minutes to complete. 

The setup is simple as the agent provides a feature called as the Recommendation Scan. This scans the profiles of the host computer and provides recommendations on the appropriate signature and the policies to apply.

The installation of the agents, subsequent patching of the agents, etc. can be automated, thereby reducing the management overhead.

The initial setup is installed locally. It can be a bit complicated as we have to do it on-premises and we need to gain console access.

The setup is straightforward and takes around a month to deploy. We deployed through the SCCM tool.

It's in a complex technological space, typically proposed into NSX or cross-hybrid cloud scenario. There are a lot of moving parts and it's a challenging space to implement technologies and controls, but I think Trend Micro does it well.

It is easy. It takes about two hours.

The initial setup is not at all complex. Anybody can do the implementation. The length of time required for deployment depends on how many systems are being integrated.

The initial setup was straightforward and we didn't have any problem with it.

The integration and configuration of Trend Micro in our AWS environment was easy. We haven't had any issues with this at all.

It was a fairly standard install as we were not a large data centre. Trevor (then Martin) – both local Trend Micro techs - took about a day to get it all settled down. Over the next month, I made several support calls but mostly because I did not yet have the experience with it. After a month or so, I no longer needed the support.

Our initial setup was somewhat complex and required a significant interaction with Trend Micro support. This is a very new concept of taking the AV engine outside the VM and it took us some time to feel comfortable with the whole idea. It also required some deep understanding of how Trend Micro Deep Security “embeds” into a VMware environment, and that was not a easy task to master.

The setup was a little complex on the security side. But the endpoints -- desktops, laptops, were pretty easy. The server environments were a little more complicated and in-depth.

It is a bit more difficult because it needs a bit of hardware, etc. Deep Security is more complex to set up than web security. Implementing Deep Security properly is usually about a week's worth of work because of the change control in the company. It is the change control that's an issue.

In terms of people required for its deployment, one engineer is usually enough.

The deployment depends on how you set up your VMware environment and what features you’re using. Following the steps described in the Administrator and Deployment guides helps you to avoid any complications.

Deployment and post-deployment implementation are a little complicated. We can't touch servers, and we can't modify the settings. It should be automated, and Trend Micro should make the process more intelligent. The scope is broad, and you have to manually monitor the file scans and respond whenever there is a detection. 

The deployment itself is not that difficult because it's client based. So you want to install clients on each of those servers, and then you have to keep monitoring and adding features. You check the server's performance, and if everything is fine, you can keep adding servers. But post-implementation is time-consuming. You have to do monitoring, and that takes time. After you set up everything, it's not a full-fledged implementation. You have to keep on monitoring and configuring. 

And there are times when the malware protection or some other virtual patching is working fine, but you need a technician to get all the more advanced features to work. It takes around two or three technicians to implement. Our team is responsible for security while a different team handles server management. Then there are one or two people who manage the security console. And then, there are OEM support and SI support.

Its initial setup is straightforward. Deployment duration depends on the environment. Sometimes, we needed to deploy two or three devices, and we had to consult Trend Micro. Their best practices are also there.

The setup is straightforward. We initially procured the tool for 50 people and we've now implemented it for 200. There are many new customers coming in so we're looking to scale it to 1000 plus endpoints.

I was not a part of the installation. It was installed by our technical team.

This solution is maintained and deployed by a team of ten managers and engineers.

Starting off with agentless, it was complex. With agentless, you have a lot of moving parts and they all have to be in-sync and working together for the whole system to work. It adds a level of complexity with vShield, the DSVA's, and all the different moving parts.

We had an engineer come out and spend a week with us to help everything run smoothly.

The initial setup was not easy because when we deployed it, we had to restart our server, and needed permissions from our client.

It took approximately six months to deploy.

The initial setup is straightforward.

It can be installed in 30 minutes.

We have a team of five to maintain this solution.

The installation is straightforward.

The integration and configuration of Trend Micro in our AWS environment seemed pretty seamless.

It is complex to install. As I said, we were not well-guided, we did not get certified support, and we weren't trained according to best practices.

The setup is easy, as is the configuration.

The setup is fairly complex. The deployment took around two months.

The initial setup is straightforward. From a deployment perspective, I would say all vendors are quite similar.

It has a perfect SaaS which integrates with AWS, offering flexibility to deploy quickly and easily in the cloud.