http://www.theregister.co.uk/2007/03/22/us_common_security_config/

Changes in US government purchasing policies due to come into effect this summer could have a huge effect on computer security, particularly for Windows desktops.

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”. 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.

This is an interesting article, and an interesting development, the government IT security team have issued a statement requiring applications to be tested against a ‘base’ build, it’s right though, the security patching process can be resource intensive enough without application dependencies on set services or configurations on the desktop, check it out.

Keeping a standard platform is a good way of limiting issues with the platform and reducing therefore your support cost.

Related posts:

  1. Talking about virtualization for local government Eweek Europe Local government is stealing a march on central...
  2. Collaboration to meet Green ICT targets in government Cisco Improved Collaboration Across Government Agencies Key To Meeting Public...
  3. Interviewing a server build engineer For the second time, I had a conversation with a...
  4. Public technology using cloud is fine, but stabilize your core first Out-law In its Digital Britain report the Government said that...

Related posts brought to you by Yet Another Related Posts Plugin.

Bookmark and Share

Leave a Reply