As computer networks have grown in size, an initial focus on connectivity has been tempered by security concerns. For example, unrestricted flow of data traffic to a network containing a server computer hosting a public information facility can compromise the facility, the server and/or other computers connected to the network. Network firewalls have become a relatively common mechanism for addressing at least some such security concerns. In a typical configuration, a conventional network firewall interrupts a network connection, and allows data traffic to flow across the interruption in accordance with a set of rules. For example, the rules may allow or deny data traffic addressed to particular computers that are behind the firewall, and/or allow or deny data traffic in accordance with particular communication protocols. However, conventional network firewalls have some problematic limitations.
Increasingly, network facilities are implemented with computing infrastructure, such as computing hardware, that is not under the direct control of the facility provider. For example, an Internet Web site maintained by a facility provider may be implemented, at least in part, with a data object storage service purchased on a commodity basis (e.g., per gigabyte stored and/or transferred) from a vendor of such computing services. Such computing services may be implemented with various collections of computers and network elements that are allocated to multiple customers (“tenants”) in accordance with service supply contracts and/or varying demand. Tenants need not be aware of which particular computers and/or network elements are allocated to implement their computing services, and this is generally regarded as a benefit. However, difficulties arise when attempting to use conventional firewalls with multi-tenant computing services. For example, rules established by one tenant at a conventional firewall protecting a multi-tenant distributed computing service can affect other tenants of the service.
Various embodiments in accordance with the present disclosure will be described with reference to the drawings, in which:
Same numbers are used throughout the disclosure and figures to reference like components and features, but such repetition of number is for purposes of simplicity of explanation and understanding, and should not be viewed as a limitation on the various embodiments.
In the following description, various embodiments will be described. For purposes of explanation, specific configurations and details are set forth in order to provide a thorough understanding of the embodiments. However, it will also be apparent to one skilled in the art that the embodiments may be practiced without the specific details. Furthermore, well-known features may be omitted or simplified in order not to obscure the embodiment being described.
In at least one embodiment, virtual firewalls are established that enforce sets of policies with respect to computing resources maintained by multi-tenant distributed services. Computing resources, such as data object stores, may be maintained by services implemented by (i.e., distributed across) multiple server computers. Particular subsets of computing resources may be associated with particular tenants of a multi-tenant distributed service. A tenant may establish a firewalling policy set enforced by a virtual firewall for an associated subset of computing resources without affecting other tenants of the multi-tenant distributed service and/or other virtual firewalls protecting other subsets of computing resources maintained by the multi-tenant distributed service.
Virtual firewalls enforcing multiple firewalling policy sets may be maintained by a common firewalling component (i.e., a common firewalling policy enforcement component) of the multi-tenant distributed service. Firewalling policy sets may be distributed at multiple locations throughout the multi-tenant distributed service, for example, some firewalling policies may be maintained local to associated computing resources, and some firewalling policies may be maintained local to an identity authentication service. Firewalling policies may be cached local to the common firewalling component, and updated responsive to policy update notifications. For a request targeting a particular computing resource, the common firewalling component may identify the associated firewalling policy set and/or enforcing virtual firewall, and submit the request to the virtual firewall for evaluation in accordance with the firewalling policy set.
Various approaches may be implemented in various environments for various applications. For example,
The network 104 may include any appropriate network, including an intranet, the Internet, a cellular network, a local area network, a wide area network, a wireless data network, or any other such network or combination thereof. Components utilized for such a system may depend at least in part upon the type of network and/or environment selected. Protocols and components for communicating via such a network are well known and will not be discussed herein in detail. Communication over the network may be enabled by wired or wireless connections, and combinations thereof. In this example, the network 104 includes the Internet, as the environment includes a Web server 106 for receiving requests and serving content in response thereto, although for other networks an alternative device serving a similar purpose could be utilized as would be apparent to one of ordinary skill in the art.
The illustrative environment 100 includes at least one application server 108 and a data store 110. It should be understood that there may be several application servers, layers, or other elements, processes, or components, which may be chained or otherwise configured, which may interact to perform tasks such as obtaining data from an appropriate data store. As used herein the term “data store” refers to any device or combination of devices capable of storing, accessing, and/or retrieving data, which may include any combination and number of data servers, databases, data storage devices, and data storage media, in any standard, distributed, or clustered environment.
The application server 108 may include any appropriate hardware and software for integrating with the data store as needed to execute aspects of one or more applications for the client device 102, and may even handle a majority of the data access and business logic for an application. The application server 108 provides access control services in cooperation with the data store 110, and is able to generate content such as text, graphics, audio, and/or video to be transferred to the user, which may be served to the user by the Web server 106 in the form of HTML, XML, or another appropriate structured language in this example.
The handling of all requests and responses, as well as the delivery of content between the client device 102 and the application server 108, may be handled by the Web server 106. It should be understood that the Web and application servers 106, 108 are not required and are merely example components, as structured code discussed herein may be executed on any appropriate device or host machine as discussed elsewhere herein. Further, the environment 100 may be architected in such a way that a test automation framework may be provided as a service to which a user or application may subscribe. A test automation framework may be provided as an implementation of any of the various testing patterns discussed herein, although various other implementations may be utilized as well, as discussed or suggested herein.
The environment 100 may also include a development and/or testing side, which includes a user device 118 allowing a user such as a developer, data administrator, or tester to access the system. The user device 118 may be any appropriate device or machine, such as is described above with respect to the client device 102. The environment 100 may also include a development server 120, which functions similar to the application server 108 but typically runs code during development and testing before the code is deployed and executed on the production side and becomes accessible to outside users, for example. In some embodiments, an application server may function as a development server, and separate production and testing storage may not be utilized.
The data store 110 may include several separate data tables, databases, or other data storage mechanisms and media for storing data relating to a particular aspect. For example, the data store 110 illustrated includes mechanisms for storing production data 112 and user information 116, which may be utilized to serve content for the production side. The data store 110 also is shown to include a mechanism for storing testing data 114, which may be utilized with the user information for the testing side. It should be understood that there may be many other aspects that are stored in the data store 110, such as for page image information and access right information, which may be stored in any of the above listed mechanisms as appropriate or in additional mechanisms in the data store 110.
The data store 110 is operable, through logic associated therewith, to receive instructions from the application server 108 or development server 120, and obtain, update, or otherwise process data in response thereto. In one example, a user might submit a search request for a certain type of item. In this case, the data store 110 might access the user information 116 to verify the identity of the user, and may access the catalog detail information to obtain information about items of that type. The information then may be returned to the user, such as in a results listing on a Web page that the user is able to view via a browser on the user device 102. Information for a particular item of interest may be viewed in a dedicated page or window of the browser.
Each server typically will include an operating system that provides executable program instructions for the general administration and operation of that server, and typically will include a computer-readable medium storing instructions that, when executed by a processor of the server, allow the server to perform its intended functions. Suitable implementations for the operating system and general functionality of the servers are known or commercially available, and are readily implemented by persons having ordinary skill in the art, particularly in light of the disclosure herein.
The environment 100 in one embodiment is a distributed computing environment utilizing several computer systems and components that are interconnected via communication links, using one or more computer networks or direct connections. However, it will be appreciated by those of ordinary skill in the art that such a system could operate equally well in a system having fewer or a greater number of components than are illustrated in
In at least one embodiment, one or more aspects of the environment 100 may incorporate and/or be incorporated into a computing resource services architecture.
The computing resource provider 202 may be implemented, at least in part, with server computers such as the Web server 106 and the application server 108 described above with reference to
Authorized clients (e.g., among the clients 204, 206) may interact with a resource policy interface 226 of the control plane 218 to specify resource policies, including firewalling policies, with respect to sets of the computing resources 208, 210, 212. A firewalling component 228 of the control plane 218 may enforce the resource policies specified with the resource policy interface 226 to maintain virtual firewalls 230, 232 around the computing resources 208, 210, 212. In the example depicted in
The computing resources 208, 210, 212 may include any computing resources suitable for provisioning to customers of the computing resource provider 202. Such customers may include the computing resource provider 202 itself. Examples of suitable computing resources include data object stores including block data stores such as virtual file volumes, data processing agents including programs, programming language interpreters, and virtual machines, and suitable combinations and configurations thereof. An example resource interface in accordance with at least one embodiment is described below in more detail with reference to
The provisioning interface 220 may include any suitable provisioning interface elements. Examples of suitable provisioning interface elements include interface elements that provision, configure, reconfigured and/or de-provision the computing resources 208, 210, 212, as well as interface elements that provide access to computing resource configuration information, and one or more interface elements enabling authentication to establish authority for such provisioning-related operations. The provisioning interface 220 may incorporate and/or be incorporated in a user interface (UI) such as a graphical user interface (GUI), a Web-based interface, a programmatic interface such as an application programming interface (API) and/or a set of remote procedure calls (RPCs) corresponding to provisioning interface elements, a messaging interface such as a messaging interface in which the interface elements of the provisioning interface 220 correspond to messages of a communication protocol, and/or any suitable combination thereof. In at least one embodiment, the provisioning interface 220 for one or more of the provisioned resource types is incorporated into its corresponding resource interface 222-224.
The resource policy interface 226 may include any suitable resource policy interface elements. Examples of suitable resource policy interface elements include interface elements that create, read, update and/or delete resource policies. As for the provisioning interface 220, the resource policy interface 226 may incorporate and/or be incorporated in a user interface (UI) such as a graphical user interface (GUI), a Web-based interface, a programmatic interface such as an application programming interface (API) and/or a set of remote procedure calls (RPCs) corresponding to resource policy interface elements, a messaging interface such as a messaging interface in which the interface elements of the resource policy interface 226 correspond to messages of a communication protocol, and/or any suitable combination thereof. An example firewalling component 228 in accordance with at least one embodiment is described below in more detail with reference to
The depiction of the computing resource provider 202 in
The ellipsis between the multi-tenant distributed services 304 and 306 indicates that the computing resource provider 302 may include any suitable number of multi-tenant distributed services, including a single multi-tenant distributed service. The computing resource provider 302 may include a multi-tenant distributed service 304, 306 for each type of provisioned computing resource 208, 210, 212 (
The policy management service 308 may manage resource policies, including firewalling policies, for the computing resource provider 302. The policy management service 308 may include a resource policy interface 332. The resource policy interface 332 is an example of the resource policy interface 226 of
Tenants of the multi-tenant distributed services 304-306 may correspond to authoritative service accounts with the computing resource provider. For example, tenants may be responsible for costs associated with maintaining the provisioned computing resources 322-328. Tenants may delegate various authorities to users of the provisioned computing resources 322-328, including authority to set resource policies 336-342 with respect to the provisioned computing resources 322-328.
Resource policies 334-344 may reference a set of the provisioned computing resources 322-328, a set of actions that may be performed with respect to the set of the provisioned computing resources 322-328, and a set of conditions to be satisfied before the set of actions are permitted. The set of actions may include any suitable action that may be performed with respect to the set of the provisioned computing resources 322-328. For example, the actions may correspond to elements of a programmatic and/or messaging interface as described below in more detail with reference to
The set of conditions may include any conditions suitable for controlling performance of the set of actions. Examples of suitable condition parameters include parameters associated with a request to perform one or more of the set of actions such as physical layer, data link layer, network layer, transport layer, session layer, presentation layer and/or application layer communication parameters in accordance with an International Standards Organization (ISO) model for open systems interconnection, e.g., the OSI reference model as described by Hubert Zimmermann, “OSI Reference Model—The ISO Model of Architecture for Open Systems Interconnection,” IEEE Transactions on Communications, April 1980. Such condition parameters include originating network address, one or more protocols associated with the request, whether the protocol utilized an internet protocol or a particular type of internet protocol such as IPv6, IPSec, whether the protocol is encrypted such as with a secure socket layer (e.g., SSL), a virtual private network (VPN), a time, time period and/or type of time period associated with the request such as time of day, an identity of the client 204-206 originating the request such as the user-agent string of an Internet browser. Further examples of suitable condition parameters include operating environment parameters such as the current time according to one or more clocks, originating geographical location, originating political and/or administrative division, authenticated provisioned computing resources 322-328 user originating the request and/or type of authentication utilized to authenticate the user, tenant-defined security boundaries corresponding to sets of provisioned computing resources 322-328, whether the request originated from within or external to the computing resource provider 302 including whether the request originated from a particular multi-tenant distributed service 304-306, and suitable combinations thereof.
At times, actions performed in response to requests may result in a transfer of data from the provisioned computing resources 322-328. Examples of suitable condition parameters further include parameters associated with destinations of such data transfers including destination network address, geographical location, political and/or administrative division, authenticated user receiving the transfer, whether the destination is external to the virtual private network (VPN) or other security boundary associated with the request including tenant-defined security boundaries corresponding to sets of provisioned computing resources 322-328, whether the destination is external to the computing resource provider 302 including whether the request originated from a particular multi-tenant distributed service 304-306, and suitable combinations thereof. In at least one embodiment, the ability to enforce firewalling policies based at least in part on such condition parameters facilitates extension of virtual private networks to virtual private clouds (VPCs) incorporating virtual private networks and corresponding sets of provisioned computing resources 208-212 (
One or more conditions in the set of conditions may explicitly permit the set of actions when a set of condition parameters take on a specified set of values, and/or when the set of condition parameters takes on values other than the specified set of values. One or more conditions may explicitly deny the set of actions when the set of condition parameters takes on the specified set of values and/or values other than the specified set of values. Wildcards may be utilized to specify the set of value, including wildcards that correspond to all possible values. Conditions in the set of conditions may be combined with Boolean operators. The firewalling component 228 may maintain a default and/or global meta-policy requiring a policy that grants explicit permission for an action and the absence of a policy that explicitly denies the action before allowing the action to occur.
For example, the provisioned computing resource 322 may have an associated firewalling policy 336 specifying that the provisioned computing resource 322 may only be accessed from a specified set of internet protocol (IP) addresses, or a specified set of geographic locations. As another example, the provisioned computing resource 324 may have an associated firewalling policy 338 specifying that the provisioned computing resource 324 may not, in response to a request, provide data over unsecured connections through the network 214 (
The authentication service 310 may provide authentication services for the computing resource provider 302. For example, the authentication service 310 may authenticate an integrity and/or an authenticity of resource policies 334, 336, 338, 340, 342, 344. In addition, the authentication service 310 may authenticate an identity of clients 204, 206, tenants and/or users of the computing resource provider 302. For example, the resource policy interface 332 and/or the resource interfaces 318, 320 may utilize the authentication service 310 to establish and/or verify an identify and/or authority of a user with respect to resource policies 334, 336, 338, 340, 342, 344 and/or computing resources 322, 324, 326, 328. The authentication service 310 may utilize any suitable authentication mechanism, including any suitable cryptographic authentication mechanism, to provide the authentication services. Such authentication mechanisms are well known in the art and need not be detailed here.
Computing resources 322, 324, 326, 328 maintained by the computing resource provider 302 may be associated with various labeling and/or naming schemes (“resource names”). Such resource names may be particular to the computing resource provider 302 and/or in accordance with a resource naming standard such the Uniform Resource Name (URN) standard described by Ryan Moats, “URN Syntax”, Internet Engineering Task Force (IETF) Request for Comments (RFC) 2141, May 1997. The resource name resolution service 312 of the computing resource provider 302 may map such resource names to computing resource 322, 324, 326, 328 locations within the computing resource provider 302. For example, the resource name resolution service 312 may map resource names to the appropriate multi-tenant distributed service 304, 306, particular server computers (not shown in
Resource policies 334, 336, 338, 340, 342, 344 may reference geographic locations and/or regions (collectively, “geographic locations”) such as countries, states, cities, geographic regions defined by laws, geographic regions defined by physical co-ordinates, geographic regions defined by any suitable attribute(s) of the geographic regions, and suitable combinations thereof. The geographic location mapping service 314 may associate one or more such geographic locations with incoming requests to and/or outgoing request responses from the resource interfaces 318, 320 and/or the resource policy interface 332. For example, the geographic location mapping service 314 may base such geographic location associations on one or more attributes of the request and/or response and/or on associated context information such as origin and/or destination network address (e.g., in the network 214 of
Each multi-tenant distributed service 304, 306 may be implemented with a collection of server computers and/or network elements.
Each resource server 404, 406 may include a node manager 412, 414. The node managers 412, 414 may co-operate with each other and/or with one or more additional supervisory servers (not shown in
Similarly, each resource server 404, 406 may maintain a subset of the resource policies 336, 338 (
The interface server(s) 408 may (collectively) maintain a resource interface 432 and a firewalling component 434. The resource interface 432 of
Clients 204-206 (
Some provisioned computing resources 322-324 (
Authorization of clients 204-206 (
The firewalling component 602 may include a policy collector 604 configured at least to collect relevant resource policies from maintenance locations throughout the computing resource provider 302 (
The policy collector 604 may periodically search for updates to firewalling policies stored in the policy cache 608. Alternatively, or in addition, the policy collector 604 may receive notifications of firewalling policy updates. The decision data collector(s) 610 may include a resource name data collector configured to interact with the resource name resolution service 312 (
The description now turns to example procedures that may be performed by the computing resource provider 202 (
At step 704, one or more sets of resource policies may be established with respect to the one or more computing resources provisioned at step 702. For example, the resource policies 334 (
At step 706, a request may be received with respect to one of the computing resources provisioned at step 702. For example, one of the clients 204-206 (
At step 714, the virtual firewall may determine whether to permit the request or else to deny the request. For example, the decision to permit or else deny the request may be based on the evaluation made by the decision engine 606 (
Virtual firewalls 230-232 (
At step 806, it may be determined whether to update a local cache based at least in part on the policy set update notification. For example, the firewalling component 602 (
The policy set update notification may include details of the policy set update. For example, the policy set update notification may include a copy of new firewalling policies to be enforced. Alternatively, or in addition, the policy set update notification may simply reference an updated policy set. In this case, additional steps may be required to obtain policy update details. At step 808, resource policy update details may be requested. For example, the firewalling component 602 (
Requests with respect to provisioned computing resources 208-212 (
At step 906, relevant resource policies detected at step 902 may be extracted and/or parsed from the request. For example, the policy collector 604 (
The resource interfaces 222-224 (
At step 1006, a set of decision data required by the resource policy set identified at step 1004 may be determined. For example, the decision engine 606 (
At step 1010, the required decision data update(s) may be requested. For example, the decision data collector(s) 610 (
At step 1012, the request may be evaluated based at least in part on the resource policy set obtained at step 1004 and the decision data set determined at step 1006. For example, the decision engine 606 (
The various embodiments described herein may be implemented in a wide variety of operating environments, which in some cases may include one or more user computers, computing devices, or processing devices which may be utilized to operate any of a number of applications. User or client devices may include any of a number of general purpose personal computers, such as desktop or laptop computers running a standard operating system, as well as cellular, wireless, and handheld devices running mobile software and capable of supporting a number of networking and messaging protocols. Such a system also may include a number of workstations running any of a variety of commercially-available operating systems and other known applications for purposes such as development and database management. These devices also may include other electronic devices, such as dummy terminals, thin-clients, gaming systems, and other devices capable of communicating via a network.
Most embodiments utilize at least one network that would be familiar to those skilled in the art for supporting communications using any of a variety of commercially-available protocols, such as TCP/IP, OSI, FTP, UPnP, NFS, CIFS, and AppleTalk. Such a network may include, for example, a local area network, a wide-area network, a virtual private network, the Internet, an intranet, an extranet, a public switched telephone network, an infrared network, a wireless network, and any combination thereof. The network may, furthermore, incorporate any suitable network topology. Examples of suitable network topologies include, but are not limited to, simple point-to-point, star topology, self organizing peer-to-peer topologies, and combinations thereof.
In embodiments utilizing a Web server, the Web server may run any of a variety of server or mid-tier applications, including HTTP servers, FTP servers, CGI servers, data servers, Java servers, and business application servers. The server(s) also may be capable of executing programs or scripts in response requests from user devices, such as by executing one or more Web applications that may be implemented as one or more scripts or programs written in any programming language, such as Java®, C, C# or C++, or any scripting language, such as Perl, Python, or TCL, as well as combinations thereof. The server(s) may also include database servers, including without limitation those commercially available from Oracle®, Microsoft®, Sybase®, and IBM®.
The environment may include a variety of data stores and other memory and storage media as discussed above. These may reside in a variety of locations, such as on a storage medium local to (and/or resident in) one or more of the computers or remote from any or all of the computers across the network. In a particular set of embodiments, the information may reside in a storage-area network (“SAN”) familiar to those skilled in the art. Similarly, any necessary files for performing the functions attributed to the computers, servers, or other network devices may be stored locally and/or remotely, as appropriate. Where a system includes computerized devices, each such device may include hardware elements that may be electrically coupled via a bus, the elements including, for example, at least one central processing unit (CPU), at least one input device (e.g., a mouse, keyboard, controller, touch screen, or keypad), and at least one output device (e.g., a display device, printer, or speaker). Such a system may also include one or more storage devices, such as disk drives, optical storage devices, and solid-state storage devices such as random access memory (“RAM”) or read-only memory (“ROM”), as well as removable media devices, memory cards, flash cards, etc.
Such devices also may include a computer-readable storage media reader, a communications device (e.g., a modem, a network card (wireless or wired), an infrared communication device, etc.), and working memory as described above. The computer-readable storage media reader may be connected with, or configured to receive, a computer-readable storage medium, representing remote, local, fixed, and/or removable storage devices as well as storage media for temporarily and/or more permanently containing, storing, transmitting, and retrieving computer-readable information. The system and various devices also typically will include a number of software applications, modules including program modules, services, or other elements located within at least one working memory device, including an operating system and application programs, such as a client application or Web browser. It should be appreciated that alternate embodiments may have numerous variations from that described above. For example, customized hardware might also be utilized and/or particular elements might be implemented in hardware, software (including portable software, such as applets), or both. Further, connection to other computing devices such as network input/output devices may be employed.
Storage media and computer readable media for containing code, or portions of code, may include any appropriate media known or used in the art, including storage media and communication media, such as but not limited to volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage and/or transmission of information such as computer readable instructions, data structures, program modules, or other data, including RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which may be utilized to store the desired information and which may be accessed by the a system device. Program modules, program components and/or programmatic objects may include computer-readable and/or computer-executable instructions of and/or corresponding to any suitable computer programming language. In at least one embodiment, each computer-readable medium may be tangible. In at least one embodiment, each computer-readable medium may be non-transitory in time. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will appreciate other ways and/or methods to implement the various embodiments.
The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. It will, however, be evident that various modifications and changes may be made thereunto without departing from the broader spirit and scope of the invention as set forth in the claims.
The use of the terms “a” and “an” and “the” and similar referents in the context of describing embodiments (especially in the context of the following claims) are to be construed to cover both the singular and the plural, unless otherwise indicated herein or clearly contradicted by context. The terms “comprising,” “having,” “including,” and “containing” are to be construed as open-ended terms (i.e., meaning “including, but not limited to,”) unless otherwise noted. The term “connected” is to be construed as partly or wholly contained within, attached to, or joined together, even if there is something intervening. Recitation of ranges of values herein are merely intended to serve as a shorthand method of referring individually to each separate value falling within the range, unless otherwise indicated herein, and each separate value is incorporated into the specification as if it were individually recited herein. All methods described herein can be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. The use of any and all examples, or exemplary language (e.g., “such as”) provided herein, is intended merely to better illuminate embodiments and does not pose a limitation on the scope unless otherwise claimed. No language in the specification should be construed as indicating any non-claimed element as essential to the practice of at least one embodiment.
Preferred embodiments are described herein, including the best mode known to the inventors. Variations of those preferred embodiments may become apparent to those of ordinary skill in the art upon reading the foregoing description. The inventors expect skilled artisans to employ such variations as appropriate, and the inventors intend for embodiments to be constructed otherwise than as specifically described herein. Accordingly, suitable embodiments include all modifications and equivalents of the subject matter recited in the claims appended hereto as permitted by applicable law. Moreover, any combination of the above-described elements in all possible variations thereof is contemplated as being incorporated into some suitable embodiment unless otherwise indicated herein or otherwise clearly contradicted by context.
All references, including publications, patent applications, and patents, cited herein are hereby incorporated by reference to the same extent as if each reference were individually and specifically indicated to be incorporated by reference and were set forth in its entirety herein.
This application is a continuation of U.S. patent application Ser. No. 14/553,915, filed Nov. 25, 2014, entitled “VIRTUAL FIREWALLS FOR MULTI-TENANT DISTRIBUTED SERVICES,” and issued to U.S. Pat. No. 10,313,346 on Jun. 4, 2019, which is a continuation of U.S. patent application Ser. No. 12/861,692, filed Aug. 23, 2010, entitled “VIRTUAL FIREWALLS FOR MULTI-TENANT DISTRIBUTED SERVICES,” and issued to U.S. Pat. No. 8,904,511 on Dec. 2, 2014, the contents of which are hereby incorporated by reference in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
5021953 | Webber | Jun 1991 | A |
5890143 | Sakurai | Mar 1999 | A |
6345288 | Reed | Feb 2002 | B1 |
6484261 | Wiegel | Nov 2002 | B1 |
6502131 | Vaid | Dec 2002 | B1 |
6728885 | Taylor et al. | Apr 2004 | B1 |
6775704 | Watson | Aug 2004 | B1 |
6779120 | Valente | Aug 2004 | B1 |
6845452 | Roddy | Jan 2005 | B1 |
6981029 | Menditto et al. | Dec 2005 | B1 |
7013482 | Krumel | Mar 2006 | B1 |
7072934 | Helgeson et al. | Jul 2006 | B2 |
7233935 | Chandler | Jun 2007 | B1 |
7324972 | Oliver | Jan 2008 | B1 |
7343488 | Yadav | Mar 2008 | B2 |
7350226 | Moriconi et al. | Mar 2008 | B2 |
7363650 | Moriconi et al. | Apr 2008 | B2 |
7418475 | Stewart | Aug 2008 | B2 |
7447755 | Maxted | Nov 2008 | B1 |
7447777 | Singh Ahuja | Nov 2008 | B1 |
7509369 | Tormasov | Mar 2009 | B1 |
7512965 | Amdur | Mar 2009 | B1 |
7522060 | Tumperi | Apr 2009 | B1 |
7606146 | Pan | Oct 2009 | B1 |
7769394 | Zhu | Aug 2010 | B1 |
7873711 | Adams et al. | Jan 2011 | B2 |
7921197 | Soundararajan | Apr 2011 | B2 |
8019812 | Janedittakarn et al. | Sep 2011 | B2 |
8131784 | Zhuge | Mar 2012 | B1 |
8281372 | Vidal | Oct 2012 | B1 |
8478226 | Bakker et al. | Jul 2013 | B2 |
8572733 | Rockwood | Oct 2013 | B1 |
8584195 | Sherlock | Nov 2013 | B2 |
8612321 | Tully | Dec 2013 | B2 |
9183384 | Bruhmuller | Nov 2015 | B1 |
9226222 | Zhou | Dec 2015 | B2 |
9462007 | Yu | Oct 2016 | B2 |
10285025 | Baker | May 2019 | B1 |
20020099834 | Sielaff et al. | Jul 2002 | A1 |
20020114274 | Sturges | Aug 2002 | A1 |
20030041266 | Ke et al. | Feb 2003 | A1 |
20040111521 | Igarashi | Jun 2004 | A1 |
20040122730 | Tucciarone | Jun 2004 | A1 |
20040133460 | Berlin | Jul 2004 | A1 |
20040136386 | Miller | Jul 2004 | A1 |
20040172520 | Smit et al. | Sep 2004 | A1 |
20050078660 | Wood | Apr 2005 | A1 |
20050125692 | Cox | Jun 2005 | A1 |
20050257256 | Supnik | Nov 2005 | A1 |
20060004832 | Langsford et al. | Jan 2006 | A1 |
20060015512 | Alon | Jan 2006 | A1 |
20060026671 | Potter | Feb 2006 | A1 |
20060036764 | Yokota | Feb 2006 | A1 |
20060143699 | Nagata | Jun 2006 | A1 |
20060156403 | Haeffele et al. | Jul 2006 | A1 |
20060200580 | Wool | Sep 2006 | A1 |
20060246495 | Garrett et al. | Nov 2006 | A1 |
20070016467 | John et al. | Jan 2007 | A1 |
20070111316 | Shi et al. | May 2007 | A1 |
20070124577 | Nielsen | May 2007 | A1 |
20070136413 | Ishikawa | Jun 2007 | A1 |
20070230503 | Jeanne et al. | Oct 2007 | A1 |
20070300296 | Kudla | Dec 2007 | A1 |
20080028055 | Dolev | Jan 2008 | A1 |
20080052395 | Wright | Feb 2008 | A1 |
20080082504 | Jasik et al. | Apr 2008 | A1 |
20080141333 | Chen | Jun 2008 | A1 |
20080163357 | Xiao | Jul 2008 | A1 |
20080167024 | Zabawskyj | Jul 2008 | A1 |
20080189776 | Constable | Aug 2008 | A1 |
20080196099 | Shastri | Aug 2008 | A1 |
20080244691 | Hilerio et al. | Oct 2008 | A1 |
20080288428 | Birdwell et al. | Nov 2008 | A1 |
20090019518 | Lee et al. | Jan 2009 | A1 |
20090104605 | Siuzdak et al. | Apr 2009 | A1 |
20090113516 | Vorreiter | Apr 2009 | A1 |
20090144444 | Chauffour et al. | Jun 2009 | A1 |
20090164269 | Gupta | Jun 2009 | A1 |
20090178107 | Karjoth et al. | Jul 2009 | A1 |
20090288084 | Astete | Nov 2009 | A1 |
20090316709 | Polch | Dec 2009 | A1 |
20100061386 | Olsson | Mar 2010 | A1 |
20100088722 | Jiang | Apr 2010 | A1 |
20100100949 | Sonwane et al. | Apr 2010 | A1 |
20100103837 | Jungck et al. | Apr 2010 | A1 |
20100121923 | Cvetkovic et al. | May 2010 | A1 |
20100161759 | Brand | Jun 2010 | A1 |
20100161967 | Roegner | Jun 2010 | A1 |
20100191863 | Wing | Jul 2010 | A1 |
20100239077 | Michaelis et al. | Sep 2010 | A1 |
20100248720 | Millet | Sep 2010 | A1 |
20100268764 | Wee | Oct 2010 | A1 |
20100325710 | Etchegoyen | Dec 2010 | A1 |
20100332617 | Goodwin et al. | Dec 2010 | A1 |
20110016499 | Liu | Jan 2011 | A1 |
20110075667 | Li et al. | Mar 2011 | A1 |
20110075675 | Koodli et al. | Mar 2011 | A1 |
20110119748 | Edwards et al. | May 2011 | A1 |
20110165858 | Gisby | Jul 2011 | A1 |
20110225625 | Wolfson et al. | Sep 2011 | A1 |
20110262957 | Yang-Woytowitz et al. | Oct 2011 | A1 |
20110321130 | Tor | Dec 2011 | A1 |
20120099599 | Keranen | Apr 2012 | A1 |
20120167160 | Carney et al. | Jun 2012 | A1 |
20130042298 | Plaza Fonseca | Feb 2013 | A1 |
20140215590 | Brand | Jul 2014 | A1 |
20170295133 | Barber | Oct 2017 | A1 |
Entry |
---|
U.S. Appl. No. 12/861,692, “Final Office Action,” dated May 14, 2013, 27 pages. |
U.S. Appl. No. 12/861,692, “Non-Final Office Action,” dated Oct. 26, 2012, 22 pages. |
U.S. Appl. No. 12/861,692, “Non-Final Office Action,” dated Mar. 28, 2014, 27 pages. |
U.S. Appl. No. 12/861,692, “Notice of Allowance,” dated Aug. 11, 2014, 8 pages. |
U.S. Appl. No. 14/553,915, “Final Office Action,” dated Apr. 15, 2016, 13 pages. |
U.S. Appl. No. 14/553,915, “Final Office Action,” dated Dec. 8, 2017, 17 pages. |
U.S. Appl. No. 14/553,915, “Non Final Office Action,” dated Jul. 10, 2018, 19 pages. |
U.S. Appl. No. 14/553,915, “Non-Final Office Action,” dated Nov. 23, 2015, 12 pages. |
U.S. Appl. No. 14/553,915, “Non-Final Office Action,” dated Apr. 19, 2017, 16 pages. |
U.S. Appl. No. 14/553,915, “Notice of Allowance,” dated Jan. 22, 2019, 8 pages. |
Jiang et al., “Protection mechanisms for application service hosting platforms”, IEEE article No. 1336693, Apr. 2004, pp. 656-663. |
Number | Date | Country | |
---|---|---|---|
Parent | 14553915 | Nov 2014 | US |
Child | 16427099 | US | |
Parent | 12861692 | Aug 2010 | US |
Child | 14553915 | US |