# US 2026/0163919 A1 · Domain specific language for defending against a threat-actor and adversarial tactics, techniques, and procedures

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

- Number: US 2026/0163919 A1
- Document ID: US20260163919A1
- Status: Published application
- Kind: A1
- Application number: 19/183,347
- Filed: 2025-04-18
- Published: 2026-06-11
- Earliest claimed: 2019-04-15
- Assignees: Qualys, Inc.
- Applicants: Qualys, Inc.
- Inventors: Mayuresh Vishwas Dani; Ankur S. Tyagi
- Web page: https://patentgrep.com/patent/US20260163919A1

## CPC

- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04L 63/1416: {Event detection, e.g. attack signature detection}
- H04L 63/1433: {Vulnerability analysis}
- H04L 63/1441: {Countermeasures against malicious traffic (countermeasures against attacks on cryptographic mechanisms H04L9/002)}
- H04L 63/145: {the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms}
- H04W 12/128: Anti-malware arrangements, e.g. protection against SMS fraud or mobile malware
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

The present disclosure describes defending against an attack execution operation. According to one aspect of the subject matter described in this disclosure, a method for generating a domain-specific language (DSL) file is disclosed. The method may comprise determining, a framework based on an attack repository, determining a first primitive based on the framework, and determining a second primitive based on the framework. In one implementation, the first primitive and the second primitive are fundamental structures or constructs within a DSL. The method further comprises combining the first primitive and the second primitive into a DSL file. In one implementation, the DSL file is executed to defend against a first attack execution operation executed by a threat-actor.

## Claims

### Claim 1

A method comprising:
determining, using one or more computing device processors, a framework based on or associated with an attack repository, the attack repository comprising attack data associated with multiple computing devices associated with at least one entity, the attack data comprising at least one of:
first data associated with a plurality of attack execution operations,
second data associated with one or more attackers associated with a first attack execution operation comprised in the plurality of attack execution operations, and
third data associated with one or more resources associated with the plurality of attack execution operations;
determining, using the one or more computing device processors, a first primitive based on or associated with the framework, the first primitive comprising at least one of:
a first identifier associated with the first attack execution operation comprised in the plurality of attack execution operations,
a first descriptor indicating an attack type associated with the first attack execution operation, the attack type comprising at least one of:
a first attack type that indicates whether a first attack step associated with the first attack execution operation is executed on a first target,
a second attack type that indicates whether the first attack step is executed as part of the first attack execution operation on a second target, and
a third attack type that indicates whether the first attack step is executed as part of the first attack execution operation on a third target,
a second descriptor indicating a vulnerability type associated with the first attack execution operation,
a third descriptor indicating a stability parameter associated with the first attack execution operation, or
a fourth descriptor indicating intensity data associated with the first attack execution operation;
determining, using the one or more computing device processors, a second primitive based on or associated with the framework, the second primitive indicating defense information associated with the first attack execution operation, the second primitive comprising at least a first defense step associated with protecting the one or more resources associated with the plurality of attack execution operations, the first defense step comprising:
a second identifier associated with the first defense step, or
a security parameter for defending against the first attack execution operation; and
generating, using the one or more computing device processors, based on the first primitive and the second primitive, a domain specific language (DSL) file, wherein:
the DSL file is executed to defend against the first attack execution operation,
the DSL file is configured to be executed in one or more domains, and
the DSL file is executed to at least partially dynamically change a security posture associated with the one or more domains.

### Claim 2 (depends on 1)

The method of claim 1, wherein the security parameter is associated with one or more security applications used for defending against the first attack execution operation.

### Claim 3 (depends on 1)

The method of claim 1, wherein the vulnerability type associated with the first attack execution operation is one of:
a public vulnerability indicating that the first attack execution operation is associated with a publicly known attack execution operation,
a private vulnerability indicating that the first attack execution operation is associated with a private attack execution operation, or
a custom vulnerability indicating that the first attack execution operation is associated with a custom attack execution operation.

### Claim 4 (depends on 1)

The method of claim 1, wherein the stability parameter associated with the first attack execution operation comprises one of:
a low stability parameter indicating that the DSL file is at least partially unstable when executed,
a medium stability parameter indicating that the DSL file is monitored when executed, and
a high stability parameter indicating that the DSL file is at least partially stable when executed.

### Claim 5 (depends on 1)

The method of claim 1, wherein the intensity data associated with the first attack execution operation indicates complexity information associated with the first attack execution operation.

### Claim 6 (depends on 1)

The method of claim 1, wherein the security parameter is associated with one or more of:
a file system,
an event viewer,
a system monitor,
an antivirus application,
an intrusion prevention system (IPS) application, or
a security information and event management (SIEM) application.

### Claim 7 (depends on 1)

The method of claim 1, wherein the DSL file is executed based on at least one of:
a file type,
a file path, or
a security event.

### Claim 8 (depends on 7)

The method of claim 7, wherein the security event comprises one or more security commands associated with or comprising one or more attack steps associated with the first attack execution operation.

### Claim 9 (depends on 1)

The method of claim 1, wherein the framework maps security events associated with one or more computing devices to one or more security operations.

### Claim 10

