[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/tech/ - Technical SEO

Site architecture, schema markup & core web vitals
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1790473952614.jpg (204.05 KB, 1024x1024, img_1790473943252_v40ufkro.jpg)ImgOps Exif Google Yandex

4ba3e No.2244

The idea that we can just rely on data classification and prompt hygiene to stop sensitive info from leaking through an API is pretty optimistic.
>Every prompt is an egress point.
It's easy to say we need access controls, but how do you actually audit free-text prompts for leaks in real time? I'm not seeing any actual proof that these architecture patterns work once you scale up RAG or agentic workflows beyond a small test group. There are way too many uncontrolled variables here to think a layered defense is enough without seeing some long-term testing data.

https://dzone.com/articles/enterprise-ai-data-security

4ba3e No.2274

>>2244
>Every prompt is an egress point.

i've been running presidio on our middleware to catch pii before it even hits the llm, which helps with the audit trail. works fine for structured stuff like ssn or emails but falls apart if someone starts leaking proprietary logic in natural language. still basically just a glorified regex filter



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]