Parallel network-based vulnerability scanning

A computing device may receive a plurality of scanning requests with at least one scanning request in the plurality identifying a target address of a target network. The computing device may for at least a subset of the plurality of scanning requests: generate a scanner instance and a virtual network interface card (VNIC) in response to the scanning request. The scanner instance and the VNIC communicating with a routing namespace that can communicate with two or more scanner instances simultaneously. Until the target address has been scanned: one or more packets can be sent from the scanner instance to the target address via the routing namespace and VNIC. The one or more packets can be wrapped in one or more packet wrappers identifying the target address and the target network. In response to the target address being scanned, the scanner instance and VNIC can be decommissioned.

BACKGROUND

Vulnerability scanning in a cloud environment can be complicated by the addresses used within a virtual cloud network (VCN). Vulnerability scanners can use an address, such as an internet protocol version 4 (IPv4) address, to find and scan a target. However, addresses in a cloud environment are not necessarily unique and an address in one VCN can be repeated in other networks. Accordingly, techniques for performing parallel vulnerability scans in a cloud environment are desirable.

BRIEF SUMMARY

Techniques are provided for performing parallel network-based vulnerability scanning.

In an embodiment, a plurality of scanning requests can be received by a computing device. At least one of the scanning requests can identify a first target address of a first target network. A scanning request identifying the first target address and a scanning request identifying the second target address can be processed simultaneously. For at least a subset of the plurality of scanning requests: a scanner instance can be accessed and a virtual network interface card (VNIC) can be generated by the computing device. The VNIC can be in communication with a root routing namespace. The root routing namespace can be configured to communicate with two or more scanner instances in parallel. The scanner instance can be wrapped in a scanner container. Until the target address has been scanned: one or more packets can be sent from the scanner to the target address by a computer device. The one or more packets can be routed by the root routing namespace and the VNIC. The VNIC can be decommissioned in response to the target address being scanned.

In one general aspect, one or more scanning requests can have target addresses that are part of the same virtual cloud network (VCN). The one or more scanning requests can be scanned simultaneously.

In one general aspect, packets from two or more scanner instances can be forwarded by a single virtual network interface card (VNIC). The packets can correspond to two or more scanning requests.

In one general aspect, the target network can contain a scan subnet.

In one general aspect, the target address in the target network can be outside the scan subnet.

In one general aspect, the target address can be provided to the scanner instance without identifying the target network.

In one general aspect, the first target address and the second target address can be the same globally non-unique identifier.

One general aspect includes a computer-readable storage medium storing a set of instructions that when executed by one or more processors of a computing device, cause the one or more processors to perform instructions comprising: receiving a plurality of scanning requests with at least one scanning request in the plurality of scanning requests identifying a first target address of a first target network and at least one scanning request identifying a second target address of a second target network. For at least a subset of the plurality of scanning requests, where at least one scanning request identifying the first target address and at least one scanning request identifying the second target address can be processed simultaneously: accessing a scanner instance and generating a virtual network interface card (VNIC). The VNIC can be generated in response to the scanning request. The VNIC can be in communication with a routing namespace. The root routing namespace can be configured to communicate with two or more scanner instances in parallel. The scanner instance can be wrapped in a scanner container. Until the target address has been scanned: one or more packets can be sent from the scanner instance to the target address. The one or more packets can be forwarded via the root routing namespace and the virtual network interface card. In response to the target address being scanned, the virtual network interface card can be decommissioned.

One general aspect includes a system with a memory configured to store a plurality of instructions and one or more processors configured to access the memory, and to execute the plurality of instructions to at least: receive a plurality of scanning requests with at least one scanning request identifying a first target address of a first target network and at least one scanning request identifying a second target address of a second target network. For at least a subset of the plurality of scanning requests, where at least one scanning request identifying the first target address and at least one scanning request identifying the second target address can be processed simultaneously: the instructions can cause the processors to access a scanner instance and generate a virtual network interface card (VNIC). The VNIC can be generated in response to the scanning request. The scanner instance and VNIC can be in communication with a routing namespace. The root routing namespace can be configured to communicate with two or more scanner instances in parallel. The scanner instance can be wrapped in a scanner container. Until the target address has been scanned: one or more packets can be sent from the scanner instance to the target address. The one or more packets can be forwarded via the root routing namespace and the virtual network interface card. In response to the target address being scanned, and the virtual network interface card can be decommissioned.

DETAILED DESCRIPTION

Embodiments of the present disclosure provide techniques for parallel vulnerability scans in a cloud-based environment. Vulnerability scans can be used to identify weaknesses that can exist in one or more devices attached to a network. The weaknesses in the one or more devices can be exploited by unauthorized actors. A vulnerability scan can be performed on a network by scanning one or more targets that are identified by addresses used in that network. A scan can be performed in response to an event, or a scan can be performed at scheduled intervals. Event-based vulnerability scans can be used to respond to immediate damage to a network caused by a security breach. In addition to immediate damage, a security breach can cause long term damage to a cloud services provider by eroding trust within the provider's customer base.

Event-based scans can provide faster vulnerability detection than scans performed at scheduled intervals. Event based scans can be triggered by a change in vulnerability patch levels on target devices, or the event based scans can be triggered by human driven events. One example of a human driven event based scan could be a scan to respond to a critical recently-discovered vulnerability in a network to measure the networks exposure based on the vulnerability.

Vulnerability scans can identify weaknesses that can allow for security breaches, but the scans are also used to obtain compliance certifications. Compliance certifications can establish that a cloud provider is in compliance with an information technology (IT) security standard (e.g., International Organization for Standardization (ISO) 27001, ISO 27002, ISO 15408, etc.). A cloud provider may need to meet certain industry and/or government IT security standard before a government agency can use a cloud provider to run its applications. Government IT security standards can include standards from defense information systems agency (DISA), security technical implementation guides (STIGs), federal risk and authorization management program (FedRAMP), etc. A record of regular vulnerability scans can be used to gain a compliance certification by establishing that the cloud provider has implemented the relevant IT security standard. Some customers may only allow their data to be hosted on a network with one or more specific compliance certifications. For example, a United States government agency may require that their data is hosted on networks that comply with DISA STIG and FedRAMP compliance certifications.

A customer can update the devices attached to their VCN with a software patch to address vulnerabilities identified in a scan. While a cloud service provider can perform hundreds of thousands of daily scans, a common customer complaint is that there can be a long delay between the update and a subsequent scan. A customer can be unsure of whether an update has addressed an identified vulnerability until the subsequent scan has been concluded. If a device attached to the network is updated shortly after a daily scheduled scan has been performed, it can take over 24 hours until the subsequent scan has been performed and processed. The lack of responsiveness can make updating inefficient, error prone and frustrating for customers.

To improve response times, event-based vulnerability scans can be performed in parallel. With event-based vulnerability scans, a user may not have to wait over 24 hours after an update for results from a scheduled scan, because an event, such as an update, can trigger the scan. Parallel scans can also enable more scans with the same resources compared to single scans. For instance, if a logical cloud function host can support two or more scans simultaneously, a larger number of smaller scans can be performed using the same number of logical cloud function hosts.

