Mimecast Insider Risk Management and Data Protection Reviews

My main use case for Mimecast Insider Risk Management and Data Protection is during the first instance when taking on a client, when conducting risk analysis, identifying where the gaps are, and establishing baselines of what the clients are experiencing, whether it is exfiltration or understanding what the users are using. This allows me to identify behaviors from end users and create policies to mitigate those risks.

A specific example of how I have used Mimecast Insider Risk Management and Data Protection to spot a risk or stop data loss involves onboarding the client, letting it run for some time, and then analyzing the data by pulling up executive reports. Depending on the licensing, I start the configuration and close the gaps identified in the risk assessment. In some instances, if the issue is user behavior, I create trainings for the end users to raise awareness about the risks, the direction the business is taking, and how to mitigate those risks. In my field, a fully equipped user is more valuable than depending solely on the technology.

Mimecast Insider Risk Management and Data Protection's best features in my experience include user behavior analysis, the executive risk summary for stakeholders, the analysis tools available for engineers and technical people, and the responsiveness of support. Mimecast support is very effective, and I can easily reach out to them whenever I need assistance.

Mimecast Insider Risk Management and Data Protection has positively impacted my organization by making it much easier to onboard a client and start using the technology. The simulation phase where insights are being built is not too long, and moving through that into a protective environment is straightforward. The multi-tenant capability is very helpful for us as a managed service provider because we can isolate clients.

User behavior analysis specifically helps my team and stakeholders by analyzing what users do and what they are prone to do, taking into account the data that Mimecast has processed. This gives direction on how to help that user become risk aware and cybersecurity aware. Support responsiveness is very effective because I understand that security solutions can impact business operations. If an executive needs to send an email to secure a deal and a normal business activity is being blocked, the vendor's responsiveness allows me to efficiently communicate to executives that we are working on the issue and can always show progress.

Mimecast Insider Risk Management and Data Protection can be improved by incorporating artificial intelligence and machine learning into the environment for ease of operation and handling processes at machine speed.

Mimecast Insider Risk Management and Data Protection is stable in my experience. I have also tested the version on Microsoft, and while their licensing model is slightly different, it is very stable.

Mimecast Insider Risk Management and Data Protection's scalability is one of the reasons we chose Mimecast because it is easy to scale up or down as the client base changes.

Customer support for Mimecast Insider Risk Management and Data Protection is top-tier. I have never had any problems with the customer support, and they are very responsive.

When onboarding a client, they want to see results sooner and want to see that they now have some level of security. Having a quick turnaround is always very beneficial because it shows presence to the client and to the end users. It also saves time because once all false positives have been cleared out, a solution can be relied upon. After tuning all those false positives, the solution becomes accurate, which is significant.

My advice to others looking into using Mimecast Insider Risk Management and Data Protection is to take a demo, see how it works, and get a look at the features. I am confident they will find it favorable. I would rate this product and experience with a five-star rating.

My main use case for Mimecast Insider Risk Management and Data Protection is email protection, blocking spam, and creating rules to avoid spam.

A specific example of how I use Mimecast for email protection and blocking spam is that users often receive emails containing links that could compromise our system or environment. In most cases, we check the link through Mimecast to determine if it contains malware or poses a risk. If the link is risky, we block it and the email that sent it, then notify all users not to click on that link. After blocking the link, even if another person attempts to click on it, they will not be able to access it.

Mimecast has additional benefits beyond manual blocking. Sometimes the system automatically detects and blocks malicious links or files without requiring manual intervention. When Mimecast identifies a malicious link or file, the user receives a notification that the email is blocked for our review to determine if it is safe. We have also created rules in our environment to specify what is allowed and what is not allowed.

The best feature that Mimecast Insider Risk Management and Data Protection offers is malware detection. I find it very useful because it detects and blocks threats before users can click on links or open documents.

The malware detection feature makes my day-to-day work easier and safer because as soon as an email arrives with a link or document that Mimecast identifies as malicious, it blocks it. This protects our environment by preventing the threat from spreading. Even though we conduct cybersecurity training, users sometimes click on links regardless, so Mimecast's ability to detect and block threats immediately stops them from spreading across the environment.

Mimecast Insider Risk Management and Data Protection has impacted my organization positively by protecting our environment from malicious links and spam. It detects and blocks links or removes attachments from emails, preventing them from spreading across our network.

