API
REST API and Swagger/OpenAPI
Use documented API definitions for exposed programmatic workflows and data access.
Interfaces and named integrations
Connect supported evidence without inventing a generic integration story.
Cyobik exposes a documented REST API and includes named Nessus and Splunk integrations. Discovery adapters remain a separate capability.
Supported today
Three explicit integration paths.
NESSUS
Nessus integration
Connect multiple Nessus instances, retrieve results on schedule and assign findings to corresponding assets.
SPLUNK
Splunk App
Allow authorised Splunk users to access exposed Cyobik data inside Splunk for the documented workflow.
Adapter model
FortiGate is a discovery and inventory adapter.
FortiGate connectivity is used through supported adapter logic to collect discovery or inventory evidence. It must not be presented as a generic bidirectional integration.
Data onboarding
Agents and file import are collection paths.
Push Based agents, Pull Based adapters and validated file import populate the asset model. They are not equivalent to generic SIEM, SOAR, EDR, NDR or ITSM connectors.
Integration discipline
Use precise claims that implementation teams can defend.
| Claim | Current status | How to describe it |
|---|---|---|
| REST API | Available today | Documented through Swagger/OpenAPI. |
| Nessus | Available today | Named integration with scheduled retrieval and asset matching. |
| Splunk | Available today | Named app exposing Cyobik data within Splunk. |
| FortiGate | Available as adapter | Discovery/inventory adapter, not bidirectional integration. |
| Generic SIEM/SOAR/EDR/NDR/ITSM | Not supported as a generic claim | Do not publish without a named documented connector. |
No generic ecosystem claim
Current product documentation does not support broad claims that Cyobik integrates with any SIEM, SOAR, EDR, NDR, Jira or ITSM platform. External content should name only documented connectors and describe each one within its actual scope.
Validate your required data sources before the demo.
Share the scanners, network devices and operational systems in scope so the discussion stays grounded in supported adapters, APIs and named integrations.