Microsoft Purview Data Loss Prevention Reviews

My main use case is to upload mailboxes. We're using Microsoft Purview Data Loss Prevention to upload mailboxes. The migration tool that's built into the Microsoft Hybrid isn't working on our domain. We're a government contractor, so we have policies, and I believe that one of those policies is preventing it from going up. We have two domains. The other one worked fine. The second domain, we weren't able to migrate. So we had to use Microsoft Purview Data Loss Prevention.

My favorite feature about Microsoft Purview Data Loss Prevention is actually quite simple. There's a handful of things that you do. You create a new batch. It'll give you a unique ID. You copy that unique ID, it's a URL, and then you can put that into a script that we wrote so we just paste that in our script and then it uses that URL to upload all of those mailboxes, and then we can use that to import. The simplicity of that interface is what I appreciate most.

I assess the ability to prevent unauthorized sharing of sensitive information within the organization by locking it down to security groups so that only administrators have access.

I think that a feature on the side where you could click on something with a question mark, and then if you click on it, it would open up a new window and give you more information on that, almost as a training tool for the website that you're already logged into and already connected to, could be improved in Microsoft Purview Data Loss Prevention.

I see that there's a lot of content in Microsoft Purview Data Loss Prevention, and when I click on it and look around, I wonder what certain features do, but there's not enough documentation and explanation.

I have been using Microsoft Purview Data Loss Prevention for one year.

I assess the stability and reliability of Microsoft Purview Data Loss Prevention as having no issues. If I'm using it on a system that doesn't kick me out and I go back, it does log me out and it says, 'You've been logged out.' I appreciate that. I know that a lot of sites don't do that. I've been logged into other systems and still logged in multiple hours later. I've never had Microsoft Purview Data Loss Prevention go down, and it has never given me any issues.

I did not use customer service. I never needed to.

Neutral

I did not consider other solutions before starting with Microsoft Purview Data Loss Prevention. We reached out to a third-party vendor to help us with the migrations. They suggested it and said that there's an option of doing this a different way. So we sat down several weeks and several months later, we created the script, tested it, got the bugs out, and then ended up using Microsoft Purview Data Loss Prevention. It worked the way they said it would.

I can describe the deployment of Microsoft Purview Data Loss Prevention as a website, so it's just a matter of logging into it.

It only takes a few clicks and that's it.

I can say that I've seen a return on investment from Microsoft Purview Data Loss Prevention because it's allowed us to do the migration for all the users so that we can move forward with other projects that are relying on the users to be in the cloud.

My experience with the pricing, setup cost, and licensing is that it goes up to upper management. I am involved with licensing. I do a lot of testing, so if I create an account in the cloud without a license, I have to go and license it. That may not be the same question that it's asking, but regarding pricing, setup, and cost, I'm not involved with that too much.

I do not use the machine learning analysis yet.

I can say that Microsoft Purview Data Loss Prevention helped improve my ability to discover sensitive data by now knowing that we can do that. We do have a security department that will send us emails or tickets saying, 'Hey, we received spam. Can you take it off everybody's mailbox?' If Microsoft Purview Data Loss Prevention can do that behind the scenes, or even through AI within Microsoft Purview Data Loss Prevention, that would be very interesting.

My experience with centralizing our DLP program is not that extensive. We just recently moved to the cloud.

I would rate this product a nine overall.

I have good hands-on experience with Microsoft Defender, Azure Sentinel, Microsoft Admin portal, Azure portal, and the tools that XDR includes such as Microsoft Defender for EDR and O365. I use all of these tools daily.

I have good hands-on experience working with the Face API, which I used in the past six months. I do not use it every day because I work as a cybersecurity analyst.

Overall, I have been working with the Face API for some project work spanning eight to ten months.

I utilize the machine learning driven analysis offered by Microsoft Purview Data Loss Prevention.

Microsoft Purview Data Loss Prevention has helped to improve my organization's ability to discover sensitive data.

Classification and policy controls enhance productivity and user experience.

There are specific missing features that I would like to see included in Microsoft Purview Data Loss Prevention in the future.

I have been working with the Face API for more than two years.

I assess the stability and reliability of Microsoft Purview Data Loss Prevention as good.

Microsoft Purview Data Loss Prevention scales well with the growing needs of my organization.

I have escalated questions to technical support and would rate the technical support as a five on a scale of one to ten, where ten is the best.

