# US 2024/0205300 A1 · Generating service-to-service dependency map from dns and authentication logs

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

- Number: US 2024/0205300 A1
- Document ID: US20240205300A1
- Status: Published application
- Kind: A1
- Application number: 18/066,235
- Filed: 2022-12-14
- Published: 2024-06-20
- Earliest claimed: 2022-12-14
- Assignees: Microsoft Technology Licensing, LLC
- Applicants: Microsoft Technology Licensing, LLC
- Inventors: George KIM; Christian Cypress CHUNG; Vivek Sanjeev TEJWANI; Sorabh Kumar GANDHI; Abhishek PATHAK
- Web page: https://patentgrep.com/patent/US20240205300A1

## CPC

- H04L 67/51: Discovery or management thereof, e.g. service location protocol [SLP] or web services
- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- H04L 61/4511: using domain name system [DNS]
- H04L 63/0846: {using time-dependent-passwords, e.g. periodically changing passwords}
- G06F 2009/45591: {Monitoring or debugging support}
- G06F 2009/45595: {Network integration; Enabling network access in virtual machine instances}
- H04L 63/1425: {Traffic logging, e.g. anomaly detection}
- H04L 63/145: {the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A distributed computing system is provided, and configured to execute a DNS log analyzer configured to identify a dependency of a first service executed on a first VM at a first server, on a second service executed on a second VM at a second server, via one or more DNS logs of a domain name server. The system is further configured to execute an authentication log analyzer configured to identify a dependency of the first service on a third service executed at a third server, via the one or more token authentication logs of an authentication server. The system is further configured to execute a dependency map generator configured to generate a service-to-service dependency map including the dependency between the first service and the second service, and the dependency between the first service and third service.

## Claims

### Claim 1

A distributed computing system, comprising:
a processor and memory storing instructions that cause the processor to execute:
a domain name service (DNS) log analyzer configured to identify a dependency of a first service executed on a first virtual machine (VM) at a first server of the distributed computing system, on a second service executed on a second VM at a second server of the distributed computing system, via one or more DNS logs of a domain name server of the distributed computing system;
an authentication log analyzer configured to identify a dependency of the first service on a third service executed at a third server of the distributed computing system, via one or more token authentication logs of an authentication server of the distributed computing system; and
a dependency map generator configured to generate a service-to-service dependency map including the dependency between the first service and the second service, and the dependency between the first service and third service.

### Claim 2 (depends on 1)

The computing system of claim 1, wherein the second service is a pass-through service that passes a request from the first service to a third service for processing.

### Claim 3 (depends on 2)

The computing system of claim 2, wherein
the authentication log analyzer is further configured to identify a dependency between the second service and the third service based on the one or more DNS logs, and
the dependency between the second service and third service is included in the service-to-service dependency map.

### Claim 4 (depends on 1)

The computing system of claim 1, wherein
the DNS log analyzer is configured to identify the dependency of the first service on the second service by:
identifying, within a DNS request log of the one or more DNS logs, a DNS request log record for a DNS request, the DNS request log record including a source identifier associated with the first service and a source IP address associated with the first service, wherein the source identifier is determined to be associated with the first service by identifying a virtual machine (VM) implementing the first service on a computer that has been assigned the source IP address, wherein the source identifier is a source virtual machine identifier or a source container identifier,
identifying, within the DNS request log record a destination fully qualified domain name requested by the DNS request,
identifying within a DNS response log record for a DNS response to the DNS request, a destination IP address for the destination fully qualified domain name, and
identifying the second service as being associated with the destination IP address.

### Claim 5 (depends on 1)

The computing system of claim 1, wherein the authentication log analyzer is configured to identify the dependency between the first service and third service, based on an authentication log record for an authentication request from the third service to authenticate a token of the first service received via the second service.

### Claim 6 (depends on 5)

The computing system of claim 5, wherein
the authentication log analyzer is further configured to identify the dependency of the first service on the third service at least in part by:
identifying, within a token generation log of the one or more authentication logs, a token generation log record, the token generation log record including the source container identifier and a globally unique identifier (GUID) as the token, wherein the source container identifier is associated with a source container implementing a virtual machine (VM) that has been assigned the GUID associated with the token;
identifying in the authentication logs a token authentication request from the second service for a token associated with the first service; and
identifying, within an authentication response log of the one or more authentication logs, an authentication response log record for an authentication response, the authentication response log record including a destination identifier that identifies a VM implementing the third service that requested authentication of the token, the token including the GUID assigned to the VM implemented by the source container.

### Claim 7 (depends on 5)

The computing system of claim 5, wherein the dependency map generator is further configured to:
determine the second service is a pass-through service by comparing a timeframe of a DNS request from the second service requesting the IP address of the third service and a DNS response to this DNS request, a timeframe of a DNS request from the first service requesting the IP address of the second service, and a timeframe of the authentication request from the third service.

### Claim 8 (depends on 1)

The computing system of claim 1, wherein
the service-to-service dependency map is output to a downstream computing program for processing;
wherein the downstream program is selected from the group consisting of a recovery program configured to compute a fault diagnosis program configured to generate a fault diagnosis based on the service-to-service dependency map as the processing operation, a recovery schedule for restarting services based on the service-to-service dependency map as the processing operation, a geographic compliance program configured to determine a geographic scope of a location of servers executing the first service and the second service as the processing operation, and a threat identification program configured to scan system logs of servers executing dependent services of the first service to identify a presence or effect or a virus or malware on the servers as the processing operation.

### Claim 9 (depends on 1)

The computing system of claim 1, wherein
the computing system is configured to display the service-to-service dependency map within a graphical user interface, and
a number of levels of dependency displayed is determined by input from a user.

### Claim 10 (depends on 1)

The computing system of claim 1, wherein
the service-to-service dependency map is mapped over a lifetime of the identified first service, including build time, test time, deployment time, run time, and retirement.

### Claim 11

A computing method for a distributed computing system, comprising:
identifying a dependency of a first service executed on a first virtual machine (VM) at a first server of the distributed computing system, on a second service executed on a second VM at a second server of the distributed computing system, via one or more domain name server (DNS) logs of a domain name server of the distributed computing system;
identifying a dependency of the first service on a third service executed at a third server of the distributed computing system, via one or more token authentication logs of an authentication server of the distributed computing system; and
generating a service-to-service dependency map including the dependency between the first service and the second service, and the dependency between the first service and third service.

### Claim 12 (depends on 11)

The computing method of claim 11, wherein the second service is a pass-through service that passes a request from the first service to a third service for processing.

### Claim 13 (depends on 12)

The computing method of claim 12, further comprising:
identifying a dependency between the second service and the third service based on the one or more DNS logs; and
including the dependency between the second service and third service in the service-to-service dependency map.

### Claim 14 (depends on 11)

The computing method of claim 11, wherein
identifying the dependency of the first service on the second service is accomplished at least in part by:
identifying, within a DNS request log of the one or more DNS logs, a DNS request log record for a DNS request, the DNS request log record including a source identifier associated with the first service and a source IP address associated with the first service, wherein the source identifier is determined to be associated with the first service by identifying a virtual machine (VM) implementing the first service on a computer that has been assigned the source IP address, wherein the source identifier is a source virtual machine identifier or a source container identifier, identifying, within the DNS request log record a destination fully qualified domain name requested by the DNS request,
identifying within a DNS response log record for a DNS response to the DNS request, a destination IP address for the destination fully qualified domain name, and
identifying the second service as being associated with the destination IP address.

### Claim 15 (depends on 11)

The computing method of claim 11, wherein
identifying the dependency of the first service on the third service is accomplished at least in part by, identifying an authentication log record for an authentication request from the third service to authenticate a token of the first service received via the second service.

### Claim 16 (depends on 15)

The computing method of claim 15, wherein
identifying the dependency of the first service on the third service is at least in part accomplished by:
identifying, within a token generation log of the one or more authentication logs, a token generation log record, the token generation log record including the source container identifier and a globally unique identifier (GUID) as the token, wherein the source container identifier is associated with a source container implementing a virtual machine (VM) that has been assigned the GUID associated with the token;
identifying in the authentication logs a token authentication request from the second service for a token associated with the first service; and
identifying, within an authentication response log of the one or more authentication logs, an authentication response log record for an authentication response, the authentication response log record including a destination identifier that identifies a VM implementing the third service that requested authentication of the token, the token including the GUID assigned to the VM implemented by the source container.

### Claim 17 (depends on 11)

The computing method of claim 11, the method further comprising:
determining the second service is a pass-through service by comparing a timeframe of a DNS request from the second service requesting the IP address of the third service and a DNS response to this DNS request, a timeframe of a DNS request from the first service requesting the IP address of the second service, and a timeframe of the authentication request from the third service.

### Claim 18 (depends on 17)

The computing method of claim 17, further comprising:
outputting the service-to-service dependency map to a downstream computing program for processing, wherein
the downstream program is selected from the group consisting of a recovery program configured to compute a recovery schedule for restarting services based on the service-to-service dependency map as the processing operation, a fault diagnosis program configured to generate a fault diagnosis based on the service-to-service dependency map as the processing operation, a geographic compliance program configured to determine a geographic scope of a location of servers executing the first service and the second service as the processing operation, and a threat identification program configured to scan system logs of servers executing dependent services of the first service to identify a presence or effect or a virus or malware on the servers.

### Claim 19 (depends on 11)

The computing method of claim 11, the method further comprising:
mapping the service-to-service dependency map over a lifetime of the identified first service, including build time, test time, deployment time, run time, and retirement.

### Claim 20

A computing method for a distributed computing system, comprising:
identifying a dependency of a first service executed on a first virtual machine (VM) at a first server of the distributed computing system, on a second service executed on a second virtual machine at a second server of the distributed computing system, via one or more domain name server (DNS) logs of a domain name server of the distributed computing system, wherein the second service is a pass-through service that passes a request from the first service to a third service for processing;
identifying a dependency of the first service on the third service executed at a third server of the distributed computing system, via one or more token authentication logs of an authentication server of the distributed computing system;
identifying a dependency between the second service and the third service based on the one or more DNS logs;
generating a service-to-service dependency map including the dependency between the first service and the second service, the dependency between the second and third service, and the dependency between the first service and third service;
outputting the service-to-service dependency map as input to a downstream program executed on a server of the distributed computing system;
performing, via the downstream program, a processing operation based on the service-to-service dependency map; and
outputting a processing result of the processing operation.