To improve Mimecast Insider Risk Management and Data Protection, I believe the product should provide more options for creating custom rules in the portal. Since hackers are constantly developing new attack methods, Mimecast should continue evolving to keep pace with these threats and give us more options to create additional rules. There have been scenarios where we felt that if Mimecast could allow us to do certain actions, we could have blocked or avoided security issues, though I do not have a specific example at this moment.

I give Mimecast Insider Risk Management and Data Protection a rating of eight because there are several areas where I feel the product could improve. There are scenarios where we find ourselves wishing we could perform certain actions within the platform. Additionally, there have been instances where a document or link has bypassed Mimecast, causing us to question why it was not blocked before reaching users.

I have been using Mimecast Insider Risk Management and Data Protection for five years. Since I joined Seacom, they have been using this solution.

Mimecast Insider Risk Management and Data Protection is stable.

I would rate the scalability of Mimecast Insider Risk Management and Data Protection between seven and ten.

I think the customer support is good, and they respond on time.

My advice for others looking into using Mimecast Insider Risk Management and Data Protection is that it is a nice product to use. I would give this product a rating of eight.

My main use case for Mimecast Insider Risk Management and Data Protection involves policy fine-tuning while analyzing patterns, incident response, and providing support and guidance to the user.

A specific example of how I use Mimecast Insider Risk Management and Data Protection for policy engineering or incident response involves working with PAN card and mobile numbers. Since we are in India, we are provided with phone number patterns, regex, and Aadhaar details as an Indian identifying number. Accordingly, we provide certain patterns so that Mimecast Insider Risk Management and Data Protection checks documents that should trigger our system to ensure nothing is violated. For the document part, as an e-commerce company, it checks that no business data is shared externally.

Regarding my main use case and how I handle sensitive information with Mimecast Insider Risk Management and Data Protection, we currently have some policies that we are not using, but we are working on different policies, such as those concerning various types of PII data. We are focused on fine-tuning to receive more critical alerts.

The best features Mimecast Insider Risk Management and Data Protection offers include providing a timestamp of each incident, which indicates when it triggers and its accuracy. However, some features we are not using yet, but we plan to proceed with them in the future.

Mimecast Insider Risk Management and Data Protection positively impacts my organization by helping us thoroughly check any kind of data that should not be mishandled, primarily for endpoint users who are sending organization documents outside. It helps us avoid any kind of data breach.

For the improvement of Mimecast Insider Risk Management and Data Protection, it would be helpful if the timestamps in the console and the timestamps in the emails where we get all outgoing mails were the same, as this would provide more clarity. Additionally, some documents do not fetch carbon copies in the emails, so we need help with that.

I have been working in my current field for three years, with two years dedicated to the DLP part and one year in endpoint EDR.

Mimecast Insider Risk Management and Data Protection is stable.

The scalability of Mimecast Insider Risk Management and Data Protection is good.

Customer support for Mimecast Insider Risk Management and Data Protection is adequate, and they are helpful.

Mimecast Insider Risk Management and Data Protection prevents data breaches by triggering alerts for each email sent outside, allowing us to see patterns of users sending documents externally. We analyze these incidents and patterns to work on any issues, and this also helps in the fine-tuning process.

I would rate Mimecast Insider Risk Management and Data Protection an eight out of ten because we need improvements in policies, and although I am not aware of other organizations' experiences, we are facing some lags, and there are points we must work on.

I advise others looking into using Mimecast Insider Risk Management and Data Protection to definitely use it for email security because it is very helpful. I have given this product an overall rating of eight out of ten.

Mimecast Insider Risk Management and Data Protection is relied upon primarily for email security, functioning as an email gateway within the company so that every email is processed through Mimecast, filtered, and then delivered to user mailboxes after security checks are completed.

Day-to-day operations involve handling tickets from users stating that their email has been held and they request release. We cross-check whether SPF is matching, if SPF has passed, and if DKIM has passed. Once everything is verified and we determine the sender is trusted, we release the email. We have different types of security gateways, including impersonation protection, which is created by establishing a profile group so that if it matches any keywords, it might flag potential impersonation. We have many policy options within the system. Based on our requirements, we can set up policies, and Mimecast helps us filter emails very effectively. We can clearly check whether emails are being delivered or not. If they are undelivered, we can check the reason for non-delivery. URLs are decoded through Mimecast, allowing us to scan links and determine whether they are safe or not. Many options exist within Mimecast for these purposes.

I have been using Mimecast Insider Risk Management and Data Protection for the past three years.

