Symantec Corporation

Rowan Trollope

Shaun P Cooley

Carey S Nachenberg

Henri J Isenberg

Chandrasekhar Cidambi

Lipphei Adam

Richard Scott Sadowsky

Caskey L Dickson

A portable hardware device such as a USB memory stick is used to provide parental locking functionality to a computer. When the device is coupled to the computer, the computer is unlocked and allowed to operate normally. When the device is not coupled to the computer, the computer is locked, and some or all of the computing functionality is blocked. This enables parents to lock and unlock a child's computer with a 'key.' A detecting module detects the coupling and uncoupling of devices to the computer. When a device is coupled to the computer, an identifying module identifies the device by reading its unique identifier, and determining whether the coupled device is the one being used as the key. If so, the computer is unlocked, and allowed to operate. If not, a blocking module blocks at least some capabilities of the computer.

Commodity hardware based parental control device

Techniques for providing protection against unsafe links on a social networking website are disclosed. In one particular exemplary embodiment, the techniques may be realized as a method for providing protection against unsafe links on a social networking website comprising: receiving, from the social networking website, user profile data associated with a user of the social networking website, scanning, from the user profile data, a plurality of links, accessing a safety rating for each of the plurality of links, and outputting, to a client device associated with the user, a link analysis report that indicates the safety rating of one or more of the plurality of links.

Techniques for providing protection against unsafe links on a social networking website

A user-assisted security software program alerts a user when a new pop-up is displayed from a suspicious source application. If the source application may be suspicious if it has a low reputation. Displayed in connection with the pop-up, the alert prompts the user to indicate whether the source application that generated the pop-up should be trusted. If the user indicates that the source application is not trusted, the security software declares the source application to be malicious. The malicious code can then be dealt with, such as by removing it from the computing system, blocking it from generating new pop-ups, and preventing further network communications. The user's feedback about the source application may also be used to adjust the application's reputation.

User-assisted security system

HTTP requests initiated from a web browser of a client computer system are proxied prior to release to a router, such as a home router. HTTP requests identifying a referrer URL corresponding to routable, public IP address and a target URL corresponding to a non-routable, private IP address are determined to be indicative of a drive-by pharming attack, and are blocked from sending to the router. HTTP requests not identifying a referrer URL corresponding to a routable, public IP address and a target URL corresponding to a non-routable, private IP address, the HTTP request are not determined to be indicative of a drive-by pharming attack, and are released for sending to the router. In some embodiments, an HTTP response received in response to a released HTTP request is proxied prior to release to the web browser. An HTTP response having content of type text/html or script is modified as indicated to prevent malicious activity and released to the web browser.

Client side protection against drive-by pharming via referrer checking

A boot failure recovery system operates to diagnose a failed system boot in a computer operating system which boots by bootstrapping from a boot sector (,) of a storage medium (,) using configuration information (,). The boot failure recovery system includes an agent (,) which monitors operating system files used during system boot and which stores information regarding changes to the system files to a change file. A repair module (,) analyzes the change file to determine the cause of the failed system boot. A boot check module (,) responds to initiation of a system boot by determining if a prior system boot was successful. Boot check module (,) causes execution of a first boot sector code module (,) upon occurrence of a successful prior system boot and causes execution of the repair module (,) upon occurrence of a failed prior system boot.

Growing community of inventors

Los Angeles, CA, United States of America

Rowan Trollope