The first dozen questions every Utelogy customer asks about CybrIQ.
Procurement, deployment, integrator role, what changes in the AV team’s day, what the CISO actually receives. If your question isn’t below, the contact page goes directly to a human.
The partnership
Is this a single product or two?
Two. Utelogy and CybrIQ remain independent companies with independent contracts. The pairing is operational: the two products read the same physical surface (managed switches) and exchange context in customer-installed components. There is no joint SKU and no merged company.
Do I have to buy both?
No. Each product stands on its own. Many customers run one of the two and add the second when an adjacent driver shows up (cyber-insurance renewal, audit cycle, NDAA Section 889 walkthrough, room-modernization project). The combined-savings calculator separates the levers so you can evaluate each side independently.
Who is my contract with?
You contract with each vendor separately. Most customers route both through the same integrator on the account, which collapses the procurement conversation into one without changing the contractual structure.
Deployment and integration
Does the integration require a vendor cloud?
No. The Both Utelogy and CybrIQ support cloud-default deployments and on-premise deployments. For regulated environments that require no vendor cloud in the path, both vendors offer fully customer-installed shapes.
What switch access does CybrIQ need?
Read-only switch access via SNMP. No SNMP write, no SPAN port, no mirror port, no inline tap. The same switch infrastructure Utelogy already touches.
Does Utelogy install agents on AV endpoints?
Utelogy uses an agent where the endpoint supports one and manufacturer APIs where it does not. CybrIQ does not place agents on AV endpoints for the primary feature; identification is from switch-side signals. The optional CybrIQ USB-protection workstation agent is separate and opt-in.
How long does the combined install take?
For an existing Utelogy customer adding CybrIQ: typically four weeks from credentials handoff to first signed inventory export. For a greenfield combined rollout: see the integrator-coordinated timeline. Both can run on the same change-management window.
Compliance, audit, and insurance
Which compliance frameworks does the pairing support?
The device-inventory side supports NIST SP 800-53 Rev. 5 (CM-8 family, SI-4), NIST SP 800-171 (3.4.1, 3.4.6), NIST CSF 2.0 (ID.AM-1, ID.AM-2, DE.CM-7), CMMC 2.0 L2, NDAA Section 889, FISMA, SOC 2 Type II, ISO/IEC 27001, and the cyber-insurance hardware-inventory question on the 2026 form. CybrIQ holds SOC 2 Type II, ISO 27001, ISO 27017, and ISO 27018 certifications. CybrIQ does not hold FedRAMP authorization.
Will this lower my cyber-insurance premium?
The renewal application now requires documented hardware-inventory evidence with a current date. CybrIQ produces that artifact. Whether the premium moves depends on claims history, the underwriter's portfolio, and the broader controls package. The combined calculator uses a conservative 5% premium-savings assumption; actual results vary.
Can I get the signed exports for an in-progress audit?
Yes. CybrIQ produces signed CSV / JSON exports at the control plane with a SHA-256 hash. The export format is structured for SSP attachments, POA&M references, and direct eMASS uploads in federal environments.
Voice and limits
Is the pairing a replacement for NAC or SIEM?
No. Both tools feed the NAC and SIEM via standard wire formats (RFC 5424 syslog and REST). The NAC enforces. The SIEM correlates. The pairing supplies the upstream identity and operational context.
What is the pairing not good at?
It is not an EDR or XDR. Software-layer attacks, identity-based attacks, credential theft, and network-traffic anomaly detection are outside scope. It is not a vulnerability scanner. It is not a packet-capture or DPI tool on the CybrIQ side. Naming the gaps is part of the honest pitch.