A computer program comprising a non-transitory computer useable medium including computer readable code that when executed by one or more computing device processors, causes the one or more computing device processors to:
determine a framework based on or associated with an attack repository, the attack repository comprising attack data associated with at least one computing device associated with at least one entity, the attack data comprising at least one of:
first data associated with a plurality of attack execution operations,
second data associated with one or more attackers associated with a first attack execution operation comprised in the plurality of attack execution operations, and
third data indicating one or more resources associated with the plurality of attack execution operations;
determine a first primitive based on or associated with the framework, the first primitive comprising at least one of:
a first identifier associated with the first attack execution operation comprised in the plurality of attack execution operations,
a first descriptor indicating an attack type associated with the first attack execution operation,
a second descriptor indicating a vulnerability type associated with the first attack execution operation,
a third descriptor indicating a stability parameter associated with the first attack execution operation, or
a fourth descriptor indicating intensity data associated with the first attack execution operation;
determine a second primitive based on or associated with the framework, the second primitive indicating defense information associated with the first attack execution operation, the second primitive comprising at least a first defense step associated with protecting the one or more resources associated with the plurality of attack execution operations, the first defense step comprising:
a second identifier associated with the first defense step, or
a security parameter for defending against the first attack execution operation; and
generate, based on the first primitive and the second primitive, a domain specific language (DSL) file, wherein:
the DSL file is executed to defend against the first attack execution operation,
the DSL file is configured to be executed in one or more domains, and
the DSL file is executed to at least partially dynamically change a security posture associated with the one or more domains.

### Claim 11 (depends on 10)

The computer program of claim 10, wherein the security parameter is associated with one or more of:
a file system,
an event viewer,
a system monitor,
an antivirus application,
an intrusion prevention system (IPS) application, or
a security information and event management (SIEM) application.

### Claim 12 (depends on 10)

The computer program of claim 10, wherein the DSL file is executed based on at least one of:
a file type,
a file path, or
a security event.

### Claim 13 (depends on 12)

The computer program of claim 12, wherein the security event comprises one or more security commands associated with or comprising one or more attack steps associated with the first attack execution operation.

### Claim 14 (depends on 10)

The computer program of claim 10, wherein the framework maps security events associated with one or more computing devices to one or more security operations.

### Claim 15

A system comprising:
one or more computing system processors; and
memory storing instructions that, when executed by the one or more computing system processors, causes the system to:
determine a framework based on or associated with an attack repository, the attack repository comprising attack data associated with at least one computing device associated with at least one entity, the attack data comprising at least one of:
first data associated with a plurality of attack execution operations,
second data associated with one or more attackers associated with a first attack execution operation comprised in the plurality of attack execution operations, or
third data indicating one or more resources associated with the plurality of attack execution operations;
determine a first primitive based on or associated with the framework, the first primitive comprising at least one of:
a first identifier associated with the first attack execution operation comprised in the plurality of attack execution operations,
a first descriptor indicating an attack type associated with the first attack execution operation,
a second descriptor indicating a vulnerability type associated with the first attack execution operation,
a third descriptor indicating a stability parameter associated with the first attack execution operation, or
a fourth descriptor indicating intensity data associated with the first attack execution operation;
determine a second primitive based on or associated with the framework, the second primitive indicating defense information associated with the first attack execution operation, the second primitive comprising at least a first defense step associated with protecting the one or more resources associated with the plurality of attack execution operations, the first defense step comprising:
a second identifier associated with the first defense step, or
a security parameter for defending against the first attack execution operation; and
generate, based on the first primitive and the second primitive, a first file, wherein:
the first file is executed to defend against the first attack execution operation,
the first file is configured to be executed in one or more domains, and
the first file is executed to at least partially dynamically change a security posture associated with the one or more domains.

### Claim 16 (depends on 15)

The system of claim 15, wherein the defense information is associated with at least one resource comprised in the one or more resources, the at least one resource comprising at least one of:
a second file,
a hardware tool, or
a software tool.

### Claim 17 (depends on 15)

The system of claim 15, wherein the security parameter for defending against the first attack execution operation is associated with at least one of:
a file system,
an event viewer,
a system monitor,
an antivirus application,
an intrusion prevention system (IPS) application, or
a security information and event management (SIEM) application.

### Claim 18 (depends on 15)

The system of claim 15, wherein the framework maps security events associated with one or more computing devices to one or more security operations.

### Claim 19

A method comprising:
determining, using one or more computing device processors, a framework based on or associated with an attack repository, the attack repository comprising attack data associated with at least one computing device associated with at least one entity the attack data comprising at least one of:
first data associated with a plurality of attack execution operations,
second data associated with one or more attackers associated with a first attack execution operation comprised in the plurality of attack execution operations, and
third data associated with one or more resources associated with the plurality of attack execution operations;
determining, using the one or more computing device processors, a first primitive based on or associated with the framework, the first primitive comprising at least one of:
a first identifier associated with the first attack execution operation comprised in the plurality of attack execution operations,
a first descriptor associated with an attack type associated with the first attack execution operation,
a second descriptor associated with a vulnerability type associated with the first attack execution operation,
a third descriptor associated with a stability parameter associated with the first attack execution operation, or
a fourth descriptor associated with intensity data associated with the first attack execution operation;
determining, using the one or more computing device processors, a second primitive based on or associated with the framework, the second primitive associated with defense information associated with the first attack execution operation, the second primitive comprising at least a first defense step associated with protecting the one or more resources associated with the plurality of attack execution operations, the first defense step comprising:
a second identifier associated with the first defense step, or
a security parameter for defending against the first attack execution operation; and
generating, using the one or more computing device processors, based on the first primitive and the second primitive, a domain specific language (DSL) file, wherein the DSL file is associated with defending against the first attack execution operation, wherein the DSL file is configured to be executed in one or more domains, and wherein the DSL file is executed to change a security posture associated with the one or more domains.

### Claim 20 (depends on 1)

The method of claim 1, wherein at least one of:
the first attack type is executed on the first target to:
select the first target,
obtain information about the first target, and
execute the first attack execution operation on the first target,
the second target comprises a mobile computing environment, or
the third target comprises an enterprise computing environment.