Whenever we block an email ID, we can do so from Mimecast profile groups, and we can add email addresses from which we no longer want to receive emails. For example, if a phishing email arrives, it stops and holds that email based on SPF, DKIM, and DMARC rules so that it does not reach the user and remains held. Mimecast also protects emails that contain URLs or links within them, as users may accidentally click on those links, which might affect the entire company. In this way, Mimecast helps us significantly.

Mimecast Insider Risk Management and Data Protection stands out the most. The URL protection, link scanning, blocking of users, and creation of multiple profile groups, gateways, and policies are valuable features. There have been many positive changes with Mimecast Insider Risk Management and Data Protection since implementation, and we feel it is working out positively. We also receive continuous support from the Mimecast team, with weekly calls to discuss technical issues within Mimecast.

Mimecast Insider Risk Management and Data Protection could be improved by providing more advanced features within the platform. If it collaborated with other different features, that would be more helpful.

I have a total of ten years of experience in my current field.

All functionality is performing well. There has been a reduction in phishing events. I would rate Mimecast Insider Risk Management and Data Protection an eight out of ten because sometimes it blocks or holds emails that are supposed to be unblocked. Occasionally, Mimecast does not work as effectively, which is the reason for this rating.

When I first became acquainted with Code42, we were implementing it at an employer I worked with, and that was a successful implementation. I now work for a consulting firm, and we do system implementations of a variety of different DLP tools, and Code42 is one of them. I still use it, but it is for the benefit of my clients, as opposed to the company I work for.

The pedigree of Code42 came from a toolset called CrashPlan. So, CrashPlan predated Code42's product, and it was mainly in helping organizations prepare for disaster recovery and business continuity planning in significant server environments. We use it in three main areas. The primary area that we use it in is in providing identity into data loss prevention and data loss protection in terms of:

• Where is that unstructured data?
• Who has access to it?
• How did they come to be authorized to use it?

It is a broad-based area of use, and then the other area of use is discovery. Many of our clients engage either with their staff in legal battles, or some other thing, where they need to perform discovery. We support discovery with Code42 as well.

Its deployment was on-premises, and that just happened to be the ecosystem that we chose to work from. It is still going fine, but I don't think it would matter one way or another. From our standpoint, it was fine. Ultimately, we'll probably move to the cloud, but at that time, we were looking for on-premises.

It is an enterprise system, so it can be used in a medium size to large size company, but the thing that we look for is data loss prevention. That's critical for us. The ability to protect against intellectual property theft, the overall insider threat prevention, and then data exfiltration is valuable to us. Many of our clients are concerned about data being exfiltrated from their organization, unbeknownst to them. That's an area around which we create visibility.

There are a couple of things. One of them is that they have what they call Incydr. Their detection and response solution to the insider threat area is called Incydr. That gives visibility to the clients that have widely dispersed employee bases due to work from home, or that had a dispersed workforce predating any of the work from home requirements. Even though they might not be inside the organization physically, they're inside the organization. It allows us to get some visibility into what people are doing, what the context is, and how to control what might be the potential for intellectual property theft or file exposure.

In a couple of instances, we had a little bit of trouble in getting it distributed throughout the organization. We ultimately managed to do it, but they talk about it being a pretty simple process, and it became a little laborious. It would just turn away. The agents were not being distributed. It was just churning and churning and churning. When we were looking for specific categories of data, it was getting bogged down, but that was not even so much Code42, although some of it was their issue. It really has to do with the overall infrastructure and what the organization is prepared to do. If the infrastructure or the networking is a little hinky or you don't have a really finely tuned network infrastructure environment and your patches aren't up to date on your servers and your endpoints, it could get a little sticky. Other than that, it was okay. We really didn't have much problem beyond that. It took a couple of days to sort that out, but it was no big deal.

It goes back to around 2018. It has been about four and a half years.

We didn't have any issues. We bolstered our network incredibly. There is a lot of stuff running through our pipes. So, we now have a pretty strong network. We didn't initially, but we now have a really strong network and pipe environment. I don't really see any problem with it. The only problems we have are not related to Code42. They're related to the fact that we have to make sure that, at times, the people who work from home leave their technology available for us to do updates, to do scans, and things like that, but that's not a Code42 issue. That's more of an internal issue.

It is an enterprise system. It can be used in a medium size to large size company. It is very scalable. We took small numbers within departments, nailed that, and then moved on to different departments and nailed that. It scaled pretty easily. I don't recall anything going off the rails.