In an illustrative example, a user patches devices on two separate cloud networks to address vulnerabilities identified in a scheduled scan. In this case, the user needs to wait for an additional scan to determine if the update has addressed the identified vulnerabilities. By updating the user's cloud infrastructure, a separate event-based scanning request is generated for each updated network. The cloud networks configuration can allow for multiple networks for the same user to share the same IP address range. This is usually not a problem as long as the two networks can be entirely separate from each other. It can become a problem when both networks are scanned by the same scanner infrastructure. In this scenario, the target address for the scanning requests are identical internet protocol version 4 (IPv4) addresses on the user's two networks hosted by the cloud infrastructure. In addition to the one or more target address, each scanning request identifies a target network. The target network can be the cloud network that contains the target address. The target network can be identified by a unique identifier that is not repeated across different networks.

Continuing the example, the target requests are picked up by an available logical cloud function host containing a routing namespace, and one or more (idle) scanners that can be used to run the scan as identified in the request. A namespace can be a Unix network namespace. The root routing namespace can be connected to a separate scanner specific routing namespace. This scanner routing namespace can have one scanner instance. Additional scanner instances can exist, and each scanner instance can use its own dedicated scanner routing namespace. The scanner instances can be created during initial host configuration and can be re-used between requests. The logical cloud function software can create a virtual network interface card (VNIC) and place it in a separate VNIC-specific routing namespace in response to each scanning request. This VNIC-specific namespace can be connected to the root routing namespace. The three namespaces can be connected together to allow packets to flow between the scanner namespace and the VNIC namespace through the root namespace as intermediary. One or more routing rules, routing tables, and network address translation (NAT) tables can also be created in response to each scanning request.

To perform each scan, the target address and the target network (e.g., the network containing the target address) can be used to configure route rules in the one or more routing tables to create a pipeline from the scanner instance to the target address. Packets can be sent to the target address via the pipeline from the scanner instance through the scanner namespace, routing namespace, VNIC namespace, and finally the VNIC itself which is connected to the target network. Responses are sent back to the scanner instance along the pipeline through the VNIC and the separate namespaces. Once the scan is concluded, the VNIC and the namespace containing the VNIC that was created to perform that scan can be decommissioned.

FIG.1shows a simplified diagram100of the logical cloud function performing vulnerability scanning according to an embodiment. Scanning requests can be received and stored in a scanning request queue102. Scanning request queue102can be a priority queue with one or more queue types. The queue types can identify which type of logical cloud function should receive a queued request. Scanning requests in the scanning request queue can also be searched or filtered to allow efficient access to the queue contents. scanning requests can be performed in priority order, but, in some circumstances, there may be scanning requests that should be performed on specific scanners. If the specific scanners are not available, a lower priority scan may be performed on a different scanner before a higher priority scanning request can be performed on the specific scanner. Priority can mean the order that events will be consumed in the scanning request queue102. Priority for event-based scans can be based at least in part on the time of the event and the type of event. In some circumstances, event-based scanning requests may be given a higher priority than periodic scanning requests.

The logical cloud function104can include an application programming interface (API) handler106. An API can be software that permits applications to communicate. Logical cloud function104can include a scanner database108. The scanner database108can provide state for API requests and individual scans. Logical cloud function104can include a scan workflow110. Scan workflow110can support parallel scans or targeted scanning using a subset of vulnerability checks. Logical cloud function104can include the scanner interface112. Scanner interface112can communicate with the scanner114. Scanner114can be located in logical cloud function104.

Logical cloud function104can communicate with the security event queue116via scan workflow110. When a scan is completed, a ScanCompleted event indicating that the scan has completed can be emitted from the scan workflow110to the security event queue116. The ScanCompleted event can include the location of the scan report120that was generated for the scan. The ScanCompleted events can be emitted from the security event queue to scanner report user interface (UI)118. Scanner report UI118can poll for new scan completed events. scanner report UI118can consume the ScanCompleted event and, in response, scanner report UI118can start ingesting the scan report120identified by the event.

FIG.2is a simplified block diagram200of a scanner interface and a scanner for implementations with a single scanner instance according to an embodiment. The scanner interface can be scanner interface112fromFIG.1. Scan workflow110can create and attach a VNIC to a host connecting scanner114and the VNIC. The connection can span scanner-0 namespace206, root namespace214, and VNIC-0 namespace216. Scanner-0 namespace206or root namespace214can be permanent. VNIC-0 namespace216can be temporary, and VNIC-0 namespace216can be created by the scan workflow110after VNIC-0228is created and attached.

Turning to diagram200in greater detail, scanner-0202can be contained in scanner_container-0204. Scanner-0202can be any commercially available vulnerability scanner (e.g., Nessus). Scanner_container-0204can be a container generated by a containerization engine (e.g., a Docker container). Scanner-0202and scanner_container-0204can be contained in scanner-0 namespace206. Elements within scanner-0 namespace206can only see or use resources assigned to that namespace. Scanner-0 namespace206can also include a routing table208.

Scanner-0 namespace206can be located in the logical cloud function host212along with a root routing namespace214and VNIC-0 routing namespace216. A virtual network interface card (VNIC, e.g. VNIC-0228, VNIC-1220, VNIC-2222, etc.) can be contained in VNIC-0 namespace216. Packets from scanner-0 namespace206can be forwarded to a customer virtual cloud network (VCN, e.g., customer 1 VCN236) via VNIC-1220, root routing namespace214, VNIC-0228, and VNIC-0 namespace216. Namespaces can be connected by an attachment230that can act as a virtual network cable. Packets sent or received by VNICs can be sent via an attachment230using communication protocols (e.g., transmission control protocol (TCP), user datagram protocol (UDP), etc.).

Root routing namespace214can communicate with the administrative (admin) VCN232via VNIC-2222. Communication can occur between root routing namespace214and admin host subnet234in admin VCN232via VNIC-3222. Instructions, such as a list of addresses to be scanned, can be received at the logical cloud function host212from the admin VCN232. New scan requests can be retrieved or sent from scan request queue102fromFIG.1, and scan request queue102can be accessible through admin VCN232or admin host subnet234. The admin VCN can be part of the scan workflow110fromFIG.1. In some circumstances, routing namespace214can communicate with VNIC-0228in VNIC-0 namespace228. VNIC-0228can forward packets between a customer VCN (e.g., Customer 1 VCN236) and root routing namespace214.

Messages can be received at customer 1 VCN236through the scan subnet244. Customer VCNs, including customer 1 VCN236, can contain one or more hosts (e.g., host240). In some circumstances, the host can be located in scan subnet244. In some circumstances, host240can be located in a host subnet242that can be separate from the scan subnet244. Communication to and from customer 1 VCN236may require available address space in scan subnet244before packets can be sent or received.

Messages, or packets, can be forwarded through a pipeline that can extend from scanner-0202to scan subnet244, host subnet242or host240. Packets from scanner-0 can be forwarded through this pipeline using routing rules defined using at least one of the route tables such as scan route table-0208, root route table248, or VNIC-0 route table250. The unique network identifier and the target address can be used to configure routing rules in at least one route table. The configured routing rules can be used to forward packets to and from scanner-0202along the pipeline. Packets can be forwarded along the pipeline in both directions.

FIG.3is a simplified flowchart of a process300for performing a scan using a single scanner instance. This process, in addition to the processes fromFIG.5and the process fromFIG.6, are illustrated as a logical flow diagram, each operation of which can be implemented in hardware, computer instructions, or a combination thereof. In the context of computer instructions, the operations may represent computer-executable instructions stored on one or more computer-readable storage media that, when executed by one or more processors, perform the recited operations. Generally, computer-executable instructions include routines, programs, objects, components, data structures and the like that perform particular functions or implement particular data types. The orders in which the operations are described are not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement the processes or the method.

