Most of our users, including customers, use it primarily as a Database Activity Monitor. They utilize it to track who is logging into which database and monitor their activities. This includes tasks such as restricting certain SQL commands and understanding environmental limits related to database access.
We have a law in Turkey similar to the GDPR in the European Union. It's almost like a replica. Complying with this law is crucial, and the service plays a significant role. Many customer inquiries revolve around not retaining their data. The service addresses this by providing functionality for masking data within the databases. So, if a user requests data deletion, we can remove any information we have on them within the database, ensuring compliance with the law.
The discovery and masking features, encompassing both static and dynamic database masking, are incredibly useful for ensuring compliance. Most of the time, not everyone accessing the database is a developer or a database admin. Developers might need to see everything, but database admins, even though they manage the database, don't necessarily need to see all the data, especially customer data. So, using masking for database admins and not displaying data in clear text is quite helpful for compliance.