Positive

The initial setup and deployment of Microsoft Purview Data Loss Prevention was straightforward, but I faced some challenges and complexities during the process.

I use Microsoft Purview Data Loss Prevention for various main use cases and for data governance purposes.

The main disadvantages of Microsoft Purview Data Loss Prevention in comparison to the Netscope product are notable considerations.

Classification and policy controls impact user productivity within the organization.

Microsoft Purview Data Loss Prevention's ability to prevent unauthorized sharing of sensitive information is valuable.

The deployment experience with Microsoft Purview Data Loss Prevention involved both positive aspects and challenges. The solution operates on a cloud-based, Azure-based DLP model.

I purchased Microsoft Purview Data Loss Prevention through Microsoft directly.

My experience with centralizing my DLP program in Microsoft Purview Data Loss Prevention has been informative, and I can share advice and recommendations with other organizations considering this solution.

I recommend Microsoft Purview Data Loss Prevention to other organizations considering a data loss prevention solution.

I am an end user of Microsoft products and work as a system analyst at Stratogent company.

Overall, I would rate Microsoft Purview Data Loss Prevention as a product and solution with a rating of ten on a scale of one to ten.

Our primary use case for Microsoft Purview Data Loss Prevention is mainly for the categorization and classification of data into different classifications, ensuring privacy.

One of the most effective features is the excellent reporting tool that shows any potential breaches. 

Additionally, it can be used across multiple platforms, such as Office 365 and file servers, which is a significant advantage. 

Furthermore, the policy customization feature is very useful, and we have successfully used the auto policy configuration.

There isn't anything specific off the top of my head for improvements. However, more training for end users on how it works would be beneficial.

I have been using Microsoft Purview Data Loss Prevention for six months.

We have had a couple of stability issues, such as an inability to change the classification of some documents due to an issue with Microsoft Purview on Office 365, but nothing significant.

Microsoft Purview Data Loss Prevention is very scalable for our environment, and I would rate it ten out of ten for scalability.

The initial setup was very easy. On a scale of one to ten, I would rate the ease of setup as eight out of ten.

It is quite expensive for us as the shift to E5 licenses represents a significant increase in cost. The cost works out to about $15 per user per month.

I recommend ensuring thorough testing and communication before rolling out Microsoft Purview Data Loss Prevention. I would rate the overall solution eight out of ten.

We use it for scheduled audit log retrieval on a monthly basis. We have strictly confidential SharePoint sites and requests come in where we have to find out the activity by users, such as who has viewed specific files or pages on a particular site. The logs contain activity by users and are part of Microsoft Purview. We can run search queries against the logs to get user activity across the tenant for a particular, confidential site.

The solution has tools for creating robotic process automation and workflows and we use them to reduce manual intervention and to handle some of the manual jobs. They make things much faster and more accurate. Of course, it involves much more testing and back and forth, but once you streamline an automated process, it's easy and accurate. It saves a lot of time because you don't need to have a manual monitoring system. Rather, the system identifies things and notifies you. It can save costs on the order of 60 or 70 percent.

With automation, the quality of insights has improved a lot. Manual processes have been replaced with something like a bot. It creates a more consistent pattern that gives you proper analytics and insights into how activities are being carried out.

Also, compliance can be viewed in real time to a certain extent. A small portion is not available in real time, but 70 to 80 percent of it is accessible in real time. Overall, Purview helps us to stay on top of compliance because it handles just about all the compliance factors.

One of the valuable features of Purview is the ability to create a legal hold on a user's account within the compliance portal. That's pretty useful when it comes to any litigation or if you want to redeem the content within a mailbox, OneDrive, or a generic public SharePoint site. If you want to retain the user's data until the case is resolved, you can use the legal hold feature.

Also, it's important that Purview can connect to iOS, Mac, and Android devices. With smartphone involvement, so many applications can now be accessed through them and it is important to apply Purview across operating systems and platforms.

Purview's natively integrated compliance across Azure Dynamics and Office 365 is also significant because within Microsoft 365 there are multiple applications. Irrespective of whether it's Dynamics or Azure, it's very important that it has native support. The data connectivity should be efficient enough to support and secure their own platform's data.

In addition, with varying regulations in different industries and matters, Purview lets you create rules and conditions based on industry standards around the world. That is important. Our company is in pharmaceuticals and the rules and conditions are different from other industries. It is important to be able to keep track of all these regulations and have a tool that is flexible enough to create the regulatory rules and conditions we need.

