Windows IT Pro is the leading independent community for IT professionals deploying Microsoft Windows server and client applications and technologies.
  
  
  Advanced Search 


October 03, 2009

Security Steps: How to block the installation of the Chrome Frame add-on for Internet Explorer

RSS
Subscribe to Windows IT Pro | See More Systems Administration Articles Here | Reprints | Or get the Monthly Online Pass—only $5.95 a month!
back to blog index

Google has recently released an add on for Internet Explorer named Chrome Frame which alters the functionality of the Microsoft browser, ostensibly to allow specific applications, notably Google’s new Wave web application, to function for users of Internet Explorer.

Organizations that are reluctant to allow add-ons to be installed in Windows Internet Explorer can block these add-ons through the Add-On Management policy node of Group Policy. This node is located under the Administrative Templates\Internet Explorer\Security Features node of both the Computer Configuration and User Configuration group policy areas. These policies function as follows:

  • Add-on List. This policy allows you to specify which add-ons are allowed or denied by Internet Explorer. This policy can be used in conjunction with the Deny All add-ons unless … policy so that only specifically authorized add-ons can be used with Internet Explorer.
  • Deny All Add-Ons Unless Specifically Allowed In The Add-On List. If you enable this policy, add-ons cannot be used unless specifically allowed in the Add-On list policy. If you do not enable this policy, the block and allow rules in the Add-On list policy will apply, however add-ons not covered by the list will be able to be used.

To block the use of Chrome Frame, you can specifically block the add-on using the Add-On list. You need to know the CLSID of Chrome Frame (which you can locate using a search engine) and set the value in the Add-On list to 0, as shown in the exhibit. Setting the value to zero blocks the use of the add-on. A better approach is to know the CLSIDs of all authorized add-ons and to have these listed in the policy, blocking anything that you have not explicitly authorized.

End of Article



Reader Comments

You must be a registered user or online subscriber to comment on this article. Please log on before posting a comment. Are you a new visitor? Register now





Search Hyperbole, Embellishment, and Sys Admins
 
Hyperbole, Embellishment, and Sys Admins
NOVEMBER 2009
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30      
or

 Recently in Hyperbole, Embellishment, and Sys Admins
Security Steps: Restricted Groups Policies
Make a Comment
Security Steps:Use Syskey on Windows 7 to encrypt the SAM to stop someone resetting the local admin password on a netbook
Make a Comment
WSUS, Server 2008 R2 and BranchCache
Make a Comment
Security Steps: How to block the installation of the Chrome Frame add-on for Internet Explorer
Make a Comment
Security Steps: Firing a Systems Administrator

Last Comment
Even when the user's account is disabled, those same admins also often know the credentials of privi...
(2 Comments)

More blogs about technology,
software, and Windows.

Windows IT Pro Home Register FAQ for Windows WinInfo News
Europe Edition About Us Contact Us/Customer Service Media Kit Affiliates / Licensing  
SQL Server Magazine Office & SharePoint Pro DevProConnections IT Job Hound
Left-Brain.com Technology Resource Directory asp.netPRO ITTV Windows SuperSite 
 
 Windows IT Pro is a Division of Penton Media Inc.
 © 2009 Penton Media, Inc. Terms of Use | Privacy Statement