Systems and methods for securing network traffic flow in a multi-service containerized application

US10439987B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10439987-B2
Application numberUS-201715619978-A
CountryUS
Kind codeB2
Filing dateJun 12, 2017
Priority dateJun 12, 2017
Publication dateOct 8, 2019
Grant dateOct 8, 2019

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Provided is a method for securing network traffic flow in a multi-service containerized application, including: obtaining, with one or more processors, a composition record defining a multi-service containerized application; analyzing, with one or more processors, the composition record to look for one or both of network traffic patterns and network traffic flow; adding, with one or more processors, to the composition record a configured firewall container definition of a network traffic enforcement container that upon execution of the multi-service containerized application is communicatively coupled between a first container and a second container of the multi-service containerized application, wherein the first container and the second container are configured to communicate with each other across a first virtualized network; and converting, with one or more processors, the first virtualized network between the first container and the second container into a second virtualized network and a third virtualized network.

First claim

Opening claim text (preview).

What is claimed is: 1. A method for securing network traffic flow in a multi-service containerized application, the method comprising: obtaining, with one or more processors, a composition record defining a multi-service containerized application; analyzing, with one or more processors, the composition record to look for one or both of network traffic patterns and network traffic flow; adding, with one or more processors, to the composition record a configured firewall container definition of a network traffic enforcement container that upon execution of the multi-service containerized application is communicatively coupled between a first container and a second container of the multi-service containerized application, wherein the first container and the second container are configured to communicate with each other across a first virtualized network; and converting, with one or more processors, the first virtualized network between the first container and the second container into a second virtualized network and a third virtualized network. 2. The method of claim 1 , wherein obtaining the composition record comprises sending instructions to a client computing device to create canvass elements that represent containers that are part of the application and how the containers are communicatively coupled with each other. 3. The method of claim 1 , wherein analyzing the composition record comprises determining a host name and port number of the second container. 4. The method of claim 3 , further comprising inferring a network traffic flow enforcement pattern from the host name and port number of the second container, wherein the network traffic flow enforcement pattern dictates that information can flow from the first container to the second container, and wherein the network traffic flow enforcement pattern dictates that information cannot flow from the second container to the first container. 5. The method of claim 1 , wherein the second virtualized network and the third virtualized network, upon execution of the multi-service containerized application, are communicatively coupled with the network traffic enforcement container. 6. The method of claim 1 , wherein the network traffic enforcement container acts as a proxy by passing on requests between the first container and the second container by transport-control protocol encapsulation or by modifying a transport or network layer protocol header recipient address in a network packet. 7. The method of claim 1 , wherein the network traffic enforcement container acts as a firewall between the first container and the second container by preventing the second container from accessing the first container. 8. The method of claim 1 , wherein the network traffic enforcement container determines whether to allow the passage of network traffic between the first container and the second container. 9. The method of claim 1 , wherein the network traffic enforcement container is configured to allow network traffic to flow from the first container to the second container. 10. The method of claim 1 , wherein the network traffic enforcement container is configured to prevent network traffic from flowing from the second container to the first container. 11. The method of claim 1 , further comprising inferring from dependency information collected from the composition record that the first container is configured to communicate with the second container at a given port associated with the second container. 12. The method of claim 1 , wherein the multi-service containerized application is a Linux multi-service containerized application. 13. The method of claim 12 , wherein the network traffic enforcement container has a Linux iptable configuration. 14. The method of claim 13 , wherein the Linux iptable configuration allows some network traffic flow and disallows other network traffic flow. 15. The method of claim 1 , wherein network traffic policies and direction of network traffic flow are enforced with no user input required. 16. The method of claim 1 , wherein securing network traffic flow comprises determining whether network traffic flow from a second container to a first container should be allowed or disallowed. 17. A tangible, non-transitory, machine-readable medium storing instructions that when executed by one or more computers effectuate operations comprising: obtaining, with one or more processors, a composition record defining a multi-service containerized application; analyzing, with one or more processors, the composition record to look for one or both of network traffic patterns and network traffic flow; adding, with one or more processors, to the composition record a configured firewall container definition of a network traffic enforcement container that upon execution of the multi-service containerized application is communicatively coupled between a first container and a second container of the multi-service containerized application, wherein the first container and the second container are configured to communicate with each other across a first virtualized network; and converting, with one or more processors, the first virtualized network between the first container and the second container into a second virtualized network and a third virtualized network. 18. The medium of claim 17 , wherein defining the composition record comprises sending instructions to a client computing device to create canvass elements that represent containers that are part of the application and how the containers are communicatively coupled with each other. 19. The medium of claim 17 , wherein analyzing the composition record comprises determining a host name and port number of the second container. 20. A method for securing network traffic flow in a multi-service containerized application, the method comprising: obtaining, with one or more processors, a composition record defining a multi-service containerized application; analyzing, with one or more processors, the composition record to look for one or both of network traffic patterns and network traffic flow; adding, with one or more processors, to the composition record a configured firewall container definition of a network traffic enforcement container that upon execution of the multi-service containerized application is communicatively coupled between a first container and a second container of the multi-service containerized application, wherein the first container and the second container are configured to communicate with each other across a first virtualized network; and converting, with one or more processors, the first virtualized network between the first container and the second container into a second virtualized network and a third virtualized network, wherein obtaining the composition record comprises sending instructions to a client computing device to create canvass elements that represent containers that are part of the application and how the containers are communicatively coupled with each other, and wherein the second virtualized network and the third virtualized network, upon execution of the multi-service containerized application, are communicatively coupled with the network traffic enforcement container.

Assignees

Inventors

Classifications

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10439987B2 cover?
Provided is a method for securing network traffic flow in a multi-service containerized application, including: obtaining, with one or more processors, a composition record defining a multi-service containerized application; analyzing, with one or more processors, the composition record to look for one or both of network traffic patterns and network traffic flow; adding, with one or more proces…
Who is the assignee on this patent?
Ca Inc
What technology area does this patent fall under?
Primary CPC classification H04L63/0263. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Oct 08 2019 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 11 related publications on this page (citations in our corpus or others sharing the same primary CPC).