And when it comes to data loss protection, Purview has features that can recognize patterns and detect any sort of data loss, where the data is being transferred from its platform to a different one. The default settings that come with it are pretty nice for identifying data transfer or data loss across the platform.

It also comes with a lot of training materials, with use cases and examples, to help educate users and make them familiar with the tool.

A site can have different containers where you store data. We have always wanted to apply compliance, labels, and policies at the container level, rather than to an outer shell or at the site level. That is something we have been looking forward to and I believe Microsoft is already planning something like that.

I have been using Microsoft Purview Data Loss Prevention for less than a year.

It's a little bit pricey compared to competitors, but it's not too high. On a scale from one to 10, where 10 is expensive, it's a seven.

Overall, it's a very nice product and can handle a lot of applications.

The solution is primarily used for preventing leaks - to protect us from getting information out of the company.

The data loss prevention is great. It can prevent things like credit card information from being taken. The data protection is excellent. 

We can use the solution on Windows and iOS. We mostly use it with Office 365 and ingest data sources from Microsoft.

The solution is natively integrated and compliant across Azure. It takes into account critical regulations from around the world. We need to comply with various regulations. For our business case, it's very important. 

If we can prevent information from going out, eventually, when a regulator is asking about our security measures, we can show what we've been doing. It helps us to reduce the likelihood of potential fines.

We can educate users on how to handle sensitive data. By showing the records we keep and explaining the technologies implemented, we can provide awareness to our users. 

The solution offers good visibility into our environment. Our security team can use the product to monitor and track.

Its dashboard allows us to show compliance in real-time.

We've been able to reduce the time to action on insider threats. Security permissions are always being monitored. In general, it has saved us time and money when dealing with security. It's made us become more efficient. We've increased our compliance capabilities by 25%.

It could cover more solutions and technologies.

One of the challenges that we're facing now is how we can identify our critical information storage level, for example, via scanning or some other method. 

While I'm no longer using the tool, I used the solution for two years. 

Support is good.

Positive

In the past, I've used Forcepoint. I used it at a different company. Purview is easier to use.

The deployment is pretty easy. As with any implementation, there may be some challenges. However, it wasn't overly complicated. It depends on the complexity of the business. 

We had a small team that handled the setup. It was specifically the networking team.

We rely on business partners to help with the technical part to reduce the impact on the business.

We have reduced ROI in terms of time and money saved. 

The pricing is a little bit better when compared to others on the market.

I'm unsure if my current company evaluated other options. 

We are Microsoft customers. 

I'd rate the solution nine out of ten.

We prioritize the control of sensitive data according to our classification, which closely aligns with Microsoft's classification system. Our main goal is to prevent the loss of personal secret data. To achieve this, we focus on specific data types. Our use case involves managing managers who interact with customers. The objective is to limit access to this sensitive data within different departments, allowing some groups to have access while denying it to others. We also control outgoing information through the extension line.

The basic use case scenario is as follows: when we receive sensitive personal data from a customer, we classify this information with Microsoft Purview Data Loss Prevention for information protection. The next step involves narrowing down the range of people who can access this data through recording management. The third step is to use DLP to prevent the loss of this personal information through the extension line.

The second part of the process deals with the use and storage of this information in OneDrive, SharePoint, and Teams. We label and save it within the perimeter system. Lastly, we implement retention policies and tuition policies to ensure that the controlled path of this information is secure and that it is deleted when necessary.

It's important to us that Purview can connect to iOS, Mac, and Android devices, as well as data in other SaaS apps. We also have numerous organizations with corporate devices, all of which are connected by the MDM and MAM systems within Azure and our on-premises network. Therefore, it's essentially within our perimeter. It's crucial to control the overall flow of data and information on all endpoints, including mobile devices such as tablets and phones. Almost everything is on iOS because we are currently transitioning from older Android devices and corporate devices to Apple devices. Essentially, iOS provides better control.

Purview's native integration for compliance across Azure Dynamics 365 and Office 365 is of utmost importance to us. We have high demands for compliance, and the current design of Purview greatly enhances the user experience for both administrators and regular users. The all-in-one user admin dashboard holds significant value, as it allows administrators to easily visualize connections between modules. Moreover, as administrators, we can effectively track the flow of data between these modules and understand the interconnections of the rules across different modules. This feature is truly impressive and well-implemented. In contrast, most specific cybersecurity programs tend to have more complicated dashboard interfaces, making it challenging to identify the next step in the data flow.