Turning to process300in greater detail, at block305a scanning request can be received. The scanning request can be obtained by root routing namespace214from the admin host subnet234in the admin VCN232. A scanning request can be received at the API handler106or the scan workflow110fromFIG.1, and the received scanning request can be enqueued to scanning request queue102. The scanning request can be obtained by polling scan request queue102via admin host subnet234or admin VCN232. The scanning request can identify one or more target addresses, e.g., an address in host subnet242, and a target network, e.g., a unique identifier for customer 1 VCN236, or a unique identifier for scan subnet244. In some circumstances, the target address can be a globally non-unique identifier. For example, the target address can be an internet protocol version 4 (IPv4) address that is repeated in different customer VCNs and on the Internet. In some circumstances, the globally non-unique target addresses may not be repeated within an individual scan request or within an individual VCN.

At block310, the scanning infrastructure can be generated. The scanning infrastructure can include a scanner instance such as scanner-0202or scanner114. Generating the scanning infrastructure can also include generating a scanner namespace, one or more route tables, or a VNICs (e.g., scanner-0 namespace206, scan route table-0208, root route table248, VNIC-0 route table250, VNIC-0228, VNIC-1220, VNIC-2222, etc.). In some circumstances, the scanner namespace, scan route table, or VNIC can be created on the initial scanner deployment. The scanning infrastructure can also include a virtual network interface card such as VNIC-0228, or a VNIC-0 namespace216.

At block315, the scan can be performed. One or more packets can be sent from the scanner instance to one or more target addresses. For example, packets could be sent from scanner-0202to host240. A packet can be forwarded to its destination via the root routing namespace (e.g., root routing namespace214). Packets can be forwarded across the Scanner-0 namespace206, root routing namespace214, and VNIC-0 namespace216using at least one of scan route table-0208, root route table248, or VNIC-0 route table250.

As an example, a packet, addressed to host240, can be generated by scanner-0202. The packet can leave scanner_container-0204. Using at least one of a target address and a customer identifier, the routing rules in scan route table-0208, root route table248, and VNIC-0 route table250can be configured to create a pipeline. The pipeline can extend from scanner-0202to host240, and the pipeline can be used to forward packets from scanner-0 to host240. Responses sent from host240to scanner-0202can also be sent along the pipeline. The packet can travel from scanner-0 namespace206to root routing namespace214via VNIC-1220and attachment230a. The packet can be forwarded using the configured route rules from scan route table-0208or root route table248. The packet can be routed using an internet protocol (IP) such as internet protocol version 4 (IPv4).

Continuing the example, the packet can be forwarded from root routing namespace214to VNIC-0 namespace216via VNIC-0228. The packet can be forwarded using routing rules from root route table248or VNIC-0 route table250. The packet can leave VNIC-0 namespace216by passing through VNIC-0228and attachment230b. After leaving the logical cloud function host212, the packet can arrive at scan subnet244in customer 1 VCN236. In some circumstances, addresses within the customer VCN, such as customer 1 VCN236, are not repeated. The packet can arrive at scan subnet244via the pipeline. The packet can be forwarded to the target, in this case host240in host subnet242, using the globally non-unique target address that may not be repeated within customer 1 VCN236. A response can be sent back to scanner-0202by sending a packet the opposite direction along the pathway described above.

At block320, the scanning infrastructure can be decommissioned. At least one of the scanner namespace (e.g., scanner-0 namespace206), the scanner container (e.g., scanner_container-0204), the scanner instance (e.g., scanner-0), the VNIC (e.g., VNIC-0228), scan route table-0208, root route table248, VNIC-0 route table250, or the VNIC namespace (e.g., VNIC-0 namespace216) can be decommissioned after performing the scan. In some circumstances, the scanner infrastructure can be decommissioned after performing one or more scans.

FIG.4is a simplified block diagram400of a scanner interface and two scanners for implementations with multiple scanner instances according to an embodiment. The description of features disclosed in relation toFIG.2can apply to similar features described in relation toFIG.3.

Turning to diagram400in greater detail, the logical cloud function host412can contain two or more scanner instances (e.g., scanner-0402and scanner-N446). The scanner instances can be contained in a scanner container. For example, scanner-N446can be contained in scanner_container-N448. The scanner container can be located in a scanner namespace such as scanner-N namespace450or scanner-0 namespace406. Two or more scanner containers can communicate with a root routing namespace (e.g., root routing namespace414) simultaneously through a virtual network interface card (VNIC) such as VNIC-0428or VNIC-N466. Packets sent from a VNIC can travel along an attachment430between namespaces. For example, packets sent via VNIC-1420can travel between scanner-0 namespace406and root routing namespace414.

Packets received at root routing namespace414can be forwarded to a virtual network interface card (VNIC) namespace such as VNIC-0 namespace416or VNIC-N namespace456. The VNIC namespaces can contain VNIC instances such as VNIC-0428and VNIC-N466. In a routing infrastructure with one scanner and VNIC namespace, packets received at the root routing namespace are routed to the VNIC namespace (e.g., VNIC-0 namespace416, etc.). In a routing infrastructure with multiple VNIC namespaces, the root routing namespace may have to determine which VNIC or VNIC namespace should receive an incoming packet. A routing module460can determine which VNIC or VNIC namespace should receive an incoming packet that is received from a scanner instance, scanner namespace, or scanner container. Root routing module460can determine which scanner instance, scanner container, or scanner namespace should receive a packet received from a VNIC. Root routing module460can use root routing table462to determine how to route packets. Root routing table462can include one or more routing tables. Root routing table462can include one or more of logical rules for routing packets or addresses.

Packets can be routed from a the routing namespace to a VNIC namespace. For example, a packet leaving root routing module460can be sent via VNIC-N466and attachment430cinto VNIC-N namespace458. The routed packet can leave the logical cloud function host412via VNIC-N466and attachment430d. The packet can arrive at a customer VCN, such as customer 2 VCN468, and enter the customer VCN via a subnet. In some circumstances, the subnet can contain a host (e.g., host470in scan/host subnet472).

The subnet receiving the packet can be a subnet that does not contain a host such as scan subnet444which is reserved for dedicated scanning use. A dedicated scan subnet reserves a set of addresses that can be leveraged by the scanner interface112to assign an address to the created VNIC without conflict with other devices requiring their own addressing. Using a subnet that does not contain a host, such as scan subnet444, can reduce errors caused by a lack of available addresses because the subnet addresses can be reserved for packet ingress.

FIG.5shows a process500for performing parallel scans with two or more scanner instances according to an embodiment.

Turning to process500in greater detail, at block505, a first scanning request can be received. The scanning request can be received at the root routing namespace414from the admin VCN432. Scan workflow110can poll for scan requests from scan request queue102. The scan workflow can poll for scan requests from scan request queue102through Admin VCN432. The packet containing the first scanning request can be sent from admin host subnet434to root routing namespace414via VNIC-2424and attachment430e. The first scanning request can identify one or more targets to be scanned in one or more different VCNs controlled by one or more customers.

