Tagged llm-apps
2 pieces
- · 9 min read
A Prompt Is Not a Lock: Three Ways Row-Level Security Leaks Even When the Rule Is Written Correctly
When an assistant answers questions about live records, the engineering is the permission boundary, not the retrieval. In a Postgres demonstrator with a correctly written row-level security policy, 3 of 8 permission checks still returned another person's full record. All three leaks came from below the policy: an owner-login exemption, a view running as its definer, and a session variable surviving in a pooled connection.
- · 11 min read
Your AI Vendor's Terms May Ban Your Users: Read the Population Restrictions Before You Pick a Model
Major generative AI providers' terms bar applications that are directed at, or likely to be used by, people under eighteen. The moment a product defines a Student or a Child role, an entire class of model provider is ruled out. Because this is almost always discovered after the architecture is drawn, it arrives as a rebuild rather than as a constraint. Here is how to read provider terms for user-population restrictions, what to do with a mixed user base, and why the clause has to be re-verified at build time.