It is important that Purview was built taking into account critical regulations from around the world. We are part of an international group, and we collaborate with other offices and colleagues from different countries. They are currently conducting their own research and starting to implement it. We understand that we can essentially use the same rules, making it clear to everyone how it works, how it is made, and how it is built. We have already modified some default rules and sensitive information types, making it unnecessary to create them from scratch and consider all the small details. Microsoft has provided this functionality for us, and it's incredibly useful, making the entire process much quicker.

We have a plan to set up Purview for the DLP model and incorporate it as a part of our Global DLP system in the company. Currently, we are in the planning and researching phase, and there is a lot of interest in the tool. We anticipate huge potential in Microsoft tools and how they evolve, such as Azure and Entra. Having a wider range of tools gathered in one place is very convenient.

We observe the clients' weaknesses because it essentially operates through pooled solutions within the organization. Whether we use it or not, the tenant's full settings are functional. As we work, and delve deeper into research, we notice some weaker spots. At present, we are in a phase similar to the planning step, but we already perceive the potential directions that Microsoft Purview Data Loss Prevention offers for us to work on. Consequently, we have discovered a few types of information that we had not taken into consideration before, and we see that our users encounter these information types in their everyday operational activities.

Purview has the potential to reduce the number of solutions, and as a result, it has logically impacted the company's budget. On the other hand, Microsoft has been very active in updating systems over the past three years. This development potential stands out compared to other cybersecurity tools that remain relatively static. Consequently, we don't foresee much progress or development in the functional side of those tools in the near future. In contrast, Microsoft offers its customers a clear and open roadmap for the development of their tools.

The AI algorithms could significantly assist cybersecurity specialists in mitigating risks, addressing potential threats, and preventing such threats from compromising the system.

The most crucial aspect is controlling how Microsoft Purview Data Loss Prevention functions within the SharePoint environment and cloud storage. Additionally, we exchange ideas because, as a centralized organization, we also make use of a variety of tools, including Symantec DLP. Consequently, we have different levels of systems that monitor the external and internal parameters of the company. These lines of defense are integral to our cybersecurity solutions, and at the heart of this framework lies Microsoft Purview Data Loss Prevention.

I currently work in the financial domain, and we have very strict regulations from national banks and the group side. Domain-related improvements could be really useful for organizations and banks. For example, sensitive information types are the basic level of information protection, similar to the Purview model. We start with creating or duplicating sensitive insights and editing them. I am talking about more sensitive information types that align with European regulations, especially in the financial sector. Having more variety would be beneficial. All of the EU considers sensitive information types in finance, but we need more variety, especially as a Ukrainian company. We face a lack of attention to our region, despite having the same strict regulations as EU companies. 

One point of improvement is related to organization and language issues. For instance, we use different sensitive information types for France, the UK, and other countries where we have offices. Unfortunately, Microsoft doesn't support the Ukrainian language, unlike Chinese and Japanese languages, which have deeper layers of understanding of information. It would be helpful to add support for Ukrainian. However, I understand that we are essentially bilingual, using both English and Ukrainian in our companies, and we are a minority in terms of languages.

Other solutions, like ERP systems, offer localization for Ukraine and have partnerships with companies. Microsoft 365 also supports the Ukrainian language from a user perspective. However, unfortunately, Defender and Azure lack deeper settings. They do not provide language options beyond the ones already available, so our language option is missing. Purview includes sensitive info types covering a wide range of languages and country specifications. For instance, it includes passport numbers for Ukraine, but we also need a sensitive input type for our tax numbers. Currently, there is no option for our tax numbers, which forces us to duplicate the data. In contrast, they include all sorts of options such as driver's license numbers and insurance policy numbers for EU companies. It would be beneficial to have those presets available for us as well.

I have been using Microsoft Purview Data Loss Prevention for a couple of months.

I rate Microsoft Purview Data Loss Prevention's stability a ten out of ten.

I rate Microsoft Purview's Data Loss Prevention scalability a ten out of ten. The tool is highly flexible, offering a wide range of capabilities that largely depend on the defense strategies and the proficiency of the managers who work with it. It provides ample opportunities to address various traditional data management problems. Furthermore, as the vendor develops additional solutions, such as AI, its potential for high scalability remains significant. 