At block510, a first scanning infrastructure can be generated. A scanner instance (e.g., scanner-0402) can be generated in response to receiving the first scanning request. The scanner instance can be contained in at least one of a scanner namespace, such as scanner-0 namespace406, and/or a scanner container (e.g., scanner_container-0404). At least one of the one or more packets containing the first scanning request can be routed to the scanner instance using routing module460or routing module table462. For example, a packet can be received at routing module460and forwarded to scanner-0402via VNIC-1420and attachment430a. In some circumstances, the scanner instance, scanner namespace or scanner container can be reused between scans and may not need to be created in response to receiving a scanning request.

The scanning infrastructure may be created in response to a scanning request (e.g., the first scanning request). The scanning infrastructure can include one or more of a scan route table (e.g., scan route table-0408), a root routing table (e.g., root routing table462), a routing module (e.g., routing module460), a VNIC routing table (e.g., VNIC-0 route table478, etc.), a VNIC namespace (e.g., VNIC-0 namespace416, etc.), or a VNIC (e.g., VNIC-0480, etc.).

At block515, a first scan can begin. The first scan can be performed by sending one or more packets to targets that are to be scanned. The one or more targets can be identified in the first scanning request. Using at least one of a target address and a customer identifier, at least one of scan route table-0408, root routing table462, VNIC-0 routing table478, or VNIC-N routing table482can be configured to create a first pipeline.

As an example, a packet, addressed to host440, can be generated by scanner-0402. The packet can leave scanner-0 namespace406and arrive at root routing namespace414via VNIC-1420and attachment430a. At root routing namespace414, the packet can be forwarded by routing module460to a VNIC in a VNIC namespace (e.g., VNIC-0428in VNIC-0 namespace416). If more than one pipeline exists, the pipeline that receives the packet can be determined by routing module460using routing module table462. The pipeline that receives the packet can be the first pipeline or a second pipeline. The second pipeline can be created using at least one of a target address and a customer identifier, at least one of scan route table-N474, route routing table462, VNIC-0 routing table478, or VNIC-N routing table482.

Continuing the example, the packet can be forwarded along the first pipeline from routing namespace414to VNIC-0 namespace416via VNIC-0428. The packet can leave VNIC-namespace416by passing along the first pipeline through VNIC-0428and attachment430b. After leaving the logical cloud function host412, the packet can arrive at scan subnet444in customer 1 VCN436. In some circumstances, addresses within the customer VCN, such as customer 1 VCN436, are not repeated, but the addresses can be repeated between different customer VCNs. For example, an address in customer 1 VCN436and customer 2 VCN468can be identical. The target address can be globally non-unique target address but the target address may not be repeated within an individual VCN or individual scan requests. The packet can be forwarded to the target, in this case host440in host subnet442, using the globally non-unique target address. A response can be sent back to scanner-0402by sending a packet the opposite direction along the first pipeline described above.

At block520, a second scanning request can be received. The second scanning request can be received at the routing namespace414from scan request queue102via admin VCN432. The one or more packets containing the second scanning request can be polled from the scan request queue102through the admin host subnet434to root routing namespace414via VNIC-2424and attachment430e. The second scanning request can identify targets in one or more of the same VCNs as the targets identified in the first scanning request, or the second scanning request can identify targets in one or more VCNs that were not identified in the first scanning request.

At block525, a second scanning infrastructure can be generated. A second scanner instance (e.g., scanner-N446) can be generated in response to receiving the scanning request. The scanner instance can be contained in at least one of a scanner namespace, such as scanner-N namespace450and/or a scanner container (e.g., scanner_container-N448). At least one of the one or more packets containing the scanner request can be routed to the scanner instance using routing module460or routing module table462. For example, a packet can be received at routing module460and forwarded to scanner-N446via VNIC-3454and attachment430f. In some circumstances, the scanner instance, scanner namespace or scanner container can be reused between scans and may not need to be created in response to receiving a scanning request.

The scanning infrastructure may be created in response to a scanning request (e.g., the second scanning request). The scanning infrastructure can include one or more of a scan route table (e.g., scan route table-N474), a root routing table (e.g., root route table462), a routing module (e.g., routing module460), a VNIC route table (e.g., VNIC-N route table482), a VNIC namespace (e.g., VNIC-N namespace458), or a VNIC (e.g., VNIC-N484).

At block530, a second scan can begin. The second scan can be performed by sending packets one or more to one or more targets that are to be scanned. The one or more targets can be identified in the second scanning request. Using at least one of a target address and a customer identifier, at least one of scan route table-N474, route routing table462, VNIC-0 routing table478, or VNIC-N routing table482can be configured to create a second pipeline.

As an example, a packet, addressed to Host-N470, can be generated by scanner-N446. The packet can leave scanner-N namespace450and arrive at root routing namespace414via VNIC-3454and attachment430f. At routing namespace414, the packet can be forwarded by routing module to a VNIC namespace. The pipeline that receives the packet can be determined by routing module460using route rules from root routing module table462, a scan route table (e.g., scan route table-N474) or a VNIC routing table (e.g., VNIC-N route table482). The pipeline that receives the packet can be the first pipeline or the second pipeline.

Continuing the example, the packet can be forwarded from routing namespace414VNIC-N namespace458via VNIC-N466and attachment430c. The packet can leave VNIC-N namespace458by passing along the second pipeline through VNIC-N466and attachment430d. After leaving the logical cloud function host412, the packet can arrive at host/scan subnet472in customer 2 VCN468. In some circumstances, addresses within the customer VCN, such as customer 2 VCN468, are not repeated, but the addresses can be repeated between different customer VCNs.

For example, an address in customer 1 VCN436and customer 2 VCN468can be identical. The packet can be unwrapped after arriving at host/scan subnet472. The packet can be forwarded along the second pipeline to the target, in this case host-N470in host/scan subnet472, using the globally non-unique target address. A response can be sent back to scanner-N446by sending a wrapped packet the opposite direction along the second pipeline described above.

At block535, the first and second scanning infrastructure can be decommissioned. The scanning infrastructure can be decommissioned in response to a scan being completed. The scanning infrastructure can be decommissioned in any order and, for instance, the scanning infrastructure created in response to the second scanning request can be decommissioned before the first scanning infrastructure. The scanning infrastructure can include one or more of a scan route table (e.g., scan route table-N474), a root routing table (e.g., root route table462), a routing module (e.g., routing module460), a VNIC route table (e.g., VNIC-N route table482), a VNIC namespace (e.g., VNIC-N namespace458), or a VNIC (e.g., VNIC-N466).

FIG.6shows a process600for performing parallel network-based vulnerability scans according to an embodiment. At block605, scanning requests can be received. Two or more scanning requests can be received at routing namespace414from admin VCN432as described above in relation toFIGS.4and5.

At block610, for at least two of the two or more scanning requests, a scanner instance and a virtual network interface card (VNIC) can be generated in response to the scanning request. A scanner instance and VNIC can be generated for two or more scanning requests identifying separate VCNs (e.g., VCN432). The scanner instance and VNIC can include a scanning infrastructure as described above in relation toFIGS.4and5. The scanning infrastructure can include one or more of a scan route table (e.g., scan route table-N474), a root routing table (e.g., root route table462), a routing module (e.g., routing module460), a VNIC route table (e.g., VNIC-N route table482), a VNIC namespace (e.g., VNIC-N namespace458), or a VNIC (e.g., VNIC-N466).

