I use it for the likelihood of incident response, intrusion prevention, intrusion detection, and malicious traffic.

Before IBM Guardium Data Protection, we didn't have any solution. We wanted to check our database activities, for example, admin activities, so with IBM Guardium Data Protection, we created some use cases and also wanted to check up on the use cases in our environment, so we deployed the solution. Right now, we have three or four use cases for IBM Guardium Data Protection: creation, table deletion, and making changes to the table, and we receive alerts when any of those activities happen.

We mostly use Guardium as a data activity monitoring solution (DAM). We also use it to perform vulnerability assessment (VA) for data. We deployed Guardium on a private cloud. It isn't a hardware product. It's all virtual machines.

We are resellers of this solution and IBM partners. I'm a manager of security solutions.

We are using the data protection module to look after the PML queries of our Oracle admin accounts. I'm the chief information security officer at a financial institution. 

We use IBM Security Guardium Data Protection for real-time monitoring, data protection, recovery of sensitive objects, and vulnerable data scanning for databases.

For compliance and risk assessment, monitoring the database traffic, as well as doing vulnerability assessments on the database to make sure that our security is up to par. We use it to keep us less vulnerable as a company as well as to keep the customers' data safe.

So far it has performed really well. Occasionally, we have issues here and there with new patches having bugs, but that's the case with any software.

We want to avoid unauthorized manipulation of data. We evaluated use cases like database discovery, identification of sensitive data, and installation and configuration of custom policies. We also conducted POC for alerts on DDL and DML commands, activity logs of users, restricted access for specific users, reporting, and dashboarding.

IBM Guardium Data Protection is used not just for protecting data, but also for vulnerability protection. We use it to monitor our active users, activity, and databases, to look at the kind of commands users do on the databases.

We also use the solution to restrict unauthorized users from accessing the databases. Apart from restricting unauthorized users from accessing these databases, we also need to have the stability to add the database, then switch to another database.

We can also turn on the blocking feature of IBM Guardium Data Protection to ensure that some IPs are unable to connect to some databases.

Our customers include financial institutions like banks, insurance companies, and government entities that use IBM Security Guardium Data Protection for the protection and hardening of their databases.

Primarily re-monitoring sensitive data and privilege user access. 

To keep track of client information, index security risks, and other information needed at a moments notice. IBM Guardium performs transparent encryption and decryption provides on the fly encryption without needing to be indoctrinated into lengthy training to use it. 

Our primary use case of this product is for privileged database activity monitoring. We are customers of IBM and I'm the DBA.

database security

We use it for security purposes, particularly because we have customers in financial sectors, banks, and other high profile industries.

We use this product to protect our information. It provides the added feature of including some protective marking rules on the data. Security is the overall high-level objective for us using this solution. We are customers of IBM and I'm a tech lead.

We are monitoring about 1500 or more applications, we have 150 million customers and their PHI/PII data in the repository. We have to protect that data. That is a big challenge because it's a vast environment that we have to protect. That is one of the prime use cases which caused us to select this product.

Initially, we had some challenges, but as we talked with IBM and they provided some good support on it, now we are evolving pretty well. Certainly, everything is not perfect yet, but we are moving into that direction. We are far better than we were two years back.

Our primary use case would be for compliance reporting: DBA activity monitoring for SOX regulations.

It has performed fairly well. There are issues here and there, but it is the only product on the market that can do this job. It is the industry leader in database security.

We are resellers of IBM. Most of the use cases of IBM Guardium are to monitor the database activity. The first is to identify any abnormal activities like trying to access the database or trying to create or delete any scheme on the tables. 

The primary use case for most of our customers is for monitoring and compliance. It's mostly deployed on-premises and it's a database activity monitoring solution. 

We will primarily use the solution for protecting our database. We're still implementing the product. It's not fully in place just yet.

We primarily use the solution for database access management where they are using DML commands. We use it for compliance and validation. If there's any change in the record, this solution will notify us.

Database activity monitoring.

It performs its job quite well.

For the mainframe, monitoring DB2 privileged access to our databases.

It has performed really well so far for the purpose, but we're not using the full capacity of it. There's also an open systems side that they're implementing now, that I'm not part of, but there's a lot more growth in that area.

Our primary use case for IBM Guardium Data Protection is audit logging. We monitor transactions and access particular tables in the database with it. 

We use the product to permanently protect data from unauthorized user access, malware, and external threats.

We use Guardium for large and medium-sized clients in the banking sector for things like monitoring, protecting sensitive data, and logins.

We acquired Guardium to encrypt certain databases to meet a customer requirement.

It has been performing to spec.

We are using this solution for a PoC.

IBM Guardium Data Protection is used to create policies, and rules for database access management.

Database monitoring. At the moment, we are using it to do a lot of data discovery from a data classification for structured data.

Database activity monitoring.

Its performance is good, most of the time.

It's being used to identify who is using what data, what resources, what they're using them for, providing audit trails. We also use it to set baselines for usage patterns, to start building cases if there are any erroneous accesses happening, and to start allowing more intuitive alerts.

So far it's installed. It was a little rocky at the beginning but everything is working pretty well now. I think the baselines have been established and so far it's performing as expected.

Now that they have the base, they are going to start creating other use cases. I'm not sure what they are, but they are going to start expanding the usage and provide more education to the security staff.

Our primary use case is for managing and monitoring the database in real time.

Currently, my customer has 10 different types of databases for their various banking applications and they intend to deploy IBM Guardium Data Protection to secure their database activities. As soon as it is deployed, we're able to get some insights into what is going on with their databases, to help ensure the integrity of their data in the future.

Two banks are also working on two opportunities with IBM Guardium right now. I believe this is a compliance requirement; nowadays, everyone has to buy database protection. In that case, technically, Oracle will get the added advantage here, because most of the banks are already using Oracle database.

One of my customers is a company that manages telecommunications in Mexico. It is a very important company, and they use Guardium for compliance purposes. They use it to comply with PCI, for example.

We have on-premises and cloud deployments. We are currently deploying a customer's environment in Microsoft Azure with SQL Server.

The primary use case is for ensuring compliance with databases. It allows monitoring of what kind of statements and alterations are going on, as well as who is accessing what data.

We want to protect our data. That's the primary use case.

So far, performance has been okay.

We deal with a range of customers and lately the issue of data privacy and user identity has become very important and many companies are now seriously evaluating tools like Guardium. Companies want to know who is accessing database applications and what they are doing. This product is geared towards medium and large size enterprise companies. We're partners of IBM and I'm a company Vice President. 

It tests security to support SOX compliance.

This solution is for database security and protecting the core of the data. It allows us to put in controls to make sure that only the right persons access the proper records in the database. It prevents unauthorized access.

For example, a customer may want to restrict the database so that it is accessible only from within a specific application. This means that the database administrator will not be able to access the data from outside of the application, as is normally allowed by their administrative rights. It can prevent the administrator from seeing or modifying any data for which they are not allowed to do so.

It is also possible to set specific permissions, such as restrictions on the field, table, or record level of the database. Only people with explicit permissions can view or modify the data.

To protect the data. We're trying to monitor privileged users, get an idea of what's normal access, and to make sure that service account usage is only coming from the appropriate places, not being used by people from their own work stations.

How I would describe how well it's performing is that we are taking a slow and steady approach to it. Right now, I would say we're going from crawl to walk as far as usage goes; not using any of the sophisticated features, more getting the base implementation in place.

Database activity management to ensure compliance audit regulations. It is also to manage risk. It is performing well, but we have a large journey to go.

• Database access monitoring
• Vulnerability assessment
• PCI compliance
• SOX compliance
• GDPR compliance 

It's a security product that works across multiple platforms, in our case it's the mainframe and the midrange. We use it to detect when somebody accesses restricted data and report on it.

So far it has performed quite well, we're happy with it.

I mainly use this solution to monitor the activity happening in the database.

We use IBM Guardium Data Protection mostly for data masking and firewalling. We restrict the administrators and other users from altering or deleting anything from the databases.

We have implemented it on an industrial network to monitor the production of medicines. This is something that is very controlled by Brazilian regulations and we have to keep an audit trail for this data. Trying to enable it on SQL Server - that was our client's main server - the load would go so high that they couldn't use the application anymore. They are using Guardium now so they can produce that audit trail for audit compliance.

We are using IBM Guardium Data Protection for activity monitoring, blocking users,  entitlement for knowing the privilege for users, and Guardium data features.

Guardium is used based on our Manual of Internal Procedures (MPI), and its uses range from creating a rule to generating customized reports. The main use case is the procedure "Investigate Incidents Recorded by Unauthorized Access," with action "notify by electronic message the manager and/or leader of the area."

Database encryption.

The primary use case is security of our data in the bank.

Performance is very good.

As a registered IBM Business Partner, our main interaction is to deploy Guardium at client sites.

To provide cyber security for databases.

It has performed very well.

We are a solution provider and IBM Guardium is one of the database products that we implement for our clients. Our customers for Guardium are mostly banks and they use it for PCI compliance.

My primary use of this solution is for database activity monitoring.