News for hackers. Stuff that matters.
Re:Copilot broke audit logs, but Microsoft won't tell customers by RachelF on Wednesday August 20, 2025 @12:14AM (#44958577)
Lots of things aren't clear.

Copilot is accessing the indexed contents of the file, not the file itself, when you tell it not to access the file.

The blog writer/marketer needs to look at the index access logs.

Re:Copilot broke audit logs, but Microsoft won't tell customers by internetter on Wednesday August 20, 2025 @12:20AM (#44958596)
> The blog writer/marketer needs to look at the index access logs.

How can you say this if microsoft is issuing a fix?

Re:Copilot broke audit logs, but Microsoft won't tell customers by pnt12 on Wednesday August 20, 2025 @03:55AM (#44959712)
But those are technicalities.

I imagine the intended feature is learning about who read some information, and who modified it.

The implementation varies, but on a CRUD app it seems easy: an authenticated GET or PUT request against a file path - easy audit log.

If you are copying information to another place, and make it accessible there in a lossy way that is hard to audit... you broke your auditing system.

Maybe it's useful, maybe it's a trade-off, but is something that should be disclosed.

Re:Copilot broke audit logs, but Microsoft won't tell customers by mr_toad on Wednesday August 20, 2025 @06:36AM (#44960607)
Not all vector databases are lossy. And even if a lossy index is used it’s totally possible to identify the original source of the information.