At block615, for at least two of the two or more scanning requests, packets can be sent to a target address until the target address has been scanned. The target address can identify a device (e.g., host440or host-N470) in a customer VCN such as customer 1 VCN436or Customer 2 VCN468. The process of sending packets to a target address is described in greater detail above in relation toFIGS.4and5.

At block620, for at least two of the two or more scanning requests, the scanning infrastructure. The scanning infrastructure can be decommissioned in response to scanning the targets identified in the scanning request. In some circumstances, the scanning infrastructure can be decommissioned in response to a determination that the targets identified in the scanning request have been scanned or the targets cannot be scanned. The process of decommissioning the scanner instance and VNIC are described in greater detail above in relation toFIGS.4and5.

The VCN706can include a local peering gateway (LPG)710that can be communicatively coupled to a secure shell (SSH) VCN712via an LPG710contained in the SSH VCN712. The SSH VCN712can include an SSH subnet714, and the SSH VCN712can be communicatively coupled to a control plane VCN716via the LPG710contained in the control plane VCN716. Also, the SSH VCN712can be communicatively coupled to a data plane VCN718via an LPG710. The control plane VCN716and the data plane VCN718can be contained in a service tenancy719that can be owned and/or operated by the IaaS provider.

The control plane VCN716can include a control plane demilitarized zone (DMZ) tier720that acts as a perimeter network (e.g., portions of a corporate network between the corporate intranet and external networks). The DMZ-based servers may have restricted responsibilities and help keep security breaches contained. Additionally, the DMZ tier720can include one or more load balancer (LB) subnet(s)722, a control plane app tier724that can include app subnet(s)726, a control plane data tier728that can include database (DB) subnet(s)730(e.g., frontend DB subnet(s) and/or backend DB subnet(s)). The LB subnet(s)722contained in the control plane DMZ tier720can be communicatively coupled to the app subnet(s)726contained in the control plane app tier724and an Internet gateway734that can be contained in the control plane VCN716, and the app subnet(s)726can be communicatively coupled to the DB subnet(s)730contained in the control plane data tier728and a service gateway736and a network address translation (NAT) gateway738. The control plane VCN716can include the service gateway736and the NAT gateway738.

The control plane VCN716can include a data plane mirror app tier740that can include app subnet(s)726. The app subnet(s)726contained in the data plane mirror app tier740can include a virtual network interface controller (VNIC)742that can execute a compute instance744. The compute instance744can communicatively couple the app subnet(s)726of the data plane mirror app tier740to app subnet(s)726that can be contained in a data plane app tier746.

The data plane VCN718can include the data plane app tier746, a data plane DMZ tier748, and a data plane data tier750. The data plane DMZ tier748can include LB subnet(s)722that can be communicatively coupled to the app subnet(s)726of the data plane app tier746and the Internet gateway734of the data plane VCN718. The app subnet(s)726can be communicatively coupled to the service gateway736of the data plane VCN718and the NAT gateway738of the data plane VCN718. The data plane data tier750can also include the DB subnet(s)730that can be communicatively coupled to the app subnet(s)726of the data plane app tier746.

The Internet gateway734of the control plane VCN716and of the data plane VCN718can be communicatively coupled to a metadata management service752that can be communicatively coupled to public Internet754. Public Internet754can be communicatively coupled to the NAT gateway738of the control plane VCN716and of the data plane VCN718. The service gateway736of the control plane VCN716and of the data plane VCN718can be communicatively couple to cloud services756.

In some examples, the service gateway736of the control plane VCN716or of the data plane VCN718can make application programming interface (API) calls to cloud services756without going through public Internet754. The API calls to cloud services756from the service gateway736can be one-way: the service gateway736can make API calls to cloud services756, and cloud services756can send requested data to the service gateway736. But, cloud services756may not initiate API calls to the service gateway736.

In some examples, the secure host tenancy704can be directly connected to the service tenancy719, which may be otherwise isolated. The secure host subnet708can communicate with the SSH subnet714through an LPG710that may enable two-way communication over an otherwise isolated system. Connecting the secure host subnet708to the SSH subnet714may give the secure host subnet708access to other entities within the service tenancy719.

The control plane VCN716may allow users of the service tenancy719to set up or otherwise provision desired resources. Desired resources provisioned in the control plane VCN716may be deployed or otherwise used in the data plane VCN718. In some examples, the control plane VCN716can be isolated from the data plane VCN718, and the data plane mirror app tier740of the control plane VCN716can communicate with the data plane app tier746of the data plane VCN718via VNICs742that can be contained in the data plane mirror app tier740and the data plane app tier746.

In some examples, users of the system, or customers, can make requests, for example create, read, update, or delete (CRUD) operations, through public Internet754that can communicate the requests to the metadata management service752. The metadata management service752can communicate the request to the control plane VCN716through the Internet gateway734. The request can be received by the LB subnet(s)722contained in the control plane DMZ tier720. The LB subnet(s)722may determine that the request is valid, and in response to this determination, the LB subnet(s)722can transmit the request to app subnet(s)726contained in the control plane app tier724. If the request is validated and requires a call to public Internet754, the call to public Internet754may be transmitted to the NAT gateway738that can make the call to public Internet754. Memory that may be desired to be stored by the request can be stored in the DB subnet(s)730.

In some examples, the data plane mirror app tier740can facilitate direct communication between the control plane VCN716and the data plane VCN718. For example, changes, updates, or other suitable modifications to configuration may be desired to be applied to the resources contained in the data plane VCN718. Via a VNIC742, the control plane VCN716can directly communicate with, and can thereby execute the changes, updates, or other suitable modifications to configuration to, resources contained in the data plane VCN718.

In some embodiments, the control plane VCN716and the data plane VCN718can be contained in the service tenancy719. In this case, the user, or the customer, of the system may not own or operate either the control plane VCN716or the data plane VCN718. Instead, the IaaS provider may own or operate the control plane VCN716and the data plane VCN718, both of which may be contained in the service tenancy719. This embodiment can enable isolation of networks that may prevent users or customers from interacting with other users', or other customers', resources. Also, this embodiment may allow users or customers of the system to store databases privately without needing to rely on public Internet754, which may not have a desired level of security, for storage.

In other embodiments, the LB subnet(s)722contained in the control plane VCN716can be configured to receive a signal from the service gateway736. In this embodiment, the control plane VCN716and the data plane VCN718may be configured to be called by a customer of the IaaS provider without calling public Internet754. Customers of the IaaS provider may desire this embodiment since database(s) that the customers use may be controlled by the IaaS provider and may be stored on the service tenancy719, which may be isolated from public Internet754.

FIG.8is a block diagram800illustrating another example pattern of an IaaS architecture, according to at least one embodiment. Service operators802(e.g. service operators702ofFIG.7) can be communicatively coupled to a secure host tenancy804(e.g. the secure host tenancy704ofFIG.7) that can include a virtual cloud network (VCN)806(e.g. the VCN706ofFIG.7) and a secure host subnet808(e.g. the secure host subnet708ofFIG.7). The VCN806can include a local peering gateway (LPG)810(e.g. the LPG710ofFIG.7) that can be communicatively coupled to a secure shell (SSH) VCN812(e.g. the SSH VCN712ofFIG.7) via an LPG710contained in the SSH VCN812. The SSH VCN812can include an SSH subnet814(e.g. the SSH subnet714ofFIG.7), and the SSH VCN812can be communicatively coupled to a control plane VCN816(e.g. the control plane VCN716ofFIG.7) via an LPG810contained in the control plane VCN816. The control plane VCN816can be contained in a service tenancy819(e.g. the service tenancy719ofFIG.7), and the data plane VCN818(e.g. the data plane VCN718ofFIG.7) can be contained in a customer tenancy821that may be owned or operated by users, or customers, of the system.

