We have cases were purview were missing logs. Fun stuff when we tried to figure out a postmortem at my work. Microsoft tools can't be trust anymore, something really broke since COVID...
Copilot broke audit logs, but Microsoft won't tell customers
141–150 of 324 posts
Re: Copilot broke audit logs, but Microsoft won't tell customers
#142> CVEs are given to fixes deployed in security releases when customers need to take action to stay protected. In this case, the mitigation will be automatically pushed to Copilot, where users do not need to manually update the product and a CVE will not be assigned. Is this a feature of CVE or of Microsoft's way of using CVE? It would seem this vulnerability would still benefit from having a common ID to be refrenced…
CVE track security incidents/vulnerabilities
just because you can emergency patch it out of band does not make it not an incident
but it falls under a trend of Microsoft acting increasingly negligent/non trusteable when it comes to security, especially when it comes to clear reporting about incidents.
Which when it comes to a provider of fundamental components like an OS or Claude is as important as getting security right.
Re: Copilot broke audit logs, but Microsoft won't tell customers
#143In 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.
They somehow don't understand how they are breaking their own business models. We can only assume its a quick spin up cash grab before they jack up prices to unbelievable corp only levels
Re: Copilot broke audit logs, but Microsoft won't tell customers
#144Earlier quoted context omitted.
As someone else mentioned the file isnt actually accessed by copilot, rather copilot is reading the pre-indexed contents of the file in a search engine... Really Microsoft should be auditing the search that copilot executes, its actually a bit misleading to be auditing the file as accessed when copilot has only read the indexed content of the file, I don't say I've visited a website when I've found a result of it in…
That makes sense on a technical level, but from a security and compliance perspective, it still doesn't really hold up
Re: Copilot broke audit logs, but Microsoft won't tell customers
#145Earlier quoted context omitted.
I asked ChatGPT the same thing and got > The system being referred to in that explanation is Microsoft 365 (M365) / Office 365 audit logging, specifically the Unified Audit Log in the Microsoft Purview Compliance Portal.
Have you confirmed that this is true?
It seems like this[1] documentation matches the stuff in TFA
Re: Copilot broke audit logs, but Microsoft won't tell customers
#146This is exactly the kind of issue that makes trust in large vendors like Microsoft feel more like a gamble than a guarantee
Re: Copilot broke audit logs, but Microsoft won't tell customers
#147Earlier quoted context omitted.
So... basically like when Delve was first introduced and was improperly security trimming things it was suggesting and search results. ... Or ... a very long-time ago, when SharePoint search would display results and synopsis's for search terms where a user couldn't open the document, but could see that it existed and could get a matching paragraph or two... Best example I would tell people of the problem was users s…
I would say "insecure by default". I talked to some Microsoft folks around the Windows Server 2025 launch, where they claimed they would be breaking more compatibility in the name of their Secure Future Initiative. But Server 2025 will load malicious ads on the Edge start screen[1] if you need to access a web interface of an internal thing from your domain controller, and they gleefully announced including winget, a…
100% agreed on the Edge-front page showing up on server machines being nasty though, server deployments should always have an empty page as the default for browsers (Always a heart-burn when you're trying to debug issues some newly installed webapp and that awful "news" frontpage pops up).
Re: Copilot broke audit logs, but Microsoft won't tell customers
#148Earlier quoted context omitted.
I would say "insecure by default". I talked to some Microsoft folks around the Windows Server 2025 launch, where they claimed they would be breaking more compatibility in the name of their Secure Future Initiative. But Server 2025 will load malicious ads on the Edge start screen[1] if you need to access a web interface of an internal thing from your domain controller, and they gleefully announced including winget, a…
Servers don't have Desktop GUI, so there is no way you can run a browser on a real server installation. That's done specifically to limit the attack surface. This applies to almost all Windows Server roles except very few such as ADFS which Microsoft is struggling to migrate for decades. Definitely to the root of all security - AD DC. If you've elected to create a Frankenstein of a domain controller and a desktop/gam…
Re: Copilot broke audit logs, but Microsoft won't tell customers
#149Re: Copilot broke audit logs, but Microsoft won't tell customers
#150A better title would be: Microsoft Copilot isn't HIPAA compliant A title like this will get it fixed faster.