What is our primary use case?
Files.com saves large amounts of data post-TSA exit, enabling divestment from the initial company and data migration from specific mainframe teams to newer systems. This includes data updates, with usage limited to a small team and access restricted to FTP protocols on Files.com.
What is most valuable?
There are many GDPR features. The API implementations are pretty easy to use, with SDKs that can be downloaded and utilized. It provides a lot of customizable features. We implemented IP whitelisting, which allows for specific IP addresses within an organization to be restricted, mitigating potential hazards. The granularity of IP whitelist settings, down to individual addresses. Those might be my favorite features.
Additionally, whenever I need to model something out, I can request a sandbox environment, which is great for testing. This way, we don't have to do everything in production immediately. Overall, IP whitelisting might be my favorite security feature. The setup process is straightforward as well. Also, by default, any FTP connection requires SSL/TLS transfer, ensuring data protection even within that framework.
What needs improvement?
There is a requirement to simplify access, particularly for managing large amounts of stored data within Files.com. Instead of navigating through firewall rules, etc., users seek the ability to bypass two-factor authentication when logging in via username and password. Missing this toggle could necessitate recreating the account. Additionally, there's a lack of clarity regarding users under this system, making monitoring challenging. However, Files.com does offer SSO, which addresses many of these concerns.
The solution should show more in terms of the way we navigate things like FTP or FTPS with a username/password configuration, if not through SSO. It requires the use of an API key, among other things. There are workarounds and ways to address a few of these issues.
For how long have I used the solution?
I have been using Files.com since September. We are using the latest version of the solution.
What do I think about the stability of the solution?
The solution’s stability is pretty fine as far as the runtime is good within SLA. There is no issues so far.
What do I think about the scalability of the solution?
Scalability is fine if you have an existing infrastructure and connections in place. You can leverage and integrate it with your current architectures. However, if you don't have these, there's a dependency on the version and other things to consider.
I rate the solution's scalability a six out of ten.
How are customer service and support?
The technical support from Files.com was excellent. They were prompt in their responses. They would often call on the same day to set up a meeting or discuss the issue and then collaborate to find a solution.
How was the initial setup?
The initial setup is easy.
What's my experience with pricing, setup cost, and licensing?
The data was valuable. We needed it. The pricing is not bad for the level of service.
What other advice do I have?
We encountered various challenges with connecting our teams and ensuring seamless communication with our business clients, often necessitating involvement from network teams to address firewall rules and other technical aspects. Additionally, discovering the full extent of what was achievable within our established framework posed another set of hurdles.
I recommend its use case to understand the intent to use Files.com, especially if it involves setting up automation. It's important to prioritize setting up SSL as quickly as possible. Additionally, using SFTP would be ideal to avoid concerns about passwords and usernames. There are various options within Files.com, such as looking for mount points or using different anchors, depending on the specific needs. If FTP is the chosen method, Files.com offers a reliable solution.
Overall, I rate the solution an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
