Abstract: In some embodiments, techniques for protecting a network may include detecting an insecure condition on a first host that has connected or is attempting to connect to a protected network, including contacting a trusted computing base and determining whether a response includes a valid digitally signed attestation of cleanliness (an attestation that the first host is not infested and/or that the presence of a patch or patch level of a software component on the first host); if not, quarantining the first host, including by re-routing a service request sent by the first host by responding with a redirect that causes a browser on the first host to be directed to a quarantine server configured to serve a quarantine notification page that provides remediation information; and permitting the first host to communicate with a remediation host configured to provide data usable to remedy the insecure condition.

Abstract: Analyzing routing information to identify and intercept unauthorized, unwanted, and/or otherwise malicious communications is disclosed. In some embodiments, routing information associated with a message currently being processed is checked against corresponding information associated with a message from the same source that was processed previously. In some embodiments, a message processing system that handled and/or otherwise has access to routing information for both messages performs the check, such as a network messaging and/or access service provider with which the sender is associated, performs the check. If the routing information for the current message does not match the corresponding information observed in the previous message, responsive action is taken. Using routing information to determine whether a source of an infected message should be notified is disclosed.

Abstract: In some embodiments, techniques for electronic messaging may include receiving an email message; receiving an interaction with a user interface relating to the email message; extracting an email address associated with the email message; determining that the email address matches an entry in a whitelist; and responsive to receiving the interaction with the user interface relating to the email message and to determining that the email address matches the entry in the whitelist, removing the entry from the whitelist.

Abstract: In some embodiments, techniques for secure data entry comprise presenting a data field in a spoof-resistant manner, receiving field data, and securing field data.

Abstract: In some embodiments, a method for detecting a shared data element comprises providing a first feature of a first data element associated with a first storage device, detecting a second feature of a second data element associated with a second storage device, wherein the second feature is the same as the first feature, providing a challenge to a remote device associated with the second storage device, receiving a response to the challenge, providing the challenge to a second remote device via a digital network, receiving a correct response via the digital network, wherein the correct response includes a hash that has been calculated, determining whether the response is acceptable, wherein determining whether the response is acceptable includes determining whether the response is compatible with the correct response, and generating a reference to the first data element, if it is determined that the response is acceptable.

Abstract: In some embodiments, techniques for secure data entry comprise receiving a request for secure data entry in an electronic document, presenting a data field in a spoof-resistant manner, receiving field data, and securing field data.

Abstract: In some embodiments, techniques for electronic messaging may include receiving an email message; receiving an interaction with a user interface relating to the email message; extracting an email address associated with the email message; determining that the email address matches an entry in a whitelist; and responsive to receiving the interaction with the user interface relating to the email message and to determining that the email address matches the entry in the whitelist, removing the entry from the whitelist.

Abstract: In some embodiments, techniques for displaying a URL comprise receiving a URL; normalizing the URL, wherein normalizing the URL includes standardizing an encoding of a character contained in the URL; determining a first element of the URL, wherein the first element of the URL includes a domain; determining a second element of the URL; displaying the URL, wherein displaying the URL includes emphasizing the first element of the URL, and wherein emphasizing the first element of the URL includes displaying the first element of the URL using a first font attribute; and wherein displaying the URL includes displaying a first portion of the second element of the URL using a second font attribute and eliding a second portion of the second element of the URL; and responsive to an interaction with a user interface element, providing a view of the URL in its entirety.

Abstract: In some embodiments, techniques for computer security comprise receiving an email message; determining a sender of the email message; determining whether the sender of the email message is trusted, wherein determining whether the sender of the email message is trusted includes determining whether the sender of the email message is associated with a whitelist; retrieving domain-related information by performing a DNS query on a domain associated with the sender; based at least in part on the domain-related information, determining whether the sender of the email message is verified; determining whether the sender is both trusted and verified; and when it is determined that the sender is both trusted and verified, treating the email message as trustworthy, wherein treating the email message as trustworthy includes bypassing a classifier.

Abstract: In some embodiments, techniques for secure data entry comprise receiving request data, requesting secure data entry via a programmatic interface, and receiving encrypted input data, wherein a key used for the encryption is associated with said identity-related data.

Abstract: In some embodiments, techniques for electronic messages may include various enhancements.

Abstract: In some embodiments, techniques for authorizing a message comprise receiving a request to authorize delivery of a message for a recipient to be sent subsequent to the request, by a specified sender, wherein the request is embedded in a web page associated with the specified sender; determining whether the request is valid; updating information associated with the specified sender to indicate that the specified sender is authorized, when it is determined that the request is valid; receiving an incoming message for the message recipient; determining that the specified sender is a sender of the incoming message; determining whether the specified sender is authorized, wherein determining whether the specified sender is authorized includes checking the information associated with the specified sender; and when it is determined that the second sender is authorized, bypassing spam filtering for the incoming message and delivering the incoming message.

Abstract: In some embodiments, techniques for electronic messaging may include presenting a message; monitoring an action, wherein the action is associated with scrolling the message; and determining a classification for the message, wherein determining the classification includes evaluating the action.

Abstract: In some embodiments, techniques for displaying a URL comprise reducing the deceptiveness of electronic communications.

Abstract: In some embodiments, techniques for computer security comprise receiving a message, receiving a user-originated request for an action, wherein the action is associated with the message, determining whether the message is trustworthy, and impairing performance of the action, if it is determined that the message is not trustworthy. In some embodiments, techniques for computer security comprise receiving a message, determining whether the message is trustworthy, rendering the message, if it is determined that the message is trustworthy, and rendering a restricted version of the message, if it is determined that the message is not trustworthy.

Abstract: In some embodiments, a technique for processing a message comprises receiving a message; classifying the message into one of a plurality of categories, wherein the classification includes using content-based message analysis; and challenging the message if the message is classified into a first category.

Abstract: In some embodiments, techniques for searching comprise providing a user interface, wherein the user interface is associated with an input area and a selector, receiving a search term and a desired category simultaneously, wherein the search term is associated with the input area and the category is associated with the selector, determining a plurality of documents, wherein each of the plurality of documents is associated with the search term and the category, and providing a search result, wherein the search result is associated with the plurality of documents.

Abstract: In some embodiments, techniques for secure data entry comprise presenting a data field in a spoof-resistant manner, receiving field data, and securing field data.

Abstract: In some embodiments, a technique for authorizing a subsequent message comprises receiving a request to authorize a subsequent message, determining whether the request is valid, and authorizing the subsequent message, if it is determined that the request is valid.

Abstract: In some embodiments, techniques may include receiving an email message; determining a non-recipient email addressee associated with the email message, wherein the non-recipient email addressee has an address that is unaffiliated with a recipient for which the email message has been received; receiving a directive to whitelist the non-recipient email addressee; and responsive to receiving the directive to whitelist the non-recipient email addressee, adding the non-recipient email addressee to a whitelist.