3rd party data explorer

1. A third party data management system, comprising:

a processing circuit configured to:

receive, from a source computing system and via a cybersecurity correlation and analytics computing system, first third party activity data;

extract an identifier from the first third party activity data, wherein the identifier is extracted from at least one of a header, footer, metadata, or payload portion of a traffic packet;

correlate the identifier to at least a portion of an item of an entity profile;

based on the item extracted from the first third party activity data, determine a computing entity external to the third party data management system associated with the first third party activity data and the identifier;

periodically monitor third party activity on a plurality of data channels associated with the computing entity, comprising operations to collect second third party activity data, wherein the computing entity is communicatively coupled to the source computing system, and wherein the operations to collect comprise querying or accessing the plurality of data channels; and

correlate the monitored second third party activity data to an entity profile.

2. The third party data management system of claim 1 , wherein the computing entity comprises the source computing system.

3. The third party data management system of claim 1 , wherein the source computing system is at least one of a proxy server, an email server, an endpoint, a network server, a firewall server, or an extranet server.

4. The third party data management system of claim 1 , wherein the processing circuit is communicatively coupled to a database comprising a system of records retrievably storing a plurality of data points associated with a plurality of third party entities, and wherein at least one in the plurality of data points represents a policy associated with the monitored third party activity, the processing circuit being further configured to correlate the monitored third party activity to the policy.

5. The third party data management system of claim 1 , wherein the processing circuit is further configured to identify an unknown computing entity external to the third party data management system associated with the first third party activity data, comprising operations to:

wherein the identifier comprises at least one of a cookie, a unique code, a public/private key, a user name, an active directory handle, a social media handle, an email address, and a financial account identifier;

wherein correlating comprises cross-reference the identifier to at least the portion of the item extracted from the entity profile; and

based on the cross-referencing, determine that the identifier does not match any records in the entity profile.

6. The third party data management system of claim 5 , wherein the processing circuit is further configured to:

generate a notification comprising the identifier; and

transmit the notification to an administrator associated with the entity profile.

7. The third party data management system of claim 1 , wherein the processing circuit is further configured to generate a user interface comprising a graphical representation of the entity profile.

8. A method of managing third party data, comprising:

receiving, by a processing circuit of a third party data management system, first third party activity data from a source computing system and via a cybersecurity correlation and analytics computing system;

extracting, by the processing circuit of the third party data management system, an identifier from the first third party activity data, wherein the identifier is extracted from at least one of a header, footer, metadata, or payload portion of a traffic packet;

correlating, by the processing circuit of the third party data management system, the identifier to at least a portion of an item of an entity profile;

determining, by the processing circuit of the third party data management system, a computing entity external to the third party data management system associated with the first third party activity data based on the item extracted from the first third party activity data and the identifier;

monitoring, periodically by the processing circuit of the third party data management system, third party activity on a plurality of data channels associated with the computing entity, comprising operations to collect second third party activity data, wherein the computing entity is communicatively coupled to the source computing system, and wherein the operations to collect comprise querying or accessing the plurality of data channels; and

correlating, by the processing circuit of the third party data management system, the monitored second third party activity data to an entity profile.

9. The method of claim 8 , wherein the computing entity comprises the source computing system.

10. The method of claim 8 , wherein the computing entity is communicatively coupled to the source computing system.

11. The method of claim 8 , wherein the source computing system is at least one of a proxy server, an email server, an endpoint, a network server, a firewall server, or an extranet server.

12. The method of claim 8 , wherein the processing circuit is communicatively coupled to a database comprising a system of records retrievably storing a plurality of data points associated with a plurality of third party entities, and wherein at least one in the plurality of data points represents a policy associated with the monitored third party activity, the processing circuit being further configured to correlate the monitored third party activity to the policy.

13. The method of claim 8 , wherein the processing circuit is further configured to identify an unknown computing entity external to the third party data management system associated with the first third party activity data, comprising:

wherein the identifier comprises at least one of a cookie, a unique code, a public/private key, a user name, an active directory handle, a social media handle, an email address, and a financial account identifier;

wherein correlating comprises cross-referencing the identifier to at least the portion of the item extracted from the entity profile; and

based on the cross-referencing, determining that the identifier does not match any records in the entity profile.

14. The method of claim 13 , wherein the processing circuit is further configured to perform operations comprising:

generating a notification comprising the identifier; and

transmitting the notification to an administrator associated with the entity profile.

15. One or more non-transitory computer readable media storing instructions that, when executed by a processor, causes the processor to perform operations for managing third party data, the operations comprising:

receiving, by a processing circuit of a third party data management system, first third party activity data from a source computing system and via a cybersecurity correlation and analytics computing system;

extracting, by the processing circuit of the third party data management system, an identifier from the first third party activity data, wherein the identifier is extracted from at least one of a header, footer, metadata, or payload portion of a traffic packet;

correlating, by the processing circuit of the third party data management system, the identifier to at least a portion of an item of an entity profile;

determining, by the processor of the third party data management system, the first third party activity data;

determining, by the processing circuit of the third party data management system, a computing entity external to the third party data management system associated with the first third party activity data based on the item extracted from the first third party activity data and the identifier;

monitoring, periodically by the processing circuit of the third party data management system, third party activity on a plurality of data channels associated with the computing entity, comprising operations to collect second third party activity data, wherein the computing entity is communicatively coupled to the source computing system, and wherein the operations to collect comprise querying or accessing the plurality of data channels; and

correlating, by the processing circuit of the third party data management system, the monitored second third party activity data to an entity profile.

16. The one or more non-transitory computer readable media of claim 15 , wherein the computing entity comprises the source computing system.

17. The one or more non-transitory computer readable media of claim 15 , wherein the computing entity is communicatively coupled to the source computing system.

18. The one or more non-transitory computer readable media of claim 15 , wherein the source computing system is at least one of a proxy server, an email server, an endpoint, a network server, a firewall server, or an extranet serve.

19. The one or more non-transitory computer readable media storing instructions of claim 15 , wherein the processing circuit is communicatively coupled to a database comprising a system of records retrievably storing a plurality of data points associated with a plurality of third party entities, and wherein at least one in the plurality of data points represents a policy associated with the monitored third party activity, the processing circuit being further configured to correlate the monitored third party activity to the policy.