# US 8,782,754 B2 · Implementing secured, event-based layered logout from a computer system

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

- Number: US 8,782,754 B2
- Document ID: US8782754B2
- Status: Granted
- Kind: B2
- Application number: 13/661,112
- Filed: 2012-10-26
- Published: 2013-02-21
- Granted: 2014-07-15
- Earliest claimed: 2010-09-30
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Girish Dhanakshirur
- Web page: https://patentgrep.com/patent/US8782754B2

## CPC

- H04L 63/105: {Multiple levels of security}
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06N 5/00: Computing arrangements using knowledge-based models
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 63/102: {Entity profiles}
- H04L 67/143: Termination or inactivation of sessions, e.g. event-controlled end of session
- 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)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS

## Abstract

A secure, layered logout of a user session is implemented in a management tool. A logout strategy is provided to include a set of security levels of varying sensitivity, with each security level having a set of permissions that are enforced upon occurrence of an event. A succeeding security level in the set of security levels is reached upon occurrence of an event associated with that level, in which case the permissions associated with the level are then enforced against at least one object while the user session continues. As each next security level is reached, the set of permissions are then enforced, once again while the user session continues. The layered logout may enforce different permissions with respect to different objects. If the user takes no action, eventually a final security level will occur, at which point the user session is finally terminated.

## Claims

### Claim 1

A method to provide a structured logout from a user session, comprising:
providing a logout strategy to include a set of predefined, ordered security levels of varying sensitivity, each security level having a set of permissions associated therewith and that are enforced upon occurrence of an event, and wherein each succeeding security level in the set of predefined, ordered security levels is reached as an event associated with the succeeding security level occurs;
upon occurrence of an event associated with a security level, enforcing the set of permissions associated with the security level against at least one managed object while continuing the user session; and
upon reaching a final security level of the set of security levels, ending the user session;
wherein at least one of the providing, enforcing and ending operations is carried out in software executing in a hardware element.

### Claim 2 (depends on 1)

The method as described in claim 1 wherein the set of permissions associated with the security level are a subset of a set of available permissions that are associated with the at least one managed object.

### Claim 3 (depends on 1)

The method as described in claim 1 wherein the event associated with the security level has a first characteristic that differs from an event associated with at least one other security level.

### Claim 4 (depends on 1)

The method as described in claim 1 further including associating a first security level with a first managed object, and a second security level with a second managed object that differs from the first managed object.

### Claim 5 (depends on 4)

The method as described in claim 4 wherein each of the first and second security levels have differing sets of permissions so that occurrence of a first event associated with the first security level enforces a first set of permissions against the first managed object and occurrence of a second event associated with the second security level enforces a second set of permissions against the second managed object.

### Claim 6 (depends on 1)

The method as described in claim 1 further including issuing a notification upon occurrence of an event associated with a security level.

### Claim 7 (depends on 1)

The method as described in claim 1 further including logging in to the user session in a trusted manner.

### Claim 8 (depends on 1)

The method as described in claim 1 wherein the managed object is an object that is managed during the user session independently of at least one other managed object.