Slashdot Mirror


White House Specifies And Mandates Secure Windows

twitter writes "The Register is reporting on an effort to bring order to the wild world of Windows patching, at least in the US Federal Government. The White House has issued a directive to federal CIOs throughout the country, issuing a call for all new PCs to use a 'common secure configuration.' 'Registry settings and which services would be turned on or off by default [are specified and] the directive calls for suppliers (integrators and software vendors) to certify that the products they supply operate effectively using these more secure configurations. "No Vista application will be able to be sold to federal agencies if the application does not run on the secure version of Vista," explained Alan Paller, director of research at The SANS Institute.'"

242 comments

  1. Heh by Ethelred+Unraed · · Score: 4, Insightful

    The phrase "don't put all your eggs into one basket" comes to mind...

    Cheers,

    Ethelred

    --
    Everyone wants to be Ethelred. Even I want to be Ethelred.
    1. Re:Heh by jimstapleton · · Score: 3, Insightful

      I would have added "All applications must run in Wine under BSD or Linux", or have a version in BSD or Linux, to the requirements to prevent lock-in

      --
      34486853790
      Connection too slow for X forwarding? Try "ssh -CX user@host"
    2. Re:Heh by Anonymous Coward · · Score: 4, Insightful

      To be fair they are mandating specific Windows configurations for systems running Windows. They are not mandating the use of Windows (or course a lot of gov system do for other reasons...).

    3. Re:Heh by jac89 · · Score: 4, Funny

      Get bigger eggs, then they wont be able to fit through the holes. Goose eggs would do, or maybe ostrich.

    4. Re:Heh by SgtChaireBourne · · Score: 1

      I would have added "All applications must run in Wine under BSD or Linux", or have a version in BSD or Linux, to the requirements to prevent lock-in

      But that defeats the purpose of mandating that no MS Vista application can be sold to federal agencies if the application does not run on the "secure" {sic} version of MS Vista. "Secure" there is probably just an euphamism for DRM'd out the wazzoo. Having the order read that the apps must be available on more secure platforms / other platforms means that the vendor lock is gone.

      You don't think this is actually about preserving the privacy, availability and integrity of government data, do you?

      --
      Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
    5. Re:Heh by FrankNputer · · Score: 4, Funny

      Show me a basket that doesn't have holes, and I'll show you a bowl.

    6. Re:Heh by morcego · · Score: 4, Funny

      Show me a bowl that doesn't have a hole, and I'll show you a sphere.

      --
      morcego
    7. Re:Heh by mysticgoat · · Score: 1

      So extending Wine such that it meets the same specifications assures that any software that can be sold to the Feds will also run under Linux.

      I think I like this idea.

    8. Re:Heh by beckerist · · Score: 2, Informative

      Show me a bowl that doesn't have a hole and I'll show you a bowl. Show me a bowl WITH a hole and I'll show you a doughnut.

    9. Re:Heh by Creepy+Crawler · · Score: 1

      Is it a European or African ostrich?

      --
    10. Re:Heh by Anonymous Coward · · Score: 0

      Show me a sphere with three holes in it and i'll show you a bowling ball.

    11. Re:Heh by kahrytan · · Score: 1


        Wine makes Linux less secure. Wine will run windows viruses and connect to the internet. Check this post out at ubuntu forums.

      --
      \
    12. Re:Heh by Anonymous Coward · · Score: 0

      Show me your holes and I'll pay you a dollar.

    13. Re:Heh by 3vi1 · · Score: 1

      I'm not sure, but I'm pretty sure it's unladen, as opposed to bin-laden.

    14. Re:Heh by 3vi1 · · Score: 1

      When you run Wine under Linux, you're running as a user - not a machine admin.

      OMG NoeZ! I purposely installed a virus, so now I gotta delete my .wine directory and re-run winecfg!

      -J

    15. Re:Heh by RincewindTVD · · Score: 1

      Show me yours and I'll show you mine.

    16. Re:Heh by X0563511 · · Score: 1

      Note that winecfg usually puts '/' as a driveletter for wine... so theoretically a virus from wine can propagate through your filesystem. Or at least the parts you have access to... which is still a pain in the ass.

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    17. Re:Heh by Anonymous Coward · · Score: 0

      A flute with no holes is not a flute. And, a doughnut with no hole is a Danish.

    18. Re:Heh by nadaou · · Score: 1

      Show me a sphere with a bit of a bulge, and I'll show you an egg which has already left the basket.

      --
      ~.~
      I'm a peripheral visionary.
    19. Re:Heh by renegadesx · · Score: 1

      Hahaha, secure windows, hahahah!

      --
      Make SELinux enforcing again!
  2. Comment removed by account_deleted · · Score: 4, Interesting

    Comment removed based on user account deletion

  3. Security by Mateo_LeFou · · Score: 5, Funny

    Well, if there's one White House that I think might be experts on Security, it's this one

    --
    My turnips listen for the soft cry of your love
    1. Re:Security by eln · · Score: 4, Insightful

      Actually, this White House seems to champion the idea of "security through obscurity," which puts them right in line with Microsoft's idea of security. This should work out well.

    2. Re:Security by k1e0x · · Score: 1

      Yeah... Cept with government they have guns.

      DHS Bureaucrat: "In the interest of national security (and the children) We here by declare that it's now a federal crime for anyone to connect to an administrative c$ share!"

      --
      Bringing liberty to the masses. - http://freetalklive.com/
  4. If I Have Learned One Thing... by Anonymous Coward · · Score: 5, Insightful

    If I have learned one thing when dealing with the federal government, it is where there is a regulation there is always a way to get an exception to that regulation.

  5. Yikes! by martyb · · Score: 3, Insightful

    One word: Monoculture.

    Yes, this might be a darn sight better than what currently exists, but having all the systems have the same configuration is just ASKING for trouble. I predict that within two years, some virus or the like which would have attacked just a department or two is going to hit a huge swath across multiple departments, instead.

    Unless, of course, the federal government has figured out how to configure their systems to be entirely secure. In which cse, I'd suggest they share it with Microsoft and the rest of the systems on the internet.

    1. Re:Yikes! by Mateo_LeFou · · Score: 1

      Are you suggesting that Bruce Schneier knows more about security than W and friends?

      I'm looking forward to color-coded "Vista Alert Level" updates and thousands of other goodies.

      --
      My turnips listen for the soft cry of your love
    2. Re:Yikes! by Trona+Andy · · Score: 4, Funny

      You have it all wrong. This is going to work because the Decider has said it has to work. Case closed, just like the wonderful success we're having making Baghdad a bastion of stability and tolerance for political, religious and cultural difference. You go, George!

    3. Re:Yikes! by gEvil+(beta) · · Score: 1

      I'm looking forward to color-coded "Vista Alert Level" updates

      Why do I suspect that the highest level will be blue?

      --
      This guy's the limit!
    4. Re:Yikes! by RingDev · · Score: 1

      I wouldn't go so far as to say Monoculture... All jokes aside, there are a lot of highly skilled IT professionals in the government sector, there just also happens to be a large number of incompetent ones as well. The competent ones will continue to run tight ships with secure and functional networks, and the incompetent will continue to run crap piles, although with this regulation they would at least be given "less smelly" crap to add to their respective piles.

      -Rick

      --
      "Most people in the U.S. wouldn't know they live in a tyrannical state if it walked up and grabbed their junk." - MyFirs
    5. Re:Yikes! by afidel · · Score: 3, Insightful

      Since the current monoculture for Windows PC's in government is probably the default windows install, a more secure default configuration can't possibly be a worse situation.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    6. Re:Yikes! by jafac · · Score: 1

      It's true that you can complain about Monoculture;
      But if you have 100 different computers, and they're all configured differently, what you have is an UNKNOWN configuration - and you can't tell your boss "every known vulnerability has been shut down".

      If you shut down all known vulnerabilities on those 100 computers, you don't have 100 secure computers. You have 100 computers, with zero known vulnerabilities, and some unspecified number of unknown vulnerabilities. Those unknowns are there, whether you've controlled the configuration and accomplished a monoculture, or not.

      The weaknesses of monoculture become apparent when a new vulnerability is discovered, and the mechanism that enforces the monoculture gets in the way of patching the vulnerability quickly, and repeatably, on all 100 machines. (The "mechanism" being this common configuration spec, and the rules that enforce it - and the government rules dictating when and whether someone can be paid to actually do the work). In theory, if you have a mechanism that allows necessary changes in a timely and consistent manner, and doesn't permit unnecessary changes - that's the best design of all possible designs).

      Now - there's a CHANCE, that if you pay the costs of say; having 50 of those boxes Windows, and 50 of those boxes Linux - that any unknown vulnerabilities will only impact half of your network. But what if one of those 50 is a critical component, like, maybe you chose Linux for your web server, and Windows for your desktops, and what if, the unknown vulnerability leads to a loss of your Linux webserver? Guess what? Your entire system STILL goes down.

      I'm not advocating picking one platform for the benefit of saving costs (on training, development expertise, supply-chain management). But advocating mixing platforms solely to avoid monoculture is similarly stupid. Of course, you want interoperability, and you want the platform that performs a given function best. That's where you want to base your Linux or Windows decision.

      The big problem I see with this "mandated configuration" approach, is the insistence on a common desktop configuration, and its enforcement through Active Directory. This forces an integrator to turn on services and open ports on a desktop that would not ordinarily need to be opened - purely to amuse Microsoft's centralized management scheme. Additional services like Distributed Transaction Coordinator, Remote Registry Service, Server Service (which exposes the IPC$ share - you can't shut this off anymore), Microsoft Installer, Task Scheduler (which has a long and sordid history of unpatched vulnerabilities), Automatic Updates, Background Intelligent Transfer Service, Computer Browser service, DCOM Server Process Launcher, Error Reporting Service - etc. the list goes on and on. You can shut off most of this crap on a Workgroup machine. A Domain member needs to have a lot of these turned on - and that exposes a lot more surface area to attack. The expertise to determine which services support which functionality; what you can turn off and still get done - is not cheap or easy. Most of these services, you can't google on and get a meaningful answer, nor is Microsoft's documentation always clear.

      What would BE nice, is more choice; on the Windows Side, of LDAP solutions that can provide the kinds of services and features that Windows Administrators have come to expect from Active Directory. And ways to take advantage of those services and features without opening you entire network to more risk. IMO - this battle was lost when Novell's NDS was essentially crushed by Microsoft in 1999-2002. And this facet was completely ignored by the MS v DoJ trial.

      --

      These are my friends, See how they glisten. See this one shine, how he smiles in the light.
    7. Re:Yikes! by Zonk+(troll) · · Score: 1

      If at first you don't succeed at breaking a cipher, you're not Bruce Schneier.

      Bruce Schneier can decypher line-noise.

      Anybody can invent a cryptosystem he cannot break himself. Except Bruce Schneier.

      When God needs a new secure certificate, he uses Bruce Schneier as the signing authority.

      (Bruce Schneier Facts).

      --
      "The Federal Reserve is a fraudulent system."--Lew Rockwell
      End The FED. -
    8. Re:Yikes! by Schraegstrichpunkt · · Score: 1

      [sarcasm]Riiight. So what would obviously be even more secure would be to have everyone write their own operating system.[/sarcasm]

      It's a trade-off. By having people with above-average competence design the system, you increase the probability that the system will withstand being attacked. On the other hand, by standardizing your operating environment, you increase the likely severity of any successful attack.

      If "monocultures" were invariably bad, then we wouldn't have had the AES competition. People would just design their own encryption primitives.

    9. Re:Yikes! by Allador · · Score: 1

      I havent seen the fed.gov specifics yet ... but I'd bet its basically the same thing that nsa suggests for configuring your boxes.

      Things like:

      - minimum password lengths
      - minimum password complexity
      - password rotation
      - password strength auditing
      - running all users as non-admin
      - do not store lm hash
      - sign & encrypt all cifs & ldap communications
      - do not allow anonymous access to anything (shares, sam, etc)
      - X services set to disabled
      - host-based firewall running
      - anti-virus running
      - run services as network service or other non-prived accounts
      - etc.

      So how does having all the computers configured thusly make them all more vulnerable, just because they're the same?

      In every case this makes the system more secure. About the only possible monoculture issue that could come up is the a/v and firewall. If they're all by the same company and they all suffer from a vulnerability then there's a weakness. But this is probably already the case anyway, as the big fed departments all will sign big contracts with an a/v vendor for cheaper prices.

    10. Re:Yikes! by Allador · · Score: 1

      The big problem I see with this "mandated configuration" approach, is the insistence on a common desktop configuration, and its enforcement through Active Directory. This forces an integrator to turn on services and open ports on a desktop that would not ordinarily need to be opened - purely to amuse Microsoft's centralized management scheme. Neither of us have seen the new fed.gov security, but I think you're misunderstanding the situation. It's not a matter of workgroup vs. domain, but of 'poorly-locked-down-domain-workstation' and 'highly-locked-down-domain-workstation'.


      No department could or would want to run as a workgroup ... you lose all the bennies of running the microsoft stack that way.

      Additional services like Distributed Transaction Coordinator, Remote Registry Service, Server Service (which exposes the IPC$ share - you can't shut this off anymore), Microsoft Installer, Task Scheduler (which has a long and sordid history of unpatched vulnerabilities), Automatic Updates, Background Intelligent Transfer Service, Computer Browser service, DCOM Server Process Launcher, Error Reporting Service - etc. the list goes on and on. You can shut off most of this crap on a Workgroup machine. A Domain member needs to have a lot of these turned on - and that exposes a lot more surface area to attack. The expertise to determine which services support which functionality; what you can turn off and still get done - is not cheap or easy. Most of these services, you can't google on and get a meaningful answer, nor is Microsoft's documentation always clear. It's not that hard, and would take a competent sysadmin about a day to figure it all out.


      And thats half the point of a common security config, you've reduced the surface area to a minimum amount.

  6. That's strange.. by Anonymous Coward · · Score: 0
    1. Re:That's strange.. by morgan_greywolf · · Score: 1

      Because, if you read the article you linked to, you'd know that Windows has had more severe vulnerabilities than both OS X and Red Hat, really making Windows the least secure.

    2. Re:That's strange.. by Anonymous Coward · · Score: 0

      Your sarcasm detection abilities are top-notch.

    3. Re:That's strange.. by mabhatter654 · · Score: 1

      I'd bet the Feds over all, through all the departments spend HUNDREDS of millions of dollars on Windows desktops per year!! If the feds would even offer Apple or Red Hat 1/10 of that business they'd comply automatically without being asked.

  7. From TFA... by Steve--Balllmer · · Score: 5, Funny

    ""No Vista application will be able to be sold to federal agencies if the application does not run on the secure version of Vista,"

    I just wanted to let you know all of those people who purchased "Unsecured Version" of Vista can upgrade to the "Secure Version" for a fee, when it is released (probably in late 2009-early 2010).

    Sincerely,
    Steve "Monkeyman" Ballmer

    1. Re:From TFA... by wizzahd · · Score: 2, Insightful

      I was unaware that there is a "secure" version.

    2. Re:From TFA... by alexandreracine · · Score: 1

      You misspell "for free"...

      --
      No sig for now.
    3. Re:From TFA... by mgblst · · Score: 1

      Wow, that is going to piss of about a dozen people, way to go Steve.

  8. So long Apple by Anonymous Coward · · Score: 1, Insightful

    Good to know the Feds are doing this for PCs.

    Say good bye to Apple in the Federal workspace, Vista is getting the 'required' stamp.

    1. Re:So long Apple by geoffrobinson · · Score: 1

      When was the last time someone saw an Apple in a federal work area? I'm not being snarky. Seriously, when?

      --
      Except for ending slavery, the Nazis, communism, & securing American independence, war has never solved anything.
    2. Re:So long Apple by Anonymous Coward · · Score: 0

      This is simply not true. The NSA, NIST and DISA (DoD) all create guides for the operating systems, network devices and applications that are commonly used within their agencies. The Mac OS X Server Security Configuration Guide
      and Mac OS X Security Configuration Guide posted on the Apple documentation website was developed in cooperation with the NSA too.

      http://www.apple.com/server/documentation/

      NIST and DISA publicly distribute their security guidance.

      http://checklists.nist.gov/
      http://iase.disa.mil/stigs/stig/

    3. Re:So long Apple by SpaceLifeForm · · Score: 1

      Just the other night, on '24'.

      --
      You are being MICROattacked, from various angles, in a SOFT manner.
    4. Re:So long Apple by Anonymous Coward · · Score: 0

      Actually, we have several hundred deployed across our command (G6...army IT), including 120 brand new Intel 24" iMacs we're spending our days disabling the cameras and wireless cards (for secure area usage). The army uses a lot of Mac servers, most notably for the main army home page and associated sites. Lt. Gen. Boutelle, CIO of the Army, carries a 15" PowerBook, as do a number of his top staff. Macs also feature prominently in our national defense labs, as well as within the Smithsonian institute. Don't count Apple out of Federal IT!

    5. Re:So long Apple by Anonymous Coward · · Score: 0

      You won't, because Apple puts webcams into all of their machines immediately invalidating their use in government offices. Everytime I see that ridiculous Apple commercial I just snicker about how many government and corporate accounts they've just locked themselves out of.

  9. Quoting myself by starglider29a · · Score: 4, Insightful

    http://slashdot.org/comments.pl?sid=152118&cid=127 64232

    Has anyone considered if [Apple adopting Intel] is *** INTEL's *** way of diversifying, as an "off world colony of Planet Wintel"? In other words, is this a backup location in the seemingly increasingly likely implosion of the 'Win Wing" of WinTel? Nothing is "unthinkable", merely improbable.

    Blustery pundits have used the phrase "national security risk" when referring to Windows. What if it were outlawed in government facilities? I have worked with LARGE corporations that 'forbade' IE on the computers. What if something unthinkable, as unthinkable as an asteroid strike is on Planet Earth, happened to Windows?

    ---
    Don't put all yer x86's in one basket
    ------
    And myself in 1998

    The day will come when WinPlanet implodes. It happened to IBM. Hell, it happened to Apple. On that day, you will ask the reflection in your blank monitor the question, "Where do you want to go today?" [made with Mac logo]

    1. Re:Quoting myself by Anonymous Coward · · Score: 0

      Has anyone considered if [Apple adopting Intel] is *** INTEL's *** way of diversifying, as an "off world colony of Planet Wintel"?

      "A new life awaits you in the Off-World Colonies. The chance to begin again in a golden land of opportunity and adventure, new climate, recreational facilities ..."

    2. Re:Quoting myself by Magada · · Score: 1

      Thanks for the laugh.

      --
      Something bad is coming when people are suddenly anxious to tell the truth.
    3. Re:Quoting myself by Anonymous Coward · · Score: 0

      > What if something unthinkable, as unthinkable as an asteroid strike is on Planet Earth, happened to Windows?

      Windows would be shattered?

    4. Re:Quoting myself by Anonymous Coward · · Score: 0
      The day will come when WinPlanet implodes. It happened to IBM. Hell, it happened to Apple. On that day, you will ask the reflection in your blank monitor the question, "Where do you want to go today?" [made with Mac logo]


      Linux. No single company to "implode". I'm already there, in fact. [made with Gimp logo]

    5. Re:Quoting myself by Anonymous Coward · · Score: 0

      WinApparently, you were WinJust as WinComprehensible in 1998.

  10. And this is unusual why? by Itninja · · Score: 3, Funny

    No Vista application will be able to be sold to federal agencies
    What!!?? You mean that my local Social Security office will not be upgrading?

    I was there a few weeks ago and they all were using what looked like Windows 98 still. I don't think 'Vista' and 'federal agency' will be in the same sentence again for many, many years.
    --
    I judt got a nre Kinesis keybiartf so please excusr ant egregiou typos.
    1. Re:And this is unusual why? by jfengel · · Score: 2, Interesting

      And ya know, that's not necessarily a bad thing.

      I don't know exactly what goes on in that office, but I suspect it hasn't changed radically in 10 years. They're probably running identical software, perhaps with occasional upgrades. Probably some custom application providing access to their database. Why replace all the hardware just to stay in place?

      Sure, the security of 98 is a nightmare. They definitely need to keep these computers behind a firewall, and in fact preferably with absolutely no access at all. Buy different computers if they need to do email or web surfing; these computers are a complete loss from a security standpoint. But if all they need to do is run some set of applications that haven't changed in years, don't fix what ain't broke.

    2. Re:And this is unusual why? by Anonymous Coward · · Score: 0

      You sure it wasn't Windows 2000?

    3. Re:And this is unusual why? by Itninja · · Score: 1

      "Microsoft. Reinventing the wheel since 1989" That's why!

      --
      I judt got a nre Kinesis keybiartf so please excusr ant egregiou typos.
    4. Re:And this is unusual why? by xealot · · Score: 1

      They're probably running identical software, perhaps with occasional upgrades. Probably some custom application providing access to their database I work for Sacramento county mental health services. Our computers here run Win2k, and the most important software we use is apparently located on a couple IBM mainframes which serve the entire county/state, which we access through telnet. I can't imagine any single area where my productivity would improve by "upgrading" to Vista. However, considering we deal with Private Health Information, which includes SS#, Medi-Cal ID, etc.. I'd feel much more comfortable running linux using ssh. I'm surprised there isn't a huge botnet running out of every county office in the state.. in fact, there probably is for all I know.
      --

      --Drive carefully. 90% of people are caused by accidents.
    5. Re:And this is unusual why? by Lord+Ender · · Score: 1

      How do you propose they get data to and from those applications if you don't want the PCs networked?

      Yeah.. that's what I thought.

      --
      A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
    6. Re:And this is unusual why? by jfengel · · Score: 1

      "Networked to each other" and "networked to the wide world" are two different things. And if they must be networked remotely, and if the Internet is the most effective way to get there, then you can dramatically limit access with a firewall. You're still potentially screwed, since custom applications are terribly prone to buffer overruns, publicly-known passwords, insertion attacks, etc., but that's a programmer problem, not a Windows problem.

    7. Re:And this is unusual why? by Lord+Ender · · Score: 1

      Firewalls are near-worthless when you are talking about PCs. People take laptops home, get malware all over them, then bring them to work and plug them in BEHIND THE FIREWALL or on a private network.

      --
      A slashdotter who didn't build his own computer is like a Jedi who didn't build his own lightsaber.
    8. Re:And this is unusual why? by lee+n.+field · · Score: 1

      You mean that my local Socialist Security office will not be upgrading?


      Local SS offices are running W2K, which is consistent with the age of the hardware (Compaq PIIIs).

    9. Re:And this is unusual why? by icepick72 · · Score: 1

      That doesn't make firewalls near worthless. The firewall wasn't meant to handle the situation you described. Instead of comparing apples and oranges, consider instead that different kinds of security are needed in addition to the firewall. This still doesn't discount the usefulness of the firewall for its purpose. Change your perspective for a moment and consider that when a malware-infested laptop is plugged into the network there are other mechanisms that can be implemented to handle it. Think outside the box.

  11. Secure Vista... by Anonymous Coward · · Score: 5, Insightful

    ...is like Unbreakable Oracle. A nice name for a marketing campaign. Something it would be nice to have. But probably a pipe dream. And it's a naming that's almost DARING people to try to break it. Not the best idea in that regard.

    That said, it must be acknowledged that the federal government is actually showing some real intelligent thinking here for a change, and we should support that. "Just use whatever configuration Microsoft shipped it with" is dangerous thinking. They're looking at what services should be running, how things should be configured, etc., with a mindset of security (and not, mercifully, "ease of use"). This is a Very Good Thing.

    Yeah, we can rail at "defective by design" ideas in Windows all we want, but one of the big security complaints about Microsoft OS'es is that they are NOT "Secure by default." Changing defaults doesn't get you home for security, but let's applaud a positive step, and hope Microsoft takes some note of this.

    1. Re:Secure Vista... by nine-times · · Score: 1

      "Just use whatever configuration Microsoft shipped it with" is dangerous thinking.

      What I find really silly (and annoying) is the amount of customization required to get Microsoft stuff set up properly. It's very deceptive, because you can install everything and get it working very easily with very little customization. However, if you go through and do a lot of research, you'll find that the default settings are often not even recommended by Microsoft. The worst part is that (AFAIK) there isn't a single Microsoft document anywhere that really tells you how you're supposed to set this stuff up.

      What I mean is, even if you just want to follow Microsoft's "best practices" for server/desktop/network/application setup, you should be editing the registry, group policies, and changing several hidden settings all over the place. Worse yet, you might encounter a problem and discover only after the fact that there's a knowledge-base article that recommends that you change a particular registry key or disable a particular service as a "best practice".

      So it's struck me many times, "Why doesn't Microsoft set these things by default?" There may be reasons, but I feel that if you're a developer and you can't roll your software out with the "best practice" settings as the defaults, you're doing something wrong. Additionally, once the "best practice" settings are the default, it'd be nice if you could generate a report detailing where you're deviating from the defaults, when those changes were made, descriptions of the effects of those deviations, and the option to fix those deviations ('restore to default', if desired).

      Some of my big complaints about administering Windows (and other operating systems are also guilty of this, to a lesser degree): there are so many hidden options with no clear "best" and the default is often wrong; many options don't have clear descriptors of their effects; when something suddenly stops working, it's not clear what setting has changed, nor how is there any obvious method to find the control to change it back.

  12. HAHAAH by Anon-Admin · · Score: 0, Flamebait

    HAHAHAHAHAHAHAHAH,,,,HAHAHAHAHAHAHAAHA Secure Windows, HAHAHAHAHAHAHAHAHAHAHAHAHA

    I wonder if the spy ware/Viruses/Trojans will run on it?

    HAHAHAHAHAHAHAHAHAHAHAHAHAHAAHHAAHAHAHAH,,,,,HAHAH AHAHAHA

    Sorry I cant help my self.... The government wants to secure windows.... HAHAHAHAHAHAHAHAHAHAHAHAHAAHA

    The only way I know to truly secure windows is to turn it off and unplug it from the network!

    HAAHAHAHAHAHAHAAH

    1. Re:HAHAAH by AP2k · · Score: 3, Funny
      Where is the "Beyond Overrated" or "Stupid" mod tags when you need them?

      You might need this:

      while(1){
            printf("HA");}
    2. Re:HAHAAH by loafing_oaf · · Score: 1

      Networking in Vista is easier than ever. Now, you'll always have access to the latest and greatest new viruses.

      --
      Always someone has power over you. The thing to consider is this: Is the power good, or bad?
    3. Re:HAHAAH by Anonymous Coward · · Score: 0

      -1, ranting like a 12-year-old.
      +1, probably quite accurate.

  13. Monoculture Worries. by twitter · · Score: 4, Insightful

    The phrase "don't put all your eggs into one basket" comes to mind...

    The net result will be identically configured computers with fewer applications, a bot maker's paradise. The comply/no-comply label give M$ more veto power over applications and that will reduce the number of applications that can be used. Everything must now be done the M$ way on Windoze, so the worst practices with the worst track record have been mandated. The identical settings are only more "secure" until someone breaks them and then they are all equally hosed.

    --

    Friends don't help friends install M$ junk.

    1. Re:Monoculture Worries. by Anonymous Coward · · Score: 1
      I mean, it's your journal and you couldn't even interpret the summary properly.

      The comply/no-comply label give M$ more veto power over applications and that will reduce the number of applications that can be used

      Everything must now be done the M$ way on Windoze It's the government mandating this version of Windows, not Microsoft. Reading comprehension much?
    2. Re:Monoculture Worries. by mabhatter654 · · Score: 2, Insightful
      This is a very good thing!! The feds are simply stating they will be using a particular configuration of windows their experts have determined increases security and removes the gaping holes the default WinTel box at the store ships with. They're mandating that all their vendors get with the program and MAKE their software work with the new increased security settings already built into Windows. It's what Microsoft keeps promising to do when they say "most secure ever" but then the first thing vendors do is require IT to "turn down" security settings because highly paid programmers can't be bothered to make their software work properly under security settings.

      We see this all the time on home PCs where you have to be Admin to run simple games... the feds are saying NO MORE to that. This is a VERY good thing!!

    3. Re:Monoculture Worries. by FlopEJoe · · Score: 4, Funny

      The net result will be identically configured computers with fewer applications

      That's a Mac, right?

    4. Re:Monoculture Worries. by bfields · · Score: 1

      Yeah, I don't run Windows myself, but what I hear from people that do is--sure, it comes with all these security features (like ability to run as a user without root-like privileges), but in practice the software they want doesn't run unless they turn that stuff off.

      So in theory it sounds like a good thing to have a major customer like the federal government telling vendors that they won't put up with that.

      (But then, a windows expert would have to say whether the particular restrictions they're suggesting are actually reasonable ones.)

    5. Re:Monoculture Worries. by Prof+Kayyos · · Score: 1

      A CIO dealing with Uncle Sam would be out of his mind to have any hardware/software configuration that strayed from a strictly Vista ready machine with a "secure" version of Vista for Business running on it. No deviations, no nada. It will break, there will be problems of an order of magnitude never seen before. This is a given. I know I'm repeating what you said but it bears repeating ! This is the dumbest thing I have ever heard of in my life. This is going to give people wet dreams over breaking government systems. It's like I read somewhere last week (Ars Technica?). M$ is more worried about DRM than it is security. I felt that statement was true when I read it and now that I've been running M$ Vista for a couple of weeks I have found that it IS true. My dog can break Vista security. My dog however can not break Vista's DRM security just yet. But she'll find a way.

    6. Re:Monoculture Worries. by drsmithy · · Score: 1

      The net result will be identically configured computers with fewer applications, a bot maker's paradise.

      The net result will be identically configured computers with fewer applications, a system administrator's paradise.

      Fixed that for you.

  14. Will make problems for R&D/scientific applicat by a_timid_mouse · · Score: 1

    There's a lot of talk around NASA how this will cause huge headaches for scientists and R&D folks. There are very determined efforts afoot to homogenize Windows support and configuration at all NASA centers. Will make for a great bot target, and will most likely stifle development of new technologies to support NASA missions and objectives.

  15. Security and Liberty. by twitter · · Score: 3, Insightful

    Well, if there's one White House that I think might be experts on Security, it's this one.

    I'm not very impressed with most of the "security" people have traded their liberty for. The failure is nowhere more apparent than the non free computing world.

    --

    Friends don't help friends install M$ junk.

    1. Re:Security and Liberty. by Macthorpe · · Score: 1

      nowhere more apparent than the non free computing world [slashdot.org]. Read that article again. 1 in 4 computers, not 1 in 4 Windows computers.

      I was so happy you managed to keep your bias out of the summary, but then you had to go and ruin it, didn't you?

      --
      "It does not do to leave a live dragon out of your calculations, if you live near him." - Tolkien
  16. If apps can run without admin accounts... by denis-The-menace · · Score: 2, Interesting

    If this makes most apps able to run without admin accounts it will be a step in the right direction.
    Where I work, I waste half my time tweaking and proding half-assed, government-mandated, useless POS apps just for them to work without being an administrator.

    It seems Windows developers will always trade end-users security to prevent permissions-issue support calls. And *ALL* of them develop and test as administrators. QA'ing with a user account is too much work.

    BTW: Yes, the other half of my time is paperwork.(close to TPS reports)

    --
    Obama's legacy: (N)othing (S)ecure (A)nywhere and (T)error (S)imulation (A)dministration
    1. Re:If apps can run without admin accounts... by mabhatter654 · · Score: 1

      bonus points if they made this an open spec to follow. Then state govts could benifit as well for their depts and schools. Hopefully it will be a "evolving" standard, perhaps on a yearly basis, then the industry could pick it apart and help make it better!!!! (I'm hungry for pie in the sky now) It's the one thing Microsoft hasn't been able to fix is their developers!developers!developers! refusing to adopt the new security features and draging the ship down.

    2. Re:If apps can run without admin accounts... by Schraegstrichpunkt · · Score: 1

      It seems Windows developers will always trade end-users security to prevent permissions-issue support calls. And *ALL* of them develop and test as administrators. QA'ing with a user account is too much work.

      The historical lack of a "Run as user..." command is partly responsible for this.

    3. Re:If apps can run without admin accounts... by drsmithy · · Score: 1

      The historical lack of a "Run as user..." command is partly responsible for this.

      It's been around since *at least* NT4, in 1996 (although prior to Windows 2000, it was added to the shell via a free Powertoy from Microsoft).

      No developer has had an excuse for releasing software that needlessly requires elevated privileges since ca. 1998. None.

    4. Re:If apps can run without admin accounts... by Schraegstrichpunkt · · Score: 1

      It's been around since *at least* NT4, in 1996 (although prior to Windows 2000, it was added to the shell via a free Powertoy from Microsoft).

      It's built into Windows 2000? Where?

      If people can't find the option, it's not much better.

    5. Re:If apps can run without admin accounts... by drsmithy · · Score: 1

      It's built into Windows 2000? Where?

      Shift+Right-click something executable.

      If people can't find the option, it's not much better.

      People shouldn't have to find it, it should be activated on-demand. Vista has improved this situation significantly, although since it is multiuser, the capability has always existed in NT (and some programs do it properly, detecting current privilege levels and prompting for higher ones if necessary, even in Windows 2000 (and maybe earlier ?)).

      Specifically having to "Run As" something - in the general case - is broken UI, and most people do not understand the concept of a multiuser OS necessary to make use of it.

      As with most "problems" in Windows, this is almost completely the fault of the software developers (although Microsoft must also share some blame for not doing the right thing with OS-included tools, eg: Control Panel applets).

  17. Something they should've done 10 years ago by Anonymous Coward · · Score: 0

    Maybe now we'll start to see a decrease of .gov and .mil boxen in the botnets...

    It's a step in the right direction. A bold baby step.

  18. Where did March go? by Anonymous Coward · · Score: 0, Funny

    Is it April 1st already?

    1. Re:Where did March go? by Anon-Admin · · Score: 1

      Thanks, You got me.

      I actually looked at my calendar to see if it was April 1st. :)

    2. Re:Where did March go? by Anonymous Coward · · Score: 0

      Secure Windows?

      [Apu] Such a thing has never been done! [/Apu]

  19. Stamp out diversity! by PingSpike · · Score: 1

    Yes...I think the security problems caused by the monoculture can definately be solved by making the various installs of this operating system as close to identical as possible. Furthermore, we should post all of these assumed similarities somewhere that all can see.

    Heh, thats not to say any other OS would do great as the defacto standard either. I'm no big fan of windows these days, but if linux or macOS were top dog they'd be the target too. I just have to question the wisdom of this logic: This isn't working, so lets do it even harder!

    1. Re:Stamp out diversity! by Anonymous Coward · · Score: 0

      You are, with due respect, an idiot. Whether you're a DANGEROUS idiot depends on whether you work in a position that requires you to deal with machine configuration, which I kind of doubt, but I'm open minded.

      Before you get into the "rail against monoculture!" Slashdot groupthink, consider the following.

      Which of the following sets of desktop firewall rules for a 1000 desktop environment do you consider more secure?
      * All 1000 have a single set of firewall rules. These rules drop all externally generated connection requests. They allow outgoing connections only from a set of approved applications, and only on specified ports.
      * All 1000 have potentially different firewall rules, ranging from the configuration above to "Wide open!" to (what I usually find) whatever you get when someone tries to "make the popups go away by telling them everything is OK" and is potentially different on each machine.

      If you think the first group is less secure because it's an evil monoculture, well, I'm glad I don't have to work with you.

    2. Re:Stamp out diversity! by B3ryllium · · Score: 1

      The obvious answer is to run everything through a single LinkSys home office router, and then not have any firewalls on individual machines. :)

    3. Re:Stamp out diversity! by DrSkwid · · Score: 1

      Definite as in finite, it's not that difficult.

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  20. I hate the US by stratjakt · · Score: 0, Troll

    They are so racist, and hate muslims.

    I'm going to move to germany, who are progressive enough to allow muslims to beat their wives, becuase the Koran says it's OkEeDokee.

    What a bunch of cowards. That's how afraid they are of the islamic world, a judge will rule it's OK for a muslim man to abuse his wife - rather than offend the muslims.

    Just like the cowards in Minnesota, who wont revoke the licenses of muslim cab drivers who refuse to pick up the blind, in blatant opposition to the ADA.

    Cowardice disguised as PC. Terrorism is real, and has worked.

    Quit blaming Bush for all of the countries problems, because you're too cowardly to point at the real problem.

    --
    I don't need no instructions to know how to rock!!!!
  21. great moments in the bush administration by circletimessquare · · Score: 0, Flamebait

    "We shall topple Saddam and Iraq will be a bulwark of^W against terror"

    (waves magic wand)

    "We shall put our best men (cough) in charge and New Orleans will be spared the worst from Hurricane Katrina"

    (waves magic wand)

    "We shall mandate that Windows be secure and it shall, simply because we say it should be so"

    (waves magic wand)

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  22. National Operating Systems Commission! by Anonymous Coward · · Score: 0

    Several years ago at the anti-trust trial they ridiculed the idea of someone else determining what should and shouldn't be in their Operating System. They twisted what the Intuit CEO said, saying it would result in a National Operating System Commission. Some of us thought that idea would come back to bite them some day - and this appears to be the day. It IS a good idea for the Feds to standardize on a minimum set of functions, saying what they think should be the operating system functionality (and by default, what not). Surely it is somewhat arguable, but it is a good start, with a CUSTOMER saying what their idea of an OS is.

    [Search Google for >> Microsoft antitrust "national operating system commission" ]

    1. Re:National Operating Systems Commission! by AP2k · · Score: 2

      Shouldnt this apply to OSes that are commercially sold? At some point I may write my own OS and release it under GPL. Should I be forced to write in functions for security, even though I am operating a car? What about embedded Linux OSes? What about FreeRTOS?

      I dont think forcing OS makers to include specific functions is a step in the right direction. I think that suggesting the same is a good idea, however.

    2. Re:National Operating Systems Commission! by DogDude · · Score: 1

      You're right... Imagine the Slashdot anger if the Feds said that all Linux needs to be standardized according to RedHat v204.x. Oooh! That would be naaaasty!

      --
      I don't respond to AC's.
  23. Standard Best Practice by Anonymous Coward · · Score: 0

    nd this differs from standard practices in most large coroprations...how?

    Yes, monocultures are "infect one, infect all." However, not knowing what's running on machines, having nonstanrard installed apps, allowing users to override security settings, etc. is a terrible idea for security as well. Not only does it usually lead to MORE possible exploit vectors, it also makes support a nightmare.

    Every company of more than 500 employees I've dealt with has had a "standard" desktop image for it's software, and and restrictions about what you can do with company equipment. I'd suggest anyone suggesting this is a bad idea has no idea what supporting a large number of user machines is like. Locking down to a standard, reviewed, "secure by default" configuration is CONSIDERABLY BETTER than any plausible alternative.

    It's too darn easy to say "monocultures bad!" Which is, in the abstract, true. But not when the difference between the pre-existing polyculture and the new monoculture is by removing exploit vectors present in the original polyculture. This is bad...how?

    Also, at the very least, with a limited and common set of vulnerabilities, the IT staff can focus on guarding the doors they know are open, without worrying about someone coming in through the now-bricked-up window.

  24. I'm a bit confused here.... by zappepcs · · Score: 1

    Not that I don't like a good MS bashing, but the government should be getting the bashing right now, not MS. The government branches/organizations should have been doing this all along, that is making every effort to ensure that their computing platforms are secure, AND comparing one vendor against another. That is how smart businesses are run. The fact that they are just now doing this is fscking scary! What compromises have already been exploited and not discovered as yet?

    That it has been mandated to secure Windows installations and applications that run on it is in fact a step in the right direction. Now they just have to do the same with ALL other computing platforms. The NSA has a few hints on that http://it.slashdot.org/article.pl?sid=07/01/09/135 6222 and there is also help for Linux? http://books.slashdot.org/article.pl?sid=07/03/14/ 1534241

    To me, this is something that should have ALREADY been done several years ago. If they manage to get through all the virus/malware attacks without suffering loss of information I'll be amazed since they are just now mandating secure computing environments??? WTF?

    1. Re:I'm a bit confused here.... by mysticgoat · · Score: 2, Informative

      The government branches/organizations should have been doing this all along, that is making every effort to ensure that their computing platforms are secure, AND comparing one vendor against another.

      Many if not all of the US Federal agencies HAVE been doing this all along. Look back over slashdot for the last 2 - 4 weeks, and you'll see stories that several government agencies have declared moratoriums on updating to Vista. Other agencies are certainly doing the same thing, but managing their moratoriums more quietly.

      I left USGOV service several years ago, but I can attest that the VA and other big agencies began actively managing update strategies as early as Win98. When Directors of VA hospitals suddenly found that their memos could not be read by the staff because they had been given the first of the fancy new computers with MS Office 97, and the staff were still using MS Office 4.3, IT departments across the country caught holy hell.

      I laud the White House for issuing this directive. (This is the first time I can actually support a decision from the White House since Jan of 2001.) But it also reminds me of a wall plaque I once saw in Department Manager's office:

      I must hurry and catch up with the others
      for I am the Leader.

  25. Honesty by DoofusOfDeath · · Score: 5, Funny

    White House Specifies And Mandates Secure Windows

    Look, if they just don't want to use Windows why can't they say so???

  26. What, no "haha" tag? by Scareduck · · Score: 0, Troll

    Seriously, can Windows — any version — be made secure?

    --

    Dog is my co-pilot.

    1. Re:What, no "haha" tag? by i.r.id10t · · Score: 1

      Yup. Just unplug the network cable (and don't go wireless) and post a physical guard for hte physical security.

      --
      Don't blame me, I voted for Kodos
    2. Re:What, no "haha" tag? by allscan · · Score: 1

      Of course, just don't hook it up to any tubes.

    3. Re:What, no "haha" tag? by Rohan427 · · Score: 1

      Sure, here's the instructions:

      1. If you have a Windows installation CD, get it and set it aside. You will need it for a later step.
      2. Boot the computer.
      3. Make a Windows Boot Floppy.
      4. Restart the computer with the floppy and boot it to the command line.
      5. Type fdisk at the command prompt and hit .
      6. Follow the on-screen instructions for deleting all partitions on all hard drives.
      7. Remove the floppy and set it aside for the moment.
      8. Reboot the computer and install any operating system that is not made by Microsoft.
      9. Take the installation CD (from step 1) and the floppy and burn them both.

      PGA

    4. Re:What, no "haha" tag? by rolfwind · · Score: 1

      I still don't trust that. How about unplugging the electric cord?

    5. Re:What, no "haha" tag? by Anonymous Coward · · Score: 0

      Dammit. I just wasted my last mod point on a post that was much less insightful than this one was funny.

    6. Re:What, no "haha" tag? by Anonymous Coward · · Score: 0

      *bing!* this is why the Linux ITs are cheering it. It's the same thing as saying "You cannot run Windows unless it can be made secure!"

      Goodbye Microsoft! Don't let the door hit your ass on the way out!

    7. Re:What, no "haha" tag? by Bogtha · · Score: 1

      Seriously, can Windows -- any version -- be made secure?

      Don't be ridiculous, of course it can. Here's a step-by-step guide.

      --
      Bogtha Bogtha Bogtha
  27. Regulated businesses already have this by zerofoo · · Score: 5, Insightful

    I was the network manager for a bank a while back, and during our audits were were given a list of registry/active directory policies required to get a good rating by those auditors. They also had a list of services that needed to be disabled as well (unless there was a compelling business case for those services).

    I have to admit, the federal regulators did not ask us to do anything that I did not agree with. The only exception was changing our default SQL server port. I think that was around the slammer virus time and that was the quick fix. Unfortunately their "quick fix" turned into months of application research trying to figure out what we were going to break by changing the SQL port. I told the auditors that a quick nmap scan would reveal the new port easily.....and future worms would have that ability built-in. They made us change it anyway.

    Beyond that, they also looked at our audit trail, monitoring and alerting, and our network/firewall architecture. You pretty much had to do everything they asked or you lost your FDIC insurance.

    You should be glad the feds care about bank security....after all, it is your money they are protecting.

    -ted

    1. Re:Regulated businesses already have this by Anonymous Coward · · Score: 0

      You should be glad the feds care about bank security....after all, it is THEIR money they are protecting.

      There. Fixed that for ya.

      Illusion is a convenient sedative for reality, don't you think?

  28. Hmmm.... by RobertM1968 · · Score: 0, Troll

    "No Vista application will be able to be sold to federal agencies if the application does not run on the secure version of Vista," explained Alan Paller, director of research at The SANS Institute.'"

    I didnt know there was such a thing... :-)

    Laugh, it was supposed to be funny!

    1. Re:Hmmm.... by RobertM1968 · · Score: 1

      This is funny, I get a -1 Troll while others get +# Funny.... ah well... regardless, there still is no such thing as a secure version of Windows - thus I thought the statement was funny...

  29. Ultimate Control. by twitter · · Score: 3, Interesting

    A very Silly AC taunts:

    It's the government mandating this version of Windows, not Microsoft. Reading comprehension much?

    Once the settings are specified, M$ can make the system do as they please. What, do you think Uncle Sam is going to give up patch Tuesday? The whole point is to make it easier to apply patches. It won't really work, of course, because M$ and others will keep playing the same anti-competitive tricks. When an application does not work with the settings, it not Windoze is rejected.

    The net result is contrary to commodity computing. The whole reason for using M$ is to gain access to cheap hardware and a universe of software. Reducing your choice in software goes a long way toward making your hardware worthless. A fancy computer that does not do the task you want it to is not doing you any good. The proposed flexibility will inevitably sink to Dell software install options and people who want to get work done with specialized programs will be forced off Windoze or suffer with second rate software on expensive hardware.

    The same kind of program would not be such a disaster in the free world. First, it's easy to tell what works and upgrades are already painless. Second, if something does not work, it will be fixed quickly. Third, and most importantly, the software does not have "owners" who want to mess with other software "owners".

    --

    Friends don't help friends install M$ junk.

    1. Re:Ultimate Control. by Afecks · · Score: 1

      A fancy computer that does not do the task you want it to is not doing you any good.

      But it is doing what the customer wants. They want a baseline configuration and any programs that don't work with their configuration aren't allowed.

      You're trying so hard to turn this around and make it about Microsoft but they have little to do with it. This is the federal government making up these rules. If they don't want to allow program X because program X doesn't support feature Y then that's nobody's problem but the authors of program X.

      The proposed flexibility will inevitably sink to Dell software install options and people who want to get work done with specialized programs will be forced off Windoze or suffer with second rate software on expensive hardware.

      Oh please, don't act like open source doesn't exist in Win32. If you think program X is "second rate" then make a better version. I know of several free compilers if you'd like me to point you to them.

      --
      Everytime someone buys a Windows PC, a twitter dies.

    2. Re:Ultimate Control. by Anonymous Coward · · Score: 0

      For someone who accuses me of being 'silly' (what are you, twelve?), you completely avoided my point: this is still a government-mandated change. I couldn't even begin to predict how much damage Microsoft would do to their relationship with the government if they acted the way you're 'predicting'. It is not Microsoft saying how a computer should operate, as pointed out in the article it is the current administration who wants limits on what will run and what won't.

      As for your 'advantages of free software': Too easy.

      First, it's easy to tell what works and upgrades are already painless.

      Ubuntu and nVidia drivers. Not all upgrades are painless, because you can't foresee everything. Developers are human, not robots. There are plenty of instances where upgrades break something important.

      Second, if something does not work, it will be fixed quickly.

      From linked article:

      RHEL Linux average time to fix any class of vulnerability: 58 days.
      Microsoft windows average time to fix any class of vulnerability: 13 days.

      Third, and most importantly, the software does not have "owners" who want to mess with other software "owners".

      Tell that to Gentoo users that have had several developers quit over the last few months due to differences of opinion. A lack of ownership can actually negatively impact development when there are conflicts that can't be resolved due to a lack of a resolution path.

    3. Re:Ultimate Control. by Anonymous Coward · · Score: 0

      Dude, Tomorrow Never Dies was not a documentary.

    4. Re:Ultimate Control. by trianglman · · Score: 1

      But it is doing what the customer wants

      It is doing what the customer (US Government) wants, but not what the users (scientists, analysts, etc. who need specialized programs) want or need.

      You're trying so hard to turn this around and make it about Microsoft but they have little to do with it.

      MS has little (as far as has been shown so far) to do with the policy itself, but once the policy is implemented they have full control over the systems and what software can and cannot run on it. This mandate states that "No Vista application will be able to be sold to federal agencies if the application does not run on the secure version of Vista." Now this could mean that as long as you can click through the "This isn't a Windows Certified program" (or whatever the error is) and it still works that it will be allowed. Or it could, more likely, mean that all software that the government runs needs Microsoft to certify it. If that doesn't give MS a lot of (imo unnecessary) power, I don't know what does. Not only that, but MS will make a ton of cash, not just from the Vista boxes, but from the thousands of government contractors with millions in government money that will need to get their software certified.

      Oh please, don't act like open source doesn't exist in Win32.

      This relates to my last point, how much open source software is MS certified? Also, how many open source projects can afford to get certified?

      <tinFoilHat>Finally, what I see in this is a move to stop the Open Document movement that many state governments are moving towards. What better way to cut it off than to talk the federal government into adopting a software infrastructure that is largely incompatible.</tinFoilHat>

      --
      Clones are people two.
    5. Re:Ultimate Control. by Allador · · Score: 1

      Could you not even be bothered to read the article?

      Microsoft has _nothing_ to do with this. Let me repeat ... nothing.

      It is a 'secure configuration', not a different sku from microsoft.

      In other words, its vista with a specified security policy applied to it.

      And then ISVs must certify that their software runs on vista configured in that manner.

      RTFA for ignorance' sake.

    6. Re:Ultimate Control. by trianglman · · Score: 1

      Yes, the security policy is being established by the government. But if you have read anything about Vista, any software that Microsoft hasn't certified will give security error warnings. I never said Microsoft would gain directly from this policy, I said that more companies are going to need to get their software MS Certified so that it can run under this more secure policy. Microsoft will make money off of these extra certifications.

      Think outside the box for ignorance's sake.

      --
      Clones are people two.
  30. That;'s one way to look at it. by khasim · · Score: 5, Insightful

    The net result will be identically configured computers with fewer applications, a bot maker's paradise.

    Yep. That's one way to look at it.

    A different way to look at it is that a known, reduced configuration allows vulnerabilities to be patched (government-wide) at the lowest level possible with minimum code necessary.

    I for one fucking HATE the 500MB "service packs" that are released. It is far easier to test frequent, minor changes than infrequent MASSIVE changes. And it looks as if the Federal Government is finally catching on to that fact.

    #1. There is no security without physical security.
    #2. Run only what you absolutely need.
    #3. Run it with the minimum possible rights.
    1. Re:That;'s one way to look at it. by twitter · · Score: 1

      A different way to look at it is that a known, reduced configuration allows vulnerabilities to be patched (government-wide) at the lowest level possible with minimum code necessary.

      You may also minimize the work your users can do, on Windoze at least.

      --

      Friends don't help friends install M$ junk.

    2. Re:That;'s one way to look at it. by ColdWetDog · · Score: 4, Funny
      You may also minimize the work your users can do, on Windoze at least.

      You're talking about the Federal Government here, I'm not sure that is at all a relevant concern. At worst, it's a feature, not a bug.

      --
      Faster! Faster! Faster would be better!
    3. Re:That;'s one way to look at it. by Anonymous Coward · · Score: 1, Insightful

      And it looks as if the Federal Government is finally catching on to that fact. ...
      #3. Run it with the minimum possible rights.


      Too bad they think that applies to people too.
    4. Re:That;'s one way to look at it. by Anonymous Coward · · Score: 0

      #4. Assume that anything and everything can and will fail at some point.
      #5. Have a plan for when a compromise/disaster does happen. Test the plan before it is needed.

    5. Re:That;'s one way to look at it. by Anonymous Coward · · Score: 0

      #2. Run only what you absolutely need. Glad you can determine that for me ahead of time, thanks. I was tempted to try new things, silly me. We should have done this a long time ago, then we could have been content with bank street writer and logo on our Apple IIe's.

      But then again looking for innovation and independent thought from government agencies is like looking for diamonds up a congressman's ass, you might find some, but you won't like the smell.
    6. Re:That;'s one way to look at it. by z-vet · · Score: 1

      #1. There is no security without physical security.
      #2. Run only what you absolutely need.
      #3. Run it with the minimum possible rights.
      #4. Profit!
      --
      326684
  31. we can't disclose the settings by Anonymous Coward · · Score: 0

    GWB and Co. live by and love security by obscurity. So, while it's mandated that software run in the most secure setup, they a) won't tell you what the settings are,
    b) will slap a gag order on if you ask what the settings are because:
    1) if the public were to know you asked then it could be dangerous
    2) if the public were the know about yet another about which the public is not allowed to know it could be dangerous
    3) if the public were to know that someone knows about yet another about which the public is not allowed to know it could be dangerous
    4) if a vendor asks about the settings then they might talk with Carl Rove of Dicky C and everybody knows those blabber mouths can't keep a secret what with Carl admitting the vote fixing last fall by claiming that he had "the math", and Dick can't keep his mouth shut about CIA operatives.

    and c) and get Bert to sue you if you point out that it's readily apparent that they left the most commonly hijacked ports wide open.

  32. Vista only? Who are you foolin'? by idiosynchronic · · Score: 1

    Nevermind that most researchers are ambivalent that Vista is actually more secure than the previous Windows XP. Nevermind that most large organizations take YEARS to adopt new operating systems - Principal Financial Services, headquartered in my town as a major employer, adopted XP 3 years after it was released! TFA is not necessarily "White House says use our secure Vista or You're Fired!" It's about standardizing the security settings on both existing XP and future Vista systems. Vista is promoted in the article because all federal databases and applications will have to run on it someday. I'll let the better geeks argue about homgeneity of systems, Vista's general health and superior security still being evaluated - and not mention the value of using MS vs the OS 'nixes. But the summary is specious. (But what else is new?)

  33. That's great, but... by evil_Tak · · Score: 1

    This won't really make much difference when Manager Bill at the Social Security Administration takes a bunch of people's personal data home, to work over the weekend, and copies it over to the spyware-infested botnet zombie sitting in his home office.

  34. But my application requires admin rights! by zerofoo · · Score: 1

    How many times have you heard this from your users?

    The government is now putting developers on notice. If your application needs something strange.....like administrative / root access for all who use the app, then guess what - you can't sell that application to the US government.

    I'm actually happy to hear this. All users on our network run as a standard user. No one outside of our IT department gets administrative or root access....if their application requires it.....too bad.

    -ted

  35. Why don't they roll their own? by Peter+Trepan · · Score: 2, Interesting

    Why don't they have a DARPA-BSD or something, so they can secure the code themselves? Can the government not afford any CS majors?

    --

    Step into a huge movement. Don't Tread In Me.

    1. Re:Why don't they roll their own? by evil_Tak · · Score: 4, Informative

      Or perhaps some kind of security-enhanced Linux variant...the NSA could even help develop it!

  36. Mandates secure windows.... by gmuslera · · Score: 3, Funny

    what next in the agenda? Mandate water to flow upwards? Ice to burn things? Pigs to fly?

    There are rumors that such things exist, in very special cases, but is easier to see pigs fly than to see a secure windows machine.

    1. Re:Mandates secure windows.... by abb3w · · Score: 1, Flamebait

      what next in the agenda? Mandate water to flow upwards? Ice to burn things? Pigs to fly?

      Trying to set "pi" equal to three is a traditional passtime of Bible thumpers, and about on my expectation level for this White House.

      There are rumors that such things exist, in very special cases, but is easier to see pigs fly than to see a secure windows machine.

      This is because most geeks who try it find building a trebuchet simple and fun, with clear documentation readily available. It also usually involves less shit being thrown at your efforts to make the project blow up.

      --
      //Information does not want to be free; it wants to breed.
    2. Re:Mandates secure windows.... by mutterc · · Score: 1

      Remember, with sufficient thrust, pigs fly just fine.

    3. Re:Mandates secure windows.... by Divide+By+Zero · · Score: 1

      I have RFC1925 (Pt 2, Sec 3: "With sufficient thrust, pigs fly just fine.") posted at my desk here at work, with the aforementioned phrase highlighted.

      I work for the Federal Government in IT.

      Derive from this what you will.

      --
      Dare to Hope. Prepare to be Disappointed.
  37. Shocking by Anonymous Coward · · Score: 0

    After six years of idiocy and incompetence, it's actually amazing an intelligent, well thought out decision was made.

    It must have accidentally slipped through the cracks. Now that Slashdot pointed it out, they will probably decide to "standardize" on Lunix. I'm sure their rollout would go as swimmingly as Munich's Linux rollout... or Bush's wars in Afghanistan or Iraq.

  38. Their real problem is by JustNiz · · Score: 0, Flamebait

    this incorrect but nevertheless pervasive presumption that the only PC os in the world is a Microsoft product.

    Why don't they just switch to Linux? end of security problem.

    1. Re:Their real problem is by inviolet · · Score: 1

      Why don't they just switch to Linux? end of security problem.

      Linux would not be so secure if it became mainstream, or if it became the dominant OS in use at a valuable target (US government computers). Presently, Linux doesn't receive near the same blackhat attention that Windows does.

      As well, Linux is no more secure than its administrators are competent. There is not a lot of Linux expertise out there right now. If the feds switched to Linux tomorrow, it would be quite a while (and truckloads of money) before we reached critical mass of Linux administration skills. Until that time, there would be a lot of broken, misconfigured, and unpatched Linux installations.

      --
      FATMOUSE + YOU = FATMOUSE
    2. Re:Their real problem is by JustNiz · · Score: 1


      >> or if it became the dominant OS in use at a valuable target (US government computers).

      Wow. How closed-minded. You need to look around you.

      Linux IS ALREADY mainstream. It has become the dominant OS in many 'valuable targets' both inside and outside the US. Yes there really is a whole world outside the US and guess what we even have electricity now.
      Most European governemts are already mandated to running open source over proprietary OS's for several years now so are not even allowed to run Windows.

      >> As well, Linux is no more secure than its administrators are competent.
      This is true, but also equally true for Windows so its irrelevant. The difference is that Linux does not have fundamentally flawed security because of the limited design decisions that went into the fundamental architecture of Windows. This means its easier for Linux admins to get it right. A Linux install by default is pretty secure. With Windows you have to find and enable hard-to-find stuff to make it that way.

      >> There is not a lot of Linux expertise out there right now.
      You're kidding right? Apart from the fact that Unix existed well before Windows, there is tons of experienced Linux-specific people and agencies around.

    3. Re: Their real problem is by mandelbr0t · · Score: 1

      Why don't they just switch to Linux? end of security problem. The biggest fallacy in the world. Ken Thompson, credited with inventing UNIX, was quoted as saying "Microsoft is bad, but Linux is worse" sometime in 1999. I've worked with Linux for a long time, but I've come to realize that I like UNIX, not Linux. Linux has always had huge security problems, but it's based on UNIX, so everyone assumed that it was just evil Microsoft FUD. Realizing that Linux was as much a part of the problem as the solution took a long time.

      I've run many Linux machines, the first one built in 1998. It was r00ted through a wu-ftpd exploit within 3 months of building it. Later Linux servers met similarly violent ends. IPFW bugs that cause the server to freeze when under certain network conditions, IPTables bugs that cause the server to freeze under certain network conditions, unstable desktop environments that randomly lose settings (GNOME & KDE equally), binary blob drivers that we trust 3rd-party vendors to make "just work", dozens of incompatible kernel versions, dozens of incompatible library versions. Buggy IDE drivers that erroneously reported problems with the disk. Buggy IDE drivers that erroneously failed to report problems with the disk. Buggy IDE drivers that randomly corrupted data... The litany is quite lengthy, and I could easily make it as long as the Windows litany.

      Security is a Big Problem. It's an even bigger problem because lots of people assume they know what they're talking aobut when they don't. Anyone who claims that "Linux is the end of the security problem" doesn't understand the problem. The OS is such a small piece of the overall puzzle; please stop spreading the idea that you can solve all your security problems in one giant step.
      --
      "Please describe the scientific nature of the 'whammy'" - Agent Scully
    4. Re:Their real problem is by drsmithy · · Score: 1

      The difference is that Linux does not have fundamentally flawed security because of the limited design decisions that went into the fundamental architecture of Windows.

      Like what ?

      The "fundamental design" of NT is vastly more secure than the "fundamental design" of Linux was. Subsequent add-on hacks like SELinux have improved the situation markedly, but hardly anyone actually *uses* properly configured SELinux machines.

      The "fundamental design" of Linux included a superuser. That alone is a massive security problem not present in Windows.

      This means its easier for Linux admins to get it right. A Linux install by default is pretty secure. With Windows you have to find and enable hard-to-find stuff to make it that way.

      Rubbish.

    5. Re:Their real problem is by Anonymous Coward · · Score: 0

      As for the mainstream target BS, BULLSHIT! Apache has run more than two thirds of all internet sites for at least half a decade now. Microsoft IIS has had less than 1/3 share for the same period, yet most bugs and viruses (the grand majority) affect Microsoft IIS. Microsoft stuff is more susceptible to bugs, worms and viruses, and so gets more. Putting it another way, Linux had grown to 5% of the desktop market several years ago, yet did not have 5% of the viruses (still just 5 viruses total) instead of the 35 viruses that show up for windows (EACH MONTH!). There have been more than 25000 viruses written for windows, most of them trivial, but damaging nevertheless. Windows was written as a single users system with no security by design. Along comes networking, and they are hosed. Linux was designed as a multi-user system, with networking in mind from the beginning. Market share has nothing to do with it.

    6. Re:Their real problem is by JustNiz · · Score: 1

      Oh gee I don't know, perhaps:
      Users run as superuser by default
      Any app can overwrite anything in the registry
      Having a registry in the first place
      Installing applications in windows permits and almost requires them to add/modify files (including the registry) in the operating system subdirectories, thus apps become extensions of the OS itself.
      Ie6
      Active X
      need I go on...?

    7. Re:Their real problem is by drsmithy · · Score: 1

      need I go on...?

      No. You have demonstrated quite well that you have no clue what you're talking about.

  39. Calculation... by Mateo_LeFou · · Score: 1

    Don't you have to finish the math before making judgment positive or negative, i.e.

    25% of computers are bots -- let's say 500 million computers. What % of those run windows? Is it higher or lower than the % of *all computers that are running windows?

    --
    My turnips listen for the soft cry of your love
    1. Re:Calculation... by Macthorpe · · Score: 1

      Let's be honest, I wasn't the one misrepresenting the situation in the first place. What I'm saying is that the number given isn't indicative of anything at all in the context of what he was saying - he says 1 in 4 computers being in a botnet shows inherent insecurity in non-free OSes, and that is not the case at all.

      I absolutely agree with you that there needs to be more facts before we can make a decision either way - hence my point.

      --
      "It does not do to leave a live dragon out of your calculations, if you live near him." - Tolkien
    2. Re:Calculation... by Mateo_LeFou · · Score: 1

      Well I don't feel like joining in the twitter vs Macthorpe festivities, but one needs very few pieces of data to make an assessment.

      If 95% of computers have proprietary OSes on them, and 25% of *all computers are in a botnet, then .95 X .25 = 23.75%
      is the average % of machines with proprietary OSes that are in a botnet

      Now, are 23.75% of machines with free OSes in a botnet? (Hint: no.)

      --
      My turnips listen for the soft cry of your love
  40. Right Hand. Meet Left Hand. by asphaltjesus · · Score: 1

    NIST does a very nice job specifying _how_ to harden a windows PC.

    I have a feeling whomever is issuing directives at the white house hasn't bothered to check with NIST. http://csrc.nist.gov/itsec/guidance_WinXP.html

    I just noticed they've got a Vista document going.

    I've hardened PC's the NIST way. Most applications do very unexpected things when you least expect it.

    This, by the way, is clearly the result of strenuous lobbying on Microsoft's part so early in the Vista game.

    --
    Got Trader Joe's? friendwich.com RSS feeds work now!
  41. A word on federal security mandates by 192939495969798999 · · Score: 2, Insightful

    In terms of making "unbreakable" anything, this will be as successful as the stripe in money. Within a week of the Mint putting a plastic stripe in money, there were guys in bars demonstrating how to take said stripe back out. While that is a fairly victimless crime, demonstrating how to hack and debilitate the "government standard" vista configuration will just lead to a massive botnet as everyone (except the appropriate govt bodies, of course) has already figured out.

    --
    stuff |
    1. Re:A word on federal security mandates by Ungrounded+Lightning · · Score: 1

      Within a week of the Mint putting a plastic stripe in money, there were guys in bars demonstrating how to take said stripe back out.

      Which makes the money worthless - and refused the first time somebody looks for the stripe.

      The trick is to figure out how to put the stripe INTO a counterfeit bill.

      --
      Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
    2. Re:A word on federal security mandates by R2.0 · · Score: 1

      "Within a week of the Mint putting a plastic stripe in money, there were guys in bars demonstrating how to take said stripe back out."

      Thereby making the bills suspect, and opening thgemselves up to charges of tampering/counterfeiting. Exactly what did they believe they were defeating? The point of the stripe isn't a tracking mechanism or some other tinfoil hat conspiracy, but an anti counterfeit measure - without the stripe, the bill is suspect and presumed counterfeit.

      So the stripe can be removed - BFD. Show me the guys that can manufacture the stripes and print the money and insert the stripes - THAT would be impressive as a bar trick.

      --
      "As God is my witness, I thought turkeys could fly." A. Carlson
  42. Dumb question, maybe. by seandiggity · · Score: 1

    Maybe this is a dumb question but it seems too obvious not to mention: If a Vista app requires one of the services the White House's "secure" Vista has turned off by default, does that mean it can't be installed (or at least shouldn't be installed if the mandate is actually followed)? How about if the application installs a new service?

    --
    Geeks like to think that they can ignore politics, you can leave politics alone, but politics won't leave you alone.-rms
  43. Switch? by HalAtWork · · Score: 1

    If it's not secure and doesn't work the way they want, shouldn't they find another product, and shouldn't Microsoft be responsible for identifying and fixing these problems and not the government with our tax dollars?

  44. The actual OMB memo by beetle496 · · Score: 3, Informative

    The actual OMB memo (pdf, sorry) can be found at URL:
    http://www.whitehouse.gov/omb/memoranda/fy2007/m07 -11.pdf

    The text follows:

    EXECUTIVE OFFICE OF THE PRESIDENT
    OFFICE OF MANAGEMENT AND BUDGET
    WASHINGTON, D.C. 20503
    DEPUTY DIRECTOR FOR MANAGEMENT
    March 22, 2007

    M-07-11 / MEMORANDUM FOR THE HEADS OF DEPARTMENTS AND AGENCIES

    FROM: Clay Johnson / Deputy Director for Management

    SUBJECT: Implementation of Commonly Accepted Security Configurations for Windows Operating Systems

    To improve information security and reduce overall IT operating costs, agencies who have Windows XP TM deployed and plan to upgrade to the VistaTM operating system, are directed to adopt the security configurations developed by the National Institute of Standards and Technology (NIST), the Department of Defense (DoD) and the Department of Homeland Security (DHS).

    The recent release of the VistaTM operating system provides a unique opportunity for agencies to deploy secure configurations for the first time when an operating system is released. Therefore, it is critical for all Federal agencies to put in place the proper governance structure with appropriate policies to ensure a very small number of secure configurations are allowed to be used.

    DoD has worked with NIST and DHS to reach a consensus agreement on secure configurations of the VistaTM operating system, and to deploy standard secure desk tops for Windows XPTM. Information is more secure, overall network performance is improved, and overall operating costs are lower.

    Agencies with these operating systems and/or plans to upgrade to these operating systems must adopt these standard security configurations by February 1, 2008. Agencies are requested to submit their draft implementation plans by May 1, 2007 at fisma@omb.eop.gov. With your endorsement we will work with your CIOs on this effort to improve our security for government information. If you have questions about this requirement, please contact Karen Evans, Administrator, E-Government and Information Technology at (202)395-1181 or at fisma@omb.eop.gov.

    --
    I paid the going retail price for a Windows screen reader and got a free Unix computer!
    1. Re:The actual OMB memo by Anonymous Coward · · Score: 0

      net stop Netman

    2. Re:The actual OMB memo by beetle496 · · Score: 1

      Here are links to a couple of more recent articles about this and, following that, the text from an email that went out earlier in the week.

      OMB to require standard Windows desktop configuration
      http://www.fcw.com/article97974-03-19-07

      OMB sets security standards for Windows computers
      http://www.govexec.com/story_page.cfm?articleid=36 410

      ----

      March 20, 2007

      MEMORANDUM FOR CHIEF INFORMATION OFFICERS

      FROM: Karen Evans
      Administrator, Office of E-Government and Information Technology

      SUBJECT: Managing Security Risk By Using Common Security Configurations

      Common security configurations provide a baseline level of security, reduce risk from security threats and vulnerabilities, and save time and resources. This allows agencies to improve system performance, decrease operating costs, and ensure public confidence in the confidentiality, integrity, and availability of government information. This memorandum requires your agency to develop plans for using the Microsoft Windows XP and Vista security configurations with an implementation date of no later than February 1, 2008. [1]

      As you know, section 3544(b)(2)(D)(iii) of the Federal Information Security Management Act (FISMA) requires agencies to develop minimally acceptable system configuration requirements and ensure compliance with them. Your agency is already required to:

      * document in your annual FISMA report the frequency by which you implement system configuration requirements; [2] and

      * use published configurations or be prepared to justify why you are not doing so.

      As a model for this effort, the Air Force uses common security configurations for Microsoft Windows XP. These configurations were developed in collaboration with the National Institute of Standards and Technology (NIST), the Department of Homeland Security (DHS), the Defense Information Systems Agency (DISA), the National Security Agency (NSA), and Microsoft. These same organizations recently established common security configurations for Microsoft Vista. With these common security configurations now in place, we have a unique opportunity when using Microsoft Windows XP and acquiring Vista.

      Requirements of Agency Plans

      Agency plans for Microsoft Windows XP and Vista should be submitted to OMB by May 1, 2007 to fisma@omb.eop.gov and should describe the following items:

      * Testing configurations in a non-production environment to identify adverse effects on system functionality;

      * Implementing and automating enforcement for using these configurations;

      * Restricting administration of these configurations to only authorized professionals;

      * Ensuring new acquisitions by June 30, 2007, to include these configurations and require information technology providers to certify their products operate effectively using these configurations;

      * Applying Microsoft patches available from DHS when addressing new Windows XP or Vista vulnerabilities;

      * Providing NIST documentation of any deviations from these configurations and rationale for doing so; and [3]

      * Ensuring these configurations are incorporated into agency capital planning and investment control processes.

      Additional Resources Available to Agencies

      By April 20, 2007, OMB in conjunction with DHS and other appropriate agencies will establish a means for information technology providers to obtain software images based on these configurations for test and development purposes. Additionally, the Chief Information Officer's Council will assist and facilitate sharing the common security configurations across the Federal government.

      NIST has established a program to develop and maintain common security configurations for many operating systems and applications, and

      --
      I paid the going retail price for a Windows screen reader and got a free Unix computer!
  45. Hrm ... by B3ryllium · · Score: 3, Insightful

    While this sounds like a good thing on the surface (the mere fact that they're paying attention to OS security is nice), I think it's bad for two reasons.

    1) It ties the entire government into Windows - and on top of that, the most expensive and resource-consuming version thereof. Think of the thousands of PCs that would have to be upgraded for Vista? Now ... what happens to all the old ones? (I sincerely hope that they get donated to schools or something)

    2) It may prevent opensource applications from achieving any traction in the US government. Unless, of course, Microsoft is willing to give them the keys to be declared "Secure/Vista Friendly" or whatever the latest gimmick certification is. Granted, the big guns like OpenOffice and Mozilla might be able to make inroads, but smaller opensource applications might be S.O.L.

    So it's nice that the issue has received consideration, but it may be a rather insidious form of consideration. And that's not a good thing.

    1. Re:Hrm ... by stuntpope · · Score: 2, Informative

      I fail to see where the directive is mandating an all-Microsoft Windows policy for the Federal Government, as some have posted here, let alone a requirement for Vista.

      From the directive, "Agencies with these operating systems and/or plans to upgrade to these operating systems must adopt these standard security configurations"

      Meaning, it only applies to existing or future Windows installs. Not, "all government computers must follow this Windows' configuration" (therefore computer must run Windows).

      Open Source *is* getting traction in the US government. Certainly there is a Microsoft monoculture, and it's frightening sometimes to see the ignorance that can result from it. But I have my choice of Windows or RedHat for servers, and not long ago I found documentation on the RedHat desktop on our help desk's web site. I groan about the .Net bandwagon-jumpers (like Java in the 90's), but there is diversity evident from where I sit.

    2. Re:Hrm ... by k1e0x · · Score: 1

      It really doesn't matter if government uses OSS or not, they invent the money from thin air. Cost is of no concern to them so long as their money is backed by their ability to take ours.

      I'm worried that government is drinking the Vista security Koolaid and may allow Microsoft to do something like forcing hardware manufactures to include chips that only run software approved by Microsoft on Windows.. in the name of security that is. Microsoft does have people on the take in DHS.

      IMHO any government at all is a bad thing tho.. so I could care less what they do so long as they aren't pointing guns at me.

      --
      Bringing liberty to the masses. - http://freetalklive.com/
  46. very good by Nex6 · · Score: 1

    The goverment has alot of different OS's I am sure. With I am sure windows having the biggest footprint. I am also sure this is an attempt to secure the windows footptint. they should have mandated patching and security settings / levels a long time ago, and once more they should do it will all OSs in use with the goverment not just microsoft OS. but all software used by the goverment should have to conform to a standard. and that should apply accross the board. with it runs on a Nix or win.

    -Nex6

  47. Re:Madness by Anonymous Coward · · Score: 0

    Your point would be taken more seriously if you could
    pluralise "virus" correctly

  48. What if Office or IE or Lookout won't run by Anonymous Coward · · Score: 0

    What if Office or IE or Lookout won't run under Secure Vista but Open Office and Firefox etc. will ? Could be an opportunity, or at the worst ( ;-) ) more secure MS apps

    1. Re:What if Office or IE or Lookout won't run by Ungrounded+Lightning · · Score: 1

      What if Office or IE or Lookout won't run under Secure Vista but Open Office and Firefox etc. will ?

      We can all dream of that.

      But I sincerely doubt that the government-mandated configurations will disable the basic Microsoft applications - at least until they decide, deliberately, to move to some other (and designated) toolset.

      --
      Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
    2. Re:What if Office or IE or Lookout won't run by QohelethMags · · Score: 1

      The Air Force has already had problems with IE7 and our online training sites (Air Force Portal, elearning etc...) not playing nicely with the other children. Not to mention our driver and PKI compatibility issues with the Standard Desktop Configuration (SDC). Then there was the propaganda spread around about how SDC was going to make Ghost obsolete and a year later we're still loading Ghost images on a separate VLAN because the deployment scheme for SDC looks like it was written by a chimp with cerebral palsy.

  49. Wow, no one on here RTFA by Raleel · · Score: 3, Interesting

    GEEEZ

    lets start with the second goddamn line of the article

    "A White House directive to federal chief information officers issued this week calls for all new Windows PC acquisitions, beginning 30 June, to use a common "secure configuration"."

    You'll notice that there is no mention of Macs or Linux. That's because this only affects _new windows PC acquisitions". That means it only affects the box when you have windows on it.

    "Applications (such as anti-virus, email etc) loaded onto systems remain flexible but what will be specified in the registry settings and which services would be turned on or off by default."

    Look here... configuration management mandated. How about that??!

    "Even more importantly, the directive calls for suppliers (integrators and software vendors) to certify that the products they supply operate effectively using these more secure configurations."

    OMFG, vendors actually have to put out products that work in secure configurations. holy crap!!! end of the goddamn world. heaven forbid we make them code securely and force them to make it work in something other than the Administrator account.

    "The federal government scheme builds on the "comply or don't connect" program of the US Air Force. The principal targets are Windows XP and Vista client systems but the same ideas might be applied in Unix and Windows Servers environments over time."

    Lookie there, it only applies to windows again. later on, it'll apply to windows Desktops! Not even servers. wtf is this call of monoculture I keep seeing.

    Every consumer should be happy to see this, because a huge client (the biggest?) of computer hardware and software says "that's quite enough. If you can't work in our secure environment, you are going to lose a lot of business. Fix it already".

    --
    -- Who is the bigger fool? The fool or the fool who follows him? --
  50. Re:Madness by LiENUS · · Score: 1

    All along, the answer to virii, malware, hacking, and botnets was right at our fingertips. Just have the government "mandate" Windows be secure!
    Ooooh better yet. Just have the government "mandate" that no one produce virii, malware or botnets and make hacking illegal!

  51. Re:Right Hand. Meet Left Hand. by redelm · · Score: 1
    NIST has had these out for at least 5 years. I would consider testing against NIST patches to be essential before app/patch release from any commercial software vendor. They're two very well defined configs, and after that, the vendor can claim "plays well with secured PCs".

    The tough thing in software testing is to reasonably define what needs to be tested. The testing is tedious but trivial and can be subcontracted.

  52. So... by BrokenHalo · · Score: 2, Insightful

    Seems to me that those criteria make sense. What doesn't make sense is that Microsoft chooses not to make those criteria the default configuration.

    1. Re:So... by cookd · · Score: 1

      The default Vista configuration works great and is quite reasonable for the average non-government, non-corporate user. It makes quite reasonable tradeoffs between usability and security. XP and earlier versions of Windows definitely had some things enabled that shouldn't have been. Vista is much better about that.

      The default Vista configuration does not work so great in a corporate environment. One size does NOT fit all. Because one size does not fit all, Microsoft decided to make the default work well for the user who installs Vista in isolation (home, home office, or non-domain business user). If you install into a domain, the defaults might not work so well, but you're likely to have domain group policies to fix the defaults automatically.

      Microsoft has distributed some guidelines for how Vista should be set up in various situations, along with group policy templates and some tools to help administrators automatically reconfigure all machines on the domain to comply with the policy. So far, administrators seem to be happy with this arrangement.

      Here is some relevant Microsoft-sponsored Kool-Aid (beware - if you watch it, you might be brainwashed!): http://channel9.msdn.com/Showpost.aspx?postid=2831 91

      --
      Time flies like an arrow. Fruit flies like a banana.
  53. You're doing a heckuva job, Billy... by condour75 · · Score: 1

    No would could've predicted the firewall would be breached...

  54. "the secure version of vista" by nurb432 · · Score: 1

    So, that pretty much means the feds cant buy anymore windows software. Cool.

    --
    ---- Booth was a patriot ----
  55. My dad used to say about this kind of thing by Ancient_Hacker · · Score: 1
    My dad used to say : "We at the Pizza Parlor have an agreement with the bank. They don't sell Italian foodstuffs, we don't cash checks".

    So maybe it's not the greatest idea to have politicos making IT policy?

    1. Re:My dad used to say about this kind of thing by Allador · · Score: 1

      It's not politico's making IT policy.

      It's IT professionals in the OMB and other fed units making IT policy.

  56. So let's see if even the NSA can come up with a secure configuration for windows.

    (Or at least one that's secure against everybody but the NSA. B-) )

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
    1. Re:NSA by Anonymous Coward · · Score: 0

      That's easy, you just put it in the configuration where the electric cord isn't attached. That, or you could just fill the case with cheese wiz.

    2. Re:NSA by LO0G · · Score: 2, Informative

      They have. It's published here

      They also have guides for OSX and Solaris.

    3. Re:NSA by Ungrounded+Lightning · · Score: 1

      They have. It's published here They also have guides for OSX and Solaris.

      I said "So let's see if even the NSA can come up with a secure configuration for windows."

      Those are the ALLEGEDLY secure configurations they came up with. Only time will tell if they are ACTUALLY secure. B-)

      --
      Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
    4. Re:NSA by Schraegstrichpunkt · · Score: 1

      Define what you mean by "secure".

  57. It's all coming together for them. by twitter · · Score: 1

    ... the first thing vendors do is require IT to "turn down" security settings because highly paid programmers can't be bothered to make their software work properly under security settings.

    We will see if M$ will give them permission for their software to work. Programmers for anti-virus, Netscape, Correl, IBM and everyone but M$ have complained about issues like this in the past. M$ only wishes it had been so easy as that to get rid of those former competitors and their wish appears to have come true.

    The ultimate loser is M$, of course. What will they be left with when they drive everyone else off their platform? How well paid will programmers be if their only potential employer has to give up most of their profits to M$?

    --

    Friends don't help friends install M$ junk.

    1. Re:It's all coming together for them. by Allador · · Score: 1

      Did you not read the article?

      This has nothing to do with Microsoft.

      I'll spell it out.

      Some IT folks in fed.gov have come up with a security policy (ie, group policies, registry tweaks, acl changes, user-rights changes, etc). They are saying that they will be running all vista machines with that exact security policy enforced.

      They are then saying that to be able to big on software contracts, the ISV must certify that their software will run on Vista configured with this policy.

      Microsoft is not involved in any way.

      It's not Microsoft creating the security policy. It's not Microsoft creating a new vista sku. It's not Microsoft creating a certification program to sign & cert tested software. It's NONE of these things.

      So to be crystal clear here ... Microsoft is not giving anyone permission for anything.

      If you could be bothered to read TFA you'd see that.

  58. Re:Will make problems for R&D/scientific appli by Anonymous Coward · · Score: 0

    Yep, ditto at NIH with this and full disk encrytion for all laptops. If you use a computer for something more than basic office tasks this becomes very problematic.

  59. Re:Will make problems for R&D/scientific appli by Down_in_the_Park · · Score: 1

    You mean NASA uses Windows for scientific applications? No wonder the think tank doesn't get any money anymore...

    --
    "People who are willing to sacrifice essential freedoms for security deserve neither freedom nor security."

    B F
  60. TFA implies they'll tell all the developers by Ungrounded+Lightning · · Score: 1

    The AC speculates: ... they a) won't tell you what the settings are, ...

    But the TFA says that one of the major points of the exercise is to give developers a common configuration to develop for and test against.

    So they'll be telling all the developers - which means all the potential developers - which means everybody.

    Cute idea. But the tinfoil brim got between the AC's eyes and the screen. B-)

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
  61. TFA sez by Ungrounded+Lightning · · Score: 1

    Now that Slashdot pointed it out, they will probably decide to "standardize" on Lunix.

    The TFA says the "same idea may be applied to Unix and Windows Servers over time".

    At the resolution of such press releases "Unix" would include Linux and OSX.

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
  62. Mandate all they want... by BlindRobin · · Score: 1

    It will never come to pass. This is like trying to create a chorus from a sack of cats.

  63. This is easier in the free world. by twitter · · Score: 2, Insightful

    But it is doing what the customer wants. They want a baseline configuration and any programs that don't work with their configuration aren't allowed.

    They could have gotten that and a much wider choice of applications by choosing any Linux distribution. Free software package management works. A side benefit is real security

    You're trying so hard to turn this around and make it about Microsoft but they have little to do with it. This is the federal government making up these rules.

    That could be, but M$ can't win for losing. It would be much harder for M$ to blame the user for M$ problems if they really told the user exactly what to do. In the end, it's all about M$ and non free software. Non free software can't be as good or work together the same way free software does. It has obvious problems and the obvious solutions are difficult or impossible.

    Two solutions are code sharing and configuration control. As you and others say, a smaller code base is cheaper and more secure. Competitive pressures keep non free companies from sharing libraries and their licensing make that most obvious cost savings impossible anyway. Everyone has to reinvent every wheel or put themselves at the mercy of their non free competitors. The second most obvious cost savings measure is configuration control, but that too is impossible in the non free world. The user can flip switches, but the switches themselves will change as applications change out libraries. Without the source code, the user does not really know what the switches do anyway.

    --

    Friends don't help friends install M$ junk.

    1. Re:This is easier in the free world. by Afecks · · Score: 1

      Everyone has to reinvent every wheel or put themselves at the mercy of their non free competitors.

      If you have problems reinventing the wheel, I doubt programming would be your chosen profession.

      If you're too lazy then go flip burgers.

  64. All these replies, so little understanding. by jimicus · · Score: 1

    Most of what I've seen so far says "This will make them easy targets". Yet the only way I can make sense of this is as follows:

    1. Every computer has an identical OS build on it (most enterprises have something like this already in place - nobody in their right mind wants to support 100 slightly different builds).

    2. That build is locked down thoroughly, so only necessary services run. (Most enterprises probably don't go quite that far, but in an environment where you're very concerned about security you might).

    2a. This probably applies to local functions as well as remote services. So things like ActiveX configuration is probably nailed down as well.

    3. Applications which require admin rights are verboten. (Not always very feasible in the real world right now, but high time someone put their foot down and said "if you want to sell us software, it must run as a restricted user". Certainly the assumption on /. that everyone out there has admin rights to their work PC "because they have to" is complete rubbish - I don't think I've ever seen that).

    I don't see how this is any different to a policy of demanding that anything which goes directly on the Internet has all unnecessary services turned off, no unnecessary software installed and ensuring that which you do have to run is secured as much as possible - and that's generally considered best practise. What's the problem?

  65. Re:Will make problems for R&D/scientific appli by truckaxle · · Score: 1

    This is true with all federal government research. Windows is increasing becoming the only tool approved and it is getting harder to use non-windows tools. Take for example the wide ranging Navy Marine contract that specifies essentially the same solution for the receptionist desktop as on the scientist/engineering desktop. All applications have to be on the "approved" list which eliminates many instances of great open source and freeware software. It is a sad trend - they may as well nationalize Microsoft.

  66. a real good common configuration by Joe+The+Dragon · · Score: 1

    only works when they all have the same hardware. There is like a lot systems that need different hardware that they can't get rid of.

  67. Registry? by Migraineman · · Score: 1

    What is this "registry" of which you speak?

    (man, I wish I could deliver that with a straight face)

  68. Why not.. by Arceliar · · Score: 1

    ..just make a standard issue 'nix distro already! SELinux or something OpenBSD based per chance? They're both already extremely secure (and not just through obscurity--though it helps).

    Of course...I'd have to walk around saying stuff like "Learning (to use it) is half the battle" and "G. I. OOOOOOOOOOOOO--S" ...and now that tune will be stuck in my head all day.

    1. Re:Why not.. by Arceliar · · Score: 1

      Er, make that "Knowing (how to use it) is half the battle" >.>

  69. In the US Air Force, this has already happened by Frosty+Piss · · Score: 2, Insightful

    In the US Air Force, this has already happened in the form of the Standard Desktop Configuration Image that we install on all PCs. This started the middle of last year.

    --
    If you want news from today, you have to come back tomorrow.
    1. Re:In the US Air Force, this has already happened by thundergeek · · Score: 1

      I am responsible for running this SDC on the computers in this squadron.

      The single most repetative complaint is that the computers are slower now!

      We modified the SDC to stand for "Slow Damn Computer." I say it's EO for computers--every computer runs equally slow.

      They say it is for security, but actually, it consolidates the problems. You comprimise one, you comprimise all of them. And there is a major issue with SDC and SMS, as patches have not been pushed as of late. Also, SAV is out of date, and the only way to fix it is to uninstall, then reinstall.

      As a result, the format process has gone from a simple ghost image with a 20 min lan load, to a 2 hour SDC load and 30 minutes of manual system patching! It's all good tho, I'm union, and get paid by the hour!

    2. Re:In the US Air Force, this has already happened by skogs · · Score: 1

      I work in the comm unit on base too.

      SDC isn't a magic wand...but it does help.

      As far as the other guy saying it takes forever....what exactly did you do before? Imaging the drive and doing necessary patches were still required. Still had to add machine to active directory. Still had to make sure the damn card reader worked so people could log in. SDC is just like everything else - different, but mostly the same.

      personally, I wish we had a *nix standard desktop configuration...then it wouldn't slow down as time went on. It may still be slow, but at least I'd know it would work forever.

      Oh yes....and isn't it wonderful reloading machines simply because they were overseas on the other domains and having them screwed up for life when they come back? I love that. I especially like users saying they need everything on it right after I wipe it.

      --
      Who is this that even the wind and the waves obey Him? Surely this computer must submit also!
    3. Re:In the US Air Force, this has already happened by Frosty+Piss · · Score: 1

      We have a custom image - Comm approved, of course - that installs the SDC as well as all the apps we normally need. But the machines do seem slower. This, however, should resolve itself in our next hardware buy, as the new machines will be Vista ready (even though we don't run it), so they are "loaded".

      --
      If you want news from today, you have to come back tomorrow.
    4. Re:In the US Air Force, this has already happened by A_Non_Moose · · Score: 1

      In the US Air Force, this has already happened in the form of the Standard Desktop Configuration Image that we install on all PCs. This started the middle of last year.

      I became aware of this via relatives whom work in a secure environment...something along the lines of:

      "The computers were so fucked up today because of the secure network/machine config/etc that they had to
      wait 6+ hours before it was fixed".

      So, yeah, so secure it can't be used.

      Oh, wait...windows...never mind.

      --
      Have you read the moderator guidelines? Well, have you, PUNK? (and I want a Karma: Gnarly option)
    5. Re:In the US Air Force, this has already happened by Anonymous Coward · · Score: 0

      You're so full of bullshit, it's not even worthy of this response. Your "relatives" are full of shit.

  70. Yes, and that's the point: Windoze is less secure by twitter · · Score: 1

    Don't you have to finish the math before making judgment positive or negative, i.e.

    Yes, but that's what this tireless M$ Defender is trying to deny without actually having the nerve to say it. All you really need to know is that botnets are more prevalent of Windoze than any other platform to know that more than 1 in 4 of Windoze computers are part of a botnet. Study after study has shown the relative security of the platforms. Macthorp and his sock puppets continue to beat the "Windoze is most secure OS" drum anyway they can. Saying so directly will get you laughed at, so they are trying to build an unreasonable fear of other OS. Only the most naive of M$ users or hard headed of fanboys could equate the service records of M$ with any other software.

    --

    Friends don't help friends install M$ junk.

  71. Monkeyman? by Life2Short · · Score: 1

    Who the hell promoted you from "monkeyboy?"

  72. Re:Yes, and that's the point: Windoze is less secu by dedazo · · Score: 1
    There's a difference between being "pro-Microsoft" or as you succintly put it, "tireless M$ defenders", and being anti-bullshit.

    Your problem is that you can't distinguish between the two. But that's an issue you seem to be afflicted with anyway.

    --
    Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
  73. Secure computing by cdrguru · · Score: 1

    Rule 1: If if can have its programming altered in the field, it is not secure.

    Rule 2: If it accepts executable instructions from any unauthorized source, it is not secure.

    Rule 3: Any deviation from an assigned purpose can be considered to be a security breach.

    It is difficult to have a toaster or microwave oven infected by malware or part of a botnet. You want security? Start using the "appliance" model and there will be security. A general-purpose computer that can have new programming installed is obviously a security risk and giving the user the ability to install such programming is an invitation to disaster.

  74. What the memo doesn't say by kaaona · · Score: 1

    1. It talks about desktop security configurations. Alan Paller from SANS talked about desktop applications, but Clay Johnson's actual memo does not.
    2. It says nothing about servers.
    3. There's no mention of Solaris, AIX, OS/X, Linux, BSD, VMS, or any other non-Microsoft operating system in common use.
    While it's true the total number of Windows XP/Vista desktops will far outnumber all the server and non-Windows systems, by ignoring them this memo is no more of a security solution than "3 cups of flour" is a recipe for bread.

  75. Vista Secure by fyoder · · Score: 1

    Home Basic, Home Premium, Business, Enterprise, Ultimate... There is no Vista Secure. Given the demand, how did Microsoft miss that one?

    --
    Loose lips lose spit.
  76. one and one and one is one by twitter · · Score: 1

    There's a difference between being "pro-Microsoft" or as you succintly put it, "tireless M$ defenders", and being anti-bullshit. Your problem is that you can't distinguish between the two.

    You listed three "personalities". Which one do you claim for the dedazo attack troll sock puppet?

    --

    Friends don't help friends install M$ junk.

    1. Re:one and one and one is one by dedazo · · Score: 1
      I don't know twitter. But would you like to clue me in as to whose "sockpuppet" I am? I must admit I've become a little confused about that.

      Also, is your sockpuppet relevant here, or is that a "righteous" sockpuppet account?

      --
      Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
  77. Re:Yes, and that's the point: Windoze is less secu by Keith+Russell · · Score: 1

    You're the one denying that "1 in 4 computers" could include operating systems that you don't loathe and despise with every beat of your blackened, shriveled heart. Why else would you continue to link to your own comments on the subject, instead of the original, OS-agnostic source?

    By the way, here's that original source article that Twitter can't bring himself to link to.

    --
    This sig intentionally left blank.
  78. Catch 22. by twitter · · Score: 1

    ... when dealing with the federal government, it is where there is a regulation there is always a way to get an exception to that regulation.

    Yes, but when they really care the exceptions are circular. An obvious exception to the new Windoze lockdown is to run gnu/linux. The obvious block is to make it so most people can't do that.

    Corporate welfare policies require frequent M$ license purchases. It's a pity they don't support other nice American companies like Red Hat, IBM, Novel, Mepis, Ubunto, and so on and so fort that should obviously be the low bidders.

    --

    Friends don't help friends install M$ junk.

  79. Bandaid for your gunshot wound? by Anonymous Coward · · Score: 0

    If my work was intended to benefit society, I wouldn't want it within 10 miles of any Windows system. The best security for Windows is to not use Windows.

  80. Hey! I work for the government, YIC! by spun · · Score: 1

    You know, people have the impression that people in government are lazy, doing nothing but posting on Internet message boards all day. Well, I for one am not going...

    Oooh! Somebody brought donuts! BRB

    Anyways, as I was saying... ah, you know what? All that sugar made me sleepy. I could use a little nap. Hell, it's Friday, I'll finish this post next week.

    Are you staying 'till five? Can you clock out for me?

    --
    - None can love freedom heartily, but good men; the rest love not freedom, but license. -- John Milton
  81. Common Criteria CAPP/EAL4 by flyingfsck · · Score: 1

    I thought that the CC already applies to all government desktop systems?

    --
    Excuse me, but please get off my Pennisetum Clandestinum, eh!
    1. Re:Common Criteria CAPP/EAL4 by Watson+Ladd · · Score: 1

      CC only says the OS must adhere to a document the vendor provides. The document for Windows says that it doesn't break if no one malicious attacks it. It is EAL4, but that is completely meaningless as the specification it follows exactly is worthless.

      --
      Inventions have long since reached their limit, and I see no hope for further development.-- Frontinus, 1st cent. AD
  82. Impenetrable fenestration! by Equis · · Score: 1

    Are they in a bad part of town or something? Are they going to use bars or Lexan?

  83. I see dollar signs by Anonymous Coward · · Score: 0

    The net re$ult will be identically configured computer$ with fewer application$, a bot maker'$ paradi$e. The comply/no-comply label give M$ more veto power over application$ and that will reduce the number of application$ that can be u$ed. Everything mu$t now be done the M$ way on Windoze, $o the wor$t practice$ with the wor$t track record have been mandated. The identical $etting$ are only more "$ecure" until $omeone break$ them and then they are all equally ho$ed.

    1. Re:I see dollar signs by webheaded · · Score: 0

      Thank you for that. That is what I see with every idiot that refuses to just type Microsoft and elects to say M$ or Micro$oft. Same goes for the idiot above that insists upon saying Windoze. LOL UR COOL GUY!! U BASH MICROSOFT LOLOLOLOL. Grow up. If you have an argument against it, go for it, but don't throw in your stupid ass anti-microsoft bullshit all over the place in it; that makes you look like a jackass. I'm not a Microsoft fanboy, but I can at least type the fucking word correctly.

      --
      "Those who would sacrifice essential liberties for a little temporary safety deserve neither liberty nor safety." - BenF
  84. They care? Did they liberate you? by twitter · · Score: 1

    I was the network manager for a bank a while back, and during our audits were were given a list of registry/active directory policies required to get a good rating by those auditors. They also had a list of services that needed to be disabled as well (unless there was a compelling business case for those services).

    Did it make a difference or was it just more busy work? Did they have you get rid of IE, Outlook Express and other trouble makers that lead to propagation like this? Even if you do get rid of those applications, can you really secure the underlying software without software freedom? I know that might be difficult at first, but it's easier than the continual patch and upgrade train most companies are already on.

    --

    Friends don't help friends install M$ junk.

  85. Re:Yes, and that's the point: Windoze is less secu by twitter · · Score: 1

    You're the one denying that "1 in 4 computers" could include operating systems that you don't loathe and despise with every beat of your blackened, shriveled heart.

    No, I just think the botnet rate for all non M$ OS is vanishingly small. Show me a study that proves something different, you insulting pest.

    --

    Friends don't help friends install M$ junk.

  86. I see dollar signs by Anonymous Coward · · Score: 0
    We will $ee if M$ will give them permi$$ion for their $oftware to work. Programmer$ for anti-viru$, Net$cape, Correl, IBM and everyone but M$ have complained about i$$ue$ like thi$ in the pa$t. M$ only wi$he$ it had been $o ea$y a$ that to get rid of tho$e former competitor$ and their wi$h appear$ to have come true.

    The ultimate lo$er i$ M$, of cour$e. What will they be left with when they drive everyone el$e off their platform? How well paid will programmer$ be if their only potential employer ha$ to give up mo$t of their profit$ to M$?

  87. Standards needed? Try common sense. by denis-The-menace · · Score: 1

    Many shit pieces I see:

    -install at the root of C:\ (users and power users have no Write perms there by default)
    -are hard coded that way so you can't move them to program files.
    -Change permissions of folders to Full Control for Everyone group (security.. what's that?)
    -only work for the user account that installed it.
    -are packaged in Installshit Quasi-MSI format that can't run Unattended or need Setup.exe
    -phone home without telling you (ie Nero, MS updates, WGA)
    -con you installing patches to you application that cripples a feature of the app to force you to upgrade (QuickBooks)
    -come bundled with spyware/adware (Adobe Acrobat reader 5x and up)

    MS and their MSI standard is not helping much:
    -Setting Permission using MSI's "Lock Permissions" is a joke since it trashes and replaces existing permissions. Must use SETACL (http://setacl.sourceforge.net/) that will do inherited perms on anything
    -Setting Permission on services is not doable in MSI natively (again use SETACL)
    (Wise and Installshield are not helping here either, too busy changing owners)
    -In any version of Windows NT, Users cannot see the calendar by double clicking the time in the system tray. (so we gave end-users Power user accounts!!)
    -IE is part of the OS and runs funny with a User account
    -You can't defrag HDs without being an Admin.

    --
    Obama's legacy: (N)othing (S)ecure (A)nywhere and (T)error (S)imulation (A)dministration
    1. Re:Standards needed? Try common sense. by drsmithy · · Score: 1

      In any version of Windows NT, Users cannot see the calendar by double clicking the time in the system tray. (so we gave end-users Power user accounts!!)

      That's because it's not a "calendar", it's a tool for setting the system time.

      There is a specific GPO for allowing users to do so, as well, so there's no need to make them Power Users just to cover that functionality (although then your users will be able to change the system time, which is itself a security hole).

      IE is part of the OS and runs funny with a User account

      IE is a user space application that works fine in any regular - hell, even 'guest' - user account.

      You can't defrag HDs without being an Admin.

      Really ? You can't read and write to arbitrary parts of the disk without elevated privileges ? You find this surprising ?

  88. Re:Yes, and that's the point: Windoze is less secu by Keith+Russell · · Score: 1

    Show me a study that proves something different

    The way you've shown anything that proves the estimates you continually cite as fact?

    I can not state with authority that 1 in 4 computers are in a botnet, because I am citing an unscientific estimate. Likewise, you can not state with authority that 1 in 4 Windows installations are in a botnet, because you are (indirectly) citing an unscientific estimate. Not that it stops you from trying.

    In fact, any time somebody asks you to cite a source for your outrageous assertions, you quickly clam up. We're still waiting for your proof that Microsoft litigated the Zaurus out of existence.

    So what's it going to be, Twitter? Accountability or spite? Your choice.

    --
    This sig intentionally left blank.
  89. I see dollar signs by Anonymous Coward · · Score: 0
    Once the $etting$ are $pecified, M$ can make the $y$tem do a$ they plea$e. What, do you think Uncle $am i$ going to give up patch Tue$day? The whole point i$ to make it ea$ier to apply patche$. It won't really work, of cour$e, becau$e M$ and other$ will keep playing the $ame anti-competitive trick$. When an application doe$ not work with the $etting$, it not Windoze i$ rejected.

    The net re$ult i$ contrary to commodity computing. The whole rea$on for u$ing M$ i$ to gain acce$$ to cheap hardware and a univer$e of $oftware. Reducing your choice in $oftware goe$ a long way toward making your hardware worthle$$. A fancy computer that doe$ not do the ta$k you want it to i$ not doing you any good. The propo$ed flexibility will inevitably $ink to Dell $oftware in$tall option$ and people who want to get work done with $pecialized program$ will be forced off Windoze or $uffer with $econd rate $oftware on expen$ive hardware.

    The $ame kind of program would not be $uch a di$a$ter in the free world. Fir$t, it'$ ea$y to tell what work$ and upgrade$ are already painle$$. $econd, if $omething doe$ not work, it will be fixed quickly. Third, and mo$t importantly, the $oftware doe$ not have "owner$" who want to me$$ with other $oftware "owner$".

  90. Common Registry settings? by PPH · · Score: 1
    Does this mean common hardware? And common applications? It must, or the registry will necessarily be different.

    Hey, as long as they standardize:

    BUGS=OFF

    everything should be just fine.

    --
    Have gnu, will travel.
  91. I see dollar signs by Anonymous Coward · · Score: 0
    That could be, but M$ can't win for lo$ing. It would be much harder for M$ to blame the u$er for M$ problem$ if they really told the u$er exactly what to do. In the end, it'$ all about M$ and non free $oftware. Non free $oftware can't be a$ good or work together the $ame way free $oftware doe$. It ha$ obviou$ problem$ and the obviou$ $olution$ are difficult or impo$$ible.

    Two $olution$ are code $haring and configuration control. A$ you and other$ $ay, a $maller code ba$e i$ cheaper and more $ecure. Competitive pre$$ure$ keep non free companie$ from $haring librarie$ and their licen$ing make that mo$t obviou$ co$t $aving$ impo$$ible anyway. Everyone ha$ to reinvent every wheel or put them$elve$ at the mercy of their non free competitor$. The $econd mo$t obviou$ co$t $aving$ mea$ure i$ configuration control, but that too i$ impo$$ible in the non free world. The u$er can flip $witche$, but the $witche$ them$elve$ will change a$ application$ change out librarie$. Without the $ource code, the u$er doe$ not really know what the $witche$ do anyway.

  92. Understanding Estimates. by twitter · · Score: 1

    I can not state with authority that 1 in 4 computers are in a botnet, because I am citing an unscientific estimate.

    I'm not asking you to better Michael Dell and Vint Cerf's estimate, I'm asking you to show me evidence of any significant gnu/linux worm. There's nothing wrong with that estimate, if you use it in rough way and that's what I've done. A one in four estimate means that they pegged their estimate around there. Based on Windoze survival time studdies, I'd say the rate is more like 95%, but you don't really care for my opinion so I'll quote Dell who has much to gain from underestimating the problem. Now, it's your turn. Go ahead and find me some news about any significant gnu/linux worm or quit wasting my time. If you can't, just adjust that 25% up by M$'s smaller than unitary share of internet connected computers because the botnet is all M$ powered.

    --

    Friends don't help friends install M$ junk.

  93. I wish XP allowed me to secure my PC by amigabill · · Score: 1

    I'm redoing my PC after scraping he hard drive clean. Things were getting weird, my wireless network card isn't as dead as I thought it was, something really wasn't right. But last time around my regular user was an administrator user, which is probably a bad idea. So this time I'm trying to do better, have an admin user to do all installing and configuring, regular user accounts I actually use to do stuff would only be limited users under XP.

    Hah! You can't freakin even do that. Half-Life 2 and/or Steam requires you to be an administrator for it to run. TaxCut requires you to be an administrator for it to run. How the heck am I supposed to secure my machine in a more responsible way if none of my software is allowed to run that way? WTF?

    I doubt I'd be able to get this sort of Vista, even if it was decided that it was a good configuration. Considering compatibility, resource requirements, slowdowns, etc. I don't want Vista at all right now anyway, maybe in a year or two. Sucks that I can't buy a laptop with XP anymore, I should have got something before Vista Day. :(

  94. Worms? by dedazo · · Score: 1

    show me evidence of any significant gnu/linux worm

    Worm? What do worms have to do with botnets? Oh, I know. You've realized and accepted that Linux botnets do exist and they're not all "M$ powered". How do those 10,000 IRC zombies get pwned twit? Magic? Or operator stupidity? How many are there out there?

    Funny that. You understand that all I need is a single happy internet-facing Server 2003 machine to essentially invalidate your implied connection between the "futility" of patching (didn't you call it "silly patches" a few posts ago?) Windows to the probablity of that box being in a botnet. Just one. That's it. That takes care of your beloved but risible "half life" statistics that deal in unpatched machines (circa 1999 no less), as well as your insane "M$ is to blame for everything" argument.

    Reality sucks, doesn't it?

    --
    Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
  95. Bush Doesn't Know... by lordSaurontheGreat · · Score: 1

    A "Secure Windows?" I think Bush mispoke (again) and really meant to say "Linux." Personally, I'd settle on Apple, too. Actually, I think we'd see a paradigm shifting without a clutch if anyone in government got an Apple PC...

    --
    Consider yourself spoken to.
  96. Valuable targets? by El_Oscuro · · Score: 0

    You mean like google, amazon, etrade, or paypal http://www.netcraft.com/? Nah, I guess hackers would never consider those valuable targets.

    --
    "Be grateful for what you have. You may never know when you may lose it."
  97. oh duh. by WeeBit · · Score: 1

    a few idiots undo all of the mandatory security settings. Then Congress informs the White House they have a problem.

  98. Vista Secure!?!?!? by kb0hae · · Score: 1

    Vista Secure?
    ROTFLMAO!!!!!
    Anyone has to have the utmost nerve to even imply that Vista could have even a remote possibility of being secure !!!!!!!!!!!!!!!!!!!!!

  99. Why not use a JPEG proxy? by cheekyboy · · Score: 1

    Why not just have all machines have zero access to the internet except via
    a special proxy that converts every single website externally accessed that is
    NOT part of a whitelist, to be converted at the server side into a big JPEG so that its still readable
    and clickable using image maps, but there is zero html rendering/js/java. If its not part of
    the good white list , its jpeged. Otherwise, its ok to pass through.

    --
    Liberty freedom are no1, not dicks in suits.
  100. Re:They care? Did they liberate you? by zerofoo · · Score: 1

    Actually, our biggest headaches came from SQL injection attacks against our internet banking application. The MS stuff never really gave us a problem thanks to many layers of security (intrusion detection, content filters, restricted internet access, anti-virus, low-default permissions....etc).

    Still, an internet banking application, that was open source, may have prevented those SQL injection vulnerabilities due to many eyeballs looking at the code.

    -ted