Systems, methods, and devices for securely managing network connections
AssigneeSnowflake Inc.
InventorsJames Calvin Armstrong, Jonathan Claybaugh
Life of this patent
Estimating the term…
Abstract
The disclosure relates generally to methods, systems, and apparatuses for managing network connections. A method may include identifying a first state of a first endpoint connection of a first networked machine and a second state of a second endpoint connection of a second network machine, and confirming the first state and the second state based on expected states for the first networked machine and the second network machine, wherein the expected states comprise a list of expected connections.
Claims27
A method comprising:
- storing a list of expected connections among a plurality of endpoints, wherein each expected connection In the list defines a first endpoint and a second endpoint between which the expected connection exists;
- and
- for each of the expected connections in the list:
- determining, by one or more processors, whether an actual connection exists between the first endpoint of the expected connection and the second endpoint of the expected connection based on a comparison of the expected connection with a configuration file of each of the first and second endpoint of the expected connection;
- if the actual connection does not exist, providing a notification indicating either that the expected connection is missing from a configuration file of one or more of the first endpoint and the second endpoint or that an entry in a configuration file of one or more of the first endpoint and the second endpoint is missing from the list of expected connections, wherein a determination of whether one or more of the actual connections maintained by the plurality of endpoints are unauthorized is based on one or more detected differences between the list of expected connections and the actual connections maintained by the plurality of endpoints.
A system comprising:
- a memory to store a list of expected connections among a plurality of endpoints, wherein each expected connection in the list defines a first endpoint and a second endpoint between which the expected connection exists;
- and
- one or more hardware processors operatively coupled to the memory, the one or more processors to:
- for each of the expected connections in the list:
- determine whether an actual connection exists between the first endpoint of the expected connection and a second endpoint of the expected connection based on a comparison of the expected connection with a configuration file of each of the first and second endpoint of the expected connection;
- if the actual connection does not exist, provide a notification indicating either that the expected connection is missing from a configuration file of one or more of the first endpoint and the second endpoint, or that an entry in the configuration file of one or more of the first endpoint and the second endpoint is missing from the list of expected connections, wherein a determination of whether one or more of the actual connections maintained by the plurality of endpoints are unauthorized is based on one or more detected differences between the list of expected connections and the actual connections maintained by the plurality of endpoints.
A non-transitory computer readable storage media storing instructions that, when executed by one or more hardware processors, cause the one or more hardware processors to:
- store a list of expected connections among a plurality of endpoints, wherein each expected connection in the list defines a first endpoint and a second endpoint between which the expected connection exists;
- for each of the expected connections in the list:
- determine, by the one or more processors, whether an actual connection exists between the first endpoint of the expected connection and a second endpoint of the expected connection based on a comparison of the expected connection with a configuration file of each of the first and second endpoint of the expected connection;
- if the actual connection does not exist, provide a notification indicating either that the expected connection is missing from a configuration file of one or more of the first endpoint and the second endpoint or that an entry in the configuration file of one or more of the first endpoint and the second endpoint is missing from the list of expected connections, wherein a determination of whether one or more of the actual connections maintained by the plurality of endpoints are unauthorized is based on one or more detected differences between the list of expected connections and the actual connections maintained by the plurality of endpoints.
Dependencies are inferred from the claim text.