3 ms·
Wrong thread? I use tools like that, but they're not the environments, credentials, & threat models (I think) we're talking about. I'd be curious if/how any d
by lmeyerov 5y ago
Wrong thread? I use tools like that, but they're not the environments, credentials, & threat models (I think) we're talking about.
I'd be curious if/how any data science teams (google/facebook/netflix/...) bake user credential & API secrets into data science notebooks. I've never seen it, but I don't get to see everyone's notebook environments. I have seen 1-2 projects attempting to do DB auth plugins/libs for jupyter notebooks, but not high-grade production ones. Instead, it gets baked into the deeper env (think Tableau, Databricks, ...), vs part of the ipynb.
Notebook security feels like 1990s/2000s browser security and the literal decades of unsafe web apis. DLP and all that is at the forefront in risks, yet most tools just do system auth and maybe a few special connector auth. The real threat model is outside of their system, so it's no surprise analysts & their data orgs fail in practice :(
- morelisp 5y agoArguably kahrl is in the wrong thread repeatedly posting about "never ever ever ever ever ever storing secrets in version control". As I said, I agree PII/PD is different. Sealed secrets can be used in various k8s-aware notebooks.