# US 2026/0100974 A1 · Methods and apparatus to improve the efficiency of an artificial intelligence-based threat detection model

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0100974 A1
- Document ID: US20260100974A1
- Status: Published application
- Kind: A1
- Application number: 18/909,665
- Filed: 2024-10-08
- Published: 2026-04-09
- Earliest claimed: 2024-10-08
- Assignees: McAfee, Inc.
- Applicants: McAfee, LLC
- Inventors: German Lancioni; Eric Wuehler
- Web page: https://patentgrep.com/patent/US20260100974A1

## CPC

- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04L 41/16: using machine learning or artificial intelligence
- H04L 63/0236: {Filtering by address, protocol, port number or service, e.g. IP-address or URL}
- H04L 63/101: {Access control lists [ACL]}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems, apparatus, articles of manufacture, and methods are disclosed to improve the efficiency of an artificial intelligence-based threat detection model. An example apparatus includes interface circuitry, machine readable instructions, and programmable circuitry to at least one of instantiate or execute the machine readable instructions to: obtain an email address from a group of email addresses to be considered as candidates for adding to the list of non-suspicious email addresses, determine that a domain of the email address is indicative of a non-email service providing entity, determine that the email address has a policy configured for a domain-based message authentication, reporting, and conformance (DMARC) record, add the email address associated to the list of non-suspicious email addresses, and cause the artificial intelligence-based threat detection model to skip an analysis of an email associated with the email address.

## Claims

### Claim 1

An apparatus to generate a list of non-suspicious email addresses to be used by an artificial intelligence-based threat detection model that is to analyze an email for a threat, the apparatus comprising:
interface circuitry;
machine readable instructions; and
programmable circuitry to at least one of instantiate or execute the machine readable instructions to:
obtain an email address from a group of email addresses to be considered as candidates for adding to the list of non-suspicious email addresses;
determine that a domain of the email address is indicative of a non-email service providing entity;
determine that the email address has a policy configured for a domain-based message authentication, reporting, and conformance (DMARC) record;
add the email address associated to the list of non-suspicious email addresses; and
cause the artificial intelligence-based threat detection model to skip an analysis of an email associated with the email address.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the email address is a first email address, and the programmable circuitry is to:
obtain a second email address from the group of email addresses;
determine that a domain of the second email address is indicative of an email service providing entity; and
remove the second email address from the group of email addresses to be considered as candidates.

### Claim 3 (depends on 1)

The apparatus of claim 1, wherein the programmable circuitry is to determine that the email address has a policy configured for the DMARC record when the policy is set to reject or quarantine.

### Claim 4 (depends on 1)

The apparatus of claim 1, wherein the programmable circuitry is to generate a lookup table based on the list of non-suspicious email addresses.

### Claim 5 (depends on 1)

The apparatus of claim 1, wherein the programmable circuitry is to append an event count to the email address after adding the email address to the list of non-suspicious email addresses, the event count to cause the programmable circuitry to reevaluate the email address after an event count has passed.

### Claim 6 (depends on 1)

The apparatus of claim 1, wherein the email address is a first email address, the non-email service providing entity is a first non-email service providing entity, the DMARC record is a first DMARC record, and the programmable circuitry is to:
obtain a second email address from the group of email addresses;
determine that a domain of the second email address is indicative of a second non-email service providing entity;
determine that the second email address has not configured a policy for a second DMARC record; and
remove the second email address from the group of email addresses to be considered as candidates.

### Claim 7 (depends on 6)

The apparatus of claim 6, wherein the second non-email service providing entity has validly configured the second DMARC record and a user of the second email address has not configured the policy for the second DMARC record.

### Claim 8

A non-transitory machine readable storage medium to generate a list of non-suspicious email addresses to be used by an artificial intelligence-based threat detection model that is to analyze an email for a threat, the non-transitory machine readable storage medium comprising instructions to cause programmable circuitry to at least:
obtain an email address from a group of email addresses to be considered as candidates for adding to the list of non-suspicious email addresses;
determine that a domain of the email address is indicative of a non-email service providing entity;
determine that the email address has a policy configured for a domain-based message authentication, reporting, and conformance (DMARC) record;
add the email address associated to the list of non-suspicious email addresses; and
cause the artificial intelligence-based threat detection model to skip an analysis of an email associated with the email address.

