METHOD AND APPARATUS FOR PROVIDING HETEROGENEOUS SECURITY MANAGEMENT

• US 20110239270A1
• Filed: 03/25/2011
• Published: 09/29/2011
• Est. Priority Date: 03/26/2010
• Status: Abandoned Application

• Current Assignee: Nokia Technologies Oy (Nokia Corporation)
• Original Assignee: Nokia Corporation
• Inventors: Terho, Mikko Juhani, Sovio, Sampo Juhani
• Application Number:
  US13/072,140
• Publication Number:
  US 20110239270A1
• Time in Patent Office: Days
• US Class Current: 726/1
• CPC Class Codes: G06F 21/6236 between heterogeneous systems
• 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/104 Grouping of entities
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04W 4/60 Subscription-based services using application servers or record carriers, e.g. SIM application toolkits

Abstract

An approach is provided for providing a heterogeneous security management platform to combine or integrate different applications employing different security requirements. An interface acts on a request that references, at least in part, a resource, the resource associated with a network identifier. The interface determines whether the network identifier is listed in a secure phonebook. The secure phonebook associates the network identifier with, at least in part, a security context. The interface provides the security context for one or more applications, scripts, executables, or combination thereof to determine access privileges to the resource based, at least in part, on the determination.

Claims

1. A method comprising:

acting on a request that references, at least in part, a resource, the resource associated with a network identifier;

determining whether the network identifier is listed in a secure phonebook, the secure phonebook associating the network identifier with, at least in part, a security context; and

providing the security context for one or more applications, scripts, executables, or combination thereof to determine access privileges to the resource based, at least in part, on the determination.

2. A method of claim 1, wherein the secure phonebook further associates the network identifier with one or more system policies, the method further comprising:

causing, at least in part, enforcement of the system policies for access to the resource.

3. A method of claim 2, further comprising:

causing, at least in part, pre-authentication of access to the resource according to at least one of the system policies;

receiving another request to access the resource; and

causing, at least in part, use of the pre-authentication for a subsequent authentication challenge associated with the resource.

4. A method of claim 2, wherein the resource shares at least one common component with another resource, the method further comprising:

determining whether a first system policy of the at least one common component has been changed with respect to the resource;

causing, at least in part, presentation of a prompt requesting an update of a second system policy of the at least one common component with respect to the another resource based, at least in part, on the determination with respect to the first system policy;

receiving a response to the prompt; and

causing, at least in part, the update of the second system policy of the at least one common component based, at least in part, on the response.

5. A method of claim 1, further comprising:

receiving another request to grant access to the resource to one or more users;

generating one or more authentication tokens based at least in part on unique credentials associated with the respective users; and

causing, at least in part, transmission of the tokens to the resource,

wherein the resource uses the tokens to automatically authenticate access to the resource by the users.

6. A method of claim 1, wherein the network identifier is not listed in the secure phonebook, the method further comprising:

providing a default security context for the applications, scripts, executables or combination thereof to access the resource.

7. A method of claim 1, wherein the resource is part of a network whose components are associated with a respective unique network identifier, the network identifier including, at least in part, a fully qualified domain name.

8. A method of claim 1, wherein the security context is unique to the resource.

9. An apparatus comprising:

at least one processor; and

at least one memory including computer program code,

the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following,

act on a request that references, at least in part, a resource, the resource associated with a network identifier;

determine whether the network identifier is listed in a secure phonebook, the secure phonebook associating the network identifier with, at least in part, a security context; and

provide the security context for one or more applications, scripts, executables, or combination thereof to determine access privileges to the resource based, at least in part, on the determination.

10. An apparatus of claim 9, wherein the secure phonebook further associates the network identifier with one or more system policies, and wherein the apparatus is further caused to:

cause, at least in part, enforcement of the system policies for access to the resource.

11. An apparatus of claim 10, wherein the apparatus is further caused to:

cause, at least in part, pre-authentication of access to the resource according to at least one of the system policies;

receive another request to access the resource; and

cause, at least in part, use of the pre-authentication for a subsequent authentication challenge associated with the resource.

12. An apparatus of claim 10, wherein the resource shares at least one common component with another resource, and wherein the apparatus is further caused to:

determine whether a first system policy of the at least one common component has been changed with respect to the resource;

cause, at least in part, presentation of a prompt requesting an update of a second system policy of the at least one common component with respect to the another resource based, at least in part, on the determination with respect to the first system policy;

receive a response to the prompt; and

cause, at least in part, the update of the second system policy of the at least one common component based, at least in part, on the response.

13. An apparatus of claim 9, wherein the apparatus is further caused to:

receive another request to grant access to the resource to one or more users;

generate one or more authentication tokens based at least in part on unique credentials associated with the respective users; and

cause, at least in part, transmission of the tokens to the resource,

wherein the resource uses the tokens to automatically authenticate access to the resource by the users.

14. An apparatus of claim 9, wherein the network identifier is not listed in the secure phonebook, and wherein the apparatus is further caused to:

provide a default security context for the applications, scripts, executables or combination thereof to access the resource.

15. An apparatus of claim 9, wherein the resource is part of a network whose components are associated with a respective unique network identifier, the network identifier including, at least in part, a fully qualified domain name.

16. An apparatus of claim 9, wherein the security context is unique to the resource.

17. A computer-readable storage medium carrying one or more sequences of one or more instructions which, when executed by one or more processors, cause an apparatus to at least perform the following steps:

acting on a request that references, at least in part, a resource, the resource associated with a network identifier;

determining whether the network identifier is listed in a secure phonebook, the secure phonebook associating the network identifier with, at least in part, a security context; and

providing the security context for one or more applications, scripts, executables, or combination thereof to determine access privileges to the resource based, at least in part, on the determination.

18. A computer-readable storage medium of claim 17, wherein the secure phonebook further associates the network identifier with one or more system policies, and wherein the apparatus is caused to further perform:

causing, at least in part, enforcement of the system policies for access to the resource.

19. A computer-readable storage medium of claim 18, wherein the apparatus is caused to further perform:

causing, at least in part, pre-authentication of access to the resource according to at least one of the system policies;

receiving another request to access the resource; and

causing, at least in part, use of the pre-authentication for a subsequent authentication challenge associated with the resource.

20. A computer-readable storage medium of claim 17, wherein the apparatus is caused to further perform:

receiving another request to grant access to the resource to one or more users;

generating one or more authentication tokens based at least in part on unique credentials associated with the respective users; and

causing, at least in part, transmission of the tokens to the resource,

wherein the resource uses the tokens to automatically authenticate access to the resource by the users.