How: We can generate a masking set using the SQL Data Catalog PowerShell each and every time as part of our pipeline. But how? Well it all depends on which approach we want to take:ĭoesn’t it always boil down to those options? What I mean is that either we have an appetite to completely generate our masking set afresh every single time based on our classifications (Automated) or do we want to ensure that we configure each rule ourselves (Manual). but one of the biggest wins is that we constantly know which fields need to be masked when we’re pulling copies back into non-Production, constantly.Īdd a table? Add columns? We know about them, they’re classified, they’re deployed… so now they need to be masked on our next refresh. The benefits of including the classifications in the upstream pipeline is that nothing ever gets to Production that hasn’t been classified – we constantly have a perfectly up to date idea of the nature of our structured data estate, how data is distributed, what risk is associated with which systems? etc. If we include cataloging in the upstream process, how do we make sure our masking sets are also staying up to date?
But one question that this always throws up is: I’ve even produced a video demonstrating this in action. You’re probably sick of me constantly talking about how the cataloging of columns should be part of the DevOps upstream deployment process. “However fast regulation moves, technology moves faster.
0 kommentar(er)
