Tufin Initial Setup

Arturo Morante
Network Architect at a transportation company with 10,001+ employees
The setup was straightforward, absolutely. The only problem we had was with Check Point, but I think it's a Check Point problem, not a Tufin problem. Check Point is horribly configured. Managing it is hell. You have to define the OPSEC server with a user name and password, and you have to create the same thing on the provider one. They have to be same user but have different passwords. It's a little difficult. You have to pay close attention so you don't make a mistake. But I think that's a Check Point issue, not a Tufin issue. The whole Tufin deployment took us about four months, with SecureChange, etc. Up to the point with Check Point, it was easy. We created a read-only user for our infrastructure, and once we had connectivity from the Tufin box to all the devices, it was pretty simple. It was just IP address of the device, username, password, and go. Except Check Point. We needed to spend a day or two on that. In terms of our implementation strategy, we wanted to test each of our technology manufacturers: F5, Check Point, Palo Alto, etc. We left our main public-facing networks out of the equation for the PoC. Whenever we implement the whole thing, we will include those. We made SecureTrack work well. We will define our security matrix correctly with all our networks, as granular as we would like it to be. Once we have that, we will go to SecureChange. So it's SecureTrack, do a good security matrix and, once we're confident with that, we'll go to SecureChange. For deployment, it was just myself and the people who deployed the VM, with the help of Tufin's team. I'm the only one who was involved in maintaining it. View full review »
NetworkS2260
Network/Security Engineer at a leisure / travel company with 51-200 employees
I don't think we had any issues installing it. That was not a problem. It is not that difficult but it is not easy either. The setup was normal and I wouldn't complain about it. Our deployment took about ten to 15 days to get things onboarded. There were many other guys who were also involved in it and I don't remember entirely, but I think that's how long it took to onboard things. The number of people involved in the deployment depends on the infrastructure and what kind of services you are looking for. If you're looking at server management, that would require one or two guys. If you're looking at onboarding of devices, you would need another one or two guys. For the auditing stuff, again, another one or two guys could do it. So for each of these areas, one or a maximum of two guys could handle it. Once you are done with onboarding, managing it takes two guys. Regarding our implementation strategy, our primary motive was to get firewall automation in place. With that in mind, we worked to bring in all the devices and all the firewalls. Then we started talking about getting the different packages over to it and working to get the firewall automation done. There were a lot of things we had to do - it took months - when we had to bring in new patches or requests. View full review »
Syahrul Fitri
Specialist in Network Security Operations Support at a financial services firm with 10,001+ employees
The initial setup was straightforward. I was able to deploy Tufin in a few minutes only. Integrating with devices - as we are using Checkpoint, API, Syslog - is simple. For now, we have only installed one server, not distributed. Soon we will go for distributed, because we need to collect all the logs from all our overseas sources. I was the only one involved in the deployment and am the only one who takes care of the maintenance and day-to-day configuration. Our firewall team will be using Tufin but they don't do the maintenance. At the moment there are about 15 users. Half of them are the firewall team and then there are a few auditors and a few people in the business unit who are monitoring the rules. View full review »
Tch32Dr8392
Technical Director at a tech services company with 201-500 employees
The initial setup is reasonably straightforward and the support team is quite good. They're very helpful and they're very knowledgeable. The deployment, overall, took about three months, in terms of studying the customer's environment and doing some consultation and a deep-dive with the Tufin consultancy team. View full review »
Mohd Majmi Mohamad
Regional OSH at Pos Malaysia Berhad
The setup was not too complex but not completely straightforward. It was so-so, at least for our environment. We had an issue with how to push the policy changes. It took about a week, during which our engineer conferred with Tufin. Tufin had to do some fine-tuning. In terms of an implementation strategy, at that time we were only doing a PoC to see the policy management functionality. Tufin can also integrate networking and security to show an overall network mapping, from site to site. We have a lot of branches. And we are now moving to SD-WAN, to see the mapping. We need to see if Tufin can integrate with that. View full review »
Managerfac3
Manager at a manufacturing company with 10,001+ employees
The initial setup was very straightforward. It was done in five days, which is pretty cool. View full review »
Samuel Taxis
Information Security Engineer at a tech company with 1,001-5,000 employees
The setup was pretty straightforward. The documentation was pretty clear in terms of what you had to do. It was just the case of executing it. View full review »
John Fulater
Security Engineering at a financial services firm with 10,001+ employees
We were the first North American company to do this product, a long time ago. So, I don't know how the initial setup went. It's been a while. However, every time we go back and do stuff, it has been a pretty straightforward installation. View full review »
NetworkS6585
Network Security at a transportation company with 10,001+ employees
The initial setup was pretty straightforward. It communicating with the firewalls and management server were the big pieces. View full review »
Shawn Babinyecz
Cyber Security Engineer at a healthcare company with 10,001+ employees
The initial setup was straightforward. It was very easy to setup and integrate. We had no issues. View full review »
Security4691
Security Engineer at a manufacturing company with 10,001+ employees
It was pretty straightforward. It was not too challenging to get it going. This issue is just maintaining it. View full review »
SrAdvisof832
Senior Adviser Cyber Security at a comms service provider with 10,001+ employees
The last time that we initialed setup, it was straightforward. If you want to install a new root automatically using the tool, the change impact analysis capabilities are useful. View full review »
Salvador Teran
Network Security at a tech services company with 5,001-10,000 employees
The initial setup was very simple. We could obtain deep knowledge information from Tufin's knowledge base (KB). View full review »
SrInfoseb35c
Senior Information Security Architect at First Citizens Bank
There were some hiccups in the initial setup. In using the new features, there was a learning curve. However, for the most part, it was fairly straightforward. View full review »
SrNetwor9adb
Senior Network Engineer at a financial services firm with 1,001-5,000 employees
The initial setup was very straightforward because the documentation was straightforward. View full review »
Profferefb28
Professional Services Engineer at a tech services company
The initial setup was straightforward. View full review »
Security1d40
Security Analyst at a government with 1,001-5,000 employees
The initial setup was straightforward, but then it became complex due to our rule set. View full review »
NetworkS3480
Network Security at a insurance company with 1,001-5,000 employees
There were some hiccups here and there with the initial setup, but we used Tufin's support to assist us with that. View full review »
Securitye57f
Security Architect at a manufacturing company with 10,001+ employees
The SecureChange implementation was straightforward. The SecureApp implementation was very complicated. The topology was so complicated that we threw it away after months of having Tufin people come out to try and make it work. View full review »
ITManage3885
IT Manager at a financial services firm with 10,001+ employees
The initial setup was very straightforward. View full review »
Marko Martin
Technical Team Lead at Paragon
The initial setup was very straightforward. View full review »
ITSecuri46f3
IT Security Professional at a pharma/biotech company with 10,001+ employees
I was not involved in the initial setup. View full review »
ChiefInf4325
Chief Information Security Officer at a tech services company with 501-1,000 employees
There was some complexity during the initial setup, but otherwise, it was fairly straightforward. View full review »
Davison Marques
Regional Manager at a tech services company with 11-50 employees
The initial setup was complex. We have a big environment which contributed to the setup's complexity. View full review »

Sign Up with Email