It is being used throughout every department such as IT, human resources, marketing, sales, HR, finance and accounting, legal, and operations. There are 16,000 people in the company. So, it pretty much is going to touch everybody. There are two primary locations: one in Northeast, Ohio, and one in New York, but then there are literally thousands of locations across the United States. People are working from home. They're all over the United States. We had an operation in Canada, but we didn't do anything overseas.

We don't really talk to them much. We talk to them from time to time about the potentiality of moving to a different infrastructure environment, but that's about it.

Their customer service is a solid eight out of ten. There are always going to be hiccups. Sometimes, you put in a call, and you'd like to get a response sooner than later, but nobody is perfect. We don't expect anybody to be perfect, but we're happy with it, especially in comparison to some of the other vendors we work with. They're light years ahead of everybody else. They got a good team. The people that you talk to, they're not just reading off of scripts somewhere, walking you through. They're doing a decent job. They know the product.

Positive

We didn't use a particular service in an enterprise environment. We used different environments. We used some of the earlier renditions of Microsoft in terms of its compliance manager tool set. We also used another tool, which was primarily an e-discovery tool that we leveraged into utilization, like a DLP system. There was another tool called InfoGPS, which was really good for financial areas and banking, but beyond that, it really wasn't a good fit.

The primary benefit that we saw was the company itself. They had an advisory team that could help us in terms of onboarding it in terms of where to look and in terms of supporting different technology platforms. They were able to give us some insights into training. They had a pretty decent Insider Risk Management Training program. Security awareness fits into that as well. We could target the training for different client requirements, which was pretty nice.

You really have to understand your network environment going into it. You can't second guess it. You have to provide them with as much information as you can about your bandwidth, the server environment, the number of users, and where those users are located. A lot of those things needed to be right-sized, which just wasn't done upfront.

In a couple of instances, we had a little bit of trouble in getting it distributed throughout the organization. We ultimately managed to do it, and that was a little hickey, but we didn't have a problem otherwise.

In terms of the implementation strategy, we had a four-phase approach. We called it the four Ds. The first was Discovery. So, we had to go through a discovery process to determine things like:

• What is the key functionality?
• What are we looking for?
• What areas of solutions do we want it to fit in? 

We then had to discover what companies might be out there. We went through an analysis of companies. We did discovery.

The second phase was when we made a decision to work with Code42. We sat down, and we did a design session. We created an architectural design at a high level, and we talked about the outcomes that we're looking for from the standpoint of:

• Policy
• Technology
• User profile
• Acceptability
• Ease of use

We had all that designed in, and then we did the actual development. We developed all the charts. We used the standard waterfall project management implementation strategies or incorporated SDLC. We did all the things you would do for standard project management, such as critical path, key stakeholders, etc. All that was done in the development phase. That's when we actually onboarded the technology on our server environment. We then worked up a test scenario and did deployment, which was the fourth D. We did deployment on a group-by-group basis. We didn't do a big bang or everybody at once deployment. We took a subset of users from a department, and we implemented it in a department. We went to another department, and we implemented it in that department. We scaled all the way through. The first department we worked with was security. We implemented it within our own security team, and then in IT in general. So, we did security, IT, marketing and sales, HR, finance and administration, and then overall operations was the way we implemented it.

They had an advisory team to help us in onboarding it. We got the consulting support. We had an individual come out. I don't know what his exact title was, but he was a senior consultant who had done multiple implementations in the past and was familiar with the product. He wasn't a junior guy by any stretch of the imagination. He knew the information he needed and he knew how to work with us. He was a pretty reasonable guy. He was around the first couple of weeks. He came on site for a week, and then after that, he came in every once in a while for about three months. By then, we had already done most of the heavy lifting, and we were into full-scale development and implementation. We would talk to him all the time, but he didn't come on-site anymore. I would rate him a five out of five. We thought he was really good. He was capable, and he was knowledgeable. He had a great personality. He wasn't high-minded or anything like that. He was a good guy to work with. In fact, he's still around today.

For the deployment, on the security team, I was the overall leader. I didn't work on it full time, but I was the overall leader of it. Then I had a security analyst from my team on it, and I had a security service engineer on it pretty much full time. As supplementary, I'd have a junior guy or a network analyst help out from time to time, but there were really about three people who worked on it throughout. There was also a project manager, but he was from the project management team, not from our team.