The control plane VCN816can include a control plane DMZ tier820(e.g. the control plane DMZ tier720ofFIG.7) that can include LB subnet(s)822(e.g. LB subnet(s)722ofFIG.7), a control plane app tier824(e.g. the control plane app tier724ofFIG.7) that can include app subnet(s)826(e.g. app subnet(s)726ofFIG.7), a control plane data tier828(e.g. the control plane data tier728ofFIG.7) that can include database (DB) subnet(s)830(e.g. similar to DB subnet(s)730ofFIG.7). The LB subnet(s)822contained in the control plane DMZ tier820can be communicatively coupled to the app subnet(s)826contained in the control plane app tier824and an Internet gateway834(e.g. the Internet gateway734ofFIG.7) that can be contained in the control plane VCN816, and the app subnet(s)826can be communicatively coupled to the DB subnet(s)830contained in the control plane data tier828and a service gateway836(e.g. the service gateway ofFIG.7) and a network address translation (NAT) gateway838(e.g. the NAT gateway738ofFIG.7). The control plane VCN816can include the service gateway836and the NAT gateway838.

The control plane VCN816can include a data plane mirror app tier840(e.g. the data plane mirror app tier740ofFIG.7) that can include app subnet(s)826. The app subnet(s)826contained in the data plane mirror app tier840can include a virtual network interface controller (VNIC)842(e.g. the VNIC of742) that can execute a compute instance844(e.g. similar to the compute instance744ofFIG.7). The compute instance844can facilitate communication between the app subnet(s)826of the data plane mirror app tier840and the app subnet(s)826that can be contained in a data plane app tier846(e.g. the data plane app tier746ofFIG.7) via the VNIC842contained in the data plane mirror app tier840and the VNIC842contained in the data plane app tier846.

The Internet gateway834contained in the control plane VCN816can be communicatively coupled to a metadata management service852(e.g. the metadata management service752ofFIG.7) that can be communicatively coupled to public Internet854(e.g. public Internet754ofFIG.7). Public Internet854can be communicatively coupled to the NAT gateway838contained in the control plane VCN816. The service gateway836contained in the control plane VCN816can be communicatively couple to cloud services856(e.g. cloud services756ofFIG.7).

In some examples, the data plane VCN818can be contained in the customer tenancy821. In this case, the IaaS provider may provide the control plane VCN816for each customer, and the IaaS provider may, for each customer, set up a unique compute instance844that is contained in the service tenancy819. Each compute instance844may allow communication between the control plane VCN816, contained in the service tenancy819, and the data plane VCN818that is contained in the customer tenancy821. The compute instance844may allow resources, that are provisioned in the control plane VCN816that is contained in the service tenancy819, to be deployed or otherwise used in the data plane VCN818that is contained in the customer tenancy821.

In other examples, the customer of the IaaS provider may have databases that live in the customer tenancy821. In this example, the control plane VCN816can include the data plane mirror app tier840that can include app subnet(s)826. The data plane mirror app tier840can reside in the data plane VCN818, but the data plane mirror app tier840may not live in the data plane VCN818. That is, the data plane mirror app tier840may have access to the customer tenancy821, but the data plane mirror app tier840may not exist in the data plane VCN818or be owned or operated by the customer of the IaaS provider. The data plane mirror app tier840may be configured to make calls to the data plane VCN818but may not be configured to make calls to any entity contained in the control plane VCN816. The customer may desire to deploy or otherwise use resources in the data plane VCN818that are provisioned in the control plane VCN816, and the data plane mirror app tier840can facilitate the desired deployment, or other usage of resources, of the customer.

In some embodiments, the customer of the IaaS provider can apply filters to the data plane VCN818. In this embodiment, the customer can determine what the data plane VCN818can access, and the customer may restrict access to public Internet854from the data plane VCN818. The IaaS provider may not be able to apply filters or otherwise control access of the data plane VCN818to any outside networks or databases. Applying filters and controls by the customer onto the data plane VCN818, contained in the customer tenancy821, can help isolate the data plane VCN818from other customers and from public Internet854.

In some embodiments, cloud services856can be called by the service gateway836to access services that may not exist on public Internet854, on the control plane VCN816, or on the data plane VCN818. The connection between cloud services856and the control plane VCN816or the data plane VCN818may not be live or continuous. Cloud services856may exist on a different network owned or operated by the IaaS provider. Cloud services856may be configured to receive calls from the service gateway836and may be configured to not receive calls from public Internet854. Some cloud services856may be isolated from other cloud services856, and the control plane VCN816may be isolated from cloud services856that may not be in the same region as the control plane VCN816. For example, the control plane VCN816may be located in “Region 1,” and cloud service “Deployment 7,” may be located in Region 1 and in “Region 2.” If a call to Deployment 7 is made by the service gateway836contained in the control plane VCN816located in Region 1, the call may be transmitted to Deployment 7 in Region 1. In this example, the control plane VCN816, or Deployment 7 in Region 1, may not be communicatively coupled to, or otherwise in communication with, Deployment 7 in Region 2.

FIG.9is a block diagram900illustrating another example pattern of an IaaS architecture, according to at least one embodiment. Service operators902(e.g. service operators702ofFIG.7) can be communicatively coupled to a secure host tenancy904(e.g. the secure host tenancy704ofFIG.7) that can include a virtual cloud network (VCN)906(e.g. the VCN706ofFIG.7) and a secure host subnet908(e.g. the secure host subnet708ofFIG.7). The VCN906can include an LPG910(e.g. the LPG710ofFIG.7) that can be communicatively coupled to an SSH VCN912(e.g. the SSH VCN712ofFIG.7) via an LPG910contained in the SSH VCN912. The SSH VCN912can include an SSH subnet914(e.g. the SSH subnet714ofFIG.7), and the SSH VCN912can be communicatively coupled to a control plane VCN916(e.g. the control plane VCN716ofFIG.7) via an LPG910contained in the control plane VCN916and to a data plane VCN918(e.g. the data plane718ofFIG.7) via an LPG910contained in the data plane VCN918. The control plane VCN916and the data plane VCN918can be contained in a service tenancy919(e.g. the service tenancy719ofFIG.7).

The control plane VCN916can include a control plane DMZ tier920(e.g. the control plane DMZ tier720ofFIG.7) that can include load balancer (LB) subnet(s)922(e.g. LB subnet(s)722ofFIG.7), a control plane app tier924(e.g. the control plane app tier724ofFIG.7) that can include app subnet(s)926(e.g. similar to app subnet(s)726ofFIG.7), a control plane data tier928(e.g. the control plane data tier728ofFIG.7) that can include DB subnet(s)930. The LB subnet(s)922contained in the control plane DMZ tier920can be communicatively coupled to the app subnet(s)926contained in the control plane app tier924and to an Internet gateway934(e.g. the Internet gateway734ofFIG.7) that can be contained in the control plane VCN916, and the app subnet(s)926can be communicatively coupled to the DB subnet(s)930contained in the control plane data tier928and to a service gateway936(e.g. the service gateway ofFIG.7) and a network address translation (NAT) gateway938(e.g. the NAT gateway738ofFIG.7). The control plane VCN916can include the service gateway936and the NAT gateway938.

