In that model, a single compromised workstation would only expose a few modules to malicious changes and only a few projects to code theft.
In the more-common wide-open implementation, a single compromised workstation exposes the entirety of code for every project to theft and malicious changes.
When you're talking about an under-the-radar hack that took place over months, hackers intentionally slipping vulnerabilities into the code is a very real risk.
A desktop developer wants their machine to run as quickly as possible to allow them to compile and run quickly. This may tempt them to turn off virus checking.
A challenge in security is making work without being too onerous. If security measures become a hassle for users, they'll find a way around them.
---
Forgive me but isn't this the function of a SCM? What other models are there?