We are currently considering the possibility of discontinuing our DLP program called Varonis. This is because it essentially duplicates the data classification capabilities of Purview for cloud storage. By doing this, we can potentially reduce costs, and one of the major advantages of Microsoft is its licensing structure. All our users are already covered by various types of licenses, and we can easily add another type, such as for level admins or security admins, to provide them with additional licenses that offer more possibilities and options to work with the system.

On the other hand, we have another system that also incurs implementation costs and requires significant human and primary resources. Additionally, we must consider various types of licensing, both long-term and short-term. However, one more significant advantage of Microsoft is its clear and transparent licensing policies. We can easily access information and conduct preliminary research without the need for additional communication with partners or vendors. This allows us to make well-informed decisions on what suits us best before involving a reseller, which is also an important aspect to consider.

As the Product Owner of Microsoft 365 and also the Project Manager involved in every step, I find it challenging to describe the process due to being the sole expert in this area. The difficulties arose due to wartime circumstances and the complexity of migrating to the cloud. The team had to handle the heavy lifting of the project, and the lack of available personnel added to the challenges we faced.

We have layers of regulations to consider, especially since we operate in the finance domain. It's a rather complicated situation overall, but the solution is actually quite easy to deploy.

We are implementing the solution in-house but are seeking a partner for consulting.

We are using the E3 license for Microsoft 365 with the E5 compliance license add-on. 

The prices are quite reasonable, but unfortunately, I don't know the hourly rates since they are globally negotiated for the entire group, and we probably have some nice discounts. In Ukraine alone, we have five thousand users.

We have a range of tools, and prior to considering Microsoft Purview Data Loss Prevention, we also evaluated other solutions.

I would rate Microsoft Purview Data Loss Prevention an eight out of ten. It is not specifically created for security purposes but rather functions as a branch for Microsoft, from what I can observe. However, they are actively working on improvements. I hope that eventually, it will be rated a ten out of ten. Currently, when comparing it to other systems we are using, such as Symantec DLP, it falls on the lower end.

We have only considered using Purview to help reduce actions on insider threats, but it could potentially be helpful for our ESS experts.

Our goal is to use Purview to serve multiple departments instead of 5,000 users within a single tenant.

Purview requires some maintenance because our managers have to do so after the deployment stage. The maintenance stage comes in, as the task for our information security managers is to analyze alerts and likely repeat certain steps such as creating an incentive prototype, establishing rules, and creating new DLP rules. This involves constant management processes, which are more like operational processes.

I would highly recommend Microsoft Purview Data Loss Prevention for researching and implementing data loss prevention measures, especially for mid-size businesses. As an enterprise-level organization, we have higher standards and demands. However, I believe small and mid-size businesses would find it particularly beneficial. Purview addresses all the traditional data management problems and offers specifications that are not commonly found in the enterprise sector. By using Purview, businesses can save on costs and efforts, particularly smaller ones that may lack a sufficient number of staff members with expertise in information security, DLP, and data management. Unlike enterprises, these businesses might not have the luxury of hiring specialized roles such as solution architects, data architects, and a full range of information security experts, which makes Purview an attractive solution for them.

I prefer to use products under Microsoft Office 365. I tell my customers to use Microsoft products.

My customers do not use Microsoft Purview Data Loss Prevention as they prefer to use Forcepoint Data Loss Prevention. My customers have used Microsoft Office 365, but they have not used its features. From next year, they might start using Microsoft Purview Data Loss Prevention.

I use Microsoft Purview Data Loss Prevention to protect information and endpoint or USB device controls. The tool is used for sensitive information protection on mobile devices and other settings.

The tool's most valuable feature is in the area of OCR. For my organization, Microsoft Purview compliance portal, Azure subscriptions and integrations were helpful. The document fingerprinting feature, information protection during integrations, and full cloud integrations are areas in which I am very experienced.

My customer wants the tool's OCR feature improved. The tool's user interface and document fingerprinting have been very poor for my customers because uploading files manually can be problematic.

The product's scalability is an area with certain shortcomings, making it an aspect where improvements are required.

I have been using Microsoft Purview Data Loss Prevention for five years. I work as Microsoft's strategic partners in Istanbul, especially for Microsoft Office 365 products.

Stability-wise, I rate the solution a nine out of ten.