### Claim 9 (depends on 8)

The non-transitory machine readable storage medium of claim 8, wherein the email address is a first email address, and the instructions are to cause the programmable circuitry to:
obtain a second email address from the group of email addresses;
determine that a domain of the second email address is indicative of an email service providing entity; and
remove the second email address from the group of email addresses to be considered as candidates.

### Claim 10 (depends on 8)

The non-transitory machine readable storage medium of claim 8, wherein the instructions are to cause the programmable circuitry to determine that the email address has a policy configured for the DMARC record when the policy is set to reject or quarantine.

### Claim 11 (depends on 8)

The non-transitory machine readable storage medium of claim 8, wherein the instructions are to cause the programmable circuitry to generate a lookup table based on the list of non-suspicious email addresses.

### Claim 12 (depends on 8)

The non-transitory machine readable storage medium of claim 8, wherein the instructions are to cause the programmable circuitry to append an event count to the email address after adding the email address to the list of non-suspicious email addresses, the event count to cause the programmable circuitry to reevaluate the email address after an event count has passed.

### Claim 13 (depends on 8)

The non-transitory machine readable storage medium of claim 8, wherein the email address is a first email address, the non-email service providing entity is a first non-email service providing entity, the DMARC record is a first DMARC record, and the instructions are to cause the programmable circuitry to:
obtain a second email address from the group of email addresses;
determine that a domain of the second email address is indicative of a second non-email service providing entity;
determine that the second email address has not configured a policy for a second DMARC record; and
remove the second email address from the group of email addresses to be considered as candidates.

### Claim 14 (depends on 13)

The non-transitory machine readable storage medium of claim 13, wherein the second non-email service providing entity has validly configured the second DMARC record and a user of the second email address has not configured the policy for the second DMARC record.

### Claim 15

A server to distribute first software instructions on a network to generate a list of non-suspicious email addresses to be used by an artificial intelligence-based threat detection model that is to analyze an email for a threat, the server comprising:
at least one storage device including second instructions; and
at least one processor to execute the second instructions to transmit the first software instructions over the network, the first software instructions, when executed, to cause at least one device to:
obtain an email address from a group of email addresses to be considered as candidates for adding to the list of non-suspicious email addresses;
determine that a domain of the email address is indicative of a non-email service providing entity;
determine that the email address has a policy configured for a domain-based message authentication, reporting, and conformance (DMARC) record;
add the email address associated to the list of non-suspicious email addresses; and
cause the artificial intelligence-based threat detection model to skip an analysis of an email associated with the email address.

### Claim 16 (depends on 15)

The server of claim 15, wherein the email address is a first email address and the first software instructions are to cause the at least one device to:
obtain a second email address from the group of email addresses;
determine that a domain of the second email address is indicative of an email service providing entity; and
remove the second email address from the group of email addresses to be considered as candidates.

### Claim 17 (depends on 15)

The server of claim 15, wherein the first software instructions are to cause the at least one device to determine that the email address has a policy configured for the DMARC record when the policy is set to reject or quarantine.

### Claim 18 (depends on 15)

The server of claim 15, wherein the first software instructions are to cause the at least one device to generate a lookup table based on the list of non-suspicious email addresses.

### Claim 19 (depends on 15)

The server of claim 15, wherein the first software instructions are to cause the at least one device to append an event count to the email address after adding the email address to the list of non-suspicious email addresses, the event count to cause the first software instructions to reevaluate the email address after an event count has passed.

### Claim 20 (depends on 15)

The server of claim 15, wherein the email address is a first email address, the non-email service providing entity is a first non-email service providing entity, the DMARC record is a first DMARC record, and the first software instructions are to cause the at least one device to:
obtain a second email address from the group of email addresses;
determine that a domain of the second email address is indicative of a second non-email service providing entity;
determine that the second email address has not configured a policy for a second DMARC record; and
remove the second email address from the group of email addresses to be considered as candidates.
