Zones were MSFT's vision from the early 2000's in which your internet access will be divided between internal corporate resources, trusted parties preferably trough some sort of AD federation (anyone remembers when MSFT tried to make global AD federation over the internet with Andromeda or w/e it was called?) and the internet. Each zone would have a different security setup which will restrict what kind of information you can pass to a site (e.g. your NTLM/Kerberos credentials) and what kind of actions the site can perform on your browsers. It wasn't a bad idea, the market just never went there and even corporate resources today are accessed via the global internet and not in the intranet or some sort of a federated network.
MSFT has always had some weird things, some were way a head of it's time and like many things which are a head of their time when they miss they miss by a mile. Heck every Windows machine connected to the internet still has (or can have i think in Windows 8 it's not enabled by default any more but i could be wrong) a globally translated name trough PNRP akin to DNS, I've actually used it during the early Vista days for remote access when DyDNS services were still in their infancy and not many trustworthy services were out there. PNRP was also quite a neat idea (especially once they've dropped the IPv6 requirement from it) in which all Windows machines publish their own unique name via DHT's these names can be signed and the address is then quite hard to spoof (ala ToR hidden services), but i doubt that even 5% of Windows power users know about it, and probably less than 5% of those who do use it.
Microsoft Marvel, the Cairo directory service - see Bill Gates (former internal) 1994 memo: "Windows: The Next Killer Application on the Internet": http://www.microsoft.com/about/companyinformation/timeline/t...
"The existing Domain Name System is becomes quickly eclipsed by the Cairo directory service; providing universal resource location services without the need for specialized, arcane applications like archie. Users of the SMTP mail infrastructure take advantage of the advanced features of EMS while remaining backward compatible with their current Internet messaging solutions. Distributed information on the Internet is indexed by Cario and browsed using the Explorer across thousands of information servers worldwide without the need of tools like WAIS and Mosaic. Windows becomes the global infostructure explorer.
The hottest content server on the Internet? Microsoft Marvel. Itβs already integrated with all of these services and has a huge content base and commercial vendor support. Perhaps most importantly, Marvel solves the difficult electronic commerce problem well ahead of the Internet: the ability to securely purchase goods in a networked environment. Cairo becomes the clear platform choice for new information providers, offering the most flexibility in both management and technology. OLE Windows applications are now Internet-enabled - people schedule meetings across the Internet and share ideas using Microsoft application products on Windows. No more specialized tools, no more need for Unix to carry the infostructure. Access to the Internet is a natural extension of the base Windows system as well as Microsoft applications."
I'm guessing, like SELinux, what users end up doing is just disabling things completely (or enabling all options) instead of figuring out all the specifics. I understand, no one wants to be responsible for shipping a vulnerability by default, like MS products used to be.
Also see their terrible HTTP.SYS reservation system. Any program can listen on a socket. But if you want to use that socket for HTTP and use the OS-provided functions? Boom, special ACLs apply; enjoy figuring out a special one off utility. Or just run your service as a local admin.
Sockets require very little permissions to bind because binding a socket cannot have adverse affects on the entire system, if it's in use by another app it wont allow you to do it.
That "zone" crap is something I never understood anyway. It's a real PITA to setup a Windows Server (tried 2008 and 2008 R2, and I believe its predecessors also had it), because you have to click a dozen different buttons, checkboxes and sliders just to visit a website - and to download stuff like a driver or, heaven forbid, another browser, even more clicks.
Also, these days I don't believe that the whitelisting approach works anymore either, because every website on the web loads content (ohai Jquery and friends) from others... hope it's gone for good in the "new IE".