In terms of maintenance, there is a regular tuning. We pay for the software maintenance. There is software maintenance, but we tune it. Like everybody else, there is regular care and checkups to make sure that everything is running properly. If we see anything that's running amiss, or if we do a heavy patch load, sometimes, we'll pay closer attention to what's going on at the endpoint because of the patch load. It is not cumbersome for sure. Its maintenance is handled by the network admin. A security architect is also there from time to time, but it is mainly done by the network administrator. He may dish that out to one of his support people, but by and large, that's all that's involved. We haven't had to call Code42 for anything that we couldn't figure out.

We have absolutely seen an ROI. We found a lot of value in being able to detect the file sharing and potential exfiltration or actual exfiltration. Not everything is done maliciously. Sometimes, people just do it, but it is not done maliciously. They might embed a PowerPoint thinking they're embedding a PowerPoint pie chart in a presentation, but they're actually embedding the entire spreadsheet. We were able to detect that. 

The other thing that it has helped us with is that it showed us where we had gaps in our security policies and acceptable use policies. It showed us how to measure the effectiveness of a policy. That was pretty strong, and we really liked that.

It was expensive. It was more expensive than Eureka, and it was more expensive than Barracuda Backup, but what we got was a full team. They didn't come in and nickel and dime us. They provided the assistance we needed. They didn't say that they need to charge us for something or it is going to take another statement of work. It was all bundled into it. The organizations that can't afford or are not interested in an enterprise solution, such as a medium-sized business, they're probably not going to want to spend the money, but you get all the maintenance. We got the training. We got the consulting support, and we got the advice and console. We had an individual come out. He really didn't need to, but he came out on-site and worked with us. So, it was pretty good.

You could certainly add on different functionality. You could buy extra consulting, and you could buy other services. We chose not to do that, and it worked out okay for us. At the time I was involved in the purchase, they had a bundled solution, or you could buy it a la carte. I don't know what they're doing in 2022, but it probably still is the same. It was, at least, through the end of last year.

We pay for the software maintenance. It is probably 18% or 20% of the license fee for rev releases.

InfoGPS was evaluated. There were a couple of other tools that were evaluated. It really got down to the fact that as an organization, Code42 had the features we were looking for. They offered a tried-and-true product. One that had come from a long pedigree. They understood the whole realm of data security and privacy. They had data and security privacy experts on staff, which were pretty good. That was very helpful.

The other tool that we evaluated was from Barracuda. It was primarily around the Barracuda backups. It was called Barracuda Backup Live or something like that. It was pretty cool, but it was limited in terms of the feature set that we were looking for. We did a proof of concept, and it took us longer to get that up to speed than Code42.

The very first thing you should do is make sure that you know exactly what you're looking for. There's a whole bunch of stuff out there. Data loss prevention or data loss protection is a big category. It can cover a lot of ground, but you have to make sure that you know what you want, and you have to prioritize that list. We call it a value-based prioritized roadmap. You have to know what you want and what's critical for you at that point in time. Don't try and do everything all at once. Give yourself the top three things that you want to accomplish within a certain timeframe and work toward those. Spend your time on those. Don't get off track because it is easy to get off track with new features and all that. You should just stick to the plan and work it through. So, definitely make sure that you have a priority list of what functionality and what services you're actually interested in.

I would rate it a solid ten out of ten. We've been very happy with it. It covers a lot of space and is very scalable. They have good people to work with. It is a little pricey, but you get what you pay for. We find it a pretty straightforward application to work with. We've been able to leverage it to help improve our policies. It is a good tool.

Data Leakage Protection on large scale environments. This can be to protect against leakage on endpoints and servers that consist of highly classified or propriety information. It can be added on as a control that integrates into the various egress solutions in the organization. As part of projects for general DLP I have used data classification to identify such silos and create identifiers or use predefined structured and unstructured data that flows through the environment. The most effective way to apply these controls is at tge point the data is accessed between differant parts of the organization.

Code42 allows you to create a policy using risk levels calculated on the basis of employees' behavior. It also provides the ability to customize the information for other solutions for automation. There are a large number of integrations with other solutions with a fully customizable API. 

Code42 has a very extensive risk-scoring system. It has a default set of risk scores out of the box but gives the user more control over them by allowing you to set custom values. There are other products in the market that also do that but have limited features and divert their focus toward a larger number of search parameters. The advantage you would have with Code42 is that their solution allows for the risk factors to be customized further down to granular details. Yet another feature is that the solution has a small footprint on resources. 

