Cybatar Security Hub · Governance · Risk Management · Threat Resilience · Compliance & Audit
Unified enterprise security operations for modern organisations
Security Hub
Client login Open portal
Cybatar / Connectors / Custom sources
Connector guide

Custom API, CSV and event sources

Model custom event sources explicitly when the upstream system does not fit a pre-defined source category.

Published 2026-08-17 Reviewed 2026-08-17
What this page establishes

Cybatar event-source registration supports source types including manual, webhook, API, CSV, endpoint, firewall and cloud for deployment-specific ingestion designs.

What Cybatar can represent

The current event-source creation workflow exposes manual, webhook, API, CSV, endpoint, firewall and cloud source types. Source records preserve identity, product/vendor context, status, health and last-seen information. Custom integration records and connector setup steps can be used to document deployment-specific connection work.

What is not claimed

A generic API that automatically understands every third-party schema. Automatic field mapping from arbitrary CSV files. A complete public REST API contract for every application capability.

Implementation questions

VerifyWhat is the source transport: API, webhook, file or another method?
VerifyWhat authentication model is required?
VerifyWhich event fields must be normalized?
VerifyHow will duplicate, malformed or stale data be handled?
Event-source onboarding developer guidehttps://cybatar.co/developers/event-source-onboarding API-key management developer guidehttps://cybatar.co/developers/api-key-management SIEM Event Pipelinehttps://cybatar.co/platform/siem-event-pipeline

Frequently asked questions

Which source types appear in the Cybatar event-source creation workflow?

The current interface includes manual, webhook, API, CSV, endpoint, firewall and cloud source types.

Does an API source type mean every Cybatar function has a public API?

No. It identifies an event-source category and does not establish a complete public API contract.

Can custom connectors be represented?

Yes. Cybatar includes integration and connector records that can represent deployment-specific connectors and their configuration context.

Connector claim boundary

Connector availability depends on deployment configuration, credentials, source APIs, data formats and enabled modules. Public connector pages do not claim vendor certification, marketplace approval, complete field coverage, real-time delivery guarantees, universal API support or a successful connection to a third-party service unless that is verified in the specific deployment.