Reply to thread

Message

<blockquote data-quote="bazang" data-source="post: 1119254" data-attributes="member: 114717">Microsoft treats everything as modular. It packages those modules together and then ships them on Windows.Windows has always been modular. Each module is independent of each other (and is intended by design to be disabled or removed if not needed).However, Microsoft has a long-standing history of not integrating modules very well and that includes management of the development of those modules. The development teams are very siloed.WDAC was launched. Then its development stalled for years. Then someone at Microsoft decided to start development again, and then integrate Smart App Control.Microsoft Security really wants to put default deny onto Windows for Home, but Microsoft will not because of all the &quot;users that want to use stuff&quot; who will complain.You and I can come up with a long list of Microsoft security items that were started, but never finished. Or they started but are now stalled at a half-baked stage.Backwards compatibility is a thing because of enterprises and government organizations.Who needs PowerShell v2.0 enabled by default? Enterprises and the US Government. That&#039;s who. So PoSh v2 - that utterly insecure garbage - gets foisted upon everyone else because Microsoft releases a generic version of its OS to everyone.</blockquote>

[QUOTE="bazang, post: 1119254, member: 114717"] Microsoft treats everything as modular. It packages those modules together and then ships them on Windows. Windows has always been modular. Each module is independent of each other (and is intended by design to be disabled or removed if not needed). However, Microsoft has a long-standing history of not integrating modules very well and that includes management of the development of those modules. The development teams are very siloed. WDAC was launched. Then its development stalled for years. Then someone at Microsoft decided to start development again, and then integrate Smart App Control. Microsoft Security really wants to put default deny onto Windows for Home, but Microsoft will not because of all the "users that want to use stuff" who will complain. You and I can come up with a long list of Microsoft security items that were started, but never finished. Or they started but are now stalled at a half-baked stage. Backwards compatibility is a thing because of enterprises and government organizations. Who needs PowerShell v2.0 enabled by default? Enterprises and the US Government. That's who. So PoSh v2 - that utterly insecure garbage - gets foisted upon everyone else because Microsoft releases a generic version of its OS to everyone. [/QUOTE]

Verification