The solution has been designed for a different approach than the one followed by other DLP solutions in the market. Most of us who come from the mindset of filtering out incidents using a content-specific approach may find this solution limited. The next updates for the solution may benefit from using some of the features provided by older solutions in the market to allow for a deep dive. There is limited support for data at rest.

We've been using this solution for a few years.

I haven't had any issues with stability. 

We have frequent contact with customer support. They have an instructor module that provides videos and an information package for users.

Code42 has a relatively simple deployment with an all-in-one sort of feel. It's simpler than deploying a lot of the three-tier solutions in the market. 

If you come with the perception that this solution uses the same policies that are used in traditional DLP products, you might find Code42 doesn't work for you. You have to adapt to their philosophy, which is a more open-ended solution. If you're looking at getting granular about a particular type of data, it becomes harder to put custom variables in there.

Code42 is more open-ended and identifies or discovers data that is going out rather than having someone build a policy to filter for it. If you're willing to look at DLP and data leakage from a different perspective then I'd go with 42. 

I rate this solution eight out of 10.

I took over as a security architect for my current company. They're happy to be using this solution, so I'll be learning more about it as time goes on.

Code42 Next-Gen DLP is deployed company-wide.

I have not evaluated the product from a feature-set perspective, but I had a system that was having CPU issues with Red Hat that Code42 solved.

It's on my radar to re-evaluate our endpoint in 2021. Right now, from a cost perspective, I don't see the ROI at the moment. For this reason, I can't really state equivocally what I think is a good feature. Presently, we have so many files that I don't have the time to really dig into the solution as a whole. 

As a newcomer into a business that is running this software, what I think could be improved is how I get support.

We Just started getting involved with Code42 Next-Gen DLP about six months ago.

When it works, it works.

Code42 Next-Gen DLP is scalable. 

This solution was already installed by the time I became involved with my company. 

I'm still new to it. I think right now I am 90% happy with it. Overall, on a scale from one to ten, I would give this solution a rating of nine. 

We primarily use the solution as a backup.

The ease of use is excellent.

The product just always has a continuous backup going, which is quite useful for us.

There doesn't seem to be any feature that is lacking.

I've been using the solution for seven or eight years. It's been quite a long time.

The solution is very stable. Very rarely do we have any issues with it. We don't have to deal with bugs or glitches. It doesn't crash or freeze. We find it to be reliable.

In terms of scalability, we've got it on two or three different servers. That's all we'll use probably. We're not likely to increase usage or to scale it in the future.

The technical support is pretty good. We've had to deal with them just a couple of times. They help us with navigation if something isn't backed up or an issue like that comes along. Typically, it's an easy fix. It's just a restart of the service or something of that nature. They're very quick and efficient. We're satisfied with the level of service they provide.

We didn't previously use a different solution.

The initial implementation was not complex at all. It was very quick and extremely straightforward to install within the scale-up.

The pricing is reasonable. It's my understanding that the cost is about $7 for unlimited storage in the cloud per server.

We're just a customer. We don't have a business relationship with the product.

I'm not sure as to which version of the solution we're using at this time.

It's just an all-around good product to have in your organization.

The product works best for smaller companies. However, larger ones may be able to benefit as well.

On a scale from one to ten, I'd rate this solution at a perfect ten. We've been very happy with it and it hasn't given us any problems.

We use it to back up corporate data. Most of our users are travelers and there have been cases where laptops were lost/stolen.

We are now able to keep our corporate data safe for those who don't work in a center with IT support. 

• Works in the background
• Admin dashboard
• Reporting
• Users are able to perform restores
• Mobile app comes handy if you need to retrieve a file 

I would like to see more flexibility on privileges, perhaps create another kind of admin for regions. Also, I would like the ability to access logs without having to be on the actual device or a super-admin.

Used for both peer-to-peer and cloud backup.

• It required very little ongoing maintenance once setup.
• Supported peer to peer storage (they are discontinuing this going forward). Due to the change in direction of the company, I am now migrating to a different solution.
• It has quite a bit of flexibility in configuring backup sets.
• It had the ability to preseed by sending in a data drive and could restore by sending the user a data drive.

The application, written in Java, required far more system resources on a Client than other solutions.

It used to be a good solution for SOHO in particular as it had unlimited storage for a reasonable price. However, their pricing model has changed and they are now primarily targeting enterprise users.

Due to recent changes that effectively abandoned an entire segment of their user base, I no longer trust nor can recommend Code42 products.