Search
  • Tim Burns

Glad to Report I wasn't Hacked on my Vacation



Seriously...

But I am reviewing database security protocols, starting with this article from Oracle

Securing data is the first thing every Data Architect thinks about when setting up a new database, but systems degrade over time, and security becomes more complex, the more data we have.


Snowflake, my database of choice, is particularly challenging because

  • It is cloud-only

  • Is accessible to the internet

  • Requires trust relationships with cloud providers.

Checklists are an excellent method to establish consistency and quality on a repeated process. Security is not a "set it and forget it" process and requires continual diligence and adaptation to change. In that way, it is fundamentally agile: You better be able to respond to change, because the security profile of your data is changing all the time.


In my new initiative, I will be outlining practical checklist and automated methods for Snowflake Data Security including:


  1. Assessment - Build actionable reports on the current state of your data security

  2. Detection - How can you automate intrusion detection

  3. Prevention - How to prevent unauthorized access to data

  4. Data Security - Secure the data at the fundamental levels

  5. User Authentication - Validating the identity of users

  6. User Authorization - Defining Roles and Privileges of users and Groups

It's a large checklist and one I'm hoping will keep me busy writing and learning. Hope you enjoy following me.



14 views0 comments

Recent Posts

See All

Calendars and dates drive our lives; a calendar dimension is essential to most data warehouses. Pope Gregory introduced the Gregorian Calendar in XIII in 1582. It took over the world, and we take it