NetOp collects network data through two independent paths that feed the same platform. Neither requires opening an inbound firewall rule. This article explains how each path works, what data lands in the platform, and how it is protected.
The two collection paths
The agent path. The NetOp Agent runs on a host inside your network and polls devices directly for performance metrics, interface configuration, inventory, and alerts. It reaches equipment that vendor cloud consoles do not cover — traditional switching, routing, and anything polled over SNMP.
The agent opens an outbound HTTPS connection to the NetOp cloud. Nothing connects inward to it, so no inbound firewall rules, VPN tunnels, or exposed services are required.
The API path. The NetOp cloud service calls your vendor cloud controllers directly, cloud to cloud — Cisco Meraki, Fortinet FortiManager and FortiGate Cloud, VMware VeloCloud SD-WAN, Ubiquiti UniFi, and others. The agent is not involved. You generate a read-only API token in the vendor console and provide it to NetOp. No additional infrastructure is deployed, because the vendor already holds the data.
Knowing which path serves a given device matters when you troubleshoot a collection problem: an agent-path failure and an API-path failure have entirely different causes.
Where processing happens
The NetOp cloud platform runs in us-central1 as multi-tenant SaaS with logical tenant isolation. Your data sits in a dedicated tenant database, and correlation, anomaly detection, and root-cause analysis all run there.
What is collected
- Device inventory and network topology
- Interface metrics and wireless infrastructure
- SD-WAN tunnel health and firmware versions
- Configuration metadata, alerts, and events
Exactly which fields arrive depends on the vendor platform and what its API exposes, so coverage varies between integrations.
NetOp cannot change your configuration
This is worth stating plainly, because it is the most common question during security review:
- Every API integration is strictly read-only. NetOp cannot modify configurations, policies, or operational settings on any connected platform.
- You create the API token in your vendor console and control its scope. NetOp does not request administrative access.
- Tokens are held in an encrypted credential vault and used only for inventory sync, monitoring, and analytics.
- Revoking the token in the vendor console stops collection immediately.
Storage and retention
Data is encrypted in transit and at rest. Default retention is 30 days unless your contract specifies otherwise; longer retention is available through your account team. If the service is terminated, data is permanently deleted.
Access control
Multi-factor authentication is supported, and single sign-on with SAML integration is available. Connecting your own identity provider means your existing access rules apply and joiners and leavers are handled through your IdP rather than a separate user list — which is the arrangement we recommend for any team above a handful of people.
Compliance and AI privacy
NetOp is SOC 2 compliant, with periodic independent penetration testing, documented vulnerability management, and a documented incident response process that includes customer notification.
Your data is never used to train third-party AI models and stays within your tenant.
Related articles
- Connecting an integration
- Onboarding checklist for a new customer
Comments
0 comments
Please sign in to leave a comment.