Over the past decade, a significant portion of IT infrastructure has moved from proprietary data centers into public clouds. This move requires examining the technique used to manage and secure these resources, especially databases. In order to adequately secure data in the cloud, an understanding of the architectural differences between public cloud and on-premises databases is required.
The use of cloud databases is growing exponentially among businesses. Yet, many organizations are not as familiar with the technology as they are with on-premises databases — or how to best secure the data in it. (Download this white paper—Database Security: Moving to the Public Cloud—to explore the architectural and security differences between the public cloud and on-premises databases in more depth).
SecureCloudDB is always working to improve our users' experience. We’re excited to announce that new features — AWS Security Hub integration, create your own security rules, customize your Risk Assessment Report — and enhancements — expanded Database Activity Monitoring capabilities, alert set-up upgrades, home dashboard upgrades — are now available.
Read More
In this 10 part series, we review the key components that are needed to formulate and apply a consistent, regimented cloud database security program that helps ensure data is only available through authorized access. Part 9 reviewed reporting recommendations. Part 10 below provides considerations for selecting security service providers and concludes the series.
In this 10 part series, we review the key components that are needed to formulate and apply a consistent, regimented cloud database security program that helps ensure data is only available through authorized access. Part 8 addressed the other side of monitoring—alerting. Part 9 below reviews reporting recommendations.
In this 10 part series, we review the key components that are needed to formulate and apply a consistent, regimented cloud database security program that helps ensure data is only available through authorized access. Part 7 delved into public cloud database activity monitoring. Part 8 below addresses the other side of monitoring—alerting.
In this 10 part series, we review the key components that are needed to formulate and apply a consistent, regimented cloud database security program that helps ensure data is only available through authorized access. Part 6 discussed remediation, including how to proactively reduce risk. Part 7 below delves into public cloud database activity monitoring.
In this 10 part series, we review the key components that are needed to formulate and apply a consistent, regimented cloud database security program that helps ensure data is only available through authorized access. Part 5 unpacked vulnerability assessments including the step-by-step process and critical areas to check. Part 6 below discusses remediation, including how to proactively reduce risk.
In this 10 part series, we review the key components that are needed to formulate and apply a consistent, regimented cloud database security program that helps ensure data is only available through authorized access. Part 4 reviewed considerations related to asset discovery.Part 5 below unpacks vulnerability assessments including the step-by-step process and critical areas to check.
In this 10 part series, we review the key components that are needed to formulate and apply a consistent, regimented cloud database security program that helps ensure data is only available through authorized access. Part 3 discussed public cloud database configuration best practices. Part 4 below reviews considerations related to asset discovery.