TECHNIQUES FOR AUTOMATIC DISCOVERY AND UPDATE OF CLIENT ENVIRONMENTAL INFORMATION IN A VIRTUAL PRIVATE NETWORK (VPN)

• US 20090228973A1
• Filed: 03/06/2008
• Published: 09/10/2009
• Est. Priority Date: 03/06/2008
• Status: Abandoned Application

• Current Assignee: EMC Corporation (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Sureshkumar, T., Kumar, Chendil
• Application Number:
  US12/043,187
• Publication Number:
  US 20090228973A1
• Time in Patent Office: Days
• US Class Current: 726/15
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 63/145 the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms

Abstract

Techniques for automatic discovery and update of client environmental information in a virtual private network (VPN) are provided. Vendor adapters dynamically monitor information produced by software vendors for change information associated with software products. The change information is transformed into policy rules that are dynamically pushed to client agents on clients. The client agents acquire client information for the policy rules from their clients and report back to a VPN server. The VPN server in cooperation with the client agents then decide whether VPN sessions are permissible between the clients and the VPN server.

Claims

1. A machine-implemented method, comprising:

monitoring a third-party vendor for information on a software product;

parsing the information from the third-party vendor to detect an update to the software product;

constructing a policy rule for the update; and

updating a policy store for the policy rule, wherein the policy rule is subsequently pushed to an agent on a client during initial virtual private network (VPN) negotiation for the agent to gather client information relating to the policy rule and report that client information back to a VPN connection manager during the VPN negotiation.

2. The method of claim 1, wherein monitoring further includes using a really simple syndication (RSS) feed reader to acquire the information from the vendor.

3. The method of claim 1, wherein monitoring further includes monitoring an email client for an email from the third-party vendor and using a subject and content associated with the email as the information.

4. The method of claim 1, wherein monitoring further includes automatically scraping a world-wide web (WWW) site of the third-party vendor to acquire the information.

5. The method of claim 1, wherein parsing further includes, acquiring from the information an identifier for an operating system (OS) associated with the software product, identifiers for other software affected by the software product, a version number associated with the software product, and a location to look for the software product on the client.

6. The method of claim 1, wherein constructing further includes checking the policy store to determine when the policy rule is inclusive of another existing rule, when the policy rule is a duplicate of an existing rule or when the policy rule is a new rule.

7. The method of claim 1 further comprising, automatically sending a notification to an administrator to check the policy rule.

8. A machine-implemented method, comprising:

dynamically pushing updated configuration information to an agent on a client during initial virtual private network (VPN) negotiation for a VPN session between the client and a server, wherein the updated configuration information identifies client information that the agent is to check for and report back on during the VPN negotiation between the client and the server; and

evaluating the client information returned from the agent to determine whether a software environment of the client permits creation of the VPN session and when it does creating the VPN session for the client and when it does not denying the creation of the VPN session.

9. The method of claim 8 further comprising, dynamically receiving the updated configuration information via a third-party agent that dynamically identifies changes to a software product from a third-party vendor.

10. The method of claim 8, wherein dynamically pushing further includes receiving the updated configuration information from a really simple syndication (RSS) feed for a third-party software product and having the updated configuration information confirmed by an administrator for delivery and enforcement by the agent.

11. The method of claim 8, wherein dynamically pushing further includes acquiring the updated configuration information in response to a detection in a policy store that policy rules were altered, wherein the altered policy rules are the updated configuration information that is dynamically pushed to the client.

12. The method of claim 8, wherein dynamically pushing further includes representing the configuration information as identifying a specific software product for a specific operating system and having a specific version number, and wherein the configuration information further identifies a directory location on the client where the configuration information can be verified by the agent.

13. The method of claim 8, wherein evaluating further includes instructing the agent to deny creation of the VPN session when the evaluation of the client information does not comport with a policy rule.

14. The method of claim 8, wherein evaluating further includes instructing the agent to create the VPN session when the evaluation of the client information comports with a policy rule.

15. A machine-implemented system, comprising:

a policy enforcer implemented in a machine-accessible and computer-readable medium on a server machine of a network; and

a vendor plugin adapter implemented in a machine-accessible and computer-readable medium on the server machine or another machine of the network;

wherein the vendor plugin adapter dynamically and in real time monitors a vendor for changes to a software product distributed by the vendor, and wherein when a change is detected, the vendor plugin adapter gathers change information for the software product and produces a policy rule that is communicated to the policy enforcer, the policy enforcer then dynamically and in real time pushes the policy rule to a client agent during a virtual private network (VPN) negotiation between the a client and a server, the client agent gathers information for the software product on the client in accordance with the policy rule and returns it to the policy enforcer, the policy enforcer then instructs the client agent whether it is permissible or not permissible for a VPN session to be established between the client and the server.

16. The system of claim 15 further comprising, a policy manager implemented in a machine-accessible and computer-readable medium and to process on the server machine, wherein the policy manager provides an administrative interface for an administrator to create, view, modify, and delete the policy rule or other policy rules that are enforced by the policy enforcer.

17. The system of claim 16 further comprising, a policy store implemented in a machine-accessible and computer-readable medium and accessible to the policy enforcer and the vendor plugin adapter, and wherein the vendor plugin adapter is to store the policy rule in the policy store where it is communicated and acquired by the policy enforcer.

18. The system of claim 17, wherein the vendor plugin adapter determines when storing the policy rule in the policy store whether the policy rule is included within an existing policy rule as a portion of that existing policy rule or whether the policy rule is an entirely new policy rule.

19. The system of claim 17, wherein the policy rule is initially inactive or in a passive state within the policy store until the administrator, via the policy manager, activates the policy rule at which time it is immediately communicated from the policy store to the policy enforcer.

20. The system of claim 17, wherein the policy manager is used by the administrator to initially configure the vendor plugin adapter for monitoring information produced by the vendor for the software product.

21. A machine-implemented system, comprising:

a virtual private network (VPN) server implemented in a machine-accessible and computer-readable medium and to process on a server machine of a network; and

a client agent implemented in a machine-accessible and computer-readable medium and to process on a client machine of the network;

wherein the VPN server interacts with one or more vendor adapters, each vendor adapter dynamically and in real time monitors a particular software vendor for information on changes to software products distributed by that particular software vendor, each vendor adapter also produces new or updated policy rules that are communicated to the VPN sever, the VPN server pushes the new or updated policy rules to the client agent, the client agent gathers client information that comports with the new or updated policy rules during VPN negotiation between the client machine and the server machine and supplies the client information back to the VPN server, the VPN server then instructs the client agent to permit or deny the creation of a VPN session between the client machine and the server machine in response to evaluation of the client information.

22. The system of claim 21, wherein the client agent during the VPN negotiation scans the client machine for antivirus software, operating system patches, patches for installed programs on the client machine, and for the presence of malware on the client machine in response to the new or updated policy rules delivered by the VPN server during the VPN negotiation.

23. The system of claim 21, wherein the client agent is preinstalled on the client machine before the VPN negotiation takes place.

24. The system of claim 21, wherein the VPN server dynamically delivers and installs the client agent on the client machine during initial configuration of the VPN negotiation.

25. The system of claim 21, wherein at least one vendor adapter is configured to evaluate really simple syndication (RSS) feeds from one of the software vendors, and wherein another of the vendor adapters is configured to scrape a world-wide web (WWW) site for another one of the software vendors, and wherein still another of the vendor adapters is configured to parse an email received from yet another one of the software vendors for purposes of acquiring the information on the changes to the software products.