The data plane VCN918can include a data plane app tier946(e.g. the data plane app tier746ofFIG.7), a data plane DMZ tier948(e.g. the data plane DMZ tier748ofFIG.7), and a data plane data tier950(e.g. the data plane data tier750ofFIG.7). The data plane DMZ tier948can include LB subnet(s)922that can be communicatively coupled to trusted app subnet(s)960and untrusted app subnet(s)962of the data plane app tier946and the Internet gateway934contained in the data plane VCN918. The trusted app subnet(s)960can be communicatively coupled to the service gateway936contained in the data plane VCN918, the NAT gateway938contained in the data plane VCN918, and DB subnet(s)930contained in the data plane data tier950. The untrusted app subnet(s)962can be communicatively coupled to the service gateway936contained in the data plane VCN918and DB subnet(s)930contained in the data plane data tier950. The data plane data tier950can include DB subnet(s)930that can be communicatively coupled to the service gateway936contained in the data plane VCN918.

The untrusted app subnet(s)962can include one or more primary VNICs964(1)-(N) that can be communicatively coupled to tenant virtual machines (VMs)966(1)-(N). Each tenant VM966(1)-(N) can be communicatively coupled to a respective app subnet967(1)-(N) that can be contained in respective container egress VCNs968(1)-(N) that can be contained in respective customer tenancies970(1)-(N). Respective secondary VNICs972(1)-(N) can facilitate communication between the untrusted app subnet(s)962contained in the data plane VCN918and the app subnet contained in the container egress VCNs968(1)-(N). Each container egress VCNs968(1)-(N) can include a NAT gateway938that can be communicatively coupled to public Internet954(e.g. public Internet754ofFIG.7).

The Internet gateway934contained in the control plane VCN916and contained in the data plane VCN918can be communicatively coupled to a metadata management service952(e.g. the metadata management system752ofFIG.7) that can be communicatively coupled to public Internet954. Public Internet954can be communicatively coupled to the NAT gateway938contained in the control plane VCN916and contained in the data plane VCN918. The service gateway936contained in the control plane VCN916and contained in the data plane VCN918can be communicatively couple to cloud services956.

In some examples, the customer of the IaaS provider may grant temporary network access to the IaaS provider and request a function to be attached to the data plane tier app946. Code to run the function may be executed in the VMs966(1)-(N), and the code may not be configured to run anywhere else on the data plane VCN918. Each VM966(1)-(N) may be connected to one customer tenancy970. Respective containers971(1)-(N) contained in the VMs966(1)-(N) may be configured to run the code. In this case, there can be a dual isolation (e.g., the containers971(1)-(N) running code, where the containers971(1)-(N) may be contained in at least the VM966(1)-(N) that are contained in the untrusted app subnet(s)962), which may help prevent incorrect or otherwise undesirable code from damaging the network of the IaaS provider or from damaging a network of a different customer. The containers971(1)-(N) may be communicatively coupled to the customer tenancy970and may be configured to transmit or receive data from the customer tenancy970. The containers971(1)-(N) may not be configured to transmit or receive data from any other entity in the data plane VCN918. Upon completion of running the code, the IaaS provider may kill or otherwise dispose of the containers971(1)-(N).

In some embodiments, the trusted app subnet(s)960may run code that may be owned or operated by the IaaS provider. In this embodiment, the trusted app subnet(s)960may be communicatively coupled to the DB subnet(s)930and be configured to execute CRUD operations in the DB subnet(s)930. The untrusted app subnet(s)962may be communicatively coupled to the DB subnet(s)930, but in this embodiment, the untrusted app subnet(s) may be configured to execute read operations in the DB subnet(s)930. The containers971(1)-(N) that can be contained in the VM966(1)-(N) of each customer and that may run code from the customer may not be communicatively coupled with the DB subnet(s)930.

In other embodiments, the control plane VCN916and the data plane VCN918may not be directly communicatively coupled. In this embodiment, there may be no direct communication between the control plane VCN916and the data plane VCN918. However, communication can occur indirectly through at least one method. An LPG910may be established by the IaaS provider that can facilitate communication between the control plane VCN916and the data plane VCN918. In another example, the control plane VCN916or the data plane VCN918can make a call to cloud services956via the service gateway936. For example, a call to cloud services956from the control plane VCN916can include a request for a service that can communicate with the data plane VCN918.

FIG.10is a block diagram1000illustrating another example pattern of an IaaS architecture, according to at least one embodiment. Service operators1002(e.g. service operators702ofFIG.7) can be communicatively coupled to a secure host tenancy1004(e.g. the secure host tenancy704ofFIG.7) that can include a virtual cloud network (VCN)1006(e.g. the VCN706ofFIG.7) and a secure host subnet1008(e.g. the secure host subnet708ofFIG.7). The VCN1006can include an LPG1010(e.g. the LPG710ofFIG.7) that can be communicatively coupled to an SSH VCN1012(e.g. the SSH VCN712ofFIG.7) via an LPG1010contained in the SSH VCN1012. The SSH VCN1012can include an SSH subnet1014(e.g. the SSH subnet714ofFIG.7), and the SSH VCN1012can be communicatively coupled to a control plane VCN1016(e.g. the control plane VCN716ofFIG.7) via an LPG1010contained in the control plane VCN1016and to a data plane VCN1018(e.g. the data plane718ofFIG.7) via an LPG1010contained in the data plane VCN1018. The control plane VCN1016and the data plane VCN1018can be contained in a service tenancy1019(e.g. the service tenancy719ofFIG.7).

The control plane VCN1016can include a control plane DMZ tier1020(e.g. the control plane DMZ tier720ofFIG.7) that can include LB subnet(s)1022(e.g. LB subnet(s)722ofFIG.7), a control plane app tier1024(e.g. the control plane app tier724ofFIG.7) that can include app subnet(s)1026(e.g. app subnet(s)726ofFIG.7), a control plane data tier1028(e.g. the control plane data tier728ofFIG.7) that can include DB subnet(s)1030(e.g. DB subnet(s)930ofFIG.9). The LB subnet(s)1022contained in the control plane DMZ tier1020can be communicatively coupled to the app subnet(s)1026contained in the control plane app tier1024and to an Internet gateway1034(e.g. the Internet gateway734ofFIG.7) that can be contained in the control plane VCN1016, and the app subnet(s)1026can be communicatively coupled to the DB subnet(s)1030contained in the control plane data tier1028and to a service gateway1036(e.g. the service gateway ofFIG.7) and a network address translation (NAT) gateway1038(e.g. the NAT gateway738ofFIG.7). The control plane VCN1016can include the service gateway1036and the NAT gateway1038.

