What is your primary use case for Imperva SecureSphere Database Security?

We use Imperva SecureSphere Database Security to monitor user activities within databases. It includes detecting DDA activities, unauthorized queries, abnormal user behavior, and potential security breaches. It allows us to check and filter activities based on IP addresses, enabling us to track the sources of incoming requests. If any application uses SQL queries, SecureSphere can monitor these activities for unusual or unauthorized patterns. Additionally, we can set alerts for updates whenever a user profile is added to the database to ensure there is no malicious activity.

We are system integrators, so we mostly work on implementing projects. We don't handle maintenance or administration. Our focus is on implementation. We use it for database security, vulnerability analysis, discovery, and handling requests from applications and users.

We use this product to monitor database administrator events and activities on all services. We also use it for preventive measures. Some sensitive queries can be blocked in line before transactions occur.

Banks need to know who is accessing their data for compliance reasons. The other use case is related to creating, managing, and auditing databases. Some organizations cannot audit their databases because it involves lots of heavy processing, so they would rather have a third party do the database monitoring. That's where Imperva comes in. My enterprise clients use Imperva on-premises, but some customers are using FlexProtect, which is a cloud-based solution. About 10 security engineers at my company use Imperva currently.

We primarily use the solution just to monitor database activity on all the in-house databases.

We are using Imperva SecureSphere Database Security for database protection.

Our customers are using Imperva SecureSphere Database Security for GDP compliance.

I use SecureSphere to monitor our core databases and privilege operations by administrators, and to provide compliance reports.

The use case is for database services, security purposes, and access capabilities. In DAM, we cannot use inline mode due to the blocking that is there. Details can be shared and accessed to see, for example, information about the DB, who's using it, its applications, et cetera. There are all kinds of reporting that can be accessed. We submit reports to the customer.

I'm the product manager for Imperva in Africa for a distributor. I manage it every day, but I don't personally use it. We sell Imperva to customers in 17 countries. Its deployment depends on the customer. Some customers have their databases in the cloud, and if they have them in the cloud, we give them the cloud database security of Imperva. If their database is on-premises, then we deploy it on-premises, and the reseller implements the solution on-premises.

We use it for database activity monitoring. We use it to monitor all the traffic that comes to the database to know about the operations that are happening on the database. At the moment, it is on-premises, but we eventually would like to go to the cloud.

We primarily use the solution for auditing purposes so collecting and archiving of logs.

Imperva SecureSphere Database Security is used to store data for if there is an emergency we can restore it.

Our primary use for this product is as an application firewall.

We use it to prevent threats to the database. It is like a firewall in front of the database servers.

Most of our clients are banks and insurance and financial institutions that want to achieve compliance. They want to achieve auditing for their regulatory compliances as well. On the database side, that includes being able to monitor DBS and to block certain activities on the DVF. On the application side, it also has to be preventative and that's also part of compliance. This solution enables clients to achieve data security, whether on cloud or on prem. We offer support services and we are a service provider for database security through Imperva and also application security through Imperva to our clients. I'm a cyber security engineer and we are gold partners of SecureSphere DS.

It is mainly used for database activity monitoring. Some customers use it to monitor all transactions in the database, such as privilege operations, grant commands. They collect all the data and see all transactions and store them. Sometimes, they also use security alerts with the database update monitoring, but generally, it is used only for regulations.

We primarily use the product for data security.

We primarily use the solution for monitoring database activities.

Our use case for the solution is for monitoring, reporting and access management as well as looking for alerts in anomalies of behavior. I'm an information security analyst and we're a customer of Imperva.

The primary use case is for database monitoring. We are also using the blocking part, which is used for: * Any suspicious activities which are done, such as delete command and query command, outside the admin, the solution is supposed to block them. * The blocking of compromised databases through cloning. Blocking will not allow the cloning. We use it for blocking and auditing. Our job is monitoring. We are a government entity and provide services to other ministries. We use Imperva for its Database Activity Monitoring and File Integrity Monitoring tools. We have also enabled Database Firewall.

We generally use Imperva as a database firewall and for activity monitoring. The solution has to fit the organization first. Once we know the product is a fit, we support in the creation of reports. We look at the core users (administrators, auditors, accountants, etc.) who need to get information and we look at the responsibility matrix. Our responsibility is the database and we try to implement the total solution for an organization. This means reports are created for the specific needs of, say, IT security administrators, top management, IT guys, etc. This shows each group or individual what they need to know. We try to make it so database administrators do not have to directly interface with the solution by creating report editors and report creators based on the unique assessment of the organization. Imperva is a high-end product and it doesn't come cheap. Most government agencies don't use it because of its expense. But those who use it, like it and it's on the wishlist of many organizations.

The primary use for our company is to enable the auditing on the DB level. The main target is to track the activities happening and by whom on critical tables. Based on that requirement, we purchased this database auditing solution because it was specific to Oracle for auditing purposes.

Our primary use for this solution is securing banking web applications. It protects the web service of one of the big Internet banks in Iran.

We do not use this solution directly. Rather, we procure it for our customers and assist with the implementation.

My team and I deploy this solution for customers. In Israel, I'm the team leader of the whole Application Security Division.

I am using Imperva in different projects for application defense.

I use this solution to discover missing data, and to find weaknesses or miscalculations in my database standards.

The primary use case is specific to database security through log auditing, to identify the actions performed by various users. That gets logged. Then policies are used to see whether any action performed by a database user is below a threshold or above a threshold; whether there should there be an alert because of it. It is used by specific teams within our organization to monitor activity, to see whether there is any malicious activity or a user who's not supposed to be performing a certain action.