# US 10,997,287 B2 · Real-time monitoring and alerting for directory object update processing

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

- Number: US 10,997,287 B2
- Document ID: US10997287B2
- Status: Granted
- Kind: B2
- Application number: 15/726,212
- Filed: 2017-10-05
- Published: 2019-04-11
- Granted: 2021-05-04
- Earliest claimed: 2017-10-05
- Assignees: Micro Focus Software Inc.
- Applicants: Micro Focus Software Inc.
- Inventors: Paul Robert Judson
- Web page: https://patentgrep.com/patent/US10997287B2

## CPC

- G06F 21/552: {involving long-term monitoring or reporting}
- G06F 11/006: {Identification (G06F11/2289 takes precedence)}
- G06F 11/302: {where the computing system component is a software system}
- G06F 11/3034: {where the computing system component is a storage system, e.g. DASD based or network based (digital input from or digital output to record carriers G06F3/06; digital recording or reproducing G11B20/18; for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS], H04L67/1097)}
- G06F 11/3055: {Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available (error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction of the data by redundancy in operations G06F11/14; error detection or correction by redundancy in hardware G06F11/16)}
- G06F 11/3612: {by runtime analysis (performance monitoring G06F11/3466)}
- G06F 21/554: {involving event detection and direct action}
- G06Q 20/40: Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06F 8/70: Software maintenance or management
- G06F 11/3692: {for test results analysis}
- G06F 2201/86: Event-based monitoring
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- 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

## Abstract

An update change request that is made against attributes of a directory object causes automatically collection of customized information for an initiator of the request. A correlation identifier for the change request is generated. The changes to the attributes are processed to update the directory object and the customized information is updated to an extension attribute for the directory object. A unique audit event is raised for each changed attribute including the extension attribute and each audit event includes the correlation identifier.

## Claims

### Claim 1

A method, comprising:
automatically collecting information for an initiator when a change request is made to update attributes of an object;
generating a second change request to update an extension attribute on the object, wherein the second change request comprising the information, and wherein the initiator is unaware of the second change request;
formulating each individual change associated with each attribute being modified with the change request and the information associated with the extension attribute for the second change request as a payload associated with multiple attribute updates to the object in a single update based on the change request and the second change request;
processing the single update with the payload on the object by updating the information to the extension attribute of the object and updating the attributes of the object with values provided in the change request;
generating a unique correlation identifier for the change request;
producing an audit event for each changed attribute;
creating first audit entries, each first audit entry comprising a corresponding audit event and the unique correlation identifier;
creating a new audit event comprising the information and the unique correlation identifier;
creating a second audit entry comprising the new audit event; and
updating an audit store with the first audit entries and the second audit entry.

### Claim 2 (depends on 1)

The method of claim 1, wherein collecting further includes collecting the information as one or more of: an initiator identifier for the initiator and a machine identifier for a machine operated by the initiator when making the change request.

### Claim 3 (depends on 2)

The method of claim 2, wherein collecting further includes adding a time stamp for when the initiator made the change request from the machine to the information.

### Claim 4 (depends on 1)

The method of claim 1, wherein processing further includes transparently updating the information to the extension attribute, wherein the initiator is unaware of the information being updated to the extension attribute.

### Claim 5 (depends on 1)

The method of claim 1, wherein creating the new audit entry further includes injecting the first audit entries and the second audit entry into an audit stream upon commitment of updates to the attributes and the extension attribute of the object to an object store.

### Claim 6 (depends on 1)

The method of claim 1 further comprising, automatically processing one or more security actions in response to the audit event associated with the extension attribute.

### Claim 7 (depends on 1)

The method of claim 1 further comprising, automatically providing the audit events to a real-time monitoring service.

### Claim 8 (depends on 1)

The method of claim 1 further comprising, automatically raising an alert to a monitoring service based on the audit events.

### Claim 9 (depends on 1)

The method of claim 1 further comprising, storing the audit events in an audit log.

### Claim 10 (depends on 1)

The method of claim 1 further comprising, processing the method as an enhancement to a directory service that manages the object as a directory object for a file system.

### Claim 11

A method, comprising:
obtaining a principal identifier for a principal in response to a change request initiated by the principal to update at least one attribute of a directory object;
generating a second change request to update an extension attribute on the directory object, wherein the second change request comprising the principal identifier, and wherein the principal is unaware of the second change request;
formulating each individual change associated with each at least one attribute being modified with the change request and the principal identifier associated with the extension attribute for the second change request as a payload associated with multiple attribute updates to the direct object in a single update based on the change request and the second change request;
committing the single update to a directory store for updating the at least one attribute of the directory attribute with at least one value provided in the change request and for updating the extension attribute with the principal identifier;
generating a unique correlation identifier for the change request;
creating at least one audit event, each of the at least one audit events comprising a specific change value made with the change request to a corresponding one of the at least one attributes of the directory object;
creating at least one first audit entry, each of the at least one first audit entries comprising a corresponding audit event and the unique correlation identifier;
creating a new audit event comprising the principal identifier of the extension attribute from the object and the unique correlation identifier;
creating a second audit entry comprising the new audit event; and
updating an audit store with the at least one first audit entries and the second audit entry.

### Claim 12 (depends on 11)

The method of claim 11, wherein obtaining further includes identifying the principal identifier as being associated with a type of principal that includes one of:
a user and an application.

### Claim 13 (depends on 11)

The method of claim 11, wherein obtaining further includes obtaining a machine identifier from a machine used by the principal when making the change request.

### Claim 14 (depends on 13)

The method of claim 13, wherein formulating further includes providing the machine identifier with the principal identifier within the payload for the single update for updating within the extension attribute during the committing.

### Claim 15 (depends on 11)

The method of claim 11 further comprising, associating the principal identifier with a security issue based on a total number of additional change requests associated with the principal identifier.

### Claim 16

A system, comprising:
a server comprising at least one hardware processor and a non-transitory computer-readable storage medium;
the non-transitory computer-readable storage medium comprising executable instructions representing a directory service and an audit service;
the directory service when executed by the at least one hardware processor from the non-transitory computer-readable storage medium causes the at least one hardware processor to perform operations comprising:
collecting identifying information for a principal making a change request to at least one attribute of a directory object;
generating a second change request to update an extension attribute on the directory object, wherein the second change request comprises the identifying information, and wherein the principal is unaware of the second change request;
formulating each individual change associated with each at least one attribute being modified with the change request and the identifying identifier associated with the extension attribute for the second change request as a payload associated with multiple attribute updates to the direct object in a single update based on the change request and the second change request;
generating a unique correlation identifier for the change request; and
submitting the single update with the payload to a directory store for processing the change request and the second change request; and
the audit service when executed by the at least one hardware processor from the non-transitory computer-readable storage medium causes the at least one hardware processor to perform second operations comprising:
creating at least one audit event, each of the at least one audit events comprising a specific change value made with the change request to a corresponding one of the at least one attributes of the directory object;
creating at least one first audit entry, each of the at least one first audit entries comprising a corresponding audit event and the unique correlation identifier;
creating a new audit event comprising the identifying information of the extension attribute from the object and the unique correlation identifier;
creating a second audit entry comprising the new audit event;
updating an audit store with the at least one first audit entry and the second audit entry; and
injecting the at least one audit event and the new audit event into an audit processing stream of a network.

### Claim 17 (depends on 16)

The system of claim 16, wherein the directory service and the audit service are integrated as enhancement processing into an existing directory service of the network.