The data plane VCN1018can include a data plane app tier1046(e.g. the data plane app tier746ofFIG.7), a data plane DMZ tier1048(e.g. the data plane DMZ tier748ofFIG.7), and a data plane data tier1050(e.g. the data plane data tier750ofFIG.7). The data plane DMZ tier1048can include LB subnet(s)1022that can be communicatively coupled to trusted app subnet(s)1060(e.g. trusted app subnet(s)960ofFIG.9) and untrusted app subnet(s)1062(e.g. untrusted app subnet(s)962ofFIG.9) of the data plane app tier1046and the Internet gateway1034contained in the data plane VCN1018. The trusted app subnet(s)1060can be communicatively coupled to the service gateway1036contained in the data plane VCN1018, the NAT gateway1038contained in the data plane VCN1018, and DB subnet(s)1030contained in the data plane data tier1050. The untrusted app subnet(s)1062can be communicatively coupled to the service gateway1036contained in the data plane VCN1018and DB subnet(s)1030contained in the data plane data tier1050. The data plane data tier1050can include DB subnet(s)1030that can be communicatively coupled to the service gateway1036contained in the data plane VCN1018.

The untrusted app subnet(s)1062can include primary VNICs1064(1)-(N) that can be communicatively coupled to tenant virtual machines (VMs)1066(1)-(N) residing within the untrusted app subnet(s)1062. Each tenant VM1066(1)-(N) can run code in a respective container1067(1)-(N), and be communicatively coupled to an app subnet1026that can be contained in a data plane app tier1046that can be contained in a container egress VCN1068. Respective secondary VNICs1072(1)-(N) can facilitate communication between the untrusted app subnet(s)1062contained in the data plane VCN1018and the app subnet contained in the container egress VCN1068. The container egress VCN can include a NAT gateway1038that can be communicatively coupled to public Internet1054(e.g. public Internet754ofFIG.7).

The Internet gateway1034contained in the control plane VCN1016and contained in the data plane VCN1018can be communicatively coupled to a metadata management service1052(e.g. the metadata management system752ofFIG.7) that can be communicatively coupled to public Internet1054. Public Internet1054can be communicatively coupled to the NAT gateway1038contained in the control plane VCN1016and contained in the data plane VCN1018. The service gateway1036contained in the control plane VCN1016and contained in the data plane VCN1018can be communicatively couple to cloud services1056.

In some examples, the pattern illustrated by the architecture of block diagram1000ofFIG.10may be considered an exception to the pattern illustrated by the architecture of block diagram900ofFIG.9and may be desirable for a customer of the IaaS provider if the IaaS provider cannot directly communicate with the customer (e.g., a disconnected region). The respective containers1067(1)-(N) that are contained in the VMs1066(1)-(N) for each customer can be accessed in real-time by the customer. The containers1067(1)-(N) may be configured to make calls to respective secondary VNICs1072(1)-(N) contained in app subnet(s)1026of the data plane app tier1046that can be contained in the container egress VCN1068. The secondary VNICs1072(1)-(N) can transmit the calls to the NAT gateway1038that may transmit the calls to public Internet1054. In this example, the containers1067(1)-(N) that can be accessed in real-time by the customer can be isolated from the control plane VCN1016and can be isolated from other entities contained in the data plane VCN1018. The containers1067(1)-(N) may also be isolated from resources from other customers.

In other examples, the customer can use the containers1067(1)-(N) to call cloud services1056. In this example, the customer may run code in the containers1067(1)-(N) that requests a service from cloud services1056. The containers1067(1)-(N) can transmit this request to the secondary VNICs1072(1)-(N) that can transmit the request to the NAT gateway that can transmit the request to public Internet1054. Public Internet1054can transmit the request to LB subnet(s)1022contained in the control plane VCN1016via the Internet gateway1034. In response to determining the request is valid, the LB subnet(s) can transmit the request to app subnet(s)1026that can transmit the request to cloud services1056via the service gateway1036.

FIG.11illustrates an example computer system1100, in which various embodiments may be implemented. The system1100may be used to implement any of the computer systems described above. As shown in the figure, computer system1100includes a processing unit1104that communicates with a number of peripheral subsystems via a bus subsystem1102. These peripheral subsystems may include a processing acceleration unit1106, an I/O subsystem1108, a storage subsystem1118and a communications subsystem1124. Storage subsystem1118includes tangible computer-readable storage media1122and a system memory1110.

Bus subsystem1102provides a mechanism for letting the various components and subsystems of computer system1100communicate with each other as intended. Although bus subsystem1102is shown schematically as a single bus, alternative embodiments of the bus subsystem may utilize multiple buses. Bus subsystem1102may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. For example, such architectures may include an Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus, which can be implemented as a Mezzanine bus manufactured to the IEEE P1386.1 standard.

Processing unit1104, which can be implemented as one or more integrated circuits (e.g., a conventional microprocessor or microcontroller), controls the operation of computer system1100. One or more processors may be included in processing unit1104. These processors may include single core or multicore processors. In certain embodiments, processing unit1104may be implemented as one or more independent processing units1132and/or1134with single or multicore processors included in each processing unit. In other embodiments, processing unit1104may also be implemented as a quad-core processing unit formed by integrating two dual-core processors into a single chip.

In various embodiments, processing unit1104can execute a variety of programs in response to program code and can maintain multiple concurrently executing programs or processes. At any given time, some or all of the program code to be executed can be resident in processor(s)1104and/or in storage subsystem1118. Through suitable programming, processor(s)1104can provide various functionalities described above. Computer system1100may additionally include a processing acceleration unit1106, which can include a digital signal processor (DSP), a special-purpose processor, and/or the like.

Computer system1100may comprise a storage subsystem1118that comprises software elements, shown as being currently located within a system memory1110. System memory1110may store program instructions that are loadable and executable on processing unit1104, as well as data generated during the execution of these programs.

Storage subsystem1100may also include a computer-readable storage media reader1120that can further be connected to computer-readable storage media1122. Together and, optionally, in combination with system memory1110, computer-readable storage media1122may comprehensively represent remote, local, fixed, and/or removable storage devices plus storage media for temporarily and/or more permanently containing, storing, transmitting, and retrieving computer-readable information.

Communications subsystem1124provides an interface to other computer systems and networks. Communications subsystem1124serves as an interface for receiving data from and transmitting data to other systems from computer system1100. For example, communications subsystem1124may enable computer system1100to connect to one or more devices via the Internet. In some embodiments communications subsystem1124can include radio frequency (RF) transceiver components for accessing wireless voice and/or data networks (e.g., using cellular telephone technology, advanced data network technology, such as 3G, 4G or EDGE (enhanced data rates for global evolution), WiFi (IEEE 802.11 family standards, or other mobile communication technologies, or any combination thereof), global positioning system (GPS) receiver components, and/or other components. In some embodiments communications subsystem1124can provide wired network connectivity (e.g., Ethernet) in addition to or instead of a wireless interface.

In some embodiments, communications subsystem1124may also receive input communication in the form of structured and/or unstructured data feeds1126, event streams1128, event updates1130, and the like on behalf of one or more users who may use computer system1100.

Additionally, communications subsystem1124may also be configured to receive data in the form of continuous data streams, which may include event streams1128of real-time events and/or event updates1130, that may be continuous or unbounded in nature with no explicit end. Examples of applications that generate continuous data may include, for example, sensor data applications, financial tickers, network performance measuring tools (e.g. network monitoring and traffic management applications), clickstream analysis tools, automobile traffic monitoring, and the like.

Communications subsystem1124may also be configured to output the structured and/or unstructured data feeds1126, event streams1128, event updates1130, and the like to one or more databases that may be in communication with one or more streaming data source computers coupled to computer system1100.