The tool offers medium scalability and not an advanced one. Scalability-wise, I rate the solution a two out of ten.

Around 300 people are using the tool.

I have used the tool in large infrastructures over a period of three to four years.

My company's teams have communicated with the solution's technical support via emails. Based on my customer's experiences, I rate the technical support a five or six out of ten. The tool's support helped my company in areas like information protection, integration support, sensitive info types, custom keywords, and keyword dictionaries. The technical support experts that I communicated with were effective in resolving my issues.

Neutral

I have used Forcepoint Data Loss Prevention, NetSense, McAfee, and Symantec. I started to use Microsoft Purview Data Loss Prevention since I had to work with Microsoft in a collaborative manner.

When it comes to the product's initial setup phase, it is difficult, especially when it comes to the DLP endpoint onboarding of agents. There are some policies that are complex for some of my customers. With all the service integrations, you can work with Microsoft Purview Data Loss Prevention in very complex architectures.

With the tool, creating policies is easy, but its settings may be difficult. If one is difficult, and ten is easy, I rate the tool's installation phase as a three out of ten. When it comes to e-commerce or credit card numbers, there can be some installation issues, which is a problem for my customers.

The solution is deployed using the cloud services offered by Microsoft Azure.

Our company deployed the solution for seven or nine projects, including PoCs and demos. A couple of hours were needed to deploy the tool.

The product's deployment phase involved the creation of policies and the onboarding of users.

The tool's deployment requires around four people, and its maintenance requires a minimum of ten people.

The tool was not very expensive. If one is very cheap and ten is very expensive, I rate the price as one out of ten.

Microsoft Purview Data Loss Prevention has been effective in identifying and mitigating potential data leaks. Microsoft handles the XDR for the endpoints and helps prevent data leaks.

I rate the tool a ten out of ten.

We do implementations for Endpoint DLP and the cloud-based DLP. It can prevent the exfiltration of documentation, automate the classification of documents, and look for PII. We work on any sensitive information that customers don't want to leave the environment.

The tool decreases the risk of data leakage for the organizations that we've been implementing it for, both accidental and intentional.

The product can block the uploads to cloud services. The users can justify why they want to do it if they want us to allow it.

The Endpoint DLP engine has a lot of delays. The just-in-time protection feature does not always work as expected, mainly when working with network files in a more classic environment.

I've been implementing the solution for about a year and a half.

It's a fairly stable product. It requires a few more improvements.

The tool is easily scalable.

The support is poor. When it comes to DLP, the cases get tossed around a lot between Endpoint DLP and the cloud-based DLP. Sometimes, some information goes to the Microsoft Defender team. The cases get tossed around a lot.

Negative

We mostly used the built-in Exchange DLP in the past.

The initial setup is fairly straightforward. Our implementation strategy varies from customer to customer.

We have seen an ROI on the product because customers do not have to go to a third-party vendor to get the DLP functionality. A lot of customers already own the licensing port anyway.

The pricing is good. It is a good value because it is bundled with a lot of things that people buy already.

Proofpoint DLP has been assessed for a lot of customers. Microsoft Purview Data Loss Prevention allows for a lot more integration into other areas within the Microsoft realm. Proofpoint doesn't really have that and the visibility and tie-ins into all the different areas.

It is important to me that Purview delivers data protection across multi-cloud and multi-platform environments. Otherwise, we would have to have multiple DLP solutions. It is very important to me that the solution was built taking into account critical regulations from around the world. It makes it easier to templatize deployments for data loss prevention.

I use the tool for data loss protection. The tool works fairly well in remediating policy violations. There could be a little bit of improvement in policy tips. Policy tips aren't consistent across different experiences.

The tool has greatly impacted the visibility of most of our customers. Some of our customers didn't realize they had a lot of PII data being sent externally until after the tool was implemented. Later, they become more aware.

The solution enables us to show our compliance as close to real-time as possible. It has affected our meetings with compliance regulators. We don't save time and money directly. The tool saves us time and money by saving on fines for regulatory compliance violations. Without the solution, one of our customers would have been fined about $2,500,000.

It is important to me that the product can connect to iOS, Mac, and Android devices, as well as data in other SaaS apps. It's not a complete solution unless it can be used everywhere. We are implementers. People evaluating the product must understand the types of data and the compliance models they must adhere to.

Overall, I rate the product an eight out of ten.