Security in Azure Managed Instance for Apache Cassandra - overview
This article discusses database security best practices and key features offered by Azure Managed Instance for Apache Cassandra to help you prevent, detect, and respond to database breaches.
How do I secure my database
Data security is a shared responsibility between you, the customer, and your database provider. Depending on the database provider you choose, the amount of responsibility you carry can vary. If you choose an on-premises solution, you need to provide everything from end-point protection to physical security of your hardware - which is no easy task. If you choose a managed service such as Azure Managed Instance for Apache Cassandra, your area of concern reduces.
How does Azure Managed Instance secure my database
Security requirement | Azure Managed Instance for Apache Cassandra's security approach |
---|---|
Network security | Azure Managed Instances for Apache Cassandra resources are hosted on a Microsoft tenant, with network interface cards (NICs) for each resource injected exclusively into Virtual Networks using private IPs. There are no public IPs exposed with this service. |
Automated online backups | Azure Managed Instance for Apache Cassandra datacenters are backed up every 4 hours and retained for two days. Backups are held in local storage accounts. |
Restore deleted data | The automated online backups can be used to recover data you may have accidentally deleted. You can back up data to any point within approximately two days after the delete event. |
HTTPS/SSL/TLS and disk encryption | In Azure Managed Instance for Apache Cassandra, all data is encrypted at rest. Server SSL (TLS 1.2) and node-to-node encryption are enforced. Client SSL is an optional configuration. Customer-managed keys for encrypting data on disk are supported - see article here for more information. |
Monitor for attacks | Azure Managed Instance for Apache Cassandra is integrated with Azure Monitor. By using audit logging and activity logs, you can monitor your account for normal and abnormal activity. You can view what operations were performed on your resources, who initiated the operation, when the operation occurred, the status of the operation, and many more tasks. |
Respond to attacks | Once you have contacted Azure support to report a potential attack, a five step incident response process is kicked off. The goal of the five step process is to restore normal service security and operations as quickly as possible after an issue is detected and an investigation is started. |
Patched servers | As a managed database, Azure Managed Instance for Apache Cassandra eliminates the need to manage and patch servers, that's done for you, automatically. |
Certifications | For the most up-to-date list of certifications, see the overall Azure Compliance site. |
Next steps
For more information about Microsoft certifications, see Azure Trust Center.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for