Você está começando um novo projeto. Quais são as melhores ferramentas de segurança de banco de dados para manter seus dados seguros?

Among the encryption approaches, you need to consider the level of security you require. There are situations in which you need to consider the use of a key management system (kms). In this scenario you split the data in chunks and encrypt the chunks with different keys (the so called data encryption keys, or dek). The dek are then encrypted with a master key stored in the kms. This is generally called a key encryption key (kek). The encrypted dek is then stored as a metadata of the chunk. When a request for data in the chunk is intercepted, the encrypted dek is sent to the kms and the chunk decrypted. This schema ensures a high level of security.

When developing web applications using ORMs or database mappers, the responsibility for security is often delegated to cloud service providers like AWS or GCP. In the context of utilizing Amazon RDS for database setup, it is crucial to leverage its fundamental features for enhanced security. Amazon RDS provides automated backups, allowing developers to easily restore data in case of issues, as well as snapshots for point-in-time recovery. Additionally, the service supports encryption at rest, adding a layer of protection to sensitive data stored in the database.

In terms of security, Transaction Data Encryption should be followed as a key step. Backup of database and restored in lower in environment is the frequent Task for any db related projects. Without TDE the complete db is accessable for all those have or can access the backup path. With TDE , even the db is accessable one cannot restore or read the data without a key.

Couple of them comes to mind - Transparent Data Encryption (TDE) - Encryption of Data in Transit - Real-time Monitoring - Auditing and Logging Additionally, regular security assessments, audits, and updates are essential to maintain the effectiveness of database security measures over time.

To ensure database security, employ encryption tools like Symantec Data Center Security, access control mechanisms such as Oracle Database Vault, and real-time monitoring tools like Imperva SecureSphere. Implement data masking with Delphix, conduct regular vulnerability assessments with QualysGuard, and use DLP solutions like Digital Guardian. Maintain software updates with ManageEngine Patch Manager Plus, enforce security policies with IBM InfoSphere Guardium, and invest in employee training. This multi-layered approach fortifies defenses, mitigates risks, and ensures compliance.

Implement strong authentication and authorization with tools like Okta, Auth0, Keycloak, OAuth, Firebase Authentication, Shibboleth, AWS IAM, Azure AD, and Authenticator Apps. Choose based on project needs for secure user access and data protection.

Always provide minimal permissions that only allow users/machines to accomplish their specific task. Use inheritance to restrict who can do what in order to remove direct permissions reducing the potential of abuse of any privileges. You also need to be able to associate any activity to a specific user, be it in the data access or app layer in order to provide traceability.

IMHO , the existing MFA & RBAC are too weak when it comes to protecting your crown jewel. In many cases, what you want to do is to change the level of access to the databases dynamically, based on the time of the day, or the load on the system. To make sure that your database is protected even from human mistakes or from consuming resources during peak days, leveraging a proxy to the databases could be your solution, some proxies like ProxySQL and Rapydo Cortex are taking these granularities to the next level

From Authentication perspective, you should make every possible effort to stay away from password based authentication. Use SSO for both human and non-human (aka service accounts) users, where not possible use key-pair for non-human users, additionally, ensure MFA is enabled for human users. From authorisation perspective RBAC is key. RBAC design should be given fair attention, as it forms the core of your database. The RBAC design should not only address the current requirements but also consider how the database usage will evolve over time. If RBAC is not done right, it creates not only security issue but also leads to complex processes, bad user experience and above all possibility of data leak and audit failures.

The Auth & Auth section should also pay reference to SASE architecture, especially in today's "work anywhere" world as you cannot assume that if a user/service account has successfully passed the Auth & Auth stage it is still safe anywhere within the internal network/solution.

O objetivo principal do uso de uma ferramenta para monitorar BD é fornecer visibilidade sobre atividades que ocorrem nos DB, proteger dados confidenciais e sensíveis, identificando e controlando acessos não autorizados, detectar tentativas de acesso indevido e monitorando o movimento de dados dentro e fora do ambiente do BD. Detectar atividades anômalas nos BD, identificar uma violação de segurança ou tentativa de acesso não autorizado. Prevenir e responder a ataques cibernéticos, gerenciamento centralizado. Atender regulatório e conformidade. Tenho boas referencias da fermenta Guardium da IBM.

Strengthen auditing and monitoring in your project with tools like Splunk, ELK Stack, Prometheus, Nagios, Graylog, SolarWinds, Wireshark, Datadog, Auditbeat, and Sysdig. Tailor choices to project size, infrastructure, and monitoring requirements for robust security and performance insights.

Database security tools, like encryption, access control, and activity monitoring, protect data integrity and confidentiality. Encryption, such as TDE, secures data at rest. Access control, like RBAC, manages user privileges. Activity monitoring tracks and logs database actions, identifying unauthorized access. Firewalls filter traffic, guarding against SQL injection. Vulnerability assessment tools find and fix system weaknesses. Data masking obscures sensitive data. Auditing tracks schema changes. Regular patching and security assessments maintain protection. Tailoring tools and staying updated mitigate risks, ensuring robust security.

Many industries have regulatory requirements (e.g., GDPR, HIPAA, PCI DSS) that mandate the protection of data. Implementing database security measures helps organizations comply with these regulations and avoid penalties. Tools such as Symantec Data loss protection, Check point data protection helps the process and to be more secure

Access Control: Restrict access to databases based on roles and responsibilities, and regularly review access permissions to ensure they are up-to-date. Audit Trails: Maintain detailed audit logs to track database activity and detect any unauthorized access or suspicious behavior. Patch Management: Keep database software and operating systems up-to-date with the latest security patches to address vulnerabilities. Firewalls and Intrusion Detection Systems: Deploy firewalls and IDS to monitor and block unauthorized access attempts and malicious activity. Data Backup and Disaster Recovery: Regularly backup database data and implement a disaster recovery plan to minimize data loss in case of a security breach or system failure.

In order to fix vulnerabilities and improve overall resilience, it's critical to think about regular updates and patches in the field of database security. While implementing authorization, authentication, and encryption is essential, continuous maintenance guarantees long-term security. Furthermore, building a security-aware culture within the project team can make a big difference in how strong the database security framework is overall. #databasesecurity

Database Activity Monitoring (DAM) involves employing solutions like McAfee Database Security to monitor and analyze database activity, enabling the identification and response to potentially suspicious behavior. Data Masking and Redaction tools, such as Oracle Data Masking and Subsetting, are utilized to obscure sensitive data in non-production environments or restrict access to specific fields based on user roles. Predefined masking formats can be employed to conceal sensitive information like credit card numbers, national identifiers, and other personally identifiable data (PII). DAM solutions, data masking, and redaction enhance database security, safeguard sensitive info, and ensure regulatory compliance.

To ensure top-notch database security, consider tools like #OracleDatabaseVault, #ImpervaSecureSphere, and #Guardium. These powerhouses offer robust features to safeguard your valuable data.

Nice LinkedIn article with lot of good points - data encryption, audit, monitoring, and multi-factor authentication. I would like to add a few points towards maintaining database security with proper tools. It is imperative to use industry standard encryption for both physical data as well as digital data. Short list tools that encrypt all data at rest as well as in-flight. AES 256 offers one of the best encryption standards especially for classified data such as the ones used by governments. AES-256 encryption is virtually uncrackable using any brute-force method. It would take millions of years to break it using the current computing technology and capabilities.

To maintain database security, will have to use robust authentication, role-based access control, data encryption, regular audits, intrusion detection systems, software updates, secure server configuration, backups, firewalls, VPNs, DAM tools, regular security audits, and comprehensive assessments.