Securely managing network connections

1. A method comprising:

receiving one or more messages from a plurality of endpoints of a network, the one or more messages comprising information from configuration files of the plurality of endpoints indicating actual connections among the plurality of endpoints of the network;

comparing, by one or more processors, a list of expected connections among a plurality of endpoints of the network with one or more of the actual connections indicated by the configuration files of the plurality of endpoints to determine one or more differences between the list of expected connections and the actual connections, wherein the expected connections are indicated by a connections master file storing information for the plurality of endpoints of the network; and

updating, by the one or more processors, at least one of the configuration files associated with at least one of the plurality of endpoints to reflect the one or more differences detected between the list of expected connections and the actual connections.

2. The method of claim 1 , further comprising:

providing a notification indicating the one or more differences between the list of expected connections and the actual connections among the plurality of endpoints.

3. The method of claim 1 , wherein each expected connection in the list defines a first endpoint and a second endpoint between which the expected connection exists.

4. The method of claim 1 , wherein the one or more differences comprise:

a number of the actual connections among the plurality of endpoints that are missing from the list of expected connections; and

a number of the expected connections from the list of expected connections that are missing a corresponding actual connection.

5. The method of claim 4 , wherein each of the one or more differences indicates an unauthorized connection or an inaccuracy of the list of expected connections.

6. The method of claim 4 , wherein comparing the list of expected connections with the actual connections comprises determining whether each expected connection in the list of expected connections has a matching connection among the one or more actual connections indicated by configuration files of a first endpoint and a second endpoint between which the expected connection exists.

7. The method of claim 1 , wherein each of the actual connections among the plurality of endpoints comprises a protocol, a port number, a port number range, or a security group.

8. The method of claim 1 , wherein the list of expected connections is stored in human readable data-serialization language format.

9. The method of claim 1 , further comprising providing version tracking and control of the list of expected connections.

10. The method of claim 1 , wherein updating the at least one of the configuration files of the plurality of endpoints comprises adding an indication of an actual connection to the at least one of the configuration files or removing an indication of an actual connection from the at least one of the configuration files.

11. A system comprising:

a memory comprising instructions; and

one or more processors operatively coupled to the memory to execute the instructions, wherein the instructions cause the one or more processors to:

receive one or more messages from a plurality of endpoints of a network, the one or more messages comprising information from configuration files of the plurality of endpoints indicating actual connections among the plurality of endpoints of the network;

compare, by one or more processors, a list of expected connections among a plurality of endpoints of the network with one or more of the actual connections indicated by the configuration files of the plurality of endpoints to determine one or more differences between the list of expected connections and the actual connections, wherein the expected connections are indicated by a connections master file storing information for the plurality of endpoints of the network; and

update at least one of the configuration files associated with at least one of the plurality of endpoints to reflect the one or more differences detected between the list of expected connections and the actual connections.

12. The system of claim 11 , wherein the one or more processors are further to:

provide a notification indicating the one or more differences between the list of expected connections and the actual connections among the plurality of endpoints.

13. The system of claim 11 , wherein each expected connection in the list defines a first endpoint and a second endpoint between which the expected connection exists.

14. The system of claim 11 , wherein the one or more differences comprise:

a number of the actual connections among the plurality of endpoints that are missing from the list of expected connections; and

a number of the expected connections from the list of expected connections that are missing a corresponding actual connection.

15. The system of claim 14 , wherein each of the one or more differences indicates an unauthorized connection or an inaccuracy of the list of expected connections.

16. The system of claim 14 , wherein to compare the list of expected connections with the actual connections, the one or more processors are to:

determine whether each expected connection in the list of expected connections has a matching connection among the one or more actual connections indicated by configuration files of a first endpoint and a second endpoint between which the expected connection exists.

17. The system of claim 11 , wherein each of the actual connections among the plurality of endpoints comprises a protocol, a port number, a port number range, or a security group.

18. The system of claim 11 , wherein the list of expected connections is stored in human readable data-serialization language format.

19. The system of claim 11 , further comprising providing version tracking and control of the list of expected connections.

20. The system of claim 11 , wherein to update the at least one of the configuration file of the plurality of endpoints the one or more processors are to:

add an indication of an actual connection to the at least one of the configuration files or remove an indication of an actual connection from the at least one of the configuration files.

21. A non-transitory computer readable medium having instructions stored thereon which, when executed by one or more processors, cause the one or more processors to:

receive one or more messages from a plurality of endpoints of a network, the one or more messages comprising information from configuration files of the plurality of endpoints indicating actual connections among the plurality of endpoints of the network;

compare, by one or more processors, a list of expected connections among a plurality of endpoints of the network with one or more of the actual connections indicated by the configuration files of the plurality of endpoints to determine one or more differences between the list of expected connections and the actual connections, wherein the expected connections are indicated by a connections master file storing information for the plurality of endpoints of the network; and

update at least one of the configuration files associated with at least one of the plurality of endpoints to reflect the one or more differences detected between the list of expected connections and the actual connections.

22. The non-transitory computer readable medium of claim 21 , wherein the one or more processors are further to:

provide a notification indicating the one or more differences between the list of expected connections and the actual connections among the plurality of endpoints.

23. The non-transitory computer readable medium of claim 21 , wherein each expected connection in the list defines a first endpoint and a second endpoint between which the expected connection exists.

24. The non-transitory computer readable medium of claim 21 , wherein the one or more differences comprise:

a number of the actual connections among the plurality of endpoints that are missing from the list of expected connections; and

a number of the expected connections from the list of expected connections that are missing a corresponding actual connection.

25. The non-transitory computer readable medium of claim 24 , wherein each of the one or more differences indicates an unauthorized connection or an inaccuracy of the list of expected connections.

26. The non-transitory computer readable medium of claim 24 , wherein to compare the list of expected connections with the actual connections, the one or more processors are to:

determine whether each expected connection in the list of expected connections has a matching connection among the one or more actual connections indicated by configuration files of a first endpoint and a second endpoint between which the expected connection exists.

27. The non-transitory computer readable medium of claim 21 , wherein each of the actual connections among the plurality of endpoints comprises a protocol, a port number, a port number range, or a security group.

28. The non-transitory computer readable medium of claim 21 , wherein the list of expected connections is stored in human readable data-serialization language format.

29. The non-transitory computer readable medium of claim 21 , further comprising providing version tracking and control of the list of expected connections.

30. The non-transitory computer readable medium of claim 21 , wherein to update the at least one of the configuration file of the plurality of endpoints the one or more processors are to:

add an indication of an actual connection to the at least one of the configuration files or remove an indication of an actual connection from the at least one of the configuration files.