That was kinda my point. Securing a laptop that will have access to data you want to protect from loss is a near bottomless pit of issues. There comes a point you have to do a risk assessment and apply a level of security that meets your legal requirements and contractual obligations. I’m sure this is all doable on Linux as well but the low cost / easily available tools are mostly for Windows.
I suspect that taking the “secured remote session” approach is probably good enough for their needs. It just needs a client app you can trust to respect the security rules they want to enforce (no screen shots, no screen recording, no data transfers for any sort, etc).
OCRing what is on screen is not really stoppable unless you force them to keep their camera on so you can monitor them 24/7. But if you try hard enough there is usually a way around most security measures.
Either way, they need to decide what the risk impact vs likelihood profile is, and what the business can tolerate. They’ll need to discuss it with legal and data protection folks to assess that.
One tip is to embed records and values that look meaningful, but are unique, into the copy of the data given to the specific employee. This can be used to potentially prove that a data breach was a result of something that employee did. We like to put QUID’s as invisible watermarks in document headers. These trigger our DLP systems which is always funny cos its usually an employee who is leaving and wants to keep something. I love those conversions.
I dual boot windows and EndeavourOS. Every 6 to 12 months I make a concerted effort to make the switch 100% but it hasn’t worked out yet. So while Linux is great windows is unavoidable. In this use case I suspect managing Windows tools will be simpler, though I agree that effectiveness next to Linux options won’t be equal.