Live data from Hacker News

Copilot broke audit logs, but Microsoft won't tell customers

pistachioapp.com

51–60 of 324 posts

Re: Copilot broke audit logs, but Microsoft won't tell customers

#51

In my opinion, using AI tools for programming at the moment, unless in a sandboxed environment and on a toy project, is just ludicrous. The amount of shady things going on in this domain (AI trained on stolen content, no proper attribution, not proper way to audit what's going out to third party servers etc.) should be a huge red flag for any professional developer.

The icing on the shit cake is a text editor programmed in typeScript with an impossible to secure plugin architecture.

Re: Copilot broke audit logs, but Microsoft won't tell customers

#52

Earlier quoted context omitted.

This is it. M365 uses RAG on your enterprise data that you allow it to access. It's not actually accessing the files directly in the cases he provided. It's working as intended.

If that's the case, then as noted in the article, the 'as intended' is probably violating liability requirements around various things.

Correct. It is precisely that a user can ask about someone’s medical history (or whatever else) and not be reported that would be in violation of any heavily audited system. LLM Summaries break the compliance.

Re: Copilot broke audit logs, but Microsoft won't tell customers

#53
post #8

Wait, copilot operates as some privileged user (that can bypass audit?), not as you (or better, you with some restrictions) That can’t be right, can it?

I can only assume that Microsoft/OpenAI have some sort of backdoor privileges that allows them to view our messages, or at least analyze and process them.

I wouldn't be surprised.

Re: Copilot broke audit logs, but Microsoft won't tell customers

#54
post #5

Generally speaking, anyone can file a CVE. Go file one yourself and force their response. This blogpost puts forth reasonably compelling evidence.

Fun, but it doesn’t deserve a CVE. CVEs are for vulnerabilities that are common across multiple products from multiple sources. Think of a vulnerability in a shared library that is used in most Linux distributions, or is statically linked into multiple programs. Copilot doesn’t meet that criteria. Honestly, the worst thing about this story is that apparently the Copilot LLM is given the instructions to create audit l…

More accurately, CVEs are for vulnerabilities that may be present on many systems. Then, the CVE number is a reference point that helps you when discussing the vulnerability, like asking whether it's present on a particular system, or what percentage of systems are patched. This vulnerability was only present on one system, so it doesn't need a CVE number. It could have a Microsoft-assigned bug number, but it doesn't need a CVE.

Re: Copilot broke audit logs, but Microsoft won't tell customers

#55

Generally speaking, anyone can file a CVE. Go file one yourself and force their response. This blogpost puts forth reasonably compelling evidence.

Is there value in requesting a CVE for a service that only Microsoft runs? What's a user supposed to do with that?

Re: Copilot broke audit logs, but Microsoft won't tell customers

#56

In my opinion, using AI tools for programming at the moment, unless in a sandboxed environment and on a toy project, is just ludicrous. The amount of shady things going on in this domain (AI trained on stolen content, no proper attribution, not proper way to audit what's going out to third party servers etc.) should be a huge red flag for any professional developer.

Companies won't use open source software because of licencing concerns but if you launder it through an LLM it's hunky-dory.

Re: Copilot broke audit logs, but Microsoft won't tell customers

#57
post #40

Earlier quoted context omitted.

No, it accesses data with the users privilege.

Are you telling me I, a normal unprivileged user, have a way to read files on windows that bypasses audit logs?

If there is a product defect? Sure.

The dude found the bug, reported the bug, they fixed the bug.

This isn’t uncommon, there bugs like this frequently in complex software.

Re: Copilot broke audit logs, but Microsoft won't tell customers

#58
post #13

are they even sure that the AI even accessed the content that second time? LLMs are really good and making up shit. I have tested this by asking various LLMs to scrape data from my websites while watching access logs. Many times, they don't and just rely on some sort of existing data or spout a bunch of BS. Gemini is especially bad like this. I have not used copilot myself, but my experience with other AI makes me cu…

This is it. M365 uses RAG on your enterprise data that you allow it to access. It's not actually accessing the files directly in the cases he provided. It's working as intended.

If this is indeed how copilot is archtected, then it needs clear documentation -- that it is a non-audited data store.

But how then did MS "fix" this bug? Did they stop pre-ingesting, indexing, and caching the content? I doubt that.

Pushing (defaulting) organizations to feed all their data to Copilot and then not providing an audit trail of data access on that replica data store -- feels like a fundamental gap that should be caught by a security 101 checklist.

Re: Copilot broke audit logs, but Microsoft won't tell customers

#59
post #9

I am so tired of Microsoft cramming Copilot into everything. Search at $dayjob is completely borked right now. It shows a page of results, but the immediately pops up some warning dialog you cannot dismiss that Copilot can’t access some file “” or something. Every VSCode update I feel like I have to turn off Copilot in some new way. And now apparently it’ll be added to Excel as well. Thankfully I don’t have to use an…

The coercion will continue until metrics improve.

Re: Copilot broke audit logs, but Microsoft won't tell customers

#60
post #40

Earlier quoted context omitted.

Are you telling me I, a normal unprivileged user, have a way to read files on windows that bypasses audit logs?

If there is a product defect? Sure. The dude found the bug, reported the bug, they fixed the bug. This isn’t uncommon, there bugs like this frequently in complex software.

I think you just defined away the entire category of vulnerability known as "privilege escalation".
Post reply on HN