Director, Cybersecurity Consulting at a tech services company with 51-200 employees
Real User
2022-06-16T18:52:10Z
Jun 16, 2022
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.
Mimecast Incydr offers a comprehensive data protection and recovery solution, ideal for organizations needing robust insider threat protection and regulatory compliance.Mimecast Incydr provides a seamless experience across platforms with lightweight clients and centralized administration. It focuses on real-time monitoring, instant access to backups, strong encryption, and customizable risk scoring. This ensures data protection against insider threats while promoting ease of use and low...
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.
We primarily use the solution as a backup.
We use it to back up corporate data. Most of our users are travelers and there have been cases where laptops were lost/stolen.