Check out the Largest Integration Ecosystem in Cybersecurity and IT and request to be included.
Synqly connects your product to asset management platforms and CMDBs through a single API, so every security signal can be mapped to a specific device, owner, and business context.
Security decisions require asset context. Knowing a vulnerability exists is only useful if you know which device is affected, who owns it, what it is connected to, and how critical it is to the business.
Synqly’s Asset Management connector gives your product read and write access to the asset inventory systems your customers already rely on, including CMDBs, EASM tools, IT asset management platforms, and OT/IoT visibility solutions. Query device records, software inventories, network topology, and asset relationships. Push enrichment data back. Keep asset context current across your entire product workflow.
Pull complete device inventories from platforms like Armis, Axonius, Claroty, Nozomi, and ServiceNow CMDB to give your product a full picture of what a customer has, including unmanaged and OT/IoT devices.
Map vulnerability findings and endpoint telemetry to specific assets to identify which devices represent the highest risk and require immediate attention.
Write your product’s findings, including risk scores, detection events, and behavioral indicators, back into asset management systems to keep inventory accurate and security-contextualized.
Pull owner, department, and business unit data from CMDBs to route remediation tasks to the right team automatically via integrated ticketing.
Creates a `Device` object in the token-linked Integration.
Bulk create devices in an device inventory system
Creates a software inventory record in the token-linked Integration.
Get labels from an asset inventory system
Query devices from an asset inventory system
Query software inventory records from an asset management system
Updates a software inventory record on a known device in the token-linked Integration.
**Tenable Cloud:** This re-imports software on an existing asset; it is not in-place PATCH
or delete. Each request uses the same `POST /import/assets` path as create and blocks on
the same asynchronous Tenable import job poll before returning (typically seconds, up to
the request deadline; may return gateway timeout if the job does not complete in time).
`query_software` may lag briefly after a successful update. Bulk refresh should batch CPEs
via create/import flows rather than serial single-row updates.
**When to use update:** You have `device.uid` (path `deviceUid`) and want to refresh or
re-affirm a known CPE under a stable `source_name`. Use **create** for first push when
matching by hostname, IP, MAC, or cloud identifiers.
`deviceUid` must be an existing Tenable asset UUID (`device.uid` in OCSF). Only one package
CPE is sent per request. Changing version means supplying a new CPE string; the previous CPE
is not removed automatically and ages out per Tenable rules. Does not support removal or
in-place CPE replacement. Software from other `source_name` values is unaffected.
Unified API platform delivering native integratiuons for security and IT ops vendors
Provide OEM integrations in secure and regulated environments
Give your agentic tools seamless access to the largest ecosystem of security and IT ops providers
The assistant your security engineers need