When set properly, a network browser's security settings can help protect the browser and its user and computer from malicious code. A browser's security settings can be altered, however. Malicious code may alter a browser's security settings to misuse the browser. Users may also alter these settings. A user can alter settings in response to an application or website instructing the user to change his or her settings to improve the browser's performance, for instance.
Security settings altered to reduce a browser's security can place the computer on which the browser operates, a user, and the network browser at risk. For example, a browser having improper security settings can permit malicious code to track a user's use of his or her browser and invade the user's privacy.
Tools are described that notify a user of a security risk in a network browser. The tools can determine that a security setting of a network browser poses a security risk and notify the user of this risk. In some situations the tools also enable a user to reduce the security risk utilizing a single user action. This single user action can alter one or multiple security settings responsible for the security risk.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
The same numbers are used throughout the disclosure and figures to reference like components and features.
Overview
The following document describes system(s) and/or method(s) (“tools”) for notifying a user of a security risk in a network browser. In one embodiment, the tools determine that a security setting of a network browser poses a security risk and notifies the user of this risk. In another embodiment, the tools notify a user of a security risk and enable the user to reduce this security risk with a single user action. This single user action can alter one or multiple security settings responsible for the security risk.
Exemplary Operating Environment
Before describing the tools in detail, the following discussion of an exemplary operating environment is provided to assist the reader in understanding where and how the tools may be employed. The description provided below constitutes but one example and is not intended to limit application of the tools to any one particular operating environment.
The predetermined settings/risk table maps possible security settings for the network browser with a security risk assessment for these settings. Particular settings may be assigned a risk level of unsafe or safe. Those given an unsafe risk level can be those settings that permit a user's browsing experience to be damaged, a user's computer to be damaged, and the like. This table enables a Boolean assessment of risk (two levels—unsafe and safe) though it may also enable a range of assessment, such as three or more levels. For relatively unsophisticated users, two levels may be appropriate so as not to confuse them. For some other users—like information technologists—many levels may be more appropriate.
The communication network enables communication between the computer and the network computer and may comprise one or more of an intranet, such as a company's internal network, the Internet, and the like. Network computer 106 is shown comprising one or more network processor(s) 124 and network computer-readable media 126. The network processor(s) are capable of executing the network computer-readable media.
Notifying a User of a Security Risk
Referring to
Any of blocks 202, 204, and 206 may be performed prior to block 208. Block 208 may act in response to any of these blocks or otherwise. In one embodiment, for instance, block 208 acts responsive to a call requesting a security risk of the browser.
Block 202 receives an indication that a security setting for a network browser has been altered. The security setting may have been altered by a user, another application, or malicious code. Block 204 receives an indication that a network browser has been started, such as on startup responsive to a user opening the browser. Block 206 receives a user's selection to view a network browser's security settings or security risks. This selection can be received through a control panel for the network browser or though a user interface related to the network browser's security, some of which are described below.
Block 208 determines whether one or more security settings of a network browser pose a security risk. Block 208 may do so without user interaction, such as automatically following blocks 202 or 204.
In an embodiment described with elements of environment 100, security module 118 compares the network browser's altered security settings 116 with predetermined settings/risk table 122. Each of the altered security settings corresponds to a risk assessment in table 122. The security module can assign a risk level of unsafe to the network browser's security settings if any of its settings correspond to an unsafe risk in table 122.
By way of illustration, consider an exemplary predetermined settings/risk table 122 shown in
The security settings for each action in each zone are marked “E” for enable the action, “P” for prompt a user for permission to enable the action, and “D” for disable the action. Some action/zone settings are left blank because an assessed security risk does not depend on the setting for these actions in their respective zones. Security settings on the left of each zone are considered safe settings. These safe settings may match default settings for the browser (e.g., default security settings 114). The safe settings are shown at 306a for Internet zone 304a, 306b for local intranet 304b, 306c for trusted zone 304c, and 306d for restricted zone 304d.
The security settings on each zone's right are considered unsafe (if any are marked). The unsafe settings are shown at 308a for Internet zone 304a and 308d for restricted zone 304d. As shown, a security setting enabling the following actions in the Internet zone are considered unsafe: downloading signed ActiveX controls; downloading unsigned ActiveX controls; initializing and scripting ActiveX controls not marked as safe; installing desktop items; launching applications and unsafe files; and launching programs and files in an IFRAME. Also as shown, all actions in restricted zone 304d are consider unsafe if they are enabled or prompted except for launching programs and files in an IFRAME. For this action in the restricted zone, a prompt security setting is considered safe and an enable security setting unsafe.
Also by way of illustration, consider exemplary altered security settings 116 shown in
Security module 118 compares the network browser's current security settings (here altered settings 116) with predetermined settings/risk table 122. The security module determines that three security settings are unsafe by comparing the security settings shown in
Block 210 notifies a user of a potential problem by notifying the user that one or more security settings pose a security risk. Block 210 may inform a user without the user's interaction, such as responsive to a user starting up the browser (e.g., block 204) or an alteration to the browser's security settings (e.g., block 202).
Block 210 can act through user interface 120 of security module 118 to inform a user through various audio and/or visual interfaces. Four exemplary visual interfaces are provided below.
Referring to
Block 210 can provide the notification interface in response to a network browser being started (e.g., block 204). Dialog notification interface 500 comprises an option to ignore the warning and continue startup; this is implicit in information bar notification interface 502. A user can ignore the dialog's warning by selecting ignore control 508.
Responsive to a user selecting or clicking on the information bar notification interface, additional controls are presented with options interface 510. The options interface and the dialog notification interface enable a user to fix the security problem through a restoration control 512a or 512b, proceed to an internet-options user interface (e.g., interface 600 of
Referring to
Security settings interface 600 also enables a user to fix security problems all at once or based on a zone. The user may do so through selecting a restore-zone-to-safe-level control 604 or restore-all-zones-to-safe-level control 606. Interface 600 also enables a user to proceed to a custom user interface by selecting a zone custom control, here marked at 608. These are discussed in greater detail below.
Referring to
Custom settings interface 700 provides a scrollable list of security settings for the Internet zone. The security settings that pose a security risk are highlighted (shown with shading at 702). These security settings are those noted above as posing a risk, namely first and second settings 402 and 404 of
User interface 120 informs the user of the settings that pose the security risk, the current setting, and/or the safe setting. This is shown by example in interface 700. The settings that pose the risk are marked 704 and 706 (corresponding to 402 and 404 of
Block 212 enables a user to reduce the security risk. Block 212 can do so through a single user action, such as pressing an enter key or clicking on a control. Block 212 can also enable this reduction in security risk by enabling a user to alter security settings one-by-one or in groups.
In the illustrated interfaces described above, user interface 120 enables a user to reduce a network browser's security risk with a single click on control 512a or 512b, control 604, control 606, button 718, button 720, or control 722. By selecting any of the controls 512a, 512b, 604, 606, or 722 a user may reduce or eliminate a security risk for multiple security settings.
For all three unsafe security settings 402, 404, and 406, block 212 enables the user to reduce or eliminate the risk posed by these settings with a single user action. User interface 120, for instance, enables a user to select restoration control 512a or 512b in notification interfaces 500 or 502, respectively, restore-all-to-safe control 606 in security settings interface 600, or selectable reset settings control 722 in custom settings interface 700. For security settings of a particular zone (e.g., either 402 and 404 or 406) block 212 enables a user to reduce or eliminate risk by selecting restore-zone-to-safe-level control 604 of the security settings interface.
Block 214 alters one or more security settings to reduce a network browser's security risk. Block 214 can do so responsive to a user's interaction, such as in response to a user selecting a control to alter security settings to a safe level.
Responsive to the user selecting to make network browser 112's security settings safe, security module 118 changes the security setting of “E” shown at 402 and 404 in
Conclusion
The above-described tools notify a user of a security risk in a network browser. They may also determine whether there is a security risk and enable a user to reduce this risk. In so doing, a user may be able to avoid or cure security risks in his or her network browser that may damage the browser or otherwise comprise his or her computer system. Although the tools have been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claimed system, method, and/or computer-readable media.
Number | Name | Date | Kind |
---|---|---|---|
5404488 | Kerrrigan et al. | Apr 1995 | A |
5649186 | Ferguson | Jul 1997 | A |
5819284 | Farber et al. | Oct 1998 | A |
5880767 | Liu | Mar 1999 | A |
5926796 | Walker et al. | Jul 1999 | A |
5974549 | Golan | Oct 1999 | A |
6085186 | Christianson et al. | Jul 2000 | A |
6094657 | Hailpern et al. | Jul 2000 | A |
6282546 | Gleichauf et al. | Aug 2001 | B1 |
6366912 | Wallent et al. | Apr 2002 | B1 |
6411331 | Sansom-Wai et al. | Jun 2002 | B1 |
6434745 | Conley, Jr. et al. | Aug 2002 | B1 |
6544295 | Bodnar | Apr 2003 | B1 |
6594692 | Reisman | Jul 2003 | B1 |
6694431 | Binding et al. | Feb 2004 | B1 |
6708172 | Wong et al. | Mar 2004 | B1 |
6732102 | Khandekar | May 2004 | B1 |
6766458 | Harris et al. | Jul 2004 | B1 |
6775772 | Binding et al. | Aug 2004 | B1 |
6874084 | Dobner et al. | Mar 2005 | B1 |
7065644 | Daniell et al. | Jun 2006 | B2 |
7143084 | Rinearson et al. | Nov 2006 | B1 |
7257564 | Loughmiller et al. | Aug 2007 | B2 |
20020108115 | Palmer | Aug 2002 | A1 |
20020116630 | Stehlin | Aug 2002 | A1 |
20020124172 | Manahan | Sep 2002 | A1 |
20020156905 | Weissman | Oct 2002 | A1 |
20020174201 | Ramer et al. | Nov 2002 | A1 |
20020184491 | Morgan et al. | Dec 2002 | A1 |
20020194151 | Fenton et al. | Dec 2002 | A1 |
20030014406 | Faieta et al. | Jan 2003 | A1 |
20030028762 | Trilli et al. | Feb 2003 | A1 |
20030117511 | Belz et al. | Jun 2003 | A1 |
20030135504 | Elvanoglu et al. | Jul 2003 | A1 |
20030167402 | Stolfo et al. | Sep 2003 | A1 |
20040003097 | Willis et al. | Jan 2004 | A1 |
20040046885 | Regan et al. | Mar 2004 | A1 |
20040093563 | Pasquali | May 2004 | A1 |
20040143683 | Greenwood | Jul 2004 | A1 |
20040181753 | Michaelides | Sep 2004 | A1 |
20040225749 | Pavlik et al. | Nov 2004 | A1 |
20040230676 | Spivack et al. | Nov 2004 | A1 |
20040250115 | Gemmel et al. | Dec 2004 | A1 |
20050010595 | Brown et al. | Jan 2005 | A1 |
20050015452 | Corson | Jan 2005 | A1 |
20050033657 | Herrington et al. | Feb 2005 | A1 |
20050038717 | McQueen, II | Feb 2005 | A1 |
20050050460 | Bedingfield, Sr. | Mar 2005 | A1 |
20050065906 | Romero | Mar 2005 | A1 |
20050097180 | Abdelhak | May 2005 | A1 |
20050108227 | Russell-Falla et al. | May 2005 | A1 |
20050119910 | Schneider | Jun 2005 | A1 |
20050119913 | Hornreich et al. | Jun 2005 | A1 |
20050165615 | Minar | Jul 2005 | A1 |
20050171836 | Leacy | Aug 2005 | A1 |
20050216439 | Kawakita | Sep 2005 | A1 |
20050256768 | Robinson | Nov 2005 | A1 |
20050268100 | Gasparini et al. | Dec 2005 | A1 |
20060053293 | Zager et al. | Mar 2006 | A1 |
20060218403 | Sauve et al. | Sep 2006 | A1 |
20060230021 | Diab et al. | Oct 2006 | A1 |
20070061711 | Bodin et al. | Mar 2007 | A1 |
20070094389 | Nussey et al. | Apr 2007 | A1 |
20070100836 | Eichstaedt et al. | May 2007 | A1 |
20070100959 | Eichstaedt et al. | May 2007 | A1 |
20070130518 | Shavit et al. | Jun 2007 | A1 |
20070282973 | Chapman et al. | Dec 2007 | A1 |
Number | Date | Country |
---|---|---|
2496672 | Feb 2004 | CA |
WO 0207013 | Jan 2002 | WO |
WO 2004107216 | Dec 2004 | WO |
WO2005027402 | Mar 2005 | WO |
Number | Date | Country | |
---|---|---|---|
20070016954 A1 | Jan 2007 | US |