
Overview
DataSunrise Security secures databases and data in real-time. DataSunrise includes Database Activity Monitoring (DAM), Dynamic Data Masking, Static Data Masking, Sensitive Data Discovery, Compliance Automation and Vulnerability Assessment. DataSunrise secures all major SQL and NoSQL databases, data-warehouses and data lakes on AWS: all RDS database engines(PostgreSQL, MySQL, MariaDB, Oracle, MSSQL), Amazon Aurora, DynamoDB, Redshift, Athena, Elasticsearch, S3. DataSunrise secures other databases such as SAP HANA,Oracle, Cassandra, Impala, Heroku, DB2, Greenplum, MongoDB, Netezza, Hive, Vertica. DataSunrise enables PII and PHI data protection, auditing, discovery, compliance with privacy law,SOX, HIPAA, ISO27001, PCI or GDPR. DataSunrise gives customers full and granular control over security of sensitive data, access to data and databases and automated compliance policies. DataSunrise empowers organizations when moving their databases workload to db managed services, preserves same level of data security and data auditing. DataSunrise High-Availability, Autoscaling and Failover for AWS, all available DataSunrise instances monitored and configured from a single console. Authentication proxy, Active Directory and LDAP support. Integration with CloudWatch and IAM and SIEM.
Highlights
- Why Take Chances with Database Security. Ultimate Database Security isn't optional
- Secure and mask data, and control of all activity and DAM in RDS, Redshift or other databases
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Pricing
Dimension | Cost/unit |
|---|---|
Protected database instances per hour | $1.40 |
Vendor refund policy
30 days trial
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
64-bit (x86) Amazon Machine Image (AMI)
Amazon Machine Image (AMI)
An AMI is a virtual image that provides the information required to launch an instance. Amazon EC2 (Elastic Compute Cloud) instances are virtual servers on which you can run your applications and workloads, offering varying combinations of CPU, memory, storage, and networking resources. You can launch as many instances from as many different AMIs as you need.
Version release notes
Additional details
Usage instructions
Use your web browser to access DataSunrise GUI at https://instance_dns:11000 Use login 'admin' and 'DS-"EC2_instance_ID"' as password To connect to the operating system, use ssh client and username "ec2-user" (https://docs.aws.amazon.com/en_us/AWSEC2/latest/UserGuide/AccessingInstancesLinux.html ). Refer to DataSunrise User Guide for more options : https://www.datasunrise.com/files/DataSunriseDatabaseSecuritySuiteUserGuide.pdf
Resources
Vendor resources
Support
Vendor support
Customer Service and Technical Support: support@datasunrise.com Phone: +1(206) 420-6611. See our Support page for detailed information (https://www.datasunrise.com/support/ ) https://www.datasunrise.com/support/
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.

Standard contract
Customer reviews
Rule-based monitoring has strengthened real-time protection against SQL injection attacks
What is our primary use case?
I use DataSunrise Database Security mainly for rule-based blocking of SQL injection, which provides a profound level of data security when it comes to securing the database.
For example, I was using a microservices architecture with my back-end database on Azure SQL. I implemented a rule stating that only respective IPs are whitelisted for members of the database security admins, meaning that only some of the security admins can directly launch DataSunrise. Additionally, I created rules to inspect SQL injections based on the pattern of the SQL data.
I was only using DataSunrise Database Security on the database fronting layer to detect and block SQL injection and some other rules. Most of my configuration has focused on the SQL injection part and rules related to database admins logging in.
What is most valuable?
One of the best features DataSunrise Database Security offers is real-time blocking. It also monitors database health very precisely, meaning all queries in my scenario function like a proxy where a database monitoring tool exists. This monitoring has handled any suspicious queries being injected by the application very smoothly.
The real-time blocking and database health monitoring have helped my team on a day-to-day basis, as it was a requirement from my organization to have a database activity monitoring tool. I reviewed Imperva and DataSunrise, and since Imperva does not have the proxy layer feature for microservices, I chose DataSunrise to act as a proxy.
Feature-wise, DataSunrise Database Security is a base monitoring tool, and it has all other features including metrics monitoring. Most crucially, it is used to track the queries initiated by the application, and based on the rules I set, it will either block, allow, or log what kind of database query has been run from the application side.
DataSunrise Database Security has positively impacted my organization, as it acts as a proxy. I was looking for a device or tool for proxy use, and although I gathered information for Imperva, it unfortunately did not work. So far, it has had a very positive impact where my databases are purely monitored via DataSunrise.
What needs improvement?
I believe the product features are good so far, but I experienced some issues. When I upgraded to a newer version, there were some bugs found that were not resolved. Therefore, I would assume that DataSunrise can improve their quality checks before releasing a new version.
I would like to see improvements mainly in support and documentation, as whenever I contact DataSunrise support, the support team is not fully aware of the new features or version revision histories. The documentation has been vague and not well done. I think DataSunrise as a product is still in the initial stage where there are many improvements that can be made regarding documentation and support.
For how long have I used the solution?
I have been using DataSunrise Database Security for more than two years.
What do I think about the stability of the solution?
Since using DataSunrise Database Security, the only query-based inspection outcome I have seen so far is more focused. There was nothing related to any time saved or measurable improvements. As this tool is specifically a security tool designed to analyze all database activity, it has helped a lot in that scenario.
What other advice do I have?
I would advise others looking into using DataSunrise Database Security to consider it a good product. I rated this review an eight out of ten.
Unified masking and discovery have protected sensitive data across hybrid production copies
What is our primary use case?
I use DataSunrise Database Security for data masking purposes in my environment. I manage a lot of production systems for different applications, and whenever teams need to copy production databases including sensitive information such as PII, PHI, or PCI to non-production environments, I apply masking to those sensitive fields and protect the data from unauthorized users.
I leverage DataSunrise Database Security for data discovery, which is another method I use to find sensitive data.
What is most valuable?
I appreciate many features, including real-time database activity monitoring and auditing.
In my environment, I manage numerous production systems for different applications. When teams need to copy production databases containing sensitive information such as PII, PHI, or PCI to non-production environments, I apply masking to those sensitive fields and protect the data from unauthorized users.
DataSunrise Database Security's data discovery capability is another valuable tool I use to identify sensitive data.
For how long have I used the solution?
I have been using DataSunrise Database Security for approximately two and a half years.
What other advice do I have?
My advice to others considering DataSunrise Database Security is that it is a good and unified tool. Overall, it is a very good.