WO2006119506A2 - Method of validating requests for sender reputation information - Google Patents
Method of validating requests for sender reputation information Download PDFInfo
- Publication number
- WO2006119506A2 WO2006119506A2 PCT/US2006/017780 US2006017780W WO2006119506A2 WO 2006119506 A2 WO2006119506 A2 WO 2006119506A2 US 2006017780 W US2006017780 W US 2006017780W WO 2006119506 A2 WO2006119506 A2 WO 2006119506A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- computer
- processor
- dns
- customer group
- authentication code
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/107—Computer-aided management of electronic mailing [e-mailing]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/212—Monitoring or handling of messages using filtering or selective blocking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/234—Monitoring or handling of messages for tracking messages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/12—Applying verification of the received information
- H04L63/123—Applying verification of the received information received data contents, e.g. message integrity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/12—Applying verification of the received information
- H04L63/126—Applying verification of the received information the source of the received data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
- H04L63/1441—Countermeasures against malicious traffic
- H04L63/145—Countermeasures against malicious traffic the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
Definitions
- the present invention generally relates to message processing, such as e-mail processing in mail transfer agents.
- the invention relates more specifically to approaches for preventing attacks on a sender reputation service.
- DNS-based blacklists and whitelists for e-mail are described in J. Levine, "DNS Based Blacklists and Whitelists for E-Mail," draft-irtf-asrg-dnsbl-01.txt, November 16, 2004.
- DNSxL is used as shorthand to refer to either a DNS-based blacklist (DNSBL) or a DNS-based whitelist (DNSWL).
- SBRS SeenderBase Reputation Score
- a mail transfer agent configured with appropriate software can issue a query to a database that stores information about the reputation of senders of electronic messages.
- the database replies with a value indicating a sender's reputation. Based on the value, the mail transfer agent can determine whether to accept or reject the message.
- a sender reputation list is implemented in the form of a DNSxL.
- the DNSxL sender reputation list enables the use of less fine-grained sender reputation score data by devices and services that are unable to process the actual scores directly.
- real-valued sender reputation list scores are separated or "discretized" into a finite set of "bins.” These bins are associated with standard DNS responses, indicating various ranges of reputation scores.
- the DNSxL format is supported by many clients, and allows a wider range of devices and services to use sender reputation list.
- MAC Message authentication code
- FIG. 1 is a block diagram that illustrates an overview of a network arrangement that includes a reputation service
- FIG. 2 is a block diagram showing an example data structure representation that can be used for mapping configuration files to querying host domains;
- FIG. 3 A is a flow diagram that provides a high-level view of a process of validating queries;
- FIG. 3B is a flow diagram that provides a more detailed view of a process of validating queries
- FIG. 3C is a flow diagram of an approach for de-authorizing querying hosts;
- FIG. 4 is a block diagram that illustrates a computer system upon which an embodiment may be implemented.
- a method for validating queries for reputation scores of message senders comprises receiving, from a first host computer, a DNS format query to obtain a reputation score associated with a second host computer, wherein the query includes an authentication code; validating the authentication code; and only when validating the authentication code is successful, performing a DNS lookup in a reputation database and returning a DNS response that provides the reputation score associated with the second host computer.
- an NXDOMAIN record is sent to the first host computer when validating the authentication code is unsuccessful.
- the method determines whether the first computer is listed in a blacklist, and sends an NXDOMAIN record to the first host computer without validating the authentication code when the first computer is listed in the blacklist.
- Another feature comprises establishing a master domain and a plurality of subdomains, wherein each of the subdomains is associated with a respective customer group; and receiving the DNS format query from the first computer at a particular subdomain that is associated with a particular customer group, wherein the first computer is associated with the particular customer group, wherein the DNS format query includes an identifier of the particular customer group.
- Yet another feature provides for retrieving configuration information associated with the particular customer group, wherein the configuration information for the particular customer group maps one or more discrete sets of reputation values to respective responsive actions; determining, by mapping the reputation score for the second host computer to one of the discrete sets in the configuration information, a particular responsive action; and performing the particular responsive action.
- Still another feature involves creating and storing, in a log file, a log entry that identifies the first computer and whether validation of the DNS format query was successful; periodically reading the log file, determining whether the first computer has issued a number of queries that exceeds an invalidation threshold for the first computer, and adding the first computer to the blacklist when the first computer has issued a number of queries that exceeds an invalidation threshold for the first computer.
- a further feature provides for retrieving configuration information associated with the first computer, wherein the configuration information identifies a time in which the first computer is allowed to send queries; determining whether the time has expired; and adding the first computer to the blacklist when the time has expired.
- the invention encompasses a computer apparatus and a computer- readable medium configured to carry out the foregoing steps.
- FIG. 1 is a block diagram that illustrates an overview of a network arrangement that includes a reputation service
- FIG. 3 A is a flow diagram that provides a high-level view of a process of validating queries.
- FIG. 1 is a block diagram of one system in which an embodiment may be used.
- a sender 102 is coupled through network 104 to mail server 106.
- the mail server 106 hosts a mailbox on behalf of receiver 108.
- sender 102 communicates with mail server 106 using simple mail transfer protocol (SMTP).
- SMSTP simple mail transfer protocol
- Sender 102 may comprise another mail server, a mail gateway, or an end station that incorporates a mail server.
- a reputation service 110 is coupled through network 104 to mail server 106.
- mail server 106 can request and receive a reputation value associated with sender 102, for use as a basis for determining whether to accept mail connections from sender 102, to deliver messages to receiver 108, or take other actions, hi one embodiment, reputation service 110 comprises DNS logic 112, validation logic 114, DNS format database 116, statistics process 118, log process 120, blacklist 126, client de-authorization logic 122, and one or more customer configuration files 124.
- DNS logic 112 processes DNS queries that seek reputation information about sending hosts, such as sender 102.
- Validation logic 114 comprises one or more computer programs or other software elements that implement the functions described herein, and is configured to identify queries from clients not authorized to use the service, and to refuse them service while making their revalidation easy and fast.
- DNS format database 116 stores reputation information about a large number of message senders in the form of DNS whitelists or blacklists.
- DNSxL is used herein as shorthand to refer to either a DNS-based blacklist (DNSBL) or a DNS-based whitelist (DNSWL).
- DNSBL DNS-based blacklist
- DNSWL DNS-based whitelist
- a mail transfer agent configured with appropriate software can issue a query to a database that stores information about the reputation of senders of electronic messages.
- the database replies with a value indicating a sender's reputation. Based on the value, the mail transfer agent can determine whether to accept or reject the message.
- a sender reputation list comprises a DNSxL.
- real-valued sender reputation list scores are separated or "discretized" into a finite set of logical bins. Bins are associated with standard DNS responses, indicating various ranges of reputation scores.
- Statistics process 118 and log process 120 can interact with a log file that records information about queries of mail servers, such as mail server 106.
- Blacklist 126 comprises a list of mail servers that are not allowed to use reputation service 110.
- the reputation service 110 maintains blacklist 126 as further described herein.
- Client de-authorization logic 122 comprises one or more computer programs or other software elements for managing blacklist 126.
- Customer configuration files 124 store configuration information for different customers of the reputation service 110, as further described below.
- FIG. 3 A An operational example is now described with reference to FIG. 3 A. For purposes of illustrating a clear example, FIG. 3 A is described in the context of the embodiment shown in FIG. 1. However, the broad approach of FIG. 3 A can be used in many other contexts and embodiments.
- a sender 102 sends one or more email messages through network 104 toward receiver 108.
- the messages are received first at mail server 106, which hosts a mailbox or mail filter on behalf of receiver 108.
- Mail server 106 issues a query to a reputation service 110, seeking to obtain a reputation score value indicating whether sender 102 is a reputable mail sender.
- the query may include sender identifying information, such as a network address, for example, an IP address.
- the query may be formatted as a DNS lookup, and in one approach, DNS type A records are returned to queries about connecting network addresses indicating their reputation.
- reputation service 110 receives, from a querying host in the form of mail server 106, a DNS-format query to obtain the reputation score of a connecting host, namely sender 102.
- reputation service 110 determines whether the querying host is allowed to process queries using the service. Step 304 may involve determining whether mail server 106 is listed in blacklist 126. If the querying host is not allowed to use the service, then in step 310 an NXDOMAIN record is returned to the querying host. Sending an
- NXDOMAIN record is equivalent to informing the querying host that sender 102 is not listed in the database of the reputation service 110.
- step 306 the query is validated before it is processed.
- reputation service 110 forwards the query to DNS logic 112, which validates the query using validation logic 114. Any of a plurality of validation mechanisms may be used, and specific techniques are described further below.
- a DNS lookup is performed in the reputation database to identify a score for the connecting host. For example, DNS logic
- 112 applies the query to a DNS format database 116, which is structured with DNS records.
- step 314 a response is returned to the querying host.
- DNS logic 112 can generate several kinds of responses to mail server 106. As a first example, DNS logic 112 can indicate whether a particular sender is listed or unlisted in database 116. As a second example, DNS logic 112 can facilitate threshold-based blocking in which a range of response codes are returned for various reputation levels, which a client can treat differently. As a third example, DNS logic 112 can perform header tagging, involving the addition of descriptive reputation information to headers or subjects.
- step 308 If the test of step 308 is negative, then control passes to step 310 in which an
- NXDOMAIN record is returned to the querying host.
- querying hosts that send invalid queries are rapidly refused service without performing more computationally intensive tasks, such as steps 312, 314.
- FIG. 2 is a block diagram showing an example data structure representation that can be used for mapping configuration files to querying host domains;
- FIG. 3B is a flow diagram that provides a more detailed view of a process of validating queries;
- FIG. 3C is a flow diagram of an approach for de-authorizing querying hosts.
- a secret string value and other message authentication code parameters are distributed to authorized customer hosts.
- the secret string value is a data set that authorized clients use to prove authorization to the reputation service 110, as further described below.
- Other message authentication code parameters may comprise an identification of what message authentication algorithm should be used (MD2, MD4, MD5, etc.) and a hash key for the algorithm to use in computing message authentication values.
- Step 320 may involve any appropriate key distribution mechanism, the details of which are beyond the scope of this disclosure. What is important is that all authorized mail servers or other querying hosts receive the secret string value and message authentication parameters.
- a plurality of mail servers 106 may be organized in one or more customer groups.
- customer group refers to the subset of clients making requests associated with a particular relationship or partner of the reputation service.
- mail server 106 may be associated with a customer of an entity that provides the reputation service 110 and that customer may have more than one mail server; all mail servers making requests form a customer group.
- Information identifying customer groups and the network addresses of mail servers within the customer groups may be stored in database 116 or in another data repository associated with reputation service 110.
- a configuration file 124 specific to that customer group specifies a mapping of scores to responses, how queries are formatted, and desired responses. Using separate configuration files 124 for each customer group allows different relationships to have different configurations and to update independently.
- reputation scores in database 116 are discretized, and configuration files 124 indicate what actions to take for discrete ranges of scores.
- score ranges and their associated responses are indicated in the configuration file 124, on a per-subdomain basis. Blacklist-only users only specify a set of negative ranges, so any network addresses or IP addresses with scores above the highest range of interest will receive an NXDOMAIN response, as though they were not listed.
- a DNS query is received from a querying host seeking the reputation score of a connecting host.
- mail server 106 creates and sends a DNS lookup query to reputation service 110 and identifying an IP address of sender 102.
- a test is performed to determine if the querying host is in a list of blocked hosts. The list may comprise blacklist 126. If the querying host is blocked, then control passes to step 326, in which an NXDOMAIN record is returned.
- the NXDOMAIN record effectively provides no substantive information to the querying host, in a manner that rapidly refuses service to blocked hosts and is compatible with standard DNS processing and does not require a special error-reporting protocol or message.
- a customer subdomain value and authentication value are extracted from the received query.
- DNS domains specified in a query vary according to the customer.
- each customer group has a specific subdomain of a master domain to query, as described further below.
- the master domain of reputation service 110 could be "senderbase.org,” and each customer has a particular subdomain, such as "acme.senderbase.org" for a customer named "Acme Corporation.”
- Each subdomain can set specific options relating to the service using configuration files 124, as described further below.
- a query from mail server 106 to reputation service 110 is formatted in the manner described in the Reputation Service Disclosures, with an additional authentication value.
- the authentication value may comprise a one-way hash of the query.
- the authentication value is used to validate the query.
- queries are formatted as an extended subdomain of the master domain of reputation service 110 (e.g., senderbase.org).
- a query about an IP address "a.b.c.d” is as follows:
- the [metafields] element comprises one or more values, delimited by period characters, containing additional information about the query, such as version information, or authentication data.
- the [query-subdomain] element identifies the relevant subdomain of the reputation service 110 that is handling DNSxL queries for the customer who has issued the query: "dnsxl-customer-1", for example. If versioning information is included, the versioning information is provided after the hash string and before the subdomain.
- a query about a connecting host with an IP address of "1.2.3.4" may have the form:
- the [metafields] element of the foregoing query comprises a unique identifier string.
- the identifier string maps to a DNSxL configuration, a customer value, and a specific licensing period.
- FIG. 2 is a block diagram showing an example data structure representation that can be used for the mapping.
- an identifier string 202 maps to an association 204 of a configuration, customer value, and licensing period.
- the configuration is stored in a table 206 organized as an array of tuples of tests and associated actions.
- the customer value identifies a customer.
- a customer mapping is provided because whenever a contract or evaluation period terminates, all queries to that DNS zone will return NXDOMAIN.
- the licensing period identifies a specific licensing period and supports a business model in which the reputation service 110 collects periodic fees for providing service to customers. In an embodiment, after the licensing period ends, all queries to the associated DNS zone will return NXDOMAIN.
- the licensing period value is optional, and can be omitted in another embodiment.
- the identifier string may have a value of "customer".
- the license period value represents a license series that is rotated every 6 months, and the customer is responsible for updating its licensed customers to use the new series. Six months after each license series expires, the system starts delivering NXDOMAIN replies. Thus, there will be 2-3 license series in active use at any one time. Enforcement of the licensing period is described further below in connection with FIG. 3C. The use of test- action table 206 is described further below relating to step 338. [0063] 3.2 QUERY VALIDATION
- step 330 the received DNS query is validated.
- a secret string is retrieved from a configuration file associated with the customer group that includes the querying host.
- a new authentication value is computed based on the retrieved secret string and the network address for which the querying host is requesting information.
- the authentication value that was extracted at step 328 is compared to the new authentication value. If the authentication values match, then the DNS query is valid, as tested at step 332.
- configuration file 124 specifies the secret string that is used to authorize queries. Most values are strings or integers; some, such as the score ranges, are specified as a CSV string of (score threshold, response code) pairs, colon-delimited. Table 1 presents a sample configuration file:
- the [authorization] section of the configuration file contains all fields needed for validation of the associated subdomain or customer group, including:
- the secret string or hash key that is used to calculate hash values is distributed to the smallest possible group. Ideally, the hash key is changed regularly, but this policy may vary in different customer groups, according to their technical details.
- validation logic 114 performs step 330 to validate each query received at DNS logic 112 before the query is processed in later steps, hi one approach, each query comprises a hash value that is calculated using a secret value that is distributed only to authorized clients, e.g., mail server 106.
- queries with validation information are formatted as an extended subdomain of a master domain of reputation service 110, e.g., senderbase.org.
- a query about an IP "a.b.c.d” is as follows:
- the [hashstring] element comprises a representation of an authorization hash.
- the [hashstring] value is determined based on performing a one-way hash function on the secret string concatenated with the network address that is being queried about.
- a hash function such as MD5 may be used.
- a query about a connecting host with IP address "1.2.3.4” could look something like the following, depending on the value of the "secret” used to calculate the hash string:
- the new hash is an MD5 hash based on a string resulting from directly concatenating the network-order, dotted-quad IP string to the end of a previously distributed secret string.
- validation of queries is performed "offline.”
- control passes from step 328 to step 334, so that every query is answered if the requesting network address is not in the blacklist at the time the query is received.
- a separate process implements steps 330, in which a query is validated by checking the included hashstring against a new hash that is calculated from the query.
- step 334 a
- DNS lookup is performed in the reputation database to obtain a reputation score for the connecting host.
- the reputation score is retrieved from the database at step 336.
- a responsive action is determined, for example, based on mapping the retrieved reputation score to the test-action table 206 of FIG. 2. The responsive action is then performed.
- tests can include any of several variables.
- tests can include an SBVS score, one or more TTRTRT, listings, and per-blacklist status values.
- valid actions may include any of the following: Default result for a particular IP address query is NXDOMAIN; add an A record result as result named ⁇ result> and set it to ⁇ IP address>; replace A record result number with the logical AND of ⁇ mask> and A record result number ⁇ number>; set TXT record result to ⁇ text>.
- the set of A records returned is the list of all results named.
- the values shown in TABLE 2 may be used. This example presumes that customer policy allows the system to pick different actions based on the return IP address result. One IP address is returned with a basic score.
- a query to reputation service 110 causes DNS logic 112 to return one of the following records:
- a TXT record comprising a URL pointing to summary of main external reasons for score.
- a response field may include a list of factors that specify information such as which blacklist an IP address is in, or other more specific information maintained locally about the IP address.
- the list may comprise codes that map to a table of blacklists.
- step 338 when DNS logic 112 is ready to issue a response to mail server 106, a network address of the mail server 106, specified in a header of the client query, is checked against blacklist 124.
- reputation service 110 maintains a list of servers or clients that are unlicensed or unauthorized and from whom queries are always refused.
- step 340 a log file record is created and stored to describe the querying host and the result of the query, whether valid or invalid.
- step 326 also may involve creating and storing a log file record indicating that the querying host made an invalid query.
- reputation service 110 may maintain a status information table in log 120 that tracks information about how a client such as mail server 106 is using the reputation service.
- log 120 may include a Client Usage Stats table with the fields shown in TABLE 3 :
- An offline process associated with reputation service 110 monitors log 120 for network addresses that are making an unacceptable number of unauthorized queries, and adds them to the blacklist. For example, statistics process 118 of reputation service 110 may perform log monitoring. However, queries from blocked addresses cannot be entirely ignored, as they may become authorized after being blocked. Therefore, blocked queries are logged separately, and immediately processed to check for authentication status changes. [0103] When a host having a particular network address makes too many queries that are incorrect, as determined by a failure of validation logic 114 to validate the queries, the querying host is added to the blacklist 124 and subsequent queries are rejected by DNS logic 112 at step 324. When such a host begins making queries with valid hashes, it is then allowed to make queries. Mechanisms for de-authorizing and re-authorizing querying hosts are described further below
- statistics process 118 periodically parses log 120 (or some sample thereof) and maintaining data on servers, clients or network addresses that are making queries. Statistics process may log total usage and may check authorization hashes in queries. Invalid queries are counted in log 120 by statistics process 118, while a single valid query will reset the count of invalid queries for that IP to zero.
- a Client De-authorization and Re-authorization process 122 periodically checks log 120 or communicates with statistics process 118 to identify servers, clients or network addresses exceeding a threshold of unauthorized queries.
- An example threshold is 100 invalid queries. Servers, clients or network addresses that exceed the threshold are added to the blacklist 126.
- client de-authorization process 122 further processes log 122 to identify rejected queries to see if any previously rejected servers, clients or network addresses have started making valid queries. Any rejected address that makes a single valid request is rapidly removed from the blacklist, and the count of invalid requests for that address is reset to zero.
- an example approach for de-authorizing querying hosts initiates at step 350 and reads a log file entry at step 352.
- the log file entry relates to a prior query for reputation score information from a querying host.
- the querying host is identified.
- a test is performed to determine whether the query was invalid.
- a counter of invalid queries for that querying host is incremented. The counter may be stored in database 116 or another repository.
- a test is performed to determine whether an invalidation threshold for the querying host has been exceeded. The invalidation threshold may be obtained from the configuration file 124 for the querying host.
- step 362 If the invalidation threshold has been exceeded, then in step 362 the querying host is placed in a blacklist, such as blacklist 124. If the invalidation threshold has not been exceeded, then in step 364 a test is performed to determine whether a license period for the querying host has expired. If so, then in step 362 the querying host is placed in a blacklist, such as blacklist 124. The license period test of step 364 is also performed when the query is determined to be valid at step 356.
- FIG. 4 is a block diagram that illustrates a computer system 400 upon which an embodiment of the invention may be implemented.
- Computer system 400 includes a bus 402 or other communication mechanism for communicating information, and a processor 404 coupled with bus 402 for processing information.
- Computer system 400 also includes a main memory 406, such as a random access memory (“RAM”) or other dynamic storage device, coupled to bus 402 for storing information and instructions to be executed by processor 404.
- Main memory 406 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 404.
- Computer system 400 further includes a read only memory (“ROM”) 408 or other static storage device coupled to bus 402 for storing static information and instructions for processor 404.
- ROM read only memory
- a storage device 410 such as a magnetic disk or optical disk, is provided and coupled to bus 402 for storing information and instructions.
- Computer system 400 may be coupled via bus 402 to a display 412, such as a cathode ray tube ("CRT"), for displaying information to a computer user.
- a display 412 such as a cathode ray tube ("CRT")
- An input device 414 is coupled to bus 402 for communicating information and command selections to processor 404.
- cursor control 416 is Another type of user input device
- cursor control 416 such as a mouse, trackball, stylus, or cursor direction keys for communicating direction information and command selections to processor 404 and for controlling cursor movement on display 412.
- This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane.
- the invention is related to the use of computer system 400 for message processing approaches.
- message-processing approaches are provided by computer system 400 in response to processor 404 executing one or more sequences of one or more instructions contained in main memory 406.
- Such instructions may be read into main memory 406 from another computer-readable medium, such as storage device 410.
- Execution of the sequences of instructions contained in main memory 406 causes processor 404 to perform the process steps described herein.
- hard- wired circuitry may be used in place of or in combination with software instructions to implement the invention.
- embodiments of the invention are not limited to any specific combination of hardware circuitry and software.
- Non- volatile media includes, for example, optical or magnetic disks, such as storage device 410.
- Volatile media includes dynamic memory, such as main memory 406.
- Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 402. Transmission media can also take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications.
- Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read.
- Various forms of computer readable media may be involved in carrying one or more sequences of one or more instructions to processor 404 for execution. For example, the instructions may initially be carried on a magnetic disk of a remote computer.
- the remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem.
- a modem local to computer system 400 can receive the data on the telephone line and use an infrared transmitter to convert the data to an infrared signal.
- An infrared detector can receive the data carried in the infrared signal and appropriate circuitry can place the data on bus 402.
- Bus 402 carries the data to main memory 406, from which processor 404 retrieves and executes the instructions.
- the instructions received by main memory 406 may optionally be stored on storage device 410 either before or after execution by processor 404.
- Computer system 400 also includes a communication interface 418 coupled to bus 402.
- Communication interface 418 provides a two-way data communication coupling to a network link 420 that is connected to a local network 422.
- communication interface 418 may be an integrated services digital network ("ISDN") card or a modem to provide a data communication connection to a corresponding type of telephone line.
- ISDN integrated services digital network
- communication interface 418 may be a local area network (“LAN”) card to provide a data communication connection to a compatible LAN.
- LAN local area network
- Wireless links may also be implemented.
- communication interface 418 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
- Network link 420 typically provides data communication through one or more networks to other data devices.
- network link 420 may provide a connection through local network 422 to a host computer 424 or to data equipment operated by an Internet Service Provider ("ISP") 426.
- ISP 426 in turn provides data communication services through the worldwide packet data communication network now commonly referred to as the "Internet” 428.
- Internet 428 uses electrical, electromagnetic or optical signals that carry digital data streams.
- the signals through the various networks and the signals on network link 420 and through communication interface 418, which carry the digital data to and from computer system 400, are exemplary forms of carrier waves transporting the information.
- Computer system 400 can send messages and receive data, including program code, through the network(s), network link 420 and communication interface 418.
- a server 430 might transmit a requested code for an application program through Internet 428, ISP 426, local network 422 and communication interface 418.
- one such downloaded application provides for message processing approaches as described herein.
- the received code may be executed by processor 404 as it is received, and/or stored in storage device 410, or other non- volatile storage for later execution. In this manner, computer system 400 may obtain application code in the form of a carrier wave. [0122] 5.0 EXTENSIONS AND ALTERNATIVES
Abstract
A method of validating queries for reputation scores of message senders comprises receiving, from a first host computer (106), a DNS format query to obtain a reputation score associated with a second host computer (102), wherein the query includes an authentication code; validating the authentication code; and only when validating the authentication code is successful, performing a DNS lookup in a reputation database (116) and returning a DNS response that provides the reputation score associated with the second host computer (102).
Description
METHOD OF VALIDATING REQUESTS FOR SENDER REPUTATION INFORMATION
FIELD OF THE INVENTION
[0001] The present invention generally relates to message processing, such as e-mail processing in mail transfer agents. The invention relates more specifically to approaches for preventing attacks on a sender reputation service.
BACKGROUND
[0002] The approaches described in this section could be pursued, but are not necessarily approaches that have been previously conceived or pursued. Therefore, unless otherwise indicated herein, the approaches described in this section are not prior art to the claims in this application and are not admitted to be prior art by inclusion in this section. [0003] DNS-based blacklists and whitelists for e-mail are described in J. Levine, "DNS Based Blacklists and Whitelists for E-Mail," draft-irtf-asrg-dnsbl-01.txt, November 16, 2004. The term "DNSxL" is used as shorthand to refer to either a DNS-based blacklist (DNSBL) or a DNS-based whitelist (DNSWL).
[0004] IronPort Systems, Inc. has introduced a service termed "SenderBase Reputation Score" or SBRS. Using SBRS, a mail transfer agent configured with appropriate software can issue a query to a database that stores information about the reputation of senders of electronic messages. The database replies with a value indicating a sender's reputation. Based on the value, the mail transfer agent can determine whether to accept or reject the message.
[0005] In one implementation of SBRS, a sender reputation list is implemented in the form of a DNSxL. The DNSxL sender reputation list enables the use of less fine-grained sender reputation score data by devices and services that are unable to process the actual scores directly. In one approach, real-valued sender reputation list scores are separated or "discretized" into a finite set of "bins." These bins are associated with standard DNS responses, indicating various ranges of reputation scores. Further, the DNSxL format is supported by many clients, and allows a wider range of devices and services to use sender reputation list.
[0006] However, because many clients support DNSxL format, a reputation service could be subject to a denial-of-service attack by clients that send large numbers of successive queries that request reputation values for non-existent senders or network addresses. To
prevent such attacks, there is a need to identify valid and invalid clients and to control their access to the service. There is a related need to perform validation and control in a way that is computationally "light" for both clients and the reputation service, and allows for time- limited access as well as distinct service groups.
[0007] Message authentication code (MAC) approaches are known for enabling a receiving network node to determine if a message has been modified in transit from a sender. Some MAC approaches are based on performing a one-way hash over the message using a collision-resistant, fixed-length-output hash algorithm such as Message Digest 5 (MD5).
BRIEF DESCRIPTION OF THE DRAWINGS
[0010] The present invention is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:
[0011] FIG. 1 is a block diagram that illustrates an overview of a network arrangement that includes a reputation service;
[0012] FIG. 2 is a block diagram showing an example data structure representation that can be used for mapping configuration files to querying host domains; [0013] FIG. 3 A is a flow diagram that provides a high-level view of a process of validating queries;
[0014] FIG. 3B is a flow diagram that provides a more detailed view of a process of validating queries;
[0015] FIG. 3C is a flow diagram of an approach for de-authorizing querying hosts; [0016] FIG. 4 is a block diagram that illustrates a computer system upon which an embodiment may be implemented.
DETAILED DESCRIPTION
[0017] A method and apparatus for validating requests for sender reputation information is described, hi the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced without these specific details, hi other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the present invention. [0018] Embodiments are described herein according to the following outline:
1.0 General Overview
2.0 Structural and Functional Overview
3.0 Validating Reputation List Queries
3.1 Process Initiation
3.2 Query Validation
3.3 Determining and Performing Responsive Actions
3.4 Blacklist and Log File Management
4.0 Implementation Mechanisms — Hardware Overview 5.0 Extensions and Alternatives
[0019] 1.0 GENERAL OVERVIEW
[0020] The needs identified in the foregoing Background, and other needs and objects that will become apparent for the following description, are achieved in the present invention, which comprises, in one aspect, a method for validating queries for reputation scores of message senders comprises receiving, from a first host computer, a DNS format query to obtain a reputation score associated with a second host computer, wherein the query includes an authentication code; validating the authentication code; and only when validating the authentication code is successful, performing a DNS lookup in a reputation database and returning a DNS response that provides the reputation score associated with the second host computer.
[0021] According to one feature of this aspect, an NXDOMAIN record is sent to the first host computer when validating the authentication code is unsuccessful. In another feature, the method determines whether the first computer is listed in a blacklist, and sends an NXDOMAIN record to the first host computer without validating the authentication code when the first computer is listed in the blacklist.
[0022] Another feature comprises establishing a master domain and a plurality of subdomains, wherein each of the subdomains is associated with a respective customer group; and receiving the DNS format query from the first computer at a particular subdomain that is associated with a particular customer group, wherein the first computer is associated with the particular customer group, wherein the DNS format query includes an identifier of the particular customer group.
[0023] Yet another feature provides for retrieving configuration information associated with the particular customer group, wherein the configuration information for the particular customer group maps one or more discrete sets of reputation values to respective responsive actions; determining, by mapping the reputation score for the second host computer to one of the discrete sets in the configuration information, a particular responsive action; and performing the particular responsive action.
[0024] Still another feature involves creating and storing, in a log file, a log entry that identifies the first computer and whether validation of the DNS format query was successful; periodically reading the log file, determining whether the first computer has issued a number of queries that exceeds an invalidation threshold for the first computer, and adding the first computer to the blacklist when the first computer has issued a number of queries that exceeds an invalidation threshold for the first computer.
[0025] A further feature provides for retrieving configuration information associated with the first computer, wherein the configuration information identifies a time in which the first computer is allowed to send queries; determining whether the time has expired; and adding the first computer to the blacklist when the time has expired.
[0026] In other aspects, the invention encompasses a computer apparatus and a computer- readable medium configured to carry out the foregoing steps.
[0027] hi the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the present invention. [0028] 2.0 STRUCTURAL AND FUNCTIONAL OVERVIEW
[0029] An approach to identify valid and invalid clients and to control their access is now described with reference to FIG. 1 and FIG. 3 A. FIG. 1 is a block diagram that illustrates an overview of a network arrangement that includes a reputation service; FIG. 3 A is a flow diagram that provides a high-level view of a process of validating queries. [0030] FIG. 1 is a block diagram of one system in which an embodiment may be used. A sender 102 is coupled through network 104 to mail server 106. The mail server 106 hosts a mailbox on behalf of receiver 108. In an embodiment, sender 102 communicates with mail server 106 using simple mail transfer protocol (SMTP). Sender 102 may comprise another mail server, a mail gateway, or an end station that incorporates a mail server. [0031] A reputation service 110 is coupled through network 104 to mail server 106. Using reputation service 110 as described herein, mail server 106 can request and receive a reputation value associated with sender 102, for use as a basis for determining whether to accept mail connections from sender 102, to deliver messages to receiver 108, or take other actions, hi one embodiment, reputation service 110 comprises DNS logic 112, validation logic 114, DNS format database 116, statistics process 118, log process 120, blacklist 126, client de-authorization logic 122, and one or more customer configuration files 124.
[0032] DNS logic 112 processes DNS queries that seek reputation information about sending hosts, such as sender 102. Validation logic 114 comprises one or more computer programs or other software elements that implement the functions described herein, and is configured to identify queries from clients not authorized to use the service, and to refuse them service while making their revalidation easy and fast.
[0033] DNS format database 116 stores reputation information about a large number of message senders in the form of DNS whitelists or blacklists. The term "DNSxL" is used herein as shorthand to refer to either a DNS-based blacklist (DNSBL) or a DNS-based whitelist (DNSWL). hi the "SenderBase Reputation Score" or SBRS service of IronPort Systems, Inc., a mail transfer agent configured with appropriate software can issue a query to a database that stores information about the reputation of senders of electronic messages. The database replies with a value indicating a sender's reputation. Based on the value, the mail transfer agent can determine whether to accept or reject the message. A sender reputation list comprises a DNSxL. In one approach, real-valued sender reputation list scores are separated or "discretized" into a finite set of logical bins. Bins are associated with standard DNS responses, indicating various ranges of reputation scores. [0034] Statistics process 118 and log process 120 can interact with a log file that records information about queries of mail servers, such as mail server 106. Blacklist 126 comprises a list of mail servers that are not allowed to use reputation service 110. The reputation service 110 maintains blacklist 126 as further described herein. Client de-authorization logic 122 comprises one or more computer programs or other software elements for managing blacklist 126. Customer configuration files 124 store configuration information for different customers of the reputation service 110, as further described below. [0035] An operational example is now described with reference to FIG. 3 A. For purposes of illustrating a clear example, FIG. 3 A is described in the context of the embodiment shown in FIG. 1. However, the broad approach of FIG. 3 A can be used in many other contexts and embodiments.
[0036] As a hypothetical example, assume that a sender 102 sends one or more email messages through network 104 toward receiver 108. The messages are received first at mail server 106, which hosts a mailbox or mail filter on behalf of receiver 108. [0037] Mail server 106 issues a query to a reputation service 110, seeking to obtain a reputation score value indicating whether sender 102 is a reputable mail sender. The query may include sender identifying information, such as a network address, for example, an IP address. The query may be formatted as a DNS lookup, and in one approach, DNS type A records are returned to queries about connecting network addresses indicating their
reputation. Thus, at step 302 (FIG. 3A), reputation service 110 receives, from a querying host in the form of mail server 106, a DNS-format query to obtain the reputation score of a connecting host, namely sender 102.
[0038] In step 304, reputation service 110 determines whether the querying host is allowed to process queries using the service. Step 304 may involve determining whether mail server 106 is listed in blacklist 126. If the querying host is not allowed to use the service, then in step 310 an NXDOMAIN record is returned to the querying host. Sending an
NXDOMAIN record is equivalent to informing the querying host that sender 102 is not listed in the database of the reputation service 110.
[0039] Otherwise, in step 306, the query is validated before it is processed. In one embodiment, reputation service 110 forwards the query to DNS logic 112, which validates the query using validation logic 114. Any of a plurality of validation mechanisms may be used, and specific techniques are described further below.
[0040] If the query is validated, as shown in step 308, then a DNS lookup is performed in the reputation database to identify a score for the connecting host. For example, DNS logic
112 applies the query to a DNS format database 116, which is structured with DNS records.
In step 314, a response is returned to the querying host.
[0041] In one embodiment, DNS logic 112 can generate several kinds of responses to mail server 106. As a first example, DNS logic 112 can indicate whether a particular sender is listed or unlisted in database 116. As a second example, DNS logic 112 can facilitate threshold-based blocking in which a range of response codes are returned for various reputation levels, which a client can treat differently. As a third example, DNS logic 112 can perform header tagging, involving the addition of descriptive reputation information to headers or subjects.
[0042] Information about queries that are received, and the response that was given, is maintained in log 120 for analysis by other processes.
[0043] If the test of step 308 is negative, then control passes to step 310 in which an
NXDOMAIN record is returned to the querying host. Thus, querying hosts that send invalid queries are rapidly refused service without performing more computationally intensive tasks, such as steps 312, 314.
[0044] 3.0 TECHNIQUES FOR VALIDATING REPUTATION LIST QUERIES
[0045] A more detailed embodiment of the broad approach herein is now described with reference to FIG. 2, FIG. 3B, and FIG. 3C. FIG. 2 is a block diagram showing an example data structure representation that can be used for mapping configuration files to querying host domains; FIG. 3B is a flow diagram that provides a more detailed view of a process of
validating queries; and FIG. 3C is a flow diagram of an approach for de-authorizing querying hosts.
[0046] 3.1 PROCESS INITIATION
[0047] In step 320, a secret string value and other message authentication code parameters are distributed to authorized customer hosts. The secret string value is a data set that authorized clients use to prove authorization to the reputation service 110, as further described below. Other message authentication code parameters may comprise an identification of what message authentication algorithm should be used (MD2, MD4, MD5, etc.) and a hash key for the algorithm to use in computing message authentication values. Step 320 may involve any appropriate key distribution mechanism, the details of which are beyond the scope of this disclosure. What is important is that all authorized mail servers or other querying hosts receive the secret string value and message authentication parameters. [0048] In an embodiment, a plurality of mail servers 106 may be organized in one or more customer groups. In this description, the term "customer group" refers to the subset of clients making requests associated with a particular relationship or partner of the reputation service. For example, mail server 106 may be associated with a customer of an entity that provides the reputation service 110 and that customer may have more than one mail server; all mail servers making requests form a customer group. Information identifying customer groups and the network addresses of mail servers within the customer groups may be stored in database 116 or in another data repository associated with reputation service 110. [0049] For a given customer group, a configuration file 124 specific to that customer group specifies a mapping of scores to responses, how queries are formatted, and desired responses. Using separate configuration files 124 for each customer group allows different relationships to have different configurations and to update independently. [0050] In an embodiment, reputation scores in database 116 are discretized, and configuration files 124 indicate what actions to take for discrete ranges of scores. In one approach, score ranges and their associated responses are indicated in the configuration file 124, on a per-subdomain basis. Blacklist-only users only specify a set of negative ranges, so any network addresses or IP addresses with scores above the highest range of interest will receive an NXDOMAIN response, as though they were not listed.
[0051] In step 322, a DNS query is received from a querying host seeking the reputation score of a connecting host. For example, mail server 106 creates and sends a DNS lookup query to reputation service 110 and identifying an IP address of sender 102. [0052] In step 324, a test is performed to determine if the querying host is in a list of blocked hosts. The list may comprise blacklist 126. If the querying host is blocked, then
control passes to step 326, in which an NXDOMAIN record is returned. The NXDOMAIN record effectively provides no substantive information to the querying host, in a manner that rapidly refuses service to blocked hosts and is compatible with standard DNS processing and does not require a special error-reporting protocol or message.
[0053] If the querying host is not blocked, then in step 328, a customer subdomain value and authentication value are extracted from the received query. In an embodiment, DNS domains specified in a query vary according to the customer. In one embodiment, each customer group has a specific subdomain of a master domain to query, as described further below. For example, the master domain of reputation service 110 could be "senderbase.org," and each customer has a particular subdomain, such as "acme.senderbase.org" for a customer named "Acme Corporation." Each subdomain can set specific options relating to the service using configuration files 124, as described further below.
[0054] An implementation of a reputation service 110 is described in prior nonprovisional application Ser. No. 10/857,641, filed May 28, 2004; Ser. No. 10/856,693, filed May 28, 2004; Ser. No. 11/062,320, filed February 17, 2005 (the "Reputation Service
Disclosures"). In one embodiment, a query from mail server 106 to reputation service 110 is formatted in the manner described in the Reputation Service Disclosures, with an additional authentication value. The authentication value may comprise a one-way hash of the query.
The authentication value is used to validate the query.
[0055] In an embodiment, queries are formatted as an extended subdomain of the master domain of reputation service 110 (e.g., senderbase.org). For example, a query about an IP address "a.b.c.d" is as follows:
[0056] d.c.b.a.[metafields].[query-subdomain]. senderbase.org
[0057] The [metafields] element comprises one or more values, delimited by period characters, containing additional information about the query, such as version information, or authentication data. The [query-subdomain] element identifies the relevant subdomain of the reputation service 110 that is handling DNSxL queries for the customer who has issued the query: "dnsxl-customer-1", for example. If versioning information is included, the versioning information is provided after the hash string and before the subdomain. Thus, a query about a connecting host with an IP address of "1.2.3.4" may have the form:
[0058] 4.3.2.1. extra-information.dnsxl-customer-l.senderbase.org.
[0059] According to one embodiment, the [metafields] element of the foregoing query comprises a unique identifier string. The identifier string maps to a DNSxL configuration, a customer value, and a specific licensing period. FIG. 2 is a block diagram showing an example data structure representation that can be used for the mapping.
-S-
[0060] In FIG. 2, an identifier string 202 maps to an association 204 of a configuration, customer value, and licensing period. The configuration is stored in a table 206 organized as an array of tuples of tests and associated actions. The customer value identifies a customer. A customer mapping is provided because whenever a contract or evaluation period terminates, all queries to that DNS zone will return NXDOMAIN.
[0061] The licensing period identifies a specific licensing period and supports a business model in which the reputation service 110 collects periodic fees for providing service to customers. In an embodiment, after the licensing period ends, all queries to the associated DNS zone will return NXDOMAIN. The licensing period value is optional, and can be omitted in another embodiment.
[0062] As an implementation example, the identifier string may have a value of "customer". The license period value represents a license series that is rotated every 6 months, and the customer is responsible for updating its licensed customers to use the new series. Six months after each license series expires, the system starts delivering NXDOMAIN replies. Thus, there will be 2-3 license series in active use at any one time. Enforcement of the licensing period is described further below in connection with FIG. 3C. The use of test- action table 206 is described further below relating to step 338. [0063] 3.2 QUERY VALIDATION
[0064] In step 330, the received DNS query is validated. In one implementation, a secret string is retrieved from a configuration file associated with the customer group that includes the querying host. A new authentication value is computed based on the retrieved secret string and the network address for which the querying host is requesting information. The authentication value that was extracted at step 328 is compared to the new authentication value. If the authentication values match, then the DNS query is valid, as tested at step 332. [0065] In an embodiment, configuration file 124 specifies the secret string that is used to authorize queries. Most values are strings or integers; some, such as the score ranges, are specified as a CSV string of (score threshold, response code) pairs, colon-delimited. Table 1 presents a sample configuration file:
TABLE 1-EXAMPLE CONFIGURATION FILE
[dns] query_domain: dnsxl-jupiter defaultjtl: 30 defaultjretries: 3 txt_response: http://ww.senderbase.org?q=[IP]
[authorization] hash_key: [DATESTRING] invalidation_threshold: 100 invalidation_horizon: 1 month
[discretization] score_ranges: -5:127.0.0.5,-4:127.0.0.4, -3:127.0.0.3,-2:127.0.0.2
[0066] In the embodiment of Table 1, the [authorization] section of the configuration file contains all fields needed for validation of the associated subdomain or customer group, including:
[0067] The secret string or hash key that is used to calculate hash values is distributed to the smallest possible group. Ideally, the hash key is changed regularly, but this policy may vary in different customer groups, according to their technical details.
[0068] According to one embodiment, validation logic 114 performs step 330 to validate each query received at DNS logic 112 before the query is processed in later steps, hi one approach, each query comprises a hash value that is calculated using a secret value that is distributed only to authorized clients, e.g., mail server 106.
[0069] In one approach, queries with validation information are formatted as an extended subdomain of a master domain of reputation service 110, e.g., senderbase.org. For example, a query about an IP "a.b.c.d" is as follows:
[0070] d.c.b.a. [hashstring] .[query-subdomain] .senderbase.org
[0071] The [hashstring] element comprises a representation of an authorization hash. In one embodiment, the [hashstring] value is determined based on performing a one-way hash function on the secret string concatenated with the network address that is being queried about. A hash function such as MD5 may be used. Thus, a query about a connecting host with IP address "1.2.3.4" could look something like the following, depending on the value of the "secret" used to calculate the hash string:
[0072] 4.3.2.1.150b87d5d7fce42bf6822a561c6d8b2b.dnsxl-customer-l.senderbase.org
[0073] In one embodiment, the new hash is an MD5 hash based on a string resulting from directly concatenating the network-order, dotted-quad IP string to the end of a previously distributed secret string. Thus, if mail server 106 is querying about IP "1.2.3.4" and using passphrase "passphrase for april," the following hash string would result:
[0074] [hashstring] = MD5( [secret] + 'd.c.b.a')
[0075] = MD5("passphrase for april" + "4.3.2.1")
[0076] = MD5("passphrase for april4.3.2.1 ")
[0077] = 150b87d5d7fce42bf6822a561c6d8b2b
[0078] Therefore, given the IP address "1.2.3.4" and the secret phrase "passphrase for april", only the first of the following queries is valid:
[0079] 4.3.2.1.150b87d5d7fce42bf6822a561c6d8b2b.dnsxl-customer.senderbase.org
[0080] 4.3.2.1.150b87d5d7fce42bf68.dnsxl-customer -1.senderbase.org
[008Ϊ] 4.3.2.1.999b87d5d7fce42bf6822a561c6d8b2b.dnsxl-customer-l .senderbase.org
[0082] 4.3.2.1.150b87d5d7fce42bf6822a561c6d8b2b.dnsbl-customer -1.senderbase.org
[0083] In this approach, a correct [hashstring] value provides to the reputation service
110 that the inquiring host is authorized to send reputation service queries, because the inquiring host has proved knowledge of the secret string and asserted that the connecting host network address has not been changed in transit.
[0084] In one approach, validation of queries is performed "offline." In an offline approach, control passes from step 328 to step 334, so that every query is answered if the requesting network address is not in the blacklist at the time the query is received. A separate process implements steps 330, in which a query is validated by checking the included hashstring against a new hash that is calculated from the query.
[0085] 3.3 DETERMINING AND PERFORMING RESPONSIVE ACTIONS
[0086] Referring again to FIG. 3B, if the query is valid at step 332, then in step 334 a
DNS lookup is performed in the reputation database to obtain a reputation score for the connecting host. The reputation score is retrieved from the database at step 336.
[0087] hi step 338, a responsive action is determined, for example, based on mapping the retrieved reputation score to the test-action table 206 of FIG. 2. The responsive action is then performed. In the test-action table 206, valid tests are logical expressions combining one or more reputation score values using standard operations (<, >, ==, !=, eq, ne, etc.). In an alternative embodiment, tests can include any of several variables. For example, in one embodiment, tests can include an SBVS score, one or more TTRTRT, listings, and per-blacklist status values.
[0088] In the test-action table 206, in one embodiment, valid actions may include any of the following: Default result for a particular IP address query is NXDOMAIN; add an A record result as result named <result> and set it to <IP address>; replace A record result number with the logical AND of <mask> and A record result number <number>; set TXT record result to <text>. The set of A records returned is the list of all results named. [0089] As one example of options for the configuration table, the values shown in TABLE 2 may be used. This example presumes that customer policy allows the system to pick different actions based on the return IP address result. One IP address is returned with a basic score.
[0090] TABLE 2— EXAMPLE TEST-ACTION TABLE Test Action
SBRS <= -5 add A record "paranoid" of 127.0.0.5
SBRS <= -4 && SBRS > -5 add A record "cautious" of 127.0.0.4 SBRS <= -3 && SBRS > -4 add A record "moderate" of 127.0.0.3 SBRS <= -2 && SBRS > -3 add A record "aggressive" of 127.0.0.2 [0091] In one embodiment, a query to reputation service 110 causes DNS logic 112 to return one of the following records:
[0092] 1. An A record response of the type described in Levine et al., such as "127.0.0.3"
[0093] 2. A TXT record, comprising a URL pointing to summary of main external reasons for score.
[0094] 3. An ANY record, comprising TXT and A records.
[0095] 4. An NXDOMAIN response, which is returned for any unknown IP, or any IP whose score isn't assigned to a bin.
[0096] Other fields may be passed back in response to a query for reputation results. As an example, a response field may include a list of factors that specify information such as which blacklist an IP address is in, or other more specific information maintained locally about the IP address. The list may comprise codes that map to a table of blacklists. This approach provides an extensible approach for maintaining DNS data that can be changed over time to provide new response data.
[0097] 3.4 BLACKLIST AND LOG FILE MANAGEMENT
[0098] In one embodiment, at step 338, when DNS logic 112 is ready to issue a response to mail server 106, a network address of the mail server 106, specified in a header of the client query, is checked against blacklist 124. Thus, reputation service 110 maintains a list of
servers or clients that are unlicensed or unauthorized and from whom queries are always refused.
[0099] In step 340, a log file record is created and stored to describe the querying host and the result of the query, whether valid or invalid. Thus, step 326 also may involve creating and storing a log file record indicating that the querying host made an invalid query.
[0100] Li one embodiment, reputation service 110 may maintain a status information table in log 120 that tracks information about how a client such as mail server 106 is using the reputation service. For example, log 120 may include a Client Usage Stats table with the fields shown in TABLE 3 :
[0101] TABLE 3— EXAMPLE LOG FILE TABLE
[0102] An offline process associated with reputation service 110 monitors log 120 for network addresses that are making an unacceptable number of unauthorized queries, and adds them to the blacklist. For example, statistics process 118 of reputation service 110 may perform log monitoring. However, queries from blocked addresses cannot be entirely ignored, as they may become authorized after being blocked. Therefore, blocked queries are logged separately, and immediately processed to check for authentication status changes. [0103] When a host having a particular network address makes too many queries that are incorrect, as determined by a failure of validation logic 114 to validate the queries, the querying host is added to the blacklist 124 and subsequent queries are rejected by DNS logic 112 at step 324. When such a host begins making queries with valid hashes, it is then allowed to make queries. Mechanisms for de-authorizing and re-authorizing querying hosts are described further below
[0104] In one embodiment, statistics process 118 periodically parses log 120 (or some sample thereof) and maintaining data on servers, clients or network addresses that are making queries. Statistics process may log total usage and may check authorization hashes in
queries. Invalid queries are counted in log 120 by statistics process 118, while a single valid query will reset the count of invalid queries for that IP to zero.
[0105] In one embodiment, a Client De-authorization and Re-authorization process 122 periodically checks log 120 or communicates with statistics process 118 to identify servers, clients or network addresses exceeding a threshold of unauthorized queries. An example threshold is 100 invalid queries. Servers, clients or network addresses that exceed the threshold are added to the blacklist 126.
[0106] In another embodiment, client de-authorization process 122 further processes log 122 to identify rejected queries to see if any previously rejected servers, clients or network addresses have started making valid queries. Any rejected address that makes a single valid request is rapidly removed from the blacklist, and the count of invalid requests for that address is reset to zero.
[0107] Referring now to FIG. 3 C, an example approach for de-authorizing querying hosts initiates at step 350 and reads a log file entry at step 352. The log file entry relates to a prior query for reputation score information from a querying host. At step 354, the querying host is identified. At step 356, a test is performed to determine whether the query was invalid. [0108] If the query was invalid, then in step 358 a counter of invalid queries for that querying host is incremented. The counter may be stored in database 116 or another repository. In step 360, a test is performed to determine whether an invalidation threshold for the querying host has been exceeded. The invalidation threshold may be obtained from the configuration file 124 for the querying host.
[0109] If the invalidation threshold has been exceeded, then in step 362 the querying host is placed in a blacklist, such as blacklist 124. If the invalidation threshold has not been exceeded, then in step 364 a test is performed to determine whether a license period for the querying host has expired. If so, then in step 362 the querying host is placed in a blacklist, such as blacklist 124. The license period test of step 364 is also performed when the query is determined to be valid at step 356.
[0110] The process of steps 352 to 362 may be repeated for all entries in the log file. [0111] 4.0 IMPLEMENTATION MECHANISMS - HARDWARE OVERVIEW [0112] FIG. 4 is a block diagram that illustrates a computer system 400 upon which an embodiment of the invention may be implemented. Computer system 400 includes a bus 402 or other communication mechanism for communicating information, and a processor 404 coupled with bus 402 for processing information. Computer system 400 also includes a main memory 406, such as a random access memory ("RAM") or other dynamic storage device, coupled to bus 402 for storing information and instructions to be executed by processor 404.
Main memory 406 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 404. Computer system 400 further includes a read only memory ("ROM") 408 or other static storage device coupled to bus 402 for storing static information and instructions for processor 404. A storage device 410, such as a magnetic disk or optical disk, is provided and coupled to bus 402 for storing information and instructions.
[0113] Computer system 400 may be coupled via bus 402 to a display 412, such as a cathode ray tube ("CRT"), for displaying information to a computer user. An input device 414, including alphanumeric and other keys, is coupled to bus 402 for communicating information and command selections to processor 404. Another type of user input device is cursor control 416, such as a mouse, trackball, stylus, or cursor direction keys for communicating direction information and command selections to processor 404 and for controlling cursor movement on display 412. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allows the device to specify positions in a plane.
[0114] The invention is related to the use of computer system 400 for message processing approaches. According to one embodiment of the invention, message-processing approaches are provided by computer system 400 in response to processor 404 executing one or more sequences of one or more instructions contained in main memory 406. Such instructions may be read into main memory 406 from another computer-readable medium, such as storage device 410. Execution of the sequences of instructions contained in main memory 406 causes processor 404 to perform the process steps described herein. In alternative embodiments, hard- wired circuitry may be used in place of or in combination with software instructions to implement the invention. Thus, embodiments of the invention are not limited to any specific combination of hardware circuitry and software.
[0115] The term "computer-readable medium" as used herein refers to any medium that participates in providing instructions to processor 404 for execution. Such a medium may take many forms, including but not limited to, non- volatile media, volatile media, and transmission media. Non- volatile media includes, for example, optical or magnetic disks, such as storage device 410. Volatile media includes dynamic memory, such as main memory 406. Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 402. Transmission media can also take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications. [0116] Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other
optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read. [0117] Various forms of computer readable media may be involved in carrying one or more sequences of one or more instructions to processor 404 for execution. For example, the instructions may initially be carried on a magnetic disk of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to computer system 400 can receive the data on the telephone line and use an infrared transmitter to convert the data to an infrared signal. An infrared detector can receive the data carried in the infrared signal and appropriate circuitry can place the data on bus 402. Bus 402 carries the data to main memory 406, from which processor 404 retrieves and executes the instructions. The instructions received by main memory 406 may optionally be stored on storage device 410 either before or after execution by processor 404.
[0118] Computer system 400 also includes a communication interface 418 coupled to bus 402. Communication interface 418 provides a two-way data communication coupling to a network link 420 that is connected to a local network 422. For example, communication interface 418 may be an integrated services digital network ("ISDN") card or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, communication interface 418 may be a local area network ("LAN") card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, communication interface 418 sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
[0119] Network link 420 typically provides data communication through one or more networks to other data devices. For example, network link 420 may provide a connection through local network 422 to a host computer 424 or to data equipment operated by an Internet Service Provider ("ISP") 426. ISP 426 in turn provides data communication services through the worldwide packet data communication network now commonly referred to as the "Internet" 428. Local network 422 and Internet 428 both use electrical, electromagnetic or optical signals that carry digital data streams. The signals through the various networks and the signals on network link 420 and through communication interface 418, which carry the digital data to and from computer system 400, are exemplary forms of carrier waves transporting the information.
[0120] Computer system 400 can send messages and receive data, including program code, through the network(s), network link 420 and communication interface 418. In the Internet example, a server 430 might transmit a requested code for an application program through Internet 428, ISP 426, local network 422 and communication interface 418. In accordance with the invention, one such downloaded application provides for message processing approaches as described herein.
[0121] The received code may be executed by processor 404 as it is received, and/or stored in storage device 410, or other non- volatile storage for later execution. In this manner, computer system 400 may obtain application code in the form of a carrier wave. [0122] 5.0 EXTENSIONS AND ALTERNATIVES
[0123] m the foregoing specification, the invention has been described with reference to specific embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.
Claims
1. An apparatus, comprising: a network interface that is coupled to the data network for receiving one or more packet flows therefrom; a processor; one or more stored sequences of instructions which, when executed by the processor, cause the processor to perform: receiving, from a first host computer, a DNS format query to obtain a reputation score associated with a second host computer, wherein the query includes an authentication code; validating the authentication code; only when validating the authentication code is successful, performing a DNS lookup in a reputation database and returning a DNS response that provides the reputation score associated with the second host computer.
2. The apparatus of claim 1, further comprising sequences of instructions which, when executed by the processor, cause the processor to perform sending an NXDOMAIN record to the first host computer when validating the authentication code is unsuccessful.
3. The apparatus of claim 1, further comprising sequences of instructions which, when executed by the processor, cause the processor to perform determining whether the first computer is listed in a blacklist, and sending an NXDOMAIN record to the first host computer without validating the authentication code when the first computer is listed in the blacklist.
4. The apparatus of claim 1, further comprising sequences of instructions which, when executed by the processor, cause the processor to perform: establishing a master domain and a plurality of subdomains, wherein each of the subdomains is associated with a respective customer group; receiving the DNS format query from the first computer at a particular subdomain that is associated with a particular customer group, wherein the first computer is associated with the particular customer group, wherein the DNS format query includes an identifier of the particular customer group.
5. The apparatus of claim 4, further comprising sequences of instructions which, when executed by the processor, cause the processor to perform: retrieving configuration information associated with the particular customer group, wherein the configuration information for the particular customer group maps one or more discrete sets of reputation values to respective responsive actions; determining, by mapping the reputation score for the second host computer to one of the discrete sets in the configuration information, a particular responsive action; and performing the particular responsive action.
6. The apparatus of claim 1, further comprising sequences of instructions which, when executed by the processor, cause the processor to perform: creating and storing, in a log file, a log entry that identifies the first computer and whether validation of the DNS format query was successful; periodically reading the log file, determining whether the first computer has issued a number of queries that exceeds an invalidation threshold for the first computer, and adding the first computer to the blacklist when the first computer has issued a number of queries that exceeds an invalidation threshold for the first computer.
7. The apparatus of claim 1, further comprising sequences of instructions which, when executed by the processor, cause the processor to perform: retrieving configuration information associated with the first computer, wherein the configuration information identifies a time in which the first computer is allowed to send queries; determining whether the time has expired; adding the first computer to the blacklist when the time has expired.
8. An apparatus, comprising: means for receiving, from a first host computer, a DNS format query to obtain a reputation score associated with a second host computer, wherein the query includes an authentication code; means for validating the authentication code; means for performing a DNS lookup in a reputation database and returning a DNS response that provides the reputation score associated with the second host computer only when validating the authentication code is successful.
9. The apparatus of claim 8, further comprising means for sending an NXDOMAIN record to the first host computer when validating the authentication code is unsuccessful.
10. The apparatus of claim 8, further comprising means for determining whether the first computer is listed in a blacklist, and sending an NXDOMAIN record to the first host computer without validating the authentication code when the first computer is listed in the blacklist.
11. The apparatus of claim 8, further comprising: means for establishing a master domain and a plurality of subdomains, wherein each of the subdomains is associated with a respective customer group; means for receiving the DNS format query from the first computer at a particular subdomain that is associated with a particular customer group, wherein the first computer is associated with the particular customer group, wherein the DNS format query includes an identifier of the particular customer group.
12. The apparatus of claim 11 , further comprising: means for retrieving configuration information associated with the particular customer group, wherein the configuration information for the particular customer group maps one or more discrete sets of reputation values to respective responsive actions; means for determining, by mapping the reputation score for the second host computer to one of the discrete sets in the configuration information, a particular responsive action; and means for performing the particular responsive action.
13. The apparatus of claim 8, further comprising: means for creating and storing, in a log file, a log entry that identifies the first computer and whether validation of the DNS format query was successful; means for periodically reading the log file, determining whether the first computer has issued a number of queries that exceeds an invalidation threshold for the first computer, and for adding the first computer to the blacklist when the first computer has issued a number of queries that exceeds an invalidation threshold for the first computer.
14. The apparatus of claim 8, further comprising: means for retrieving configuration information associated with the first computer, wherein the configuration information identifies a time in which the first computer is allowed to send queries; means for determining whether the time has expired; means for adding the first computer to the blacklist when the time has expired.
15. A machine-implemented method comprising: receiving, from a first host computer, a DNS format query to obtain a reputation score associated with a second host computer, wherein the query includes an authentication code; validating the authentication code; only when validating the authentication code is successful, performing a DNS lookup in a reputation database and returning a DNS response that provides the reputation score associated with the second host computer.
16. The method of claim 15, further comprising sending an NXDOMAIN record to the first host computer when validating the authentication code is unsuccessful.
17. The method of claim 15, further comprising determining whether the first computer is listed in a blacklist, and sending an NXDOMAJN record to the first host computer without validating the authentication code when the first computer is listed in the blacklist.
18. The method of claim 15, further comprising: establishing a master domain and a plurality of subdomains, wherein each of the subdomains is associated with a respective customer group; receiving the DNS format query from the first computer at a particular subdomain that is associated with a particular customer group, wherein the first computer is associated with the particular customer group, wherein the DNS format query includes an identifier of the particular customer group.
19. The method of claim 18, further comprising: retrieving configuration information associated with the particular customer group, wherein the configuration information for the particular customer group maps one or more discrete sets of reputation values to respective responsive actions; determining, by mapping the reputation score for the second host computer to one of the discrete sets in the configuration information, a particular responsive action; and performing the particular responsive action.
20. The method of claim 15, further comprising: creating and storing, in a log file, a log entry that identifies the first computer and whether validation of the DNS format query was successful; periodically reading the log file, determining whether the first computer has issued a number of queries that exceeds an invalidation threshold for the first computer, and adding the first computer to the blacklist when the first computer has issued a number of queries that exceeds an invalidation threshold for the first computer.
21. The method of claim 15, further comprising: retrieving configuration information associated with the first computer, wherein the configuration information identifies a time in which the first computer is allowed to send queries; determining whether the time has expired; adding the first computer to the blacklist when the time has expired.
22. A computer-readable medium carrying one or more sequences of instructions, which instructions, when executed by one or more processors, cause the one or more processors to carry out the steps of: receiving, from a first host computer, a DNS format query to obtain a reputation score associated with a second host computer, wherein the query includes an authentication code; validating the authentication code; only when validating the authentication code is successful, performing a DNS lookup in a reputation database and returning a DNS response that provides the reputation score associated with the second host computer.
23. The computer-readable medium of claim 22, further comprising sequences of instructions which, when executed by the processor, cause the processor to perform sending an NXDOMAIN record to the first host computer when validating the authentication code is unsuccessful.
24. The computer-readable medium of claim 22, further comprising sequences of instructions which, when executed by the processor, cause the processor to perform determining whether the first computer is listed in a blacklist, and sending an NXDOMAIN record to the first host computer without validating the authentication code when the first computer is listed in the blacklist.
25. The computer-readable medium of claim 22, further comprising sequences of instructions which, when executed by the processor, cause the processor to perform: establishing a master domain and a plurality of subdomains, wherein each of the subdomains is associated with a respective customer group; receiving the DNS format query from the first computer at a particular subdomain that is associated with a particular customer group, wherein the first computer is associated with the particular customer group, wherein the DNS format query includes an identifier of the particular customer group.
26. The computer-readable medium of claim 25, further comprising sequences of instructions which, when executed by the processor, cause the processor to perform: retrieving configuration information associated with the particular customer group, wherein the configuration information for the particular customer group maps one or more discrete sets of reputation values to respective responsive actions; determining, by mapping the reputation score for the second host computer to one of the discrete sets in the configuration information, a particular responsive action; and performing the particular responsive action.
27. The computer-readable medium of claim 22, further comprising sequences of instructions which, when executed by the processor, cause the processor to perform: creating and storing, in a log file, a log entry that identifies the first computer and whether validation of the DNS format query was successful; periodically reading the log file, determining whether the first computer has issued a number of queries that exceeds an invalidation threshold for the first computer, and adding the first computer to the blacklist when the first computer has issued a number of queries that exceeds an invalidation threshold for the first computer.
28. The computer-readable medium of claim 22, further comprising sequences of instructions which, when executed by the processor, cause the processor to perform: retrieving configuration information associated with the first computer, wherein the configuration information identifies a time in which the first computer is allowed to send queries; determining whether the time has expired; adding the first computer to the blacklist when the time has expired.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US67839105P | 2005-05-05 | 2005-05-05 | |
US60/678,391 | 2005-05-05 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2006119506A2 true WO2006119506A2 (en) | 2006-11-09 |
WO2006119506A3 WO2006119506A3 (en) | 2009-04-16 |
Family
ID=37308748
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2006/017780 WO2006119506A2 (en) | 2005-05-05 | 2006-05-05 | Method of validating requests for sender reputation information |
PCT/US2006/017783 WO2006119509A2 (en) | 2005-05-05 | 2006-05-05 | Identifying threats in electronic messages |
PCT/US2006/017782 WO2006119508A2 (en) | 2005-05-05 | 2006-05-05 | Detecting unwanted electronic mail messages based on probabilistic analysis of referenced resources |
PCT/US2006/017773 WO2006122055A2 (en) | 2005-05-05 | 2006-05-05 | Method of determining network addresses of senders of electronic mail messages |
Family Applications After (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2006/017783 WO2006119509A2 (en) | 2005-05-05 | 2006-05-05 | Identifying threats in electronic messages |
PCT/US2006/017782 WO2006119508A2 (en) | 2005-05-05 | 2006-05-05 | Detecting unwanted electronic mail messages based on probabilistic analysis of referenced resources |
PCT/US2006/017773 WO2006122055A2 (en) | 2005-05-05 | 2006-05-05 | Method of determining network addresses of senders of electronic mail messages |
Country Status (6)
Country | Link |
---|---|
US (6) | US7548544B2 (en) |
EP (2) | EP1877905B1 (en) |
JP (2) | JP4880675B2 (en) |
CN (2) | CN101495969B (en) |
CA (2) | CA2607005C (en) |
WO (4) | WO2006119506A2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101378407B (en) * | 2008-09-26 | 2012-10-17 | 成都市华为赛门铁克科技有限公司 | Method, system and equipment for pushing information |
EP3206364A1 (en) * | 2016-02-10 | 2017-08-16 | Agari Data, Inc | Message authenticity and risk assessment |
Families Citing this family (663)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030097654A1 (en) * | 1998-06-05 | 2003-05-22 | Franken Kenneth A. | System and method of geographic authorization for television and radio programming distributed by multiple delivery mechanisms |
US8010981B2 (en) | 2001-02-08 | 2011-08-30 | Decisionmark Corp. | Method and system for creating television programming guide |
US8219620B2 (en) | 2001-02-20 | 2012-07-10 | Mcafee, Inc. | Unwanted e-mail filtering system including voting feedback |
US7913287B1 (en) | 2001-06-15 | 2011-03-22 | Decisionmark Corp. | System and method for delivering data over an HDTV digital television spectrum |
US8407798B1 (en) | 2002-10-01 | 2013-03-26 | Skybox Secutiry Inc. | Method for simulation aided security event management |
US8359650B2 (en) * | 2002-10-01 | 2013-01-22 | Skybox Secutiry Inc. | System, method and computer readable medium for evaluating potential attacks of worms |
US8195714B2 (en) * | 2002-12-11 | 2012-06-05 | Leaper Technologies, Inc. | Context instantiated application protocol |
US8548170B2 (en) | 2003-12-10 | 2013-10-01 | Mcafee, Inc. | Document de-registration |
US7984175B2 (en) | 2003-12-10 | 2011-07-19 | Mcafee, Inc. | Method and apparatus for data capture and analysis system |
US8656039B2 (en) | 2003-12-10 | 2014-02-18 | Mcafee, Inc. | Rule parser |
US8214438B2 (en) | 2004-03-01 | 2012-07-03 | Microsoft Corporation | (More) advanced spam detection features |
US7587537B1 (en) | 2007-11-30 | 2009-09-08 | Altera Corporation | Serializer-deserializer circuits formed from input-output circuit registers |
US8584239B2 (en) | 2004-04-01 | 2013-11-12 | Fireeye, Inc. | Virtual machine with dynamic data flow analysis |
US8528086B1 (en) | 2004-04-01 | 2013-09-03 | Fireeye, Inc. | System and method of detecting computer worms |
US9106694B2 (en) | 2004-04-01 | 2015-08-11 | Fireeye, Inc. | Electronic message analysis for malware detection |
US8898788B1 (en) | 2004-04-01 | 2014-11-25 | Fireeye, Inc. | Systems and methods for malware attack prevention |
US8171553B2 (en) | 2004-04-01 | 2012-05-01 | Fireeye, Inc. | Heuristic based capture with replay to virtual machine |
US8881282B1 (en) | 2004-04-01 | 2014-11-04 | Fireeye, Inc. | Systems and methods for malware attack detection and identification |
US8566946B1 (en) | 2006-04-20 | 2013-10-22 | Fireeye, Inc. | Malware containment on connection |
US8549638B2 (en) | 2004-06-14 | 2013-10-01 | Fireeye, Inc. | System and method of containing computer worms |
US8793787B2 (en) | 2004-04-01 | 2014-07-29 | Fireeye, Inc. | Detecting malicious network content using virtual environment components |
US8560534B2 (en) | 2004-08-23 | 2013-10-15 | Mcafee, Inc. | Database for a capture system |
US7949849B2 (en) | 2004-08-24 | 2011-05-24 | Mcafee, Inc. | File system for a capture system |
US20060200528A1 (en) * | 2005-01-25 | 2006-09-07 | Krishna Pathiyal | Method and system for processing data messages |
US7860006B1 (en) * | 2005-04-27 | 2010-12-28 | Extreme Networks, Inc. | Integrated methods of performing network switch functions |
US7562304B2 (en) * | 2005-05-03 | 2009-07-14 | Mcafee, Inc. | Indicating website reputations during website manipulation of user information |
US8438499B2 (en) * | 2005-05-03 | 2013-05-07 | Mcafee, Inc. | Indicating website reputations during user interactions |
US20060253584A1 (en) * | 2005-05-03 | 2006-11-09 | Dixon Christopher J | Reputation of an entity associated with a content item |
US7765481B2 (en) * | 2005-05-03 | 2010-07-27 | Mcafee, Inc. | Indicating website reputations during an electronic commerce transaction |
US9384345B2 (en) * | 2005-05-03 | 2016-07-05 | Mcafee, Inc. | Providing alternative web content based on website reputation assessment |
US8566726B2 (en) | 2005-05-03 | 2013-10-22 | Mcafee, Inc. | Indicating website reputations based on website handling of personal information |
US7822620B2 (en) * | 2005-05-03 | 2010-10-26 | Mcafee, Inc. | Determining website reputations using automatic testing |
US20060253582A1 (en) * | 2005-05-03 | 2006-11-09 | Dixon Christopher J | Indicating website reputations within search results |
US20060277259A1 (en) * | 2005-06-07 | 2006-12-07 | Microsoft Corporation | Distributed sender reputations |
GB2427048A (en) | 2005-06-09 | 2006-12-13 | Avecho Group Ltd | Detection of unwanted code or data in electronic mail |
US20070036279A1 (en) * | 2005-06-09 | 2007-02-15 | Tam Kenneth C | Personal notification and broadcasting |
US8522347B2 (en) * | 2009-03-16 | 2013-08-27 | Sonicwall, Inc. | Real-time network updates for malicious content |
US7636734B2 (en) * | 2005-06-23 | 2009-12-22 | Microsoft Corporation | Method for probabilistic analysis of most frequently occurring electronic message addresses within personal store (.PST) files to determine owner with confidence factor based on relative weight and set of user-specified factors |
US20090144826A2 (en) * | 2005-06-30 | 2009-06-04 | Webroot Software, Inc. | Systems and Methods for Identifying Malware Distribution |
US8560413B1 (en) * | 2005-07-14 | 2013-10-15 | John S. Quarterman | Method and system for detecting distributed internet crime |
US7610345B2 (en) | 2005-07-28 | 2009-10-27 | Vaporstream Incorporated | Reduced traceability electronic message system and method |
US9282081B2 (en) | 2005-07-28 | 2016-03-08 | Vaporstream Incorporated | Reduced traceability electronic message system and method |
US7565358B2 (en) * | 2005-08-08 | 2009-07-21 | Google Inc. | Agent rank |
US7907608B2 (en) | 2005-08-12 | 2011-03-15 | Mcafee, Inc. | High speed packet capture |
US8024799B2 (en) * | 2005-08-19 | 2011-09-20 | Cpacket Networks, Inc. | Apparatus and method for facilitating network security with granular traffic modifications |
US8665868B2 (en) * | 2005-08-19 | 2014-03-04 | Cpacket Networks, Inc. | Apparatus and method for enhancing forwarding and classification of network traffic with prioritized matching and categorization |
US8296846B2 (en) * | 2005-08-19 | 2012-10-23 | Cpacket Networks, Inc. | Apparatus and method for associating categorization information with network traffic to facilitate application level processing |
US8346918B2 (en) * | 2005-08-19 | 2013-01-01 | Cpacket Networks, Inc. | Apparatus and method for biased and weighted sampling of network traffic to facilitate network monitoring |
US8769663B2 (en) | 2005-08-24 | 2014-07-01 | Fortinet, Inc. | Systems and methods for detecting undesirable network traffic content |
US8028337B1 (en) | 2005-08-30 | 2011-09-27 | Sprint Communications Company L.P. | Profile-aware filtering of network traffic |
US8204974B1 (en) * | 2005-08-30 | 2012-06-19 | Sprint Communications Company L.P. | Identifying significant behaviors within network traffic |
US7818326B2 (en) | 2005-08-31 | 2010-10-19 | Mcafee, Inc. | System and method for word indexing in a capture system and querying thereof |
US20070061402A1 (en) * | 2005-09-15 | 2007-03-15 | Microsoft Corporation | Multipurpose internet mail extension (MIME) analysis |
US7925786B2 (en) * | 2005-09-16 | 2011-04-12 | Microsoft Corp. | Hosting of network-based services |
US7730011B1 (en) | 2005-10-19 | 2010-06-01 | Mcafee, Inc. | Attributes of captured objects in a capture system |
US20070129999A1 (en) * | 2005-11-18 | 2007-06-07 | Jie Zhou | Fraud detection in web-based advertising |
US8255480B2 (en) | 2005-11-30 | 2012-08-28 | At&T Intellectual Property I, L.P. | Substitute uniform resource locator (URL) generation |
US8595325B2 (en) * | 2005-11-30 | 2013-11-26 | At&T Intellectual Property I, L.P. | Substitute uniform resource locator (URL) form |
US20070124500A1 (en) * | 2005-11-30 | 2007-05-31 | Bedingfield James C Sr | Automatic substitute uniform resource locator (URL) generation |
US8255996B2 (en) | 2005-12-30 | 2012-08-28 | Extreme Networks, Inc. | Network threat detection and mitigation |
US8185741B1 (en) * | 2006-01-30 | 2012-05-22 | Adobe Systems Incorporated | Converting transport level transactional security into a persistent document signature |
US8601160B1 (en) | 2006-02-09 | 2013-12-03 | Mcafee, Inc. | System, method and computer program product for gathering information relating to electronic content utilizing a DNS server |
US9392009B2 (en) * | 2006-03-02 | 2016-07-12 | International Business Machines Corporation | Operating a network monitoring entity |
US8504537B2 (en) | 2006-03-24 | 2013-08-06 | Mcafee, Inc. | Signature distribution in a document registration system |
US7854006B1 (en) | 2006-03-31 | 2010-12-14 | Emc Corporation | Differential virus scan |
US8443445B1 (en) * | 2006-03-31 | 2013-05-14 | Emc Corporation | Risk-aware scanning of objects |
US8701196B2 (en) | 2006-03-31 | 2014-04-15 | Mcafee, Inc. | System, method and computer program product for obtaining a reputation associated with a file |
US8205261B1 (en) | 2006-03-31 | 2012-06-19 | Emc Corporation | Incremental virus scan |
US7752274B2 (en) * | 2006-04-03 | 2010-07-06 | International Business Machines Corporation | Apparatus and method for filtering and selectively inspecting e-mail |
US7849502B1 (en) | 2006-04-29 | 2010-12-07 | Ironport Systems, Inc. | Apparatus for monitoring network traffic |
US8849760B2 (en) * | 2006-05-02 | 2014-09-30 | International Business Machines Corporation | Determining whether predefined data controlled by a server is replicated to a client machine |
US8706470B2 (en) * | 2006-05-08 | 2014-04-22 | David T. Lorenzen | Methods of offering guidance on common language usage utilizing a hashing function consisting of a hash triplet |
US7603350B1 (en) | 2006-05-09 | 2009-10-13 | Google Inc. | Search result ranking based on trust |
US20070282770A1 (en) * | 2006-05-15 | 2007-12-06 | Nortel Networks Limited | System and methods for filtering electronic communications |
US7921063B1 (en) | 2006-05-17 | 2011-04-05 | Daniel Quinlan | Evaluating electronic mail messages based on probabilistic analysis |
US20080082662A1 (en) * | 2006-05-19 | 2008-04-03 | Richard Dandliker | Method and apparatus for controlling access to network resources based on reputation |
US7958227B2 (en) | 2006-05-22 | 2011-06-07 | Mcafee, Inc. | Attributes of captured objects in a capture system |
US8191140B2 (en) * | 2006-05-31 | 2012-05-29 | The Invention Science Fund I, Llc | Indicating a security breach of a protected set of files |
US8640247B2 (en) * | 2006-05-31 | 2014-01-28 | The Invention Science Fund I, Llc | Receiving an indication of a security breach of a protected set of files |
US20070282723A1 (en) * | 2006-05-31 | 2007-12-06 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Monitoring a status of a database by placing a false identifier in the database |
US8209755B2 (en) * | 2006-05-31 | 2012-06-26 | The Invention Science Fund I, Llc | Signaling a security breach of a protected set of files |
US20070294767A1 (en) * | 2006-06-20 | 2007-12-20 | Paul Piccard | Method and system for accurate detection and removal of pestware |
US8122507B1 (en) | 2006-06-28 | 2012-02-21 | Emc Corporation | Efficient scanning of objects |
US8087084B1 (en) | 2006-06-28 | 2011-12-27 | Emc Corporation | Security for scanning objects |
US20080005315A1 (en) * | 2006-06-29 | 2008-01-03 | Po-Ching Lin | Apparatus, system and method for stream-based data filtering |
US20080005249A1 (en) * | 2006-07-03 | 2008-01-03 | Hart Matt E | Method and apparatus for determining the importance of email messages |
US8615800B2 (en) | 2006-07-10 | 2013-12-24 | Websense, Inc. | System and method for analyzing web content |
US8020206B2 (en) | 2006-07-10 | 2011-09-13 | Websense, Inc. | System and method of analyzing web content |
US8059646B2 (en) | 2006-07-11 | 2011-11-15 | Napo Enterprises, Llc | System and method for identifying music content in a P2P real time recommendation network |
US7970922B2 (en) * | 2006-07-11 | 2011-06-28 | Napo Enterprises, Llc | P2P real time media recommendations |
US8327266B2 (en) | 2006-07-11 | 2012-12-04 | Napo Enterprises, Llc | Graphical user interface system for allowing management of a media item playlist based on a preference scoring system |
US9003056B2 (en) | 2006-07-11 | 2015-04-07 | Napo Enterprises, Llc | Maintaining a minimum level of real time media recommendations in the absence of online friends |
US8001603B1 (en) * | 2006-07-24 | 2011-08-16 | Symantec Corporation | Variable scan of files based on file context |
US8082587B2 (en) * | 2006-08-02 | 2011-12-20 | Lycos, Inc. | Detecting content in files |
US7971257B2 (en) * | 2006-08-03 | 2011-06-28 | Symantec Corporation | Obtaining network origins of potential software threats |
US8190868B2 (en) | 2006-08-07 | 2012-05-29 | Webroot Inc. | Malware management through kernel detection |
US8090606B2 (en) | 2006-08-08 | 2012-01-03 | Napo Enterprises, Llc | Embedded media recommendations |
US8620699B2 (en) | 2006-08-08 | 2013-12-31 | Napo Enterprises, Llc | Heavy influencer media recommendations |
US20160248813A1 (en) * | 2006-08-23 | 2016-08-25 | Threatstop, Inc. | Method and system for propagating network policy |
US8533822B2 (en) * | 2006-08-23 | 2013-09-10 | Threatstop, Inc. | Method and system for propagating network policy |
US20080077704A1 (en) * | 2006-09-24 | 2008-03-27 | Void Communications, Inc. | Variable Electronic Communication Ping Time System and Method |
US8087088B1 (en) | 2006-09-28 | 2011-12-27 | Whitehat Security, Inc. | Using fuzzy classification models to perform matching operations in a web application security scanner |
CN101155182A (en) * | 2006-09-30 | 2008-04-02 | 阿里巴巴公司 | Garbage information filtering method and apparatus based on network |
US20080086555A1 (en) * | 2006-10-09 | 2008-04-10 | David Alexander Feinleib | System and Method for Search and Web Spam Filtering |
US7882187B2 (en) | 2006-10-12 | 2011-02-01 | Watchguard Technologies, Inc. | Method and system for detecting undesired email containing image-based messages |
US8306199B2 (en) * | 2006-10-20 | 2012-11-06 | Nokia Corporation | Accounting in a transit network |
CN101569136B (en) * | 2006-11-03 | 2013-08-28 | 网络通保安有限公司 | Administration portal |
US8484733B2 (en) | 2006-11-28 | 2013-07-09 | Cisco Technology, Inc. | Messaging security device |
US7962460B2 (en) | 2006-12-01 | 2011-06-14 | Scenera Technologies, Llc | Methods, systems, and computer program products for determining availability of presentable content via a subscription service |
US9654495B2 (en) * | 2006-12-01 | 2017-05-16 | Websense, Llc | System and method of analyzing web addresses |
GB2444514A (en) * | 2006-12-04 | 2008-06-11 | Glasswall | Electronic file re-generation |
US9729513B2 (en) | 2007-11-08 | 2017-08-08 | Glasswall (Ip) Limited | Using multiple layers of policy management to manage risk |
CN100555991C (en) * | 2006-12-29 | 2009-10-28 | 华为技术有限公司 | The method of message access control, forwarding engine device and communication equipment |
US8312536B2 (en) * | 2006-12-29 | 2012-11-13 | Symantec Corporation | Hygiene-based computer security |
WO2008087438A1 (en) * | 2007-01-18 | 2008-07-24 | Roke Manor Research Limited | A method of extracting sections of a data stream |
GB2458094A (en) * | 2007-01-09 | 2009-09-09 | Surfcontrol On Demand Ltd | URL interception and categorization in firewalls |
US20090070185A1 (en) * | 2007-01-17 | 2009-03-12 | Concert Technology Corporation | System and method for recommending a digital media subscription service |
KR100850911B1 (en) * | 2007-01-19 | 2008-08-07 | 삼성전자주식회사 | Apparatus and method for message transmission |
US20080177843A1 (en) * | 2007-01-22 | 2008-07-24 | Microsoft Corporation | Inferring email action based on user input |
US8214497B2 (en) | 2007-01-24 | 2012-07-03 | Mcafee, Inc. | Multi-dimensional reputation scoring |
US8763114B2 (en) | 2007-01-24 | 2014-06-24 | Mcafee, Inc. | Detecting image spam |
US8027975B2 (en) * | 2007-01-31 | 2011-09-27 | Reputation.Com, Inc. | Identifying and changing personal information |
CN101622849B (en) | 2007-02-02 | 2014-06-11 | 网圣公司 | System and method for adding context to prevent data leakage over a computer network |
US20080201722A1 (en) * | 2007-02-20 | 2008-08-21 | Gurusamy Sarathy | Method and System For Unsafe Content Tracking |
US7904958B2 (en) * | 2007-02-27 | 2011-03-08 | Symantec Corporation | Spam honeypot domain identification |
US9224427B2 (en) | 2007-04-02 | 2015-12-29 | Napo Enterprises LLC | Rating media item recommendations using recommendation paths and/or media item usage |
US8112720B2 (en) | 2007-04-05 | 2012-02-07 | Napo Enterprises, Llc | System and method for automatically and graphically associating programmatically-generated media item recommendations related to a user's socially recommended media items |
US9246938B2 (en) * | 2007-04-23 | 2016-01-26 | Mcafee, Inc. | System and method for detecting malicious mobile program code |
US20080281606A1 (en) * | 2007-05-07 | 2008-11-13 | Microsoft Corporation | Identifying automated click fraud programs |
US8230023B2 (en) | 2007-05-17 | 2012-07-24 | International Business Machines Corporation | Managing email disk usage based on user specified conditions |
GB0709527D0 (en) | 2007-05-18 | 2007-06-27 | Surfcontrol Plc | Electronic messaging system, message processing apparatus and message processing method |
US8613092B2 (en) * | 2007-05-21 | 2013-12-17 | Mcafee, Inc. | System, method and computer program product for updating a security system definition database based on prioritized instances of known unwanted data |
US9083556B2 (en) * | 2007-05-31 | 2015-07-14 | Rpx Clearinghouse Llc | System and method for detectng malicious mail from spam zombies |
US9037632B2 (en) | 2007-06-01 | 2015-05-19 | Napo Enterprises, Llc | System and method of generating a media item recommendation message with recommender presence information |
US8285776B2 (en) | 2007-06-01 | 2012-10-09 | Napo Enterprises, Llc | System and method for processing a received media item recommendation message comprising recommender presence information |
US9164993B2 (en) | 2007-06-01 | 2015-10-20 | Napo Enterprises, Llc | System and method for propagating a media item recommendation message comprising recommender presence information |
US20090049045A1 (en) | 2007-06-01 | 2009-02-19 | Concert Technology Corporation | Method and system for sorting media items in a playlist on a media device |
US7865965B2 (en) | 2007-06-15 | 2011-01-04 | Microsoft Corporation | Optimization of distributed anti-virus scanning |
US9374242B2 (en) | 2007-11-08 | 2016-06-21 | Invention Science Fund I, Llc | Using evaluations of tentative message content |
US20090063585A1 (en) * | 2007-08-31 | 2009-03-05 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Using party classifiability to inform message versioning |
US8984133B2 (en) | 2007-06-19 | 2015-03-17 | The Invention Science Fund I, Llc | Providing treatment-indicative feedback dependent on putative content treatment |
US20080320088A1 (en) * | 2007-06-19 | 2008-12-25 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Helping valuable message content pass apparent message filtering |
US20090063632A1 (en) * | 2007-08-31 | 2009-03-05 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Layering prospective activity information |
US7899870B2 (en) * | 2007-06-25 | 2011-03-01 | Microsoft Corporation | Determination of participation in a malicious software campaign |
US20090064329A1 (en) * | 2007-06-25 | 2009-03-05 | Google Inc. | Zero-hour quarantine of suspect electronic messages |
US8849921B2 (en) * | 2007-06-28 | 2014-09-30 | Symantec Corporation | Method and apparatus for creating predictive filters for messages |
US8584094B2 (en) * | 2007-06-29 | 2013-11-12 | Microsoft Corporation | Dynamically computing reputation scores for objects |
US20090006211A1 (en) * | 2007-07-01 | 2009-01-01 | Decisionmark Corp. | Network Content And Advertisement Distribution System and Method |
US20090012965A1 (en) * | 2007-07-01 | 2009-01-08 | Decisionmark Corp. | Network Content Objection Handling System and Method |
JP4945344B2 (en) * | 2007-07-02 | 2012-06-06 | 日本電信電話株式会社 | Packet filtering method and packet filtering system |
US8849909B2 (en) * | 2007-07-06 | 2014-09-30 | Yahoo! Inc. | Real-time asynchronous event aggregation systems |
US20090019041A1 (en) * | 2007-07-11 | 2009-01-15 | Marc Colando | Filename Parser and Identifier of Alternative Sources for File |
US7818384B2 (en) * | 2007-07-26 | 2010-10-19 | Rachal Eric M | Simultaneous synchronous split-domain email routing with conflict resolution |
CN101373456A (en) * | 2007-08-22 | 2009-02-25 | 国际商业机器公司 | Method and proxy for supporting software and computer system |
US20090063631A1 (en) * | 2007-08-31 | 2009-03-05 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Message-reply-dependent update decisions |
JP4943278B2 (en) | 2007-09-06 | 2012-05-30 | 株式会社日立製作所 | Virus scanning method and computer system using the method |
US8219686B2 (en) | 2007-09-17 | 2012-07-10 | Mcafee, Inc. | Method and computer program product utilizing multiple UDP data packets to transfer a quantity of data otherwise in excess of a single UDP packet |
US8230025B2 (en) * | 2007-09-20 | 2012-07-24 | Research In Motion Limited | System and method for delivering variable size messages based on spam probability |
US20090083413A1 (en) * | 2007-09-24 | 2009-03-26 | Levow Zachary S | Distributed frequency data collection via DNS |
US10606901B1 (en) * | 2007-09-28 | 2020-03-31 | Emc Corporation | Data disposition services orchestrated in an information management infrastructure |
US8730946B2 (en) * | 2007-10-18 | 2014-05-20 | Redshift Internetworking, Inc. | System and method to precisely learn and abstract the positive flow behavior of a unified communication (UC) application and endpoints |
WO2009053767A2 (en) * | 2007-10-23 | 2009-04-30 | Gecad Technologies Sa | Methods of processing or filtering and system for filtering email data |
US8959624B2 (en) * | 2007-10-31 | 2015-02-17 | Bank Of America Corporation | Executable download tracking system |
US9060034B2 (en) * | 2007-11-09 | 2015-06-16 | Napo Enterprises, Llc | System and method of filtering recommenders in a media item recommendation system |
US8037536B2 (en) * | 2007-11-14 | 2011-10-11 | Bank Of America Corporation | Risk scoring system for the prevention of malware |
US8590039B1 (en) | 2007-11-28 | 2013-11-19 | Mcafee, Inc. | System, method and computer program product for sending information extracted from a potentially unwanted data sample to generate a signature |
US8144841B2 (en) * | 2007-12-05 | 2012-03-27 | Microsoft Corporation | Multimedia spam determination using speech conversion |
US20090150497A1 (en) * | 2007-12-06 | 2009-06-11 | Mcafee Randolph Preston | Electronic mail message handling and presentation methods and systems |
US8396951B2 (en) | 2007-12-20 | 2013-03-12 | Napo Enterprises, Llc | Method and system for populating a content repository for an internet radio service based on a recommendation network |
US9734507B2 (en) | 2007-12-20 | 2017-08-15 | Napo Enterprise, Llc | Method and system for simulating recommendations in a social network for an offline user |
US10318730B2 (en) * | 2007-12-20 | 2019-06-11 | Bank Of America Corporation | Detection and prevention of malicious code execution using risk scoring |
US8316015B2 (en) | 2007-12-21 | 2012-11-20 | Lemi Technology, Llc | Tunersphere |
EP2235657B1 (en) * | 2007-12-21 | 2014-11-26 | Motorola Mobility LLC | System and method for preventing unauthorised use of digital media |
US8060525B2 (en) | 2007-12-21 | 2011-11-15 | Napo Enterprises, Llc | Method and system for generating media recommendations in a distributed environment based on tagging play history information with location information |
US8117193B2 (en) | 2007-12-21 | 2012-02-14 | Lemi Technology, Llc | Tunersphere |
US8296245B2 (en) * | 2008-01-03 | 2012-10-23 | Kount Inc. | Method and system for creation and validation of anonymous digital credentials |
US9183368B2 (en) * | 2008-01-24 | 2015-11-10 | Go Daddy Operating Company, LLC | Validating control of domain zone |
US8433747B2 (en) * | 2008-02-01 | 2013-04-30 | Microsoft Corporation | Graphics remoting architecture |
US8706820B2 (en) * | 2008-02-08 | 2014-04-22 | Microsoft Corporation | Rules extensibility engine |
US20110225244A1 (en) * | 2008-02-13 | 2011-09-15 | Barracuda Networks Inc. | Tracing domains to authoritative servers associated with spam |
JP4488074B2 (en) * | 2008-02-13 | 2010-06-23 | 日本電気株式会社 | Pattern detection device, pattern detection system, pattern detection program, and pattern detection method |
US9306796B1 (en) | 2008-03-18 | 2016-04-05 | Mcafee, Inc. | System, method, and computer program product for dynamically configuring a virtual environment for identifying unwanted data |
US8407784B2 (en) | 2008-03-19 | 2013-03-26 | Websense, Inc. | Method and system for protection against information stealing software |
US9015842B2 (en) | 2008-03-19 | 2015-04-21 | Websense, Inc. | Method and system for protection against information stealing software |
US9130986B2 (en) * | 2008-03-19 | 2015-09-08 | Websense, Inc. | Method and system for protection against information stealing software |
US8266672B2 (en) * | 2008-03-21 | 2012-09-11 | Sophos Plc | Method and system for network identification via DNS |
US7865561B2 (en) * | 2008-04-01 | 2011-01-04 | Mcafee, Inc. | Increasing spam scanning accuracy by rescanning with updated detection rules |
US8244752B2 (en) * | 2008-04-21 | 2012-08-14 | Microsoft Corporation | Classifying search query traffic |
US8302192B1 (en) * | 2008-04-30 | 2012-10-30 | Netapp, Inc. | Integrating anti-virus in a clustered storage system |
US20090282075A1 (en) * | 2008-05-06 | 2009-11-12 | Dawson Christopher J | System and method for identifying and blocking avatar-based unsolicited advertising in a virtual universe |
US9985978B2 (en) * | 2008-05-07 | 2018-05-29 | Lookingglass Cyber Solutions | Method and system for misuse detection |
US9123027B2 (en) * | 2010-10-19 | 2015-09-01 | QinetiQ North America, Inc. | Social engineering protection appliance |
US8028030B2 (en) * | 2008-05-22 | 2011-09-27 | International Business Machines Corporation | Method and system for supervising electronic text communications of an enterprise |
US20090300012A1 (en) * | 2008-05-28 | 2009-12-03 | Barracuda Inc. | Multilevel intent analysis method for email filtration |
US8301904B1 (en) * | 2008-06-24 | 2012-10-30 | Mcafee, Inc. | System, method, and computer program product for automatically identifying potentially unwanted data as unwanted |
US8490185B2 (en) * | 2008-06-27 | 2013-07-16 | Microsoft Corporation | Dynamic spam view settings |
EP2318955A1 (en) * | 2008-06-30 | 2011-05-11 | Websense, Inc. | System and method for dynamic and real-time categorization of webpages |
US8381298B2 (en) * | 2008-06-30 | 2013-02-19 | Microsoft Corporation | Malware detention for suspected malware |
US20100011420A1 (en) * | 2008-07-02 | 2010-01-14 | Barracuda Networks Inc. | Operating a service on a network as a domain name system server |
US8219644B2 (en) * | 2008-07-03 | 2012-07-10 | Barracuda Networks, Inc. | Requesting a service or transmitting content as a domain name system resolver |
US8205242B2 (en) | 2008-07-10 | 2012-06-19 | Mcafee, Inc. | System and method for data mining and security policy management |
US8676903B2 (en) * | 2008-07-17 | 2014-03-18 | International Business Machines Corporation | System and method to control email whitelists |
US20100023871A1 (en) * | 2008-07-25 | 2010-01-28 | Zumobi, Inc. | Methods and Systems Providing an Interactive Social Ticker |
US9253154B2 (en) | 2008-08-12 | 2016-02-02 | Mcafee, Inc. | Configuration management for a capture/registration system |
US9641537B2 (en) * | 2008-08-14 | 2017-05-02 | Invention Science Fund I, Llc | Conditionally releasing a communiqué determined to be affiliated with a particular source entity in response to detecting occurrence of one or more environmental aspects |
US20100057895A1 (en) * | 2008-08-29 | 2010-03-04 | At& T Intellectual Property I, L.P. | Methods of Providing Reputation Information with an Address and Related Devices and Computer Program Products |
EP2169897A1 (en) * | 2008-09-25 | 2010-03-31 | Avira GmbH | Computer-based method for the prioritization of potential malware sample messages |
US8997219B2 (en) | 2008-11-03 | 2015-03-31 | Fireeye, Inc. | Systems and methods for detecting malicious PDF network content |
US8850571B2 (en) | 2008-11-03 | 2014-09-30 | Fireeye, Inc. | Systems and methods for detecting malicious network content |
US20100125663A1 (en) * | 2008-11-17 | 2010-05-20 | Donovan John J | Systems, methods, and devices for detecting security vulnerabilities in ip networks |
US8181251B2 (en) * | 2008-12-18 | 2012-05-15 | Symantec Corporation | Methods and systems for detecting malware |
US8375435B2 (en) * | 2008-12-19 | 2013-02-12 | International Business Machines Corporation | Host trust report based filtering mechanism in a reverse firewall |
US9697535B2 (en) | 2008-12-23 | 2017-07-04 | International Business Machines Corporation | System and method in a virtual universe for identifying spam avatars based upon avatar multimedia characteristics |
US9704177B2 (en) | 2008-12-23 | 2017-07-11 | International Business Machines Corporation | Identifying spam avatars in a virtual universe (VU) based upon turing tests |
US8424075B1 (en) * | 2008-12-31 | 2013-04-16 | Qurio Holdings, Inc. | Collaborative firewall for a distributed virtual environment |
US8850591B2 (en) * | 2009-01-13 | 2014-09-30 | Mcafee, Inc. | System and method for concept building |
US8706709B2 (en) | 2009-01-15 | 2014-04-22 | Mcafee, Inc. | System and method for intelligent term grouping |
US8265658B2 (en) * | 2009-02-02 | 2012-09-11 | Waldeck Technology, Llc | System and method for automated location-based widgets |
US8200602B2 (en) | 2009-02-02 | 2012-06-12 | Napo Enterprises, Llc | System and method for creating thematic listening experiences in a networked peer media recommendation environment |
US8473442B1 (en) | 2009-02-25 | 2013-06-25 | Mcafee, Inc. | System and method for intelligent state management |
US8627461B2 (en) | 2009-03-04 | 2014-01-07 | Mcafee, Inc. | System, method, and computer program product for verifying an identification of program information as unwanted |
US9141794B1 (en) * | 2009-03-10 | 2015-09-22 | Trend Micro Incorporated | Preemptive and/or reduced-intrusion malware scanning |
US20110047192A1 (en) * | 2009-03-19 | 2011-02-24 | Hitachi, Ltd. | Data processing system, data processing method, and program |
US8904520B1 (en) | 2009-03-19 | 2014-12-02 | Symantec Corporation | Communication-based reputation system |
US9350755B1 (en) * | 2009-03-20 | 2016-05-24 | Symantec Corporation | Method and apparatus for detecting malicious software transmission through a web portal |
US8447722B1 (en) | 2009-03-25 | 2013-05-21 | Mcafee, Inc. | System and method for data mining and security policy management |
US8667121B2 (en) | 2009-03-25 | 2014-03-04 | Mcafee, Inc. | System and method for managing data and policies |
US11489857B2 (en) | 2009-04-21 | 2022-11-01 | Webroot Inc. | System and method for developing a risk profile for an internet resource |
US8234259B2 (en) * | 2009-05-08 | 2012-07-31 | Raytheon Company | Method and system for adjudicating text against a defined policy |
CN101582887B (en) * | 2009-05-20 | 2014-02-26 | 华为技术有限公司 | Safety protection method, gateway device and safety protection system |
US8621614B2 (en) * | 2009-05-26 | 2013-12-31 | Microsoft Corporation | Managing potentially phishing messages in a non-web mail client context |
US9130972B2 (en) | 2009-05-26 | 2015-09-08 | Websense, Inc. | Systems and methods for efficient detection of fingerprinted data and information |
US8656476B2 (en) * | 2009-05-28 | 2014-02-18 | International Business Machines Corporation | Providing notification of spam avatars |
US8176069B2 (en) | 2009-06-01 | 2012-05-08 | Aol Inc. | Systems and methods for improved web searching |
CN101576947B (en) * | 2009-06-05 | 2012-08-08 | 成都市华为赛门铁克科技有限公司 | Method, device and system for file protection treatment |
CN101600207A (en) * | 2009-06-18 | 2009-12-09 | 中兴通讯股份有限公司 | A kind of SP access control method and system based on WAP |
JP5147078B2 (en) * | 2009-07-01 | 2013-02-20 | 日本電信電話株式会社 | Address list construction method, address list construction system, and program therefor |
US8347394B1 (en) * | 2009-07-15 | 2013-01-01 | Trend Micro, Inc. | Detection of downloaded malware using DNS information |
US8271650B2 (en) * | 2009-08-25 | 2012-09-18 | Vizibility Inc. | Systems and method of identifying and managing abusive requests |
US8800030B2 (en) * | 2009-09-15 | 2014-08-05 | Symantec Corporation | Individualized time-to-live for reputation scores of computer files |
US8510835B1 (en) * | 2009-09-18 | 2013-08-13 | Trend Micro Incorporated | Techniques for protecting data in cloud computing environments |
US8832829B2 (en) | 2009-09-30 | 2014-09-09 | Fireeye, Inc. | Network-based binary file extraction and analysis for malware detection |
US8302194B2 (en) * | 2009-10-26 | 2012-10-30 | Symantec Corporation | Using file prevalence to inform aggressiveness of behavioral heuristics |
US8539583B2 (en) | 2009-11-03 | 2013-09-17 | Mcafee, Inc. | Rollback feature |
US8356354B2 (en) * | 2009-11-23 | 2013-01-15 | Kaspersky Lab, Zao | Silent-mode signature testing in anti-malware processing |
US20110136542A1 (en) * | 2009-12-09 | 2011-06-09 | Nokia Corporation | Method and apparatus for suggesting information resources based on context and preferences |
US20110144567A1 (en) * | 2009-12-15 | 2011-06-16 | Alcon Research, Ltd. | Phacoemulsification Hand Piece With Integrated Aspiration Pump and Cartridge |
US8479286B2 (en) | 2009-12-15 | 2013-07-02 | Mcafee, Inc. | Systems and methods for behavioral sandboxing |
US20110153035A1 (en) * | 2009-12-22 | 2011-06-23 | Caterpillar Inc. | Sensor Failure Detection System And Method |
US8719939B2 (en) * | 2009-12-31 | 2014-05-06 | Mcafee, Inc. | Malware detection via reputation system |
US8549642B2 (en) * | 2010-01-20 | 2013-10-01 | Symantec Corporation | Method and system for using spam e-mail honeypots to identify potential malware containing e-mails |
US8800034B2 (en) | 2010-01-26 | 2014-08-05 | Bank Of America Corporation | Insider threat correlation tool |
US8782209B2 (en) | 2010-01-26 | 2014-07-15 | Bank Of America Corporation | Insider threat correlation tool |
US9038187B2 (en) * | 2010-01-26 | 2015-05-19 | Bank Of America Corporation | Insider threat correlation tool |
US8793789B2 (en) | 2010-07-22 | 2014-07-29 | Bank Of America Corporation | Insider threat correlation tool |
US8443452B2 (en) * | 2010-01-28 | 2013-05-14 | Microsoft Corporation | URL filtering based on user browser history |
US8719352B2 (en) * | 2010-01-29 | 2014-05-06 | Mcafee, Inc. | Reputation management for network content classification |
US8516100B1 (en) * | 2010-02-04 | 2013-08-20 | Symantec Corporation | Method and apparatus for detecting system message misrepresentation using a keyword analysis |
US8606792B1 (en) | 2010-02-08 | 2013-12-10 | Google Inc. | Scoring authors of posts |
US20110209207A1 (en) * | 2010-02-25 | 2011-08-25 | Oto Technologies, Llc | System and method for generating a threat assessment |
US8863279B2 (en) * | 2010-03-08 | 2014-10-14 | Raytheon Company | System and method for malware detection |
US9009820B1 (en) | 2010-03-08 | 2015-04-14 | Raytheon Company | System and method for malware detection using multiple techniques |
US8910279B2 (en) * | 2010-03-10 | 2014-12-09 | Sonicwall, Inc. | Reputation-based threat protection |
CN101789105B (en) * | 2010-03-15 | 2013-01-30 | 北京安天电子设备有限公司 | Packet-level dynamic mail attachment virus detection method |
US8856165B1 (en) * | 2010-03-26 | 2014-10-07 | Google Inc. | Ranking of users who report abuse |
US8782794B2 (en) | 2010-04-16 | 2014-07-15 | Bank Of America Corporation | Detecting secure or encrypted tunneling in a computer network |
US8544100B2 (en) | 2010-04-16 | 2013-09-24 | Bank Of America Corporation | Detecting secure or encrypted tunneling in a computer network |
CN101827104B (en) * | 2010-04-27 | 2013-01-02 | 南京邮电大学 | Multi anti-virus engine-based network virus joint defense method |
US9361130B2 (en) | 2010-05-03 | 2016-06-07 | Apple Inc. | Systems, methods, and computer program products providing an integrated user interface for reading content |
US8719900B2 (en) * | 2010-05-18 | 2014-05-06 | Amazon Technologies, Inc. | Validating updates to domain name system records |
US8601114B1 (en) | 2010-05-21 | 2013-12-03 | Socialware, Inc. | Method, system and computer program product for interception, quarantine and moderation of internal communications of uncontrolled systems |
US8244818B2 (en) | 2010-05-28 | 2012-08-14 | Research In Motion Limited | System and method for visual representation of spam probability |
US8627476B1 (en) * | 2010-07-05 | 2014-01-07 | Symantec Corporation | Altering application behavior based on content provider reputation |
CN101877710B (en) * | 2010-07-13 | 2012-10-17 | 成都市华为赛门铁克科技有限公司 | Proxy gateway anti-virus implement method, pre-sorter and proxy gateway |
US8595830B1 (en) | 2010-07-27 | 2013-11-26 | Symantec Corporation | Method and system for detecting malware containing E-mails based on inconsistencies in public sector “From” addresses and a sending IP address |
US8464342B2 (en) * | 2010-08-31 | 2013-06-11 | Microsoft Corporation | Adaptively selecting electronic message scanning rules |
US9021043B2 (en) * | 2010-09-28 | 2015-04-28 | Microsoft Technology Licensing Llc | Message gateway with hybrid proxy/store-and-forward logic |
US9148432B2 (en) * | 2010-10-12 | 2015-09-29 | Microsoft Technology Licensing, Llc | Range weighted internet protocol address blacklist |
US8806615B2 (en) | 2010-11-04 | 2014-08-12 | Mcafee, Inc. | System and method for protecting specified data combinations |
US8990316B1 (en) * | 2010-11-05 | 2015-03-24 | Amazon Technologies, Inc. | Identifying message deliverability problems using grouped message characteristics |
US20120123778A1 (en) * | 2010-11-11 | 2012-05-17 | At&T Intellectual Property I, L.P. | Security Control for SMS and MMS Support Using Unified Messaging System |
US8819816B2 (en) * | 2010-11-15 | 2014-08-26 | Facebook, Inc. | Differentiating between good and bad content in a user-provided content system |
US8826437B2 (en) * | 2010-12-14 | 2014-09-02 | General Electric Company | Intelligent system and method for mitigating cyber attacks in critical systems through controlling latency of messages in a communications network |
US8769060B2 (en) | 2011-01-28 | 2014-07-01 | Nominum, Inc. | Systems and methods for providing DNS services |
US8554907B1 (en) * | 2011-02-15 | 2013-10-08 | Trend Micro, Inc. | Reputation prediction of IP addresses |
US8667592B2 (en) * | 2011-03-15 | 2014-03-04 | Symantec Corporation | Systems and methods for looking up anti-malware metadata |
US9122877B2 (en) | 2011-03-21 | 2015-09-01 | Mcafee, Inc. | System and method for malware and network reputation correlation |
US9473527B1 (en) * | 2011-05-05 | 2016-10-18 | Trend Micro Inc. | Automatically generated and shared white list |
US9858415B2 (en) * | 2011-06-16 | 2018-01-02 | Microsoft Technology Licensing, Llc | Cloud malware false positive recovery |
US9106680B2 (en) | 2011-06-27 | 2015-08-11 | Mcafee, Inc. | System and method for protocol fingerprinting and reputation correlation |
US20130018965A1 (en) * | 2011-07-12 | 2013-01-17 | Microsoft Corporation | Reputational and behavioral spam mitigation |
US9087324B2 (en) | 2011-07-12 | 2015-07-21 | Microsoft Technology Licensing, Llc | Message categorization |
US8650649B1 (en) * | 2011-08-22 | 2014-02-11 | Symantec Corporation | Systems and methods for determining whether to evaluate the trustworthiness of digitally signed files based on signer reputation |
US9319404B2 (en) | 2011-09-23 | 2016-04-19 | Jerome Svigals | Security for the internet of things |
US8997188B2 (en) * | 2012-04-11 | 2015-03-31 | Jerome Svigals | System for enabling a smart device to securely accept unsolicited transactions |
US9432378B1 (en) | 2011-09-23 | 2016-08-30 | Jerome Svigals | Internet of things security |
US9344437B2 (en) | 2011-09-23 | 2016-05-17 | Jerome Svigals | Internet of things security |
JP5667957B2 (en) * | 2011-09-30 | 2015-02-12 | Kddi株式会社 | Malware detection device and program |
US8726385B2 (en) * | 2011-10-05 | 2014-05-13 | Mcafee, Inc. | Distributed system and method for tracking and blocking malicious internet hosts |
GB201117262D0 (en) * | 2011-10-06 | 2011-11-16 | Clark Steven D | Electronic mail system |
US8909667B2 (en) | 2011-11-01 | 2014-12-09 | Lemi Technology, Llc | Systems, methods, and computer readable media for generating recommendations in a media recommendation system |
GB2509872A (en) * | 2011-11-03 | 2014-07-16 | Raytheon Co | Intrusion prevention system (IPS) mode for a malware detection system |
US9832221B1 (en) * | 2011-11-08 | 2017-11-28 | Symantec Corporation | Systems and methods for monitoring the activity of devices within an organization by leveraging data generated by an existing security solution deployed within the organization |
US8549612B2 (en) * | 2011-11-28 | 2013-10-01 | Dell Products, Lp | System and method for incorporating quality-of-service and reputation in an intrusion detection and prevention system |
US20130159497A1 (en) * | 2011-12-16 | 2013-06-20 | Microsoft Corporation | Heuristic-Based Rejection of Computing Resource Requests |
US10365911B2 (en) * | 2011-12-18 | 2019-07-30 | International Business Machines Corporation | Determining optimal update frequency for software application updates |
US8886651B1 (en) | 2011-12-22 | 2014-11-11 | Reputation.Com, Inc. | Thematic clustering |
US20130198203A1 (en) * | 2011-12-22 | 2013-08-01 | John Bates | Bot detection using profile-based filtration |
US9001699B2 (en) * | 2011-12-26 | 2015-04-07 | Jaya MEGHANI | Systems and methods for communication setup via reconciliation of internet protocol addresses |
US20130246431A1 (en) | 2011-12-27 | 2013-09-19 | Mcafee, Inc. | System and method for providing data protection workflows in a network environment |
US9270638B2 (en) | 2012-01-20 | 2016-02-23 | Cisco Technology, Inc. | Managing address validation states in switches snooping IPv6 |
WO2013112153A1 (en) * | 2012-01-26 | 2013-08-01 | Hewlett-Packard Development Company, L.P. | Identifying a push communication pattern |
US8494973B1 (en) | 2012-03-05 | 2013-07-23 | Reputation.Com, Inc. | Targeting review placement |
US10636041B1 (en) | 2012-03-05 | 2020-04-28 | Reputation.Com, Inc. | Enterprise reputation evaluation |
RU2510982C2 (en) * | 2012-04-06 | 2014-04-10 | Закрытое акционерное общество "Лаборатория Касперского" | User evaluation system and method for message filtering |
US8931043B2 (en) | 2012-04-10 | 2015-01-06 | Mcafee Inc. | System and method for determining and using local reputations of users and hosts to protect information in a network environment |
US8782793B2 (en) * | 2012-05-22 | 2014-07-15 | Kaspersky Lab Zao | System and method for detection and treatment of malware on data storage devices |
US11093984B1 (en) | 2012-06-29 | 2021-08-17 | Reputation.Com, Inc. | Determining themes |
US9876742B2 (en) * | 2012-06-29 | 2018-01-23 | Microsoft Technology Licensing, Llc | Techniques to select and prioritize application of junk email filtering rules |
US9432401B2 (en) * | 2012-07-06 | 2016-08-30 | Microsoft Technology Licensing, Llc | Providing consistent security information |
US9049235B2 (en) * | 2012-07-16 | 2015-06-02 | Mcafee, Inc. | Cloud email message scanning with local policy application in a network environment |
US9124472B1 (en) | 2012-07-25 | 2015-09-01 | Symantec Corporation | Providing file information to a client responsive to a file download stability prediction |
US9461897B1 (en) | 2012-07-31 | 2016-10-04 | United Services Automobile Association (Usaa) | Monitoring and analysis of social network traffic |
US10164929B2 (en) | 2012-09-28 | 2018-12-25 | Avaya Inc. | Intelligent notification of requests for real-time online interaction via real-time communications and/or markup protocols, and related methods, systems, and computer-readable media |
RU2514140C1 (en) * | 2012-09-28 | 2014-04-27 | Закрытое акционерное общество "Лаборатория Касперского" | System and method for improving quality of detecting malicious objects using rules and priorities |
US9363133B2 (en) | 2012-09-28 | 2016-06-07 | Avaya Inc. | Distributed application of enterprise policies to Web Real-Time Communications (WebRTC) interactive sessions, and related methods, systems, and computer-readable media |
US8918473B1 (en) | 2012-10-09 | 2014-12-23 | Whatsapp Inc. | System and method for detecting unwanted content |
CN103824018B (en) * | 2012-11-19 | 2017-11-14 | 腾讯科技(深圳)有限公司 | A kind of executable file processing method and executable file monitoring method |
US8904526B2 (en) * | 2012-11-20 | 2014-12-02 | Bank Of America Corporation | Enhanced network security |
US8869275B2 (en) * | 2012-11-28 | 2014-10-21 | Verisign, Inc. | Systems and methods to detect and respond to distributed denial of service (DDoS) attacks |
US9258263B2 (en) * | 2012-11-29 | 2016-02-09 | International Business Machines Corporation | Dynamic granular messaging persistence |
US9241259B2 (en) | 2012-11-30 | 2016-01-19 | Websense, Inc. | Method and apparatus for managing the transfer of sensitive information to mobile devices |
US9560069B1 (en) * | 2012-12-02 | 2017-01-31 | Symantec Corporation | Method and system for protection of messages in an electronic messaging system |
US9106681B2 (en) * | 2012-12-17 | 2015-08-11 | Hewlett-Packard Development Company, L.P. | Reputation of network address |
US8805699B1 (en) | 2012-12-21 | 2014-08-12 | Reputation.Com, Inc. | Reputation report with score |
US8744866B1 (en) | 2012-12-21 | 2014-06-03 | Reputation.Com, Inc. | Reputation report with recommendation |
US8955137B2 (en) * | 2012-12-21 | 2015-02-10 | State Farm Mutual Automobile Insurance Company | System and method for uploading and verifying a document |
US10572665B2 (en) | 2012-12-28 | 2020-02-25 | Fireeye, Inc. | System and method to create a number of breakpoints in a virtual machine via virtual machine trapping events |
US9356948B2 (en) | 2013-02-08 | 2016-05-31 | PhishMe, Inc. | Collaborative phishing attack detection |
US8966637B2 (en) | 2013-02-08 | 2015-02-24 | PhishMe, Inc. | Performance benchmarking for simulated phishing attacks |
US9398038B2 (en) | 2013-02-08 | 2016-07-19 | PhishMe, Inc. | Collaborative phishing attack detection |
US9195829B1 (en) | 2013-02-23 | 2015-11-24 | Fireeye, Inc. | User interface with real-time visual playback along with synchronous textual analysis log display and event/time index for anomalous behavior detection in applications |
US9367681B1 (en) | 2013-02-23 | 2016-06-14 | Fireeye, Inc. | Framework for efficient security coverage of mobile software applications using symbolic execution to reach regions of interest within an application |
US8990944B1 (en) | 2013-02-23 | 2015-03-24 | Fireeye, Inc. | Systems and methods for automatically detecting backdoors |
US9009823B1 (en) | 2013-02-23 | 2015-04-14 | Fireeye, Inc. | Framework for efficient security coverage of mobile software applications installed on mobile devices |
US9176843B1 (en) | 2013-02-23 | 2015-11-03 | Fireeye, Inc. | Framework for efficient security coverage of mobile software applications |
US9137049B2 (en) * | 2013-02-28 | 2015-09-15 | Apple Inc. | Dynamically overriding alert suppressions based on prior actions |
US10659480B2 (en) * | 2013-03-07 | 2020-05-19 | Inquest, Llc | Integrated network threat analysis |
US9104867B1 (en) | 2013-03-13 | 2015-08-11 | Fireeye, Inc. | Malicious content analysis using simulated user interaction without user involvement |
US9626509B1 (en) | 2013-03-13 | 2017-04-18 | Fireeye, Inc. | Malicious content analysis with multi-version application support within single operating environment |
US9355247B1 (en) | 2013-03-13 | 2016-05-31 | Fireeye, Inc. | File extraction from memory dump for malicious content analysis |
US8925099B1 (en) | 2013-03-14 | 2014-12-30 | Reputation.Com, Inc. | Privacy scoring |
US9430646B1 (en) | 2013-03-14 | 2016-08-30 | Fireeye, Inc. | Distributed systems and methods for automatically detecting unknown bots and botnets |
US10649970B1 (en) * | 2013-03-14 | 2020-05-12 | Invincea, Inc. | Methods and apparatus for detection of functionality |
US9294458B2 (en) | 2013-03-14 | 2016-03-22 | Avaya Inc. | Managing identity provider (IdP) identifiers for web real-time communications (WebRTC) interactive flows, and related methods, systems, and computer-readable media |
US9311479B1 (en) | 2013-03-14 | 2016-04-12 | Fireeye, Inc. | Correlation and consolidation of analytic data for holistic view of a malware attack |
US10713358B2 (en) | 2013-03-15 | 2020-07-14 | Fireeye, Inc. | System and method to extract and utilize disassembly features to classify software intent |
US10164989B2 (en) * | 2013-03-15 | 2018-12-25 | Nominum, Inc. | Distinguishing human-driven DNS queries from machine-to-machine DNS queries |
US9722918B2 (en) | 2013-03-15 | 2017-08-01 | A10 Networks, Inc. | System and method for customizing the identification of application or content type |
US9413781B2 (en) | 2013-03-15 | 2016-08-09 | Fireeye, Inc. | System and method employing structured intelligence to verify and contain threats at endpoints |
US9244903B2 (en) | 2013-04-15 | 2016-01-26 | Vmware, Inc. | Efficient data pattern matching |
US10318397B2 (en) * | 2013-04-15 | 2019-06-11 | Vmware, Inc. | Efficient data pattern matching |
US9838425B2 (en) * | 2013-04-25 | 2017-12-05 | A10 Networks, Inc. | Systems and methods for network access control |
US9634970B2 (en) | 2013-04-30 | 2017-04-25 | Cloudmark, Inc. | Apparatus and method for augmenting a message to facilitate spam identification |
US9495180B2 (en) | 2013-05-10 | 2016-11-15 | Fireeye, Inc. | Optimized resource allocation for virtual machines within a malware content detection system |
US9635039B1 (en) | 2013-05-13 | 2017-04-25 | Fireeye, Inc. | Classifying sets of malicious indicators for detecting command and control communications associated with malware |
US10205624B2 (en) | 2013-06-07 | 2019-02-12 | Avaya Inc. | Bandwidth-efficient archiving of real-time interactive flows, and related methods, systems, and computer-readable media |
US10133863B2 (en) | 2013-06-24 | 2018-11-20 | Fireeye, Inc. | Zero-day discovery system |
US9300686B2 (en) | 2013-06-28 | 2016-03-29 | Fireeye, Inc. | System and method for detecting malicious links in electronic messages |
US9639693B2 (en) * | 2013-06-28 | 2017-05-02 | Symantec Corporation | Techniques for detecting a security vulnerability |
US9525718B2 (en) | 2013-06-30 | 2016-12-20 | Avaya Inc. | Back-to-back virtual web real-time communications (WebRTC) agents, and related methods, systems, and computer-readable media |
US9065969B2 (en) | 2013-06-30 | 2015-06-23 | Avaya Inc. | Scalable web real-time communications (WebRTC) media engines, and related methods, systems, and computer-readable media |
US9112840B2 (en) | 2013-07-17 | 2015-08-18 | Avaya Inc. | Verifying privacy of web real-time communications (WebRTC) media channels via corresponding WebRTC data channels, and related methods, systems, and computer-readable media |
CN103338211A (en) * | 2013-07-19 | 2013-10-02 | 腾讯科技(深圳)有限公司 | Malicious URL (unified resource locator) authenticating method and device |
US9614890B2 (en) | 2013-07-31 | 2017-04-04 | Avaya Inc. | Acquiring and correlating web real-time communications (WEBRTC) interactive flow characteristics, and related methods, systems, and computer-readable media |
US9531808B2 (en) | 2013-08-22 | 2016-12-27 | Avaya Inc. | Providing data resource services within enterprise systems for resource level sharing among multiple applications, and related methods, systems, and computer-readable media |
KR101480903B1 (en) * | 2013-09-03 | 2015-01-13 | 한국전자통신연구원 | Method for multiple checking a mobile malicious code |
US10225212B2 (en) | 2013-09-26 | 2019-03-05 | Avaya Inc. | Providing network management based on monitoring quality of service (QOS) characteristics of web real-time communications (WEBRTC) interactive flows, and related methods, systems, and computer-readable media |
US9628507B2 (en) | 2013-09-30 | 2017-04-18 | Fireeye, Inc. | Advanced persistent threat (APT) detection center |
US9736179B2 (en) | 2013-09-30 | 2017-08-15 | Fireeye, Inc. | System, apparatus and method for using malware analysis results to drive adaptive instrumentation of virtual machines to improve exploit detection |
US10515214B1 (en) | 2013-09-30 | 2019-12-24 | Fireeye, Inc. | System and method for classifying malware within content created during analysis of a specimen |
US9294501B2 (en) | 2013-09-30 | 2016-03-22 | Fireeye, Inc. | Fuzzy hash of behavioral results |
US9171160B2 (en) | 2013-09-30 | 2015-10-27 | Fireeye, Inc. | Dynamically adaptive framework and method for classifying malware using intelligent static, emulation, and dynamic analyses |
US9690936B1 (en) | 2013-09-30 | 2017-06-27 | Fireeye, Inc. | Multistage system and method for analyzing obfuscated content for malware |
RU2013144681A (en) | 2013-10-03 | 2015-04-10 | Общество С Ограниченной Ответственностью "Яндекс" | ELECTRONIC MESSAGE PROCESSING SYSTEM FOR DETERMINING ITS CLASSIFICATION |
GB2518880A (en) | 2013-10-04 | 2015-04-08 | Glasswall Ip Ltd | Anti-Malware mobile content data management apparatus and method |
GB2519516B (en) * | 2013-10-21 | 2017-05-10 | Openwave Mobility Inc | A method, apparatus and computer program for modifying messages in a communications network |
EP3061030A4 (en) | 2013-10-24 | 2017-04-19 | McAfee, Inc. | Agent assisted malicious application blocking in a network environment |
US10263952B2 (en) | 2013-10-31 | 2019-04-16 | Avaya Inc. | Providing origin insight for web applications via session traversal utilities for network address translation (STUN) messages, and related methods, systems, and computer-readable media |
US9319423B2 (en) | 2013-11-04 | 2016-04-19 | At&T Intellectual Property I, L.P. | Malware and anomaly detection via activity recognition based on sensor data |
US9769214B2 (en) | 2013-11-05 | 2017-09-19 | Avaya Inc. | Providing reliable session initiation protocol (SIP) signaling for web real-time communications (WEBRTC) interactive flows, and related methods, systems, and computer-readable media |
US10694029B1 (en) | 2013-11-07 | 2020-06-23 | Rightquestion, Llc | Validating automatic number identification data |
US9921978B1 (en) | 2013-11-08 | 2018-03-20 | Fireeye, Inc. | System and method for enhanced security of storage devices |
GB2520972A (en) | 2013-12-05 | 2015-06-10 | Ibm | Workload management |
US9756074B2 (en) | 2013-12-26 | 2017-09-05 | Fireeye, Inc. | System and method for IPS and VM-based detection of suspicious objects |
US9747446B1 (en) | 2013-12-26 | 2017-08-29 | Fireeye, Inc. | System and method for run-time object classification |
US10129243B2 (en) | 2013-12-27 | 2018-11-13 | Avaya Inc. | Controlling access to traversal using relays around network address translation (TURN) servers using trusted single-use credentials |
US9288221B2 (en) * | 2014-01-14 | 2016-03-15 | Pfu Limited | Information processing apparatus, method for determining unauthorized activity and computer-readable medium |
US9292686B2 (en) | 2014-01-16 | 2016-03-22 | Fireeye, Inc. | Micro-virtualization architecture for threat-aware microvisor deployment in a node of a network environment |
US9262635B2 (en) | 2014-02-05 | 2016-02-16 | Fireeye, Inc. | Detection efficacy of virtual machine-based analysis with application specific events |
US9264418B1 (en) * | 2014-02-20 | 2016-02-16 | Amazon Technologies, Inc. | Client-side spam detection and prevention |
US10289838B2 (en) | 2014-02-21 | 2019-05-14 | Entit Software Llc | Scoring for threat observables |
CN103823761B (en) * | 2014-03-09 | 2017-01-25 | 林虎 | Method for increasing blacklist terminal capacity and retrieval speed |
US9241010B1 (en) | 2014-03-20 | 2016-01-19 | Fireeye, Inc. | System and method for network behavior detection |
US10242185B1 (en) | 2014-03-21 | 2019-03-26 | Fireeye, Inc. | Dynamic guest image creation and rollback |
US9591015B1 (en) | 2014-03-28 | 2017-03-07 | Fireeye, Inc. | System and method for offloading packet processing and static analysis operations |
US9223972B1 (en) | 2014-03-31 | 2015-12-29 | Fireeye, Inc. | Dynamically remote tuning of a malware content detection system |
US9432389B1 (en) | 2014-03-31 | 2016-08-30 | Fireeye, Inc. | System, apparatus and method for detecting a malicious attack based on static analysis of a multi-flow object |
US9749363B2 (en) | 2014-04-17 | 2017-08-29 | Avaya Inc. | Application of enterprise policies to web real-time communications (WebRTC) interactive sessions using an enterprise session initiation protocol (SIP) engine, and related methods, systems, and computer-readable media |
US10581927B2 (en) | 2014-04-17 | 2020-03-03 | Avaya Inc. | Providing web real-time communications (WebRTC) media services via WebRTC-enabled media servers, and related methods, systems, and computer-readable media |
US9245123B1 (en) | 2014-05-07 | 2016-01-26 | Symantec Corporation | Systems and methods for identifying malicious files |
US9906422B2 (en) | 2014-05-16 | 2018-02-27 | A10 Networks, Inc. | Distributed system to determine a server's health |
US9594912B1 (en) | 2014-06-06 | 2017-03-14 | Fireeye, Inc. | Return-oriented programming detection |
US9438623B1 (en) | 2014-06-06 | 2016-09-06 | Fireeye, Inc. | Computer exploit detection using heap spray pattern matching |
US9973531B1 (en) | 2014-06-06 | 2018-05-15 | Fireeye, Inc. | Shellcode detection |
WO2015195093A1 (en) | 2014-06-17 | 2015-12-23 | Hewlett-Packard Development Company, L. P. | Dns based infection scores |
US9912705B2 (en) | 2014-06-24 | 2018-03-06 | Avaya Inc. | Enhancing media characteristics during web real-time communications (WebRTC) interactive sessions by using session initiation protocol (SIP) endpoints, and related methods, systems, and computer-readable media |
US10084813B2 (en) | 2014-06-24 | 2018-09-25 | Fireeye, Inc. | Intrusion prevention and remedy system |
US9652615B1 (en) | 2014-06-25 | 2017-05-16 | Symantec Corporation | Systems and methods for analyzing suspected malware |
US9398028B1 (en) | 2014-06-26 | 2016-07-19 | Fireeye, Inc. | System, device and method for detecting a malicious attack based on communcations between remotely hosted virtual machines and malicious web servers |
US10805340B1 (en) | 2014-06-26 | 2020-10-13 | Fireeye, Inc. | Infection vector and malware tracking with an interactive user display |
US20150381533A1 (en) * | 2014-06-29 | 2015-12-31 | Avaya Inc. | System and Method for Email Management Through Detection and Analysis of Dynamically Variable Behavior and Activity Patterns |
US10002252B2 (en) | 2014-07-01 | 2018-06-19 | Fireeye, Inc. | Verification of trusted threat-aware microvisor |
CN105338126B (en) * | 2014-07-17 | 2018-10-23 | 阿里巴巴集团控股有限公司 | The method and server of remote-query information |
US9654484B2 (en) * | 2014-07-31 | 2017-05-16 | Cisco Technology, Inc. | Detecting DGA-based malicious software using network flow information |
US9548988B1 (en) | 2014-08-18 | 2017-01-17 | Symantec Corporation | Systems and methods for attributing potentially malicious email campaigns to known threat groups |
US10666676B1 (en) * | 2014-08-18 | 2020-05-26 | Trend Micro Incorporated | Detection of targeted email attacks |
US9363280B1 (en) | 2014-08-22 | 2016-06-07 | Fireeye, Inc. | System and method of detecting delivery of malware using cross-customer data |
US9729565B2 (en) * | 2014-09-17 | 2017-08-08 | Cisco Technology, Inc. | Provisional bot activity recognition |
US10671726B1 (en) | 2014-09-22 | 2020-06-02 | Fireeye Inc. | System and method for malware analysis using thread-level event monitoring |
US10027689B1 (en) | 2014-09-29 | 2018-07-17 | Fireeye, Inc. | Interactive infection visualization for improved exploit detection and signature generation for malware and malware families |
US9773112B1 (en) | 2014-09-29 | 2017-09-26 | Fireeye, Inc. | Exploit detection of malware and malware families |
US9754106B2 (en) * | 2014-10-14 | 2017-09-05 | Symantec Corporation | Systems and methods for classifying security events as targeted attacks |
US9571510B1 (en) | 2014-10-21 | 2017-02-14 | Symantec Corporation | Systems and methods for identifying security threat sources responsible for security events |
KR102295664B1 (en) * | 2014-10-21 | 2021-08-27 | 삼성에스디에스 주식회사 | Global server load balancer apparatus and method for dynamically controlling time-to-live |
US9870534B1 (en) | 2014-11-06 | 2018-01-16 | Nominum, Inc. | Predicting network activities associated with a given site |
US9374385B1 (en) | 2014-11-07 | 2016-06-21 | Area 1 Security, Inc. | Remediating computer security threats using distributed sensor computers |
WO2016073793A1 (en) * | 2014-11-07 | 2016-05-12 | Area 1 Security, Inc. | Remediating computer security threats using distributed sensor computers |
US9398047B2 (en) | 2014-11-17 | 2016-07-19 | Vade Retro Technology, Inc. | Methods and systems for phishing detection |
US9330264B1 (en) | 2014-11-26 | 2016-05-03 | Glasswall (Ip) Limited | Statistical analytic method for the determination of the risk posed by file based content |
US10318728B2 (en) | 2014-12-16 | 2019-06-11 | Entit Software Llc | Determining permissible activity based on permissible activity rules |
US9690933B1 (en) | 2014-12-22 | 2017-06-27 | Fireeye, Inc. | Framework for classifying an object as malicious with machine learning for deploying updated predictive models |
US10075455B2 (en) | 2014-12-26 | 2018-09-11 | Fireeye, Inc. | Zero-day rotating guest image profile |
US9378364B1 (en) * | 2014-12-27 | 2016-06-28 | Intel Corporation | Technologies for managing security threats to a computing system utilizing user interactions |
US9621575B1 (en) * | 2014-12-29 | 2017-04-11 | A10 Networks, Inc. | Context aware threat protection |
US9934376B1 (en) | 2014-12-29 | 2018-04-03 | Fireeye, Inc. | Malware detection appliance architecture |
US9838417B1 (en) | 2014-12-30 | 2017-12-05 | Fireeye, Inc. | Intelligent context aware user interaction for malware detection |
US10164927B2 (en) | 2015-01-14 | 2018-12-25 | Vade Secure, Inc. | Safe unsubscribe |
US9674053B2 (en) * | 2015-01-30 | 2017-06-06 | Gigamon Inc. | Automatic target selection |
JP2016148967A (en) * | 2015-02-12 | 2016-08-18 | 富士通株式会社 | Information processor, information processing method and program |
MA41502A (en) | 2015-02-14 | 2017-12-19 | Valimail Inc | CENTRALIZED VALIDATION OF EMAIL SENDERS BY TARGETING EHLO NAMES AND IP ADDRESSES |
US9690606B1 (en) | 2015-03-25 | 2017-06-27 | Fireeye, Inc. | Selective system call monitoring |
US10148693B2 (en) | 2015-03-25 | 2018-12-04 | Fireeye, Inc. | Exploit detection system |
US9438613B1 (en) | 2015-03-30 | 2016-09-06 | Fireeye, Inc. | Dynamic content activation for automated analysis of embedded objects |
US10474813B1 (en) | 2015-03-31 | 2019-11-12 | Fireeye, Inc. | Code injection technique for remediation at an endpoint of a network |
US10417031B2 (en) | 2015-03-31 | 2019-09-17 | Fireeye, Inc. | Selective virtualization for security threat detection |
US9483644B1 (en) | 2015-03-31 | 2016-11-01 | Fireeye, Inc. | Methods for detecting file altering malware in VM based analysis |
US10298602B2 (en) | 2015-04-10 | 2019-05-21 | Cofense Inc. | Suspicious message processing and incident response |
US9906539B2 (en) | 2015-04-10 | 2018-02-27 | PhishMe, Inc. | Suspicious message processing and incident response |
WO2016164844A1 (en) * | 2015-04-10 | 2016-10-13 | PhishMe, Inc. | Message report processing and threat prioritization |
US9654485B1 (en) | 2015-04-13 | 2017-05-16 | Fireeye, Inc. | Analytics-based security monitoring system and method |
US9594904B1 (en) | 2015-04-23 | 2017-03-14 | Fireeye, Inc. | Detecting malware based on reflection |
US20160337394A1 (en) * | 2015-05-11 | 2016-11-17 | The Boeing Company | Newborn domain screening of electronic mail messages |
US11363035B2 (en) | 2015-05-22 | 2022-06-14 | Fisher-Rosemount Systems, Inc. | Configurable robustness agent in a plant security system |
US9961090B2 (en) * | 2015-06-18 | 2018-05-01 | Bank Of America Corporation | Message quarantine |
US9521157B1 (en) * | 2015-06-24 | 2016-12-13 | Bank Of America Corporation | Identifying and assessing malicious resources |
US10642753B1 (en) | 2015-06-30 | 2020-05-05 | Fireeye, Inc. | System and method for protecting a software component running in virtual machine using a virtualization layer |
US10454950B1 (en) | 2015-06-30 | 2019-10-22 | Fireeye, Inc. | Centralized aggregation technique for detecting lateral movement of stealthy cyber-attacks |
US11113086B1 (en) | 2015-06-30 | 2021-09-07 | Fireeye, Inc. | Virtual system and method for securing external network connectivity |
US10726127B1 (en) | 2015-06-30 | 2020-07-28 | Fireeye, Inc. | System and method for protecting a software component running in a virtual machine through virtual interrupts by the virtualization layer |
KR101666614B1 (en) * | 2015-07-06 | 2016-10-14 | (주)다우기술 | Detection system and method for Advanced Persistent Threat using record |
US9954804B2 (en) * | 2015-07-30 | 2018-04-24 | International Business Machines Coporation | Method and system for preemptive harvesting of spam messages |
US9690938B1 (en) | 2015-08-05 | 2017-06-27 | Invincea, Inc. | Methods and apparatus for machine learning based malware detection |
US10715542B1 (en) | 2015-08-14 | 2020-07-14 | Fireeye, Inc. | Mobile application risk analysis |
CN105187408A (en) * | 2015-08-17 | 2015-12-23 | 北京神州绿盟信息安全科技股份有限公司 | Network attack detection method and equipment |
CN105743876B (en) * | 2015-08-28 | 2019-09-13 | 哈尔滨安天科技股份有限公司 | A kind of method and system based on mail source data discovery targeted attacks |
US10536449B2 (en) | 2015-09-15 | 2020-01-14 | Mimecast Services Ltd. | User login credential warning system |
US10728239B2 (en) | 2015-09-15 | 2020-07-28 | Mimecast Services Ltd. | Mediated access to resources |
US9467435B1 (en) | 2015-09-15 | 2016-10-11 | Mimecast North America, Inc. | Electronic message threat protection system for authorized users |
US9654492B2 (en) * | 2015-09-15 | 2017-05-16 | Mimecast North America, Inc. | Malware detection system based on stored data |
US11595417B2 (en) | 2015-09-15 | 2023-02-28 | Mimecast Services Ltd. | Systems and methods for mediating access to resources |
US10536408B2 (en) * | 2015-09-16 | 2020-01-14 | Litéra Corporation | Systems and methods for detecting, reporting and cleaning metadata from inbound attachments |
US9787581B2 (en) | 2015-09-21 | 2017-10-10 | A10 Networks, Inc. | Secure data flow open information analytics |
US10686817B2 (en) | 2015-09-21 | 2020-06-16 | Hewlett Packard Enterprise Development Lp | Identification of a DNS packet as malicious based on a value |
US10176321B2 (en) | 2015-09-22 | 2019-01-08 | Fireeye, Inc. | Leveraging behavior-based rules for malware family classification |
US10033747B1 (en) | 2015-09-29 | 2018-07-24 | Fireeye, Inc. | System and method for detecting interpreter-based exploit attacks |
US10601865B1 (en) | 2015-09-30 | 2020-03-24 | Fireeye, Inc. | Detection of credential spearphishing attacks using email analysis |
US10706149B1 (en) | 2015-09-30 | 2020-07-07 | Fireeye, Inc. | Detecting delayed activation malware using a primary controller and plural time controllers |
US10210329B1 (en) | 2015-09-30 | 2019-02-19 | Fireeye, Inc. | Method to detect application execution hijacking using memory protection |
US9825989B1 (en) | 2015-09-30 | 2017-11-21 | Fireeye, Inc. | Cyber attack early warning system |
US10817606B1 (en) | 2015-09-30 | 2020-10-27 | Fireeye, Inc. | Detecting delayed activation malware using a run-time monitoring agent and time-dilation logic |
US9825976B1 (en) | 2015-09-30 | 2017-11-21 | Fireeye, Inc. | Detection and classification of exploit kits |
US10284575B2 (en) | 2015-11-10 | 2019-05-07 | Fireeye, Inc. | Launcher for setting analysis environment variations for malware detection |
FR3043807B1 (en) * | 2015-11-18 | 2017-12-08 | Bull Sas | COMMUNICATION VALIDATION DEVICE |
EP3171567B1 (en) * | 2015-11-23 | 2018-10-24 | Alcatel Lucent | Advanced persistent threat detection |
US10846117B1 (en) | 2015-12-10 | 2020-11-24 | Fireeye, Inc. | Technique for establishing secure communication between host and guest processes of a virtualization architecture |
US10447728B1 (en) | 2015-12-10 | 2019-10-15 | Fireeye, Inc. | Technique for protecting guest processes using a layered virtualization architecture |
US10108446B1 (en) | 2015-12-11 | 2018-10-23 | Fireeye, Inc. | Late load technique for deploying a virtualization layer underneath a running operating system |
US9954877B2 (en) * | 2015-12-21 | 2018-04-24 | Ebay Inc. | Automatic detection of hidden link mismatches with spoofed metadata |
US10133866B1 (en) | 2015-12-30 | 2018-11-20 | Fireeye, Inc. | System and method for triggering analysis of an object for malware in response to modification of that object |
US10050998B1 (en) | 2015-12-30 | 2018-08-14 | Fireeye, Inc. | Malicious message analysis system |
US10565378B1 (en) | 2015-12-30 | 2020-02-18 | Fireeye, Inc. | Exploit of privilege detection framework |
US10621338B1 (en) | 2015-12-30 | 2020-04-14 | Fireeye, Inc. | Method to detect forgery and exploits using last branch recording registers |
US10706368B2 (en) * | 2015-12-30 | 2020-07-07 | Veritas Technologies Llc | Systems and methods for efficiently classifying data objects |
US10581874B1 (en) | 2015-12-31 | 2020-03-03 | Fireeye, Inc. | Malware detection system with contextual analysis |
US11552986B1 (en) | 2015-12-31 | 2023-01-10 | Fireeye Security Holdings Us Llc | Cyber-security framework for application of virtual features |
US9824216B1 (en) | 2015-12-31 | 2017-11-21 | Fireeye, Inc. | Susceptible environment detection system |
US10049193B2 (en) * | 2016-01-04 | 2018-08-14 | Bank Of America Corporation | System for neutralizing misappropriated electronic files |
US10218656B2 (en) | 2016-03-08 | 2019-02-26 | International Business Machines Corporation | Smart message delivery based on transaction processing status |
JP5982597B1 (en) * | 2016-03-10 | 2016-08-31 | 株式会社Ffri | Information processing apparatus, information processing method, program, and computer-readable recording medium recording the program |
US10142366B2 (en) | 2016-03-15 | 2018-11-27 | Vade Secure, Inc. | Methods, systems and devices to mitigate the effects of side effect URLs in legitimate and phishing electronic messages |
US10432661B2 (en) * | 2016-03-24 | 2019-10-01 | Cisco Technology, Inc. | Score boosting strategies for capturing domain-specific biases in anomaly detection systems |
US10601863B1 (en) | 2016-03-25 | 2020-03-24 | Fireeye, Inc. | System and method for managing sensor enrollment |
US10671721B1 (en) | 2016-03-25 | 2020-06-02 | Fireeye, Inc. | Timeout management services |
US10476906B1 (en) | 2016-03-25 | 2019-11-12 | Fireeye, Inc. | System and method for managing formation and modification of a cluster within a malware detection system |
US10785255B1 (en) | 2016-03-25 | 2020-09-22 | Fireeye, Inc. | Cluster configuration within a scalable malware detection system |
US10893059B1 (en) | 2016-03-31 | 2021-01-12 | Fireeye, Inc. | Verification and enhancement using detection systems located at the network periphery and endpoint devices |
US9591012B1 (en) * | 2016-03-31 | 2017-03-07 | Viewpost Ip Holdings, Llc | Systems and methods for detecing fraudulent electronic communication |
US11277416B2 (en) * | 2016-04-22 | 2022-03-15 | Sophos Limited | Labeling network flows according to source applications |
US10938781B2 (en) | 2016-04-22 | 2021-03-02 | Sophos Limited | Secure labeling of network flows |
US11102238B2 (en) | 2016-04-22 | 2021-08-24 | Sophos Limited | Detecting triggering events for distributed denial of service attacks |
US11165797B2 (en) | 2016-04-22 | 2021-11-02 | Sophos Limited | Detecting endpoint compromise based on network usage history |
US10986109B2 (en) | 2016-04-22 | 2021-04-20 | Sophos Limited | Local proxy detection |
EP3475822B1 (en) | 2016-06-22 | 2020-07-22 | Invincea, Inc. | Methods and apparatus for detecting whether a string of characters represents malicious activity using machine learning |
US10169585B1 (en) | 2016-06-22 | 2019-01-01 | Fireeye, Inc. | System and methods for advanced malware detection through placement of transition events |
US10073968B1 (en) * | 2016-06-24 | 2018-09-11 | Symantec Corporation | Systems and methods for classifying files |
WO2018004600A1 (en) * | 2016-06-30 | 2018-01-04 | Sophos Limited | Proactive network security using a health heartbeat |
US10462173B1 (en) | 2016-06-30 | 2019-10-29 | Fireeye, Inc. | Malware detection verification and enhancement by coordinating endpoint and malware detection systems |
US10812348B2 (en) | 2016-07-15 | 2020-10-20 | A10 Networks, Inc. | Automatic capture of network data for a detected anomaly |
US10938844B2 (en) | 2016-07-22 | 2021-03-02 | At&T Intellectual Property I, L.P. | Providing security through characterizing mobile traffic by domain names |
US10341118B2 (en) | 2016-08-01 | 2019-07-02 | A10 Networks, Inc. | SSL gateway with integrated hardware security module |
RU2649793C2 (en) | 2016-08-03 | 2018-04-04 | ООО "Группа АйБи" | Method and system of detecting remote connection when working on web resource pages |
WO2018039792A1 (en) | 2016-08-31 | 2018-03-08 | Wedge Networks Inc. | Apparatus and methods for network-based line-rate detection of unknown malware |
US11182476B2 (en) * | 2016-09-07 | 2021-11-23 | Micro Focus Llc | Enhanced intelligence for a security information sharing platform |
US10592678B1 (en) | 2016-09-09 | 2020-03-17 | Fireeye, Inc. | Secure communications between peers using a verified virtual trusted platform module |
RU2634209C1 (en) | 2016-09-19 | 2017-10-24 | Общество с ограниченной ответственностью "Группа АйБи ТДС" | System and method of autogeneration of decision rules for intrusion detection systems with feedback |
US10805314B2 (en) * | 2017-05-19 | 2020-10-13 | Agari Data, Inc. | Using message context to evaluate security of requested data |
US9847973B1 (en) | 2016-09-26 | 2017-12-19 | Agari Data, Inc. | Mitigating communication risk by detecting similarity to a trusted message contact |
US10880322B1 (en) | 2016-09-26 | 2020-12-29 | Agari Data, Inc. | Automated tracking of interaction with a resource of a message |
US11936604B2 (en) | 2016-09-26 | 2024-03-19 | Agari Data, Inc. | Multi-level security analysis and intermediate delivery of an electronic message |
US10491627B1 (en) | 2016-09-29 | 2019-11-26 | Fireeye, Inc. | Advanced malware detection using similarity analysis |
US10218716B2 (en) * | 2016-10-01 | 2019-02-26 | Intel Corporation | Technologies for analyzing uniform resource locators |
US10382562B2 (en) | 2016-11-04 | 2019-08-13 | A10 Networks, Inc. | Verification of server certificates using hash codes |
US10795991B1 (en) | 2016-11-08 | 2020-10-06 | Fireeye, Inc. | Enterprise search |
GB2555858B (en) * | 2016-11-15 | 2021-06-23 | F Secure Corp | Remote malware scanning method and apparatus |
US10587647B1 (en) | 2016-11-22 | 2020-03-10 | Fireeye, Inc. | Technique for malware detection capability comparison of network security devices |
US11722513B2 (en) | 2016-11-30 | 2023-08-08 | Agari Data, Inc. | Using a measure of influence of sender in determining a security risk associated with an electronic message |
US11044267B2 (en) | 2016-11-30 | 2021-06-22 | Agari Data, Inc. | Using a measure of influence of sender in determining a security risk associated with an electronic message |
US10250475B2 (en) | 2016-12-08 | 2019-04-02 | A10 Networks, Inc. | Measurement of application response delay time |
US10552610B1 (en) | 2016-12-22 | 2020-02-04 | Fireeye, Inc. | Adaptive virtual machine snapshot update framework for malware behavioral analysis |
US10581879B1 (en) | 2016-12-22 | 2020-03-03 | Fireeye, Inc. | Enhanced malware detection for generated objects |
CN111541674A (en) * | 2016-12-23 | 2020-08-14 | 新东网科技有限公司 | WEB site safety protection method and system with high detection efficiency |
US10523609B1 (en) | 2016-12-27 | 2019-12-31 | Fireeye, Inc. | Multi-vector malware detection and analysis |
RU2637477C1 (en) | 2016-12-29 | 2017-12-04 | Общество с ограниченной ответственностью "Траст" | System and method for detecting phishing web pages |
RU2671991C2 (en) | 2016-12-29 | 2018-11-08 | Общество с ограниченной ответственностью "Траст" | System and method for collecting information for detecting phishing |
US10397270B2 (en) | 2017-01-04 | 2019-08-27 | A10 Networks, Inc. | Dynamic session rate limiter |
US10187377B2 (en) | 2017-02-08 | 2019-01-22 | A10 Networks, Inc. | Caching network generated security certificates |
US10904286B1 (en) | 2017-03-24 | 2021-01-26 | Fireeye, Inc. | Detection of phishing attacks using similarity analysis |
US10554507B1 (en) | 2017-03-30 | 2020-02-04 | Fireeye, Inc. | Multi-level control for enhanced resource and object evaluation management of malware detection system |
US10902119B1 (en) | 2017-03-30 | 2021-01-26 | Fireeye, Inc. | Data extraction system for malware analysis |
US10791138B1 (en) | 2017-03-30 | 2020-09-29 | Fireeye, Inc. | Subscription-based malware detection |
US10798112B2 (en) | 2017-03-30 | 2020-10-06 | Fireeye, Inc. | Attribute-controlled malware detection |
US11019076B1 (en) | 2017-04-26 | 2021-05-25 | Agari Data, Inc. | Message security assessment using sender identity profiles |
JP6533823B2 (en) * | 2017-05-08 | 2019-06-19 | デジタルア−ツ株式会社 | INFORMATION PROCESSING APPARATUS, INFORMATION PROCESSING SYSTEM, PROGRAM, RECORDING MEDIUM, AND INFORMATION PROCESSING METHOD |
US10170112B2 (en) * | 2017-05-11 | 2019-01-01 | Google Llc | Detecting and suppressing voice queries |
US11757914B1 (en) * | 2017-06-07 | 2023-09-12 | Agari Data, Inc. | Automated responsive message to determine a security risk of a message sender |
US11102244B1 (en) * | 2017-06-07 | 2021-08-24 | Agari Data, Inc. | Automated intelligence gathering |
JP6378808B2 (en) * | 2017-06-28 | 2018-08-22 | エヌ・ティ・ティ・コミュニケーションズ株式会社 | Connection destination information determination device, connection destination information determination method, and program |
US10601848B1 (en) | 2017-06-29 | 2020-03-24 | Fireeye, Inc. | Cyber-security system and method for weak indicator detection and correlation to generate strong indicators |
US10855700B1 (en) | 2017-06-29 | 2020-12-01 | Fireeye, Inc. | Post-intrusion detection of cyber-attacks during lateral movement within networks |
US10503904B1 (en) | 2017-06-29 | 2019-12-10 | Fireeye, Inc. | Ransomware detection and mitigation |
US10893068B1 (en) | 2017-06-30 | 2021-01-12 | Fireeye, Inc. | Ransomware file modification prevention technique |
US10742669B2 (en) * | 2017-08-09 | 2020-08-11 | NTT Security Corporation | Malware host netflow analysis system and method |
RU2666644C1 (en) | 2017-08-10 | 2018-09-11 | Акционерное общество "Лаборатория Касперского" | System and method of identifying potentially hazardous devices at user interaction with bank services |
US10891373B2 (en) * | 2017-08-31 | 2021-01-12 | Micro Focus Llc | Quarantining electronic messages based on relationships among associated addresses |
US10983602B2 (en) * | 2017-09-05 | 2021-04-20 | Microsoft Technology Licensing, Llc | Identifying an input device |
US10747872B1 (en) | 2017-09-27 | 2020-08-18 | Fireeye, Inc. | System and method for preventing malware evasion |
US10805346B2 (en) | 2017-10-01 | 2020-10-13 | Fireeye, Inc. | Phishing attack detection |
US10708308B2 (en) * | 2017-10-02 | 2020-07-07 | Servicenow, Inc. | Automated mitigation of electronic message based security threats |
US11108809B2 (en) | 2017-10-27 | 2021-08-31 | Fireeye, Inc. | System and method for analyzing binary code for malware classification using artificial neural network techniques |
AU2018358228A1 (en) * | 2017-10-31 | 2020-05-07 | GoSecure, Inc | Analysis and reporting of suspicious email |
RU2689816C2 (en) | 2017-11-21 | 2019-05-29 | ООО "Группа АйБи" | Method for classifying sequence of user actions (embodiments) |
US11356482B2 (en) * | 2017-11-27 | 2022-06-07 | ArmorBlox, Inc. | Message validation using machine-learned user models |
US11271955B2 (en) | 2017-12-28 | 2022-03-08 | Fireeye Security Holdings Us Llc | Platform and method for retroactive reclassification employing a cybersecurity-based global data store |
US11005860B1 (en) | 2017-12-28 | 2021-05-11 | Fireeye, Inc. | Method and system for efficient cybersecurity analysis of endpoint events |
US11240275B1 (en) | 2017-12-28 | 2022-02-01 | Fireeye Security Holdings Us Llc | Platform and method for performing cybersecurity analyses employing an intelligence hub with a modular architecture |
RU2680736C1 (en) | 2018-01-17 | 2019-02-26 | Общество с ограниченной ответственностью "Группа АйБи ТДС" | Malware files in network traffic detection server and method |
RU2677368C1 (en) | 2018-01-17 | 2019-01-16 | Общество С Ограниченной Ответственностью "Группа Айби" | Method and system for automatic determination of fuzzy duplicates of video content |
RU2677361C1 (en) | 2018-01-17 | 2019-01-16 | Общество с ограниченной ответственностью "Траст" | Method and system of decentralized identification of malware programs |
RU2676247C1 (en) | 2018-01-17 | 2018-12-26 | Общество С Ограниченной Ответственностью "Группа Айби" | Web resources clustering method and computer device |
RU2668710C1 (en) | 2018-01-17 | 2018-10-02 | Общество с ограниченной ответственностью "Группа АйБи ТДС" | Computing device and method for detecting malicious domain names in network traffic |
RU2681699C1 (en) | 2018-02-13 | 2019-03-12 | Общество с ограниченной ответственностью "Траст" | Method and server for searching related network resources |
US10826931B1 (en) | 2018-03-29 | 2020-11-03 | Fireeye, Inc. | System and method for predicting and mitigating cybersecurity system misconfigurations |
US11003773B1 (en) | 2018-03-30 | 2021-05-11 | Fireeye, Inc. | System and method for automatically generating malware detection rule recommendations |
US11558401B1 (en) | 2018-03-30 | 2023-01-17 | Fireeye Security Holdings Us Llc | Multi-vector malware detection data sharing system for improved detection |
US10956477B1 (en) | 2018-03-30 | 2021-03-23 | Fireeye, Inc. | System and method for detecting malicious scripts through natural language processing modeling |
JP6768732B2 (en) * | 2018-04-05 | 2020-10-14 | デジタルア−ツ株式会社 | Information processing equipment, information processing programs, recording media and information processing methods |
US10880319B2 (en) * | 2018-04-26 | 2020-12-29 | Micro Focus Llc | Determining potentially malware generated domain names |
US11431745B2 (en) * | 2018-04-30 | 2022-08-30 | Microsoft Technology Licensing, Llc | Techniques for curating threat intelligence data |
US10785188B2 (en) * | 2018-05-22 | 2020-09-22 | Proofpoint, Inc. | Domain name processing systems and methods |
US10839353B2 (en) * | 2018-05-24 | 2020-11-17 | Mxtoolbox, Inc. | Systems and methods for improved email security by linking customer domains to outbound sources |
US11372893B2 (en) | 2018-06-01 | 2022-06-28 | Ntt Security Holdings Corporation | Ensemble-based data curation pipeline for efficient label propagation |
US11075930B1 (en) | 2018-06-27 | 2021-07-27 | Fireeye, Inc. | System and method for detecting repetitive cybersecurity attacks constituting an email campaign |
US11314859B1 (en) | 2018-06-27 | 2022-04-26 | FireEye Security Holdings, Inc. | Cyber-security system and method for detecting escalation of privileges within an access token |
US11228491B1 (en) | 2018-06-28 | 2022-01-18 | Fireeye Security Holdings Us Llc | System and method for distributed cluster configuration monitoring and management |
US11316900B1 (en) | 2018-06-29 | 2022-04-26 | FireEye Security Holdings Inc. | System and method for automatically prioritizing rules for cyber-threat detection and mitigation |
US11182473B1 (en) | 2018-09-13 | 2021-11-23 | Fireeye Security Holdings Us Llc | System and method for mitigating cyberattacks against processor operability by a guest process |
US11374977B2 (en) * | 2018-09-20 | 2022-06-28 | Forcepoint Llc | Endpoint risk-based network protection |
US11763004B1 (en) | 2018-09-27 | 2023-09-19 | Fireeye Security Holdings Us Llc | System and method for bootkit detection |
US11025651B2 (en) | 2018-12-06 | 2021-06-01 | Saudi Arabian Oil Company | System and method for enhanced security analysis for quarantined email messages |
RU2708508C1 (en) | 2018-12-17 | 2019-12-09 | Общество с ограниченной ответственностью "Траст" | Method and a computing device for detecting suspicious users in messaging systems |
US11743290B2 (en) | 2018-12-21 | 2023-08-29 | Fireeye Security Holdings Us Llc | System and method for detecting cyberattacks impersonating legitimate sources |
US11176251B1 (en) | 2018-12-21 | 2021-11-16 | Fireeye, Inc. | Determining malware via symbolic function hash analysis |
US11368475B1 (en) | 2018-12-21 | 2022-06-21 | Fireeye Security Holdings Us Llc | System and method for scanning remote services to locate stored objects with malware |
RU2701040C1 (en) | 2018-12-28 | 2019-09-24 | Общество с ограниченной ответственностью "Траст" | Method and a computer for informing on malicious web resources |
US11601444B1 (en) | 2018-12-31 | 2023-03-07 | Fireeye Security Holdings Us Llc | Automated system for triage of customer issues |
US11411990B2 (en) * | 2019-02-15 | 2022-08-09 | Forcepoint Llc | Early detection of potentially-compromised email accounts |
SG11202101624WA (en) | 2019-02-27 | 2021-03-30 | Group Ib Ltd | Method and system for user identification by keystroke dynamics |
US11063897B2 (en) * | 2019-03-01 | 2021-07-13 | Cdw Llc | Method and system for analyzing electronic communications and customer information to recognize and mitigate message-based attacks |
US11310238B1 (en) | 2019-03-26 | 2022-04-19 | FireEye Security Holdings, Inc. | System and method for retrieval and analysis of operational data from customer, cloud-hosted virtual resources |
US10686826B1 (en) * | 2019-03-28 | 2020-06-16 | Vade Secure Inc. | Optical scanning parameters computation methods, devices and systems for malicious URL detection |
RU2710739C1 (en) * | 2019-03-29 | 2020-01-10 | Акционерное общество "Лаборатория Касперского" | System and method of generating heuristic rules for detecting messages containing spam |
US11677786B1 (en) | 2019-03-29 | 2023-06-13 | Fireeye Security Holdings Us Llc | System and method for detecting and protecting against cybersecurity attacks on servers |
US11636198B1 (en) | 2019-03-30 | 2023-04-25 | Fireeye Security Holdings Us Llc | System and method for cybersecurity analyzer update and concurrent management system |
US11582120B2 (en) | 2019-05-30 | 2023-02-14 | Vmware, Inc. | Partitioning health monitoring in a global server load balancing system |
US11258806B1 (en) | 2019-06-24 | 2022-02-22 | Mandiant, Inc. | System and method for automatically associating cybersecurity intelligence to cyberthreat actors |
US11405363B2 (en) | 2019-06-26 | 2022-08-02 | Microsoft Technology Licensing, Llc | File upload control for client-side applications in proxy solutions |
US11556640B1 (en) | 2019-06-27 | 2023-01-17 | Mandiant, Inc. | Systems and methods for automated cybersecurity analysis of extracted binary string sets |
US11392700B1 (en) | 2019-06-28 | 2022-07-19 | Fireeye Security Holdings Us Llc | System and method for supporting cross-platform data verification |
US11178178B2 (en) * | 2019-07-29 | 2021-11-16 | Material Security Inc. | Secure communications service for intercepting suspicious messages and performing backchannel verification thereon |
CN110443051B (en) * | 2019-07-30 | 2022-12-27 | 空气动力学国家重点实验室 | Method for preventing confidential documents from spreading on Internet |
US11159464B2 (en) * | 2019-08-02 | 2021-10-26 | Dell Products L.P. | System and method for detecting and removing electronic mail storms |
KR102300193B1 (en) * | 2019-09-02 | 2021-09-08 | 주식회사 엘지유플러스 | Method and apparatus for preventing error remittance |
KR102219277B1 (en) * | 2019-09-03 | 2021-02-23 | 구글 엘엘씨 | System and method for controlling the delivery of authenticated content |
US11886585B1 (en) | 2019-09-27 | 2024-01-30 | Musarubra Us Llc | System and method for identifying and mitigating cyberattacks through malicious position-independent code execution |
US11637862B1 (en) | 2019-09-30 | 2023-04-25 | Mandiant, Inc. | System and method for surfacing cyber-security threats with a self-learning recommendation engine |
RU2728498C1 (en) | 2019-12-05 | 2020-07-29 | Общество с ограниченной ответственностью "Группа АйБи ТДС" | Method and system for determining software belonging by its source code |
RU2728497C1 (en) | 2019-12-05 | 2020-07-29 | Общество с ограниченной ответственностью "Группа АйБи ТДС" | Method and system for determining belonging of software by its machine code |
RU2743974C1 (en) | 2019-12-19 | 2021-03-01 | Общество с ограниченной ответственностью "Группа АйБи ТДС" | System and method for scanning security of elements of network architecture |
US11838300B1 (en) | 2019-12-24 | 2023-12-05 | Musarubra Us Llc | Run-time configurable cybersecurity system |
US11436327B1 (en) | 2019-12-24 | 2022-09-06 | Fireeye Security Holdings Us Llc | System and method for circumventing evasive code for cyberthreat detection |
US11522884B1 (en) | 2019-12-24 | 2022-12-06 | Fireeye Security Holdings Us Llc | Subscription and key management system |
US11582190B2 (en) * | 2020-02-10 | 2023-02-14 | Proofpoint, Inc. | Electronic message processing systems and methods |
SG10202001963TA (en) | 2020-03-04 | 2021-10-28 | Group Ib Global Private Ltd | System and method for brand protection based on the search results |
US11641375B2 (en) * | 2020-04-29 | 2023-05-02 | KnowBe4, Inc. | Systems and methods for reporting based simulated phishing campaign |
EP4135281A4 (en) * | 2020-05-29 | 2024-01-31 | Siemens Ltd China | Industrial control system safety analysis method and apparatus, and computer-readable medium |
US11475090B2 (en) | 2020-07-15 | 2022-10-18 | Group-Ib Global Private Limited | Method and system for identifying clusters of affiliated web resources |
US11483314B2 (en) | 2020-08-04 | 2022-10-25 | Mastercard Technologies Canada ULC | Distributed evaluation list updating |
RU2743619C1 (en) | 2020-08-06 | 2021-02-20 | Общество с ограниченной ответственностью "Группа АйБи ТДС" | Method and system for generating the list of compromise indicators |
US11050698B1 (en) * | 2020-09-18 | 2021-06-29 | Area 1 Security, Inc. | Message processing system with business email compromise detection |
US20220116406A1 (en) * | 2020-10-12 | 2022-04-14 | Microsoft Technology Licensing, Llc | Malware detection and mitigation via a forward proxy server |
US11588848B2 (en) | 2021-01-05 | 2023-02-21 | Bank Of America Corporation | System and method for suspending a computing device suspected of being infected by a malicious code using a kill switch button |
US11748680B2 (en) | 2021-02-22 | 2023-09-05 | Intone Networks India Pvt. Ltd | System for internal audit and internal control management and related methods |
US11947572B2 (en) | 2021-03-29 | 2024-04-02 | Group IB TDS, Ltd | Method and system for clustering executable files |
US11882112B2 (en) | 2021-05-26 | 2024-01-23 | Bank Of America Corporation | Information security system and method for phishing threat prevention using tokens |
US11799824B2 (en) * | 2021-06-14 | 2023-10-24 | Vmware, Inc. | Method and apparatus for enhanced client persistence in multi-site GSLB deployments |
US20230004638A1 (en) * | 2021-06-30 | 2023-01-05 | Citrix Systems, Inc. | Redirection of attachments based on risk and context |
US11934402B2 (en) * | 2021-08-06 | 2024-03-19 | Bank Of America Corporation | System and method for generating optimized data queries to improve hardware efficiency and utilization |
US20230041397A1 (en) * | 2021-08-06 | 2023-02-09 | Vmware, Inc. | System and method for checking reputations of executable files using file origin analysis |
US11941121B2 (en) * | 2021-12-28 | 2024-03-26 | Uab 360 It | Systems and methods for detecting malware using static and dynamic malware models |
CN115348234B (en) * | 2022-08-10 | 2023-11-03 | 山石网科通信技术股份有限公司 | Server detection method and device and electronic equipment |
WO2024044037A1 (en) * | 2022-08-26 | 2024-02-29 | Stairwell, Inc. | Evaluating files using a rule- or feature-based system for detection of malicious and/or suspicious patterns |
CN115632878B (en) * | 2022-12-06 | 2023-03-31 | 中海油能源发展股份有限公司采油服务分公司 | Data transmission method, device, equipment and storage medium based on network isolation |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4956769A (en) * | 1988-05-16 | 1990-09-11 | Sysmith, Inc. | Occurence and value based security system for computer databases |
US5970149A (en) * | 1996-11-19 | 1999-10-19 | Johnson; R. Brent | Combined remote access and security system |
US6334193B1 (en) * | 1997-05-29 | 2001-12-25 | Oracle Corporation | Method and apparatus for implementing user-definable error handling processes |
US20020073240A1 (en) * | 2000-11-27 | 2002-06-13 | Heikki Kokkinen | Server |
US20020143888A1 (en) * | 2001-04-02 | 2002-10-03 | Akamai Technologies, Inc. | Scalable, high performance and highly available distributed storage system for internet content |
US20030208562A1 (en) * | 2002-05-06 | 2003-11-06 | Hauck Leon E. | Method for restricting access to a web site by remote users |
Family Cites Families (132)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5715466A (en) | 1995-02-14 | 1998-02-03 | Compuserve Incorporated | System for parallel foreign language communication over a computer network |
US5623600A (en) * | 1995-09-26 | 1997-04-22 | Trend Micro, Incorporated | Virus detection and removal apparatus for computer networks |
US5926462A (en) * | 1995-11-16 | 1999-07-20 | Loran Network Systems, Llc | Method of determining topology of a network of objects which compares the similarity of the traffic sequences/volumes of a pair of devices |
US6453327B1 (en) * | 1996-06-10 | 2002-09-17 | Sun Microsystems, Inc. | Method and apparatus for identifying and discarding junk electronic mail |
US6072942A (en) | 1996-09-18 | 2000-06-06 | Secure Computing Corporation | System and method of electronic mail filtering using interconnected nodes |
US6119236A (en) | 1996-10-07 | 2000-09-12 | Shipley; Peter M. | Intelligent network security device and method |
US7778877B2 (en) | 2001-07-09 | 2010-08-17 | Linkshare Corporation | Enhanced network based promotional tracking system |
US7117358B2 (en) | 1997-07-24 | 2006-10-03 | Tumbleweed Communications Corp. | Method and system for filtering communication |
US6073165A (en) * | 1997-07-29 | 2000-06-06 | Jfax Communications, Inc. | Filtering computer network messages directed to a user's e-mail box based on user defined filters, and forwarding a filtered message to the user's receiver |
US6006329A (en) | 1997-08-11 | 1999-12-21 | Symantec Corporation | Detection of computer viruses spanning multiple data streams |
US6393465B2 (en) | 1997-11-25 | 2002-05-21 | Nixmail Corporation | Junk electronic mail detector and eliminator |
US6052709A (en) | 1997-12-23 | 2000-04-18 | Bright Light Technologies, Inc. | Apparatus and method for controlling delivery of unsolicited electronic mail |
US6161185A (en) * | 1998-03-06 | 2000-12-12 | Mci Communications Corporation | Personal authentication system and method for multiple computer platform |
JP3225924B2 (en) | 1998-07-09 | 2001-11-05 | 日本電気株式会社 | Communication quality control device |
US6067619A (en) | 1998-09-24 | 2000-05-23 | Hewlett-Packard Company | Apparatus and method for configuring a computer networking device |
US6546416B1 (en) | 1998-12-09 | 2003-04-08 | Infoseek Corporation | Method and system for selectively blocking delivery of bulk electronic mail |
US6615242B1 (en) | 1998-12-28 | 2003-09-02 | At&T Corp. | Automatic uniform resource locator-based message filter |
US6654787B1 (en) | 1998-12-31 | 2003-11-25 | Brightmail, Incorporated | Method and apparatus for filtering e-mail |
US6507866B1 (en) | 1999-07-19 | 2003-01-14 | At&T Wireless Services, Inc. | E-mail usage pattern detection |
US7184971B1 (en) | 1999-11-20 | 2007-02-27 | Advertising.Com | Method and apparatus for an E-mail affiliate program |
CA2392397A1 (en) * | 1999-11-23 | 2001-05-31 | Escom Corporation | Electronic message filter having a whitelist database and a quarantining mechanism |
US6728690B1 (en) | 1999-11-23 | 2004-04-27 | Microsoft Corporation | Classification system trainer employing maximum margin back-propagation with probabilistic outputs |
US6701440B1 (en) | 2000-01-06 | 2004-03-02 | Networks Associates Technology, Inc. | Method and system for protecting a computer using a remote e-mail scanning device |
US7822977B2 (en) * | 2000-02-08 | 2010-10-26 | Katsikas Peter L | System for eliminating unauthorized electronic mail |
JP2001222480A (en) * | 2000-02-14 | 2001-08-17 | Fujitsu Ltd | Electronic mail operation management system |
US20040006747A1 (en) | 2000-03-13 | 2004-01-08 | Tyler Joseph C. | Electronic publishing system and method |
US6931437B2 (en) * | 2000-04-27 | 2005-08-16 | Nippon Telegraph And Telephone Corporation | Concentrated system for controlling network interconnections |
US7428576B2 (en) | 2000-05-16 | 2008-09-23 | Hoshiko Llc | Addressee-defined mail addressing system and method |
US6732153B1 (en) * | 2000-05-23 | 2004-05-04 | Verizon Laboratories Inc. | Unified message parser apparatus and system for real-time event correlation |
US8972717B2 (en) * | 2000-06-15 | 2015-03-03 | Zixcorp Systems, Inc. | Automatic delivery selection for electronic content |
US7328349B2 (en) | 2001-12-14 | 2008-02-05 | Bbn Technologies Corp. | Hash-based systems and methods for detecting, preventing, and tracing network worms and viruses |
GB2357939B (en) * | 2000-07-05 | 2002-05-15 | Gfi Fax & Voice Ltd | Electronic mail message anti-virus system and method |
US20020059418A1 (en) | 2000-07-17 | 2002-05-16 | Alan Bird | Method of and system for recording and displaying electronic mail statistics |
TW569106B (en) | 2000-07-29 | 2004-01-01 | Hai Lin | A method preventing spam |
US7149778B1 (en) | 2000-08-24 | 2006-12-12 | Yahoo! Inc. | Unsolicited electronic mail reduction |
GB2366706B (en) | 2000-08-31 | 2004-11-03 | Content Technologies Ltd | Monitoring electronic mail messages digests |
US6886099B1 (en) | 2000-09-12 | 2005-04-26 | Networks Associates Technology, Inc. | Computer virus detection |
US6785712B1 (en) | 2000-09-21 | 2004-08-31 | Rockwell Collins, Inc. | Airborne e-mail data transfer protocol |
US6757830B1 (en) * | 2000-10-03 | 2004-06-29 | Networks Associates Technology, Inc. | Detecting unwanted properties in received email messages |
JP2002123469A (en) * | 2000-10-13 | 2002-04-26 | Nec System Technologies Ltd | Electronic mail transmitter-receiver, electronic mail system, electronic mail processing method and recording medium |
US6748422B2 (en) | 2000-10-19 | 2004-06-08 | Ebay Inc. | System and method to control sending of unsolicited communications relating to a plurality of listings in a network-based commerce facility |
EP1360597A4 (en) | 2001-02-15 | 2005-09-28 | Suffix Mail Inc | E-mail messaging system |
US8219620B2 (en) | 2001-02-20 | 2012-07-10 | Mcafee, Inc. | Unwanted e-mail filtering system including voting feedback |
US6941466B2 (en) * | 2001-02-22 | 2005-09-06 | International Business Machines Corporation | Method and apparatus for providing automatic e-mail filtering based on message semantics, sender's e-mail ID, and user's identity |
US20020120600A1 (en) * | 2001-02-26 | 2002-08-29 | Schiavone Vincent J. | System and method for rule-based processing of electronic mail messages |
GB2373130B (en) * | 2001-03-05 | 2004-09-22 | Messagelabs Ltd | Method of,and system for,processing email in particular to detect unsolicited bulk email |
US7249195B2 (en) | 2001-03-30 | 2007-07-24 | Minor Ventures, Llc | Apparatus and methods for correlating messages sent between services |
US20020184533A1 (en) | 2001-05-30 | 2002-12-05 | Fox Paul D. | System and method for providing network security policy enforcement |
US7380126B2 (en) | 2001-06-01 | 2008-05-27 | Logan James D | Methods and apparatus for controlling the transmission and receipt of email messages |
US7076527B2 (en) * | 2001-06-14 | 2006-07-11 | Apple Computer, Inc. | Method and apparatus for filtering email |
US7673342B2 (en) | 2001-07-26 | 2010-03-02 | Mcafee, Inc. | Detecting e-mail propagated malware |
JP2003046576A (en) * | 2001-07-27 | 2003-02-14 | Fujitsu Ltd | Message delivery system, message delivery management server, message distribution management program, and computer-readable recording medium with the program recorded thereon |
US7657935B2 (en) | 2001-08-16 | 2010-02-02 | The Trustees Of Columbia University In The City Of New York | System and methods for detecting malicious email transmission |
US7146402B2 (en) * | 2001-08-31 | 2006-12-05 | Sendmail, Inc. | E-mail system providing filtering methodology on a per-domain basis |
US7331061B1 (en) * | 2001-09-07 | 2008-02-12 | Secureworks, Inc. | Integrated computer security management system and method |
US7433923B2 (en) * | 2001-10-03 | 2008-10-07 | Reginald Adkins | Authorized email control system |
JP3717829B2 (en) | 2001-10-05 | 2005-11-16 | 日本デジタル株式会社 | Junk mail repelling system |
US20030096605A1 (en) * | 2001-11-16 | 2003-05-22 | Schlieben Karl J. | System for handling proprietary files |
US7319858B2 (en) * | 2001-11-16 | 2008-01-15 | Cingular Wireless Ii, Llc | System and method for querying message information |
US20030095555A1 (en) * | 2001-11-16 | 2003-05-22 | Mcnamara Justin | System for the validation and routing of messages |
US6944616B2 (en) | 2001-11-28 | 2005-09-13 | Pavilion Technologies, Inc. | System and method for historical database training of support vector machines |
US20030149726A1 (en) * | 2002-02-05 | 2003-08-07 | At&T Corp. | Automating the reduction of unsolicited email in real time |
KR100871581B1 (en) * | 2002-02-19 | 2008-12-02 | 포스티니 코포레이션 | E-mail management services |
EP1482696A4 (en) * | 2002-02-22 | 2006-03-15 | Access Co Ltd | Method and device for processing electronic mail undesirable for user |
US7400722B2 (en) * | 2002-03-28 | 2008-07-15 | Broadcom Corporation | Methods and apparatus for performing hash operations in a cryptography accelerator |
AUPS193202A0 (en) | 2002-04-23 | 2002-05-30 | Pickup, Robert Barkley Mr | A method and system for authorising electronic mail |
US7231428B2 (en) * | 2002-05-28 | 2007-06-12 | Teague Alan H | Communication system using alias management rules for automatically changing sender alias in a message based on group that includes recipient address |
US20040003255A1 (en) | 2002-06-28 | 2004-01-01 | Storage Technology Corporation | Secure email time stamping |
US7539726B1 (en) * | 2002-07-16 | 2009-05-26 | Sonicwall, Inc. | Message testing |
US20040019651A1 (en) * | 2002-07-29 | 2004-01-29 | Andaker Kristian L. M. | Categorizing electronic messages based on collaborative feedback |
US20040024632A1 (en) | 2002-08-05 | 2004-02-05 | Avenue A, Inc. | Method of determining the effect of internet advertisement on offline commercial activity |
AU2003265811A1 (en) * | 2002-08-26 | 2004-03-11 | Guardednet, Inc. | Determining threat level associated with network activity |
US7748039B2 (en) * | 2002-08-30 | 2010-06-29 | Symantec Corporation | Method and apparatus for detecting malicious code in an information handling system |
US7072944B2 (en) * | 2002-10-07 | 2006-07-04 | Ebay Inc. | Method and apparatus for authenticating electronic mail |
US20040083270A1 (en) | 2002-10-23 | 2004-04-29 | David Heckerman | Method and system for identifying junk e-mail |
US7159149B2 (en) * | 2002-10-24 | 2007-01-02 | Symantec Corporation | Heuristic detection and termination of fast spreading network worm attacks |
US7664963B2 (en) | 2002-11-04 | 2010-02-16 | Riverbed Technology, Inc. | Data collectors in connection-based intrusion detection |
US8990723B1 (en) * | 2002-12-13 | 2015-03-24 | Mcafee, Inc. | System, method, and computer program product for managing a plurality of applications via a single interface |
US7373664B2 (en) * | 2002-12-16 | 2008-05-13 | Symantec Corporation | Proactive protection against e-mail worms and spam |
US7533148B2 (en) | 2003-01-09 | 2009-05-12 | Microsoft Corporation | Framework to enable integration of anti-spam technologies |
US7171450B2 (en) | 2003-01-09 | 2007-01-30 | Microsoft Corporation | Framework to enable integration of anti-spam technologies |
US8595495B2 (en) * | 2003-01-12 | 2013-11-26 | Yaron Mayer | System and method for secure communications |
JP4344922B2 (en) | 2003-01-27 | 2009-10-14 | 富士ゼロックス株式会社 | Evaluation apparatus and method |
JP2004254034A (en) * | 2003-02-19 | 2004-09-09 | Fujitsu Ltd | System and method for controlling spam mail suppression policy |
US7249162B2 (en) | 2003-02-25 | 2007-07-24 | Microsoft Corporation | Adaptive junk message filtering system |
US7219148B2 (en) * | 2003-03-03 | 2007-05-15 | Microsoft Corporation | Feedback loop for spam prevention |
US20050091319A1 (en) * | 2003-10-09 | 2005-04-28 | Kirsch Steven T. | Database for receiving, storing and compiling information about email messages |
US20040177120A1 (en) * | 2003-03-07 | 2004-09-09 | Kirsch Steven T. | Method for filtering e-mail messages |
US7206814B2 (en) * | 2003-10-09 | 2007-04-17 | Propel Software Corporation | Method and system for categorizing and processing e-mails |
US20050091320A1 (en) * | 2003-10-09 | 2005-04-28 | Kirsch Steven T. | Method and system for categorizing and processing e-mails |
US7366761B2 (en) * | 2003-10-09 | 2008-04-29 | Abaca Technology Corporation | Method for creating a whitelist for processing e-mails |
US20040181581A1 (en) | 2003-03-11 | 2004-09-16 | Michael Thomas Kosco | Authentication method for preventing delivery of junk electronic mail |
US20060168006A1 (en) | 2003-03-24 | 2006-07-27 | Mr. Marvin Shannon | System and method for the classification of electronic communication |
US7342906B1 (en) * | 2003-04-04 | 2008-03-11 | Airespace, Inc. | Distributed wireless network security system |
US7346700B2 (en) | 2003-04-07 | 2008-03-18 | Time Warner Cable, A Division Of Time Warner Entertainment Company, L.P. | System and method for managing e-mail message traffic |
US7320020B2 (en) * | 2003-04-17 | 2008-01-15 | The Go Daddy Group, Inc. | Mail server probability spam filter |
US7366919B1 (en) * | 2003-04-25 | 2008-04-29 | Symantec Corporation | Use of geo-location data for spam detection |
US7653698B2 (en) * | 2003-05-29 | 2010-01-26 | Sonicwall, Inc. | Identifying e-mail messages from allowed senders |
US7272853B2 (en) * | 2003-06-04 | 2007-09-18 | Microsoft Corporation | Origination/destination features and lists for spam prevention |
JP4013835B2 (en) * | 2003-06-11 | 2007-11-28 | 日本電気株式会社 | E-mail relay device and e-mail relay method used therefor |
US20040254990A1 (en) | 2003-06-13 | 2004-12-16 | Nokia, Inc. | System and method for knock notification to an unsolicited message |
US8533270B2 (en) * | 2003-06-23 | 2013-09-10 | Microsoft Corporation | Advanced spam detection techniques |
US7051077B2 (en) * | 2003-06-30 | 2006-05-23 | Mx Logic, Inc. | Fuzzy logic voting method and system for classifying e-mail using inputs from multiple spam classifiers |
WO2005008417A2 (en) * | 2003-07-11 | 2005-01-27 | Computer Associates Think, Inc. | Method and system for protecting against computer viruses |
JP2005056048A (en) * | 2003-08-01 | 2005-03-03 | Fact-Real:Kk | Electronic mail monitoring system, electronic mail monitoring program and electronic mail monitoring method |
GB2405229B (en) | 2003-08-19 | 2006-01-11 | Sophos Plc | Method and apparatus for filtering electronic mail |
US20050060643A1 (en) * | 2003-08-25 | 2005-03-17 | Miavia, Inc. | Document similarity detection and classification system |
US20050060295A1 (en) | 2003-09-12 | 2005-03-17 | Sensory Networks, Inc. | Statistical classification of high-speed network data through content inspection |
US20050071432A1 (en) * | 2003-09-29 | 2005-03-31 | Royston Clifton W. | Probabilistic email intrusion identification methods and systems |
US7257564B2 (en) * | 2003-10-03 | 2007-08-14 | Tumbleweed Communications Corp. | Dynamic message filtering |
US20050080858A1 (en) * | 2003-10-10 | 2005-04-14 | Microsoft Corporation | System and method for searching a peer-to-peer network |
US7181498B2 (en) * | 2003-10-31 | 2007-02-20 | Yahoo! Inc. | Community-based green list for antispam |
JP2005208780A (en) * | 2004-01-21 | 2005-08-04 | Nec Corp | Mail filtering system and url black list dynamic construction method to be used for the same |
US8918466B2 (en) | 2004-03-09 | 2014-12-23 | Tonny Yu | System for email processing and analysis |
US7554974B2 (en) | 2004-03-09 | 2009-06-30 | Tekelec | Systems and methods of performing stateful signaling transactions in a distributed processing environment |
US7631044B2 (en) * | 2004-03-09 | 2009-12-08 | Gozoom.Com, Inc. | Suppression of undesirable network messages |
US20050204005A1 (en) | 2004-03-12 | 2005-09-15 | Purcell Sean E. | Selective treatment of messages based on junk rating |
PL1733532T3 (en) * | 2004-03-30 | 2008-12-31 | Maestro Shipping Sa | A filter and a method of filtering electronic messages |
JP4128975B2 (en) * | 2004-04-02 | 2008-07-30 | 株式会社古河テクノマテリアル | Superelastic titanium alloy for living body |
US7627670B2 (en) | 2004-04-29 | 2009-12-01 | International Business Machines Corporation | Method and apparatus for scoring unsolicited e-mail |
US7457823B2 (en) | 2004-05-02 | 2008-11-25 | Markmonitor Inc. | Methods and systems for analyzing data related to possible online fraud |
US7391725B2 (en) | 2004-05-18 | 2008-06-24 | Christian Huitema | System and method for defeating SYN attacks |
US7748038B2 (en) | 2004-06-16 | 2010-06-29 | Ironport Systems, Inc. | Method and apparatus for managing computer virus outbreaks |
US20060095410A1 (en) * | 2004-10-29 | 2006-05-04 | Ostrover Lewis S | Personal video recorder for home network providing filtering and format conversion of content |
US7634810B2 (en) * | 2004-12-02 | 2009-12-15 | Microsoft Corporation | Phishing detection, prevention, and notification |
US20060123083A1 (en) * | 2004-12-03 | 2006-06-08 | Xerox Corporation | Adaptive spam message detector |
US7610344B2 (en) * | 2004-12-13 | 2009-10-27 | Microsoft Corporation | Sender reputations for spam prevention |
US20060167971A1 (en) * | 2004-12-30 | 2006-07-27 | Sheldon Breiner | System and method for collecting and disseminating human-observable data |
US20060149820A1 (en) * | 2005-01-04 | 2006-07-06 | International Business Machines Corporation | Detecting spam e-mail using similarity calculations |
US7716743B2 (en) * | 2005-01-14 | 2010-05-11 | Microsoft Corporation | Privacy friendly malware quarantines |
CA2613083A1 (en) * | 2005-07-01 | 2007-01-11 | Markmonitor Inc. | Enhanced fraud monitoring systems |
US7475118B2 (en) | 2006-02-03 | 2009-01-06 | International Business Machines Corporation | Method for recognizing spam email |
-
2006
- 2006-05-05 JP JP2008510320A patent/JP4880675B2/en not_active Expired - Fee Related
- 2006-05-05 EP EP06770093.0A patent/EP1877905B1/en active Active
- 2006-05-05 WO PCT/US2006/017780 patent/WO2006119506A2/en active Application Filing
- 2006-05-05 CN CN200680019314XA patent/CN101495969B/en active Active
- 2006-05-05 CN CN2006800194833A patent/CN101558398B/en active Active
- 2006-05-05 WO PCT/US2006/017783 patent/WO2006119509A2/en active Application Filing
- 2006-05-05 JP JP2008510321A patent/JP5118020B2/en not_active Expired - Fee Related
- 2006-05-05 US US11/429,474 patent/US7548544B2/en active Active
- 2006-05-05 EP EP06759351.7A patent/EP1877904B1/en active Active
- 2006-05-05 CA CA2607005A patent/CA2607005C/en not_active Expired - Fee Related
- 2006-05-05 WO PCT/US2006/017782 patent/WO2006119508A2/en active Application Filing
- 2006-05-05 US US11/418,812 patent/US7854007B2/en active Active
- 2006-05-05 US US11/429,393 patent/US7877493B2/en not_active Expired - Fee Related
- 2006-05-05 WO PCT/US2006/017773 patent/WO2006122055A2/en active Application Filing
- 2006-05-05 CA CA2606998A patent/CA2606998C/en not_active Expired - Fee Related
- 2006-05-05 US US11/418,823 patent/US7836133B2/en active Active
- 2006-12-07 US US11/636,150 patent/US7712136B2/en not_active Expired - Fee Related
- 2006-12-07 US US11/635,921 patent/US20070220607A1/en not_active Abandoned
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4956769A (en) * | 1988-05-16 | 1990-09-11 | Sysmith, Inc. | Occurence and value based security system for computer databases |
US5970149A (en) * | 1996-11-19 | 1999-10-19 | Johnson; R. Brent | Combined remote access and security system |
US6334193B1 (en) * | 1997-05-29 | 2001-12-25 | Oracle Corporation | Method and apparatus for implementing user-definable error handling processes |
US20020073240A1 (en) * | 2000-11-27 | 2002-06-13 | Heikki Kokkinen | Server |
US20020143888A1 (en) * | 2001-04-02 | 2002-10-03 | Akamai Technologies, Inc. | Scalable, high performance and highly available distributed storage system for internet content |
US20030208562A1 (en) * | 2002-05-06 | 2003-11-06 | Hauck Leon E. | Method for restricting access to a web site by remote users |
Non-Patent Citations (2)
Title |
---|
ANDREWS: 'RFC 2308: Negative Caching of DNS Queries' IETF March 1998, pages 1 - 19 * |
LEVINE: 'DNS Based Blacklists and Whitelists for E-Mail' IETF 26 April 2004, pages 1 - 7 * |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101378407B (en) * | 2008-09-26 | 2012-10-17 | 成都市华为赛门铁克科技有限公司 | Method, system and equipment for pushing information |
EP3206364A1 (en) * | 2016-02-10 | 2017-08-16 | Agari Data, Inc | Message authenticity and risk assessment |
US10154056B2 (en) | 2016-02-10 | 2018-12-11 | Agari Data, Inc. | Message authenticity and risk assessment |
US10757130B2 (en) | 2016-02-10 | 2020-08-25 | Agari Data, Inc. | Message authenticity and risk assessment |
US11552981B2 (en) | 2016-02-10 | 2023-01-10 | Agari Data, Inc. | Message authenticity and risk assessment |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7877493B2 (en) | Method of validating requests for sender reputation information | |
US7603472B2 (en) | Zero-minute virus and spam detection | |
US7954155B2 (en) | Identifying unwanted electronic messages | |
US8725889B2 (en) | E-mail management services | |
US8108477B2 (en) | Message classification using legitimate contact points | |
US7849142B2 (en) | Managing connections, messages, and directory harvest attacks at a server | |
US7873695B2 (en) | Managing connections and messages at a server by associating different actions for both different senders and different recipients | |
US7870200B2 (en) | Monitoring the flow of messages received at a server | |
US7921063B1 (en) | Evaluating electronic mail messages based on probabilistic analysis | |
US8468601B1 (en) | Method and system for statistical analysis of botnets | |
US7774420B2 (en) | Managing on-demand email storage | |
US20060031314A1 (en) | Techniques for determining the reputation of a message sender | |
US20100100957A1 (en) | Method And Apparatus For Controlling Unsolicited Messages In A Messaging Network Using An Authoritative Domain Name Server | |
US8195750B1 (en) | Method and system for tracking botnets | |
WO2012115990A1 (en) | System and method to customize dns replies | |
US20060265459A1 (en) | Systems and methods for managing the transmission of synchronous electronic messages | |
US20140040403A1 (en) | System, method and computer program product for gathering information relating to electronic content utilizing a dns server | |
US7958187B2 (en) | Systems and methods for managing directory harvest attacks via electronic messages | |
Pathak et al. | The case for spam-aware high performance mail server architecture |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
NENP | Non-entry into the national phase |
Ref country code: DE |
|
NENP | Non-entry into the national phase |
Ref country code: RU |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 06759349 Country of ref document: EP Kind code of ref document: A2 |