This article doesn't make any sense. An LLM is just the model. This is why you have things like Guardrails and sandboxes. Also you guard the inputs for the LLM prompt the same way you guard against SQL injection attacks.
It's a bit like saying "If you give someone unlimited access to the database they can run queries!"
The security doesn't come from how you train the LLM, it comes from how you guard the input and output tokens.
This article doesn't make any sense. An LLM is just the model. This is why you have things like Guardrails and sandboxes. Also you guard the inputs for the LLM prompt the same way you guard against SQL injection attacks.
It's a bit like saying "If you give someone unlimited access to the database they can run queries!"
The security doesn't come from how you train the LLM, it comes from how you guard the input and output tokens.
SQL supports quoting but LLMs do not. This makes it much more difficult to block prompt injection.
Yes? SQL injection attacks have been a thing for decades now, and some people are still failing to guard against them.
But nobody is saying that is a flaw of the database.
I'd bet people are saying it - you're just too isolated from low-experience/low-competence DB users to notice it. Vs. the much newer LLM's...