TechPulseTechPulse
Back to News
Advertisement
Advertisement

⚡ Community Insights

Discussion Sentiment

50% Positive

Analyzed from 122 words in the discussion.

Trending Topics

#deepsql#different#risk#database#confidentiality#problematic#managing#access#availability#entire

Discussion (2 Comments)Read Original on HackerNews

duttish•about 2 hours ago
It seems they're conflating two different risks? Read-only connection is a solution to Integrity risk, while they straight away start talking about Confidentiality risk instead.

They're also problematic, but different kinds of problematic and I don't see how this is different from managing employees database access.

Then there's no mention of handling Availability risk management. An employee or agent querying the entire order table joined with... and the entire db cluster is choked for two hours.

venkat971•2 minutes ago
Data confidentiality and sovereignty matter a lot to enterprises. You may want to redact access to the most sensitive data from both humans and agents, and it gets tricky to enforce such dynamic policies at the database level. DeepSQL solves this by managing all DB users (humans and agents) at the DeepSQL layer.

DB availability is out of scope for DeepSQL at the moment.

venkat971•about 5 hours ago
https://deepsql.ai/blog/giving-an-llm-your-database-is-easy-...