Data Scope

Netify deployments range from a single office location, to large distributed enterprises, to core ISP networks and more. We separate these different types of deployments into three categories:

  • Cloud network: AWS, Google Cloud Platform, etc.
  • Core network: ISP, mobile operator, MVNO, etc.
  • Edge network: offices, schools, retail locations, etc.

In order to accommodate the various types of deployments, the Netify network information and intelligence data are organized into different data hierarchies.

Scope - Core and Cloud Networks

For deployments on core and cloud networks, we work with clients to find data solutions to meet their needs. For example, Netify Informatics deployed at mobile operators have been organized by:

  • Subscriber
  • Data center
  • Customer type (business vs residential)

Please contact us for solutions to meet the needs of your network.

Scope - Edge Network

For deployments at the edge of the network, we have created a hierarchical data structure. Let's walk through an example. Imagine the scenario where Acme Company has two office locations:

  • Toronto
  • Ottawa

To get full network visibility, these two medium-sized offices have deployed two Netify agents across their local networks:

  • 1st and 2nd floor in Toronto
  • East and west wings in Ottawa

For smaller offices, only one agent would be required.

Netify Data Scope

Organizations - x-net-organization

At the top-level, we have our Organization called Acme Company. Owner and device information about a specific laptop is stored at the organization level so that we can track its movement from one office location (Toronto) to another (Ottawa).

By default, Netify stores certain types of data at the organization level:

  • Devices and MAC addresses
  • Owners
  • Groups
  • Performance scores
  • Security scores
  • Events

API endpoints that provide data at the organization level require the x-net-organization parameter in the REST header request. For example, to get a list of all detected MAC addresses in an organization, the API call would like:

curl --header 'x-net-organization: 00000000_0000_0000_0000_000000000000' ....

Sites - x-net-site

When dealing with forensics, we need to keep track of the metadata of every single network conversation... that's a lot of data! This data is used by the Netify Intelligence engine to generate bandwidth summaries, performance scores, security scores, and alerts. However, sometimes an end user will need to make a deep dive into the network details.

  • Details on specific connections
  • Drill-down information on specific device over a span of a specific hour

API endpoints that provide data at the site level require the x-net-site parameter in the REST header request. For example, a list of the top DNS queries from a specific mobile device can be fetched from the API.

Integration and Custom Solutions

Do you have any questions about integration, APIs or custom development?

Contact Us