Privileged account plug-in framework—usage policies

• US 10,541,988 B2
• Filed: 08/03/2017
• Issued: 01/21/2020
• Est. Priority Date: 09/19/2013
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Kottahachchi, Buddhika, Sharma, Himanshu, Sathyanarayan, Ramaprakash Hosalli, Ho, Fannie, Theebaprakasam, Arun, Tirumalai, Srikant Krishnapuram, Stullich, Olaf
• Primary Examiner(s): Choudhury, Azizul
• Application Number:
  US15/668,441
• Publication Number:
  US 20170359327A1
• Time in Patent Office: 901 Days
• CPC Class Codes: G06F 21/30 Authentication, i.e. establishing the identity or authorisation of security principals
• CPC Class Codes: G06F 21/604 Tools and structures for managing or administering access control systems
• CPC Class Codes: G06F 2221/2101 Auditing as a secondary aspect
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices
• CPC Class Codes: G06F 2221/2149 Restricted operating environment
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 67/562 Brokering proxy services

Abstract

Techniques for managing privileged accounts via a privileged access management service are provided. In some examples, the service may be configured with a plug-in framework for accessing secure resources. In some aspects, a log-in request that includes authentication information and corresponds to the service may be received. Session access to at least one secure resource may be provided when a user is authenticated. In some examples, a request to perform an action associated with the secure resource may be received during the session. Additionally, in some examples, the plug-in framework may be implemented to determine whether the user is allowed to perform the action. Further, performance of the action may be allowed or denied during the session based on the determination.

Claims

1. A system, comprising:

a memory storing computer-executable instructions; and

a processor that accesses the memory and executes the computer-executable instructions to at least;

receive plug-in code for implementing runtime privileges;

receive, from a first user, a log-in request to start a session, the log-in request including at least first authentication information;

establishing the session for the first user; and

during the session;

receive, from a computing device of the first user, a request to perform an action associated with at least one secure network resource; and

perform the action for the first user based at least in part on a second user being authenticated and being logged in to share the session with the first user.

2. The system of claim 1, wherein the action is performed for the first user at least in response to a determination that the first user is allowed to perform the action based at least in part on the runtime privileges and a runtime factor.

3. The system of claim 2, wherein the runtime factor is associated with the first user or the at least one secure network resource.

4. The system of claim 3, wherein the runtime factor comprises at least one of a time, a locality, a client, a number of requests, or a privilege granted to the first user.

5. The system of claim 1, wherein the at least one secure network resource is a privileged account of a privileged access management service.

6. The system of claim 5, wherein the privileged access management service is implemented by a first virtual machine and a plug-in framework is implemented by a second virtual machine, the first virtual machine and the second virtual machine being different virtual machines.

7. The system of claim 6, wherein the second virtual machine is sandboxed and separated from the first virtual machine.

8. The system of claim 6, wherein the plug-in framework is implemented to determine whether the first user is allowed to perform the action by executing instructions to at least:

transmit the request to perform the action to the second virtual machine;

configure the second virtual machine to execute the plug-in code;

receive, from the second virtual machine, a result of executing the plug-in code; and

process, utilizing the first virtual machine, the result to perform the action within the session if it is determined, by the plug-in code, that the first user is allowed to perform the action.

9. A non-transitory computer-readable storage memory storing a plurality of instructions executed by one or more processors to:

receive plug-in code for implementing runtime privileges;

receive, from a first user, a log-in request to start a session, the log-in request including at least first authentication information;

establishing the session for the first user; and

during the session;

receive, from a computing device of the first user, a request to perform an action associated with at least one secure network resource; and

perform the action for the first user based at least in part on a second user being authenticated and being logged in to share the session with the first user.

10. The non-transitory computer-readable storage memory of claim 9, wherein the action is performed for the first user at least in response to a determination that the first user is allowed to perform the action based at least in part on the runtime privileges and a runtime factor.

11. The non-transitory computer-readable storage memory of claim 10, wherein the runtime factor includes at least one of a time, a locality, a client, a number of requests, or a privilege granted to the first user.

12. The non-transitory computer-readable storage memory of claim 9, wherein the at least one secure network resource is a privileged account of a privileged access management service.

13. The non-transitory computer-readable storage memory of claim 12, wherein a privileged access management service is implemented by a first virtual machine and a plug-in framework is implemented by a second virtual machine.

14. The non-transitory computer-readable storage memory of claim 13, wherein the second virtual machine is sandboxed and separated from the first virtual machine.

15. The non-transitory computer-readable storage memory of claim 13, wherein the plug-in framework is implemented to determine whether the first user is allowed to perform the action by further implementing the plurality of instructions to:

transmit the request to perform the action to the second virtual machine;

instruct the second virtual machine to execute the plug-in code;

receive, from the second virtual machine, a result of executing the plug-in code; and

process the result to perform the action if it is determined, by the plug-in code, that the first user is allowed to perform the action.

16. A computer-implemented method, comprising:

receiving, by a computer system, plug-in code for implementing runtime privileges;

receiving, from a first user, a log-in request to start a session, the log-in request including at least first authentication information;

establishing the session for the first user; and

during the session;

receiving, from a computing device of the first user, a request to perform an action associated with at least one secure network resource; and

performing, by the computer system, the action for the first user based at least in part on a second user being authenticated and being logged in to share the session with the first user.

17. The computer-implemented method of 16, wherein the at least one secure network resource is a privileged account of a privileged access management service.

18. The computer-implemented method of 17, wherein the runtime factor includes at least one of a time, a locality, a client, a number of requests, or a privilege granted to the first user.

19. The computer-implemented method of 17, wherein the privileged access management service is implemented by a first virtual machine and a plug-in framework is implemented by a second virtual machine.

20. The computer-implemented method of claim 19, wherein the second virtual machine is sandboxed and separated from the first virtual machine.