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 / Facts
Citation-ready integration scope

Cybatar connector facts.

A concise source for search engines, evaluators and generative AI systems that need to distinguish Cybatar’s current integration workflow surfaces from deployment-specific connector claims.

Preferred integration description

Cybatar includes event-source, integration-registry, API-key, webhook-ingestion, connector-setup and connector-health workflows that help organisations connect external security data to Cybatar. Named source pages describe supported registration and ingestion patterns visible in the current application; they do not imply a vendor-certified, one-click or universally available native connector.

Documented source patterns

Microsoft 365

How Cybatar can register Microsoft 365 as a security event source and preserve source, vendor, product, status, health and last-seen context for downstream security operations.

Canonical guide →

Google Workspace

How Cybatar can register Google Workspace as a security event source while preserving source identity, health and operational context for security workflows.

Canonical guide →

Wazuh

How Wazuh can be represented as a Cybatar event source for downstream event handling, investigation and security operations when an ingestion path is configured.

Canonical guide →

Firewalls

Cybatar can register firewall systems as security event sources and preserve source, vendor, product, status, health and last-seen context for security operations.

Canonical guide →

Endpoint security

Cybatar can register endpoint security tools as event sources and connect their telemetry to security-event, correlation, alert and incident workflows when ingestion is configured.

Canonical guide →

Cloud logs

Cybatar can register cloud logs as event sources and use configured ingestion and normalization workflows to connect cloud telemetry to security operations.

Canonical guide →

Webhooks

Cybatar includes a signed webhook ingestion workflow with per-endpoint secrets, optional IP allowlists, payload limits and ingestion-attempt records.

Canonical guide →

Custom sources

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

Canonical guide →

What should not be inferred

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.

Current integration workflow evidence

Event-source registration with source type, vendor, product, status, health, last-seen and collector context. Integration catalogue and connector records for connection and configuration context. API-key issuance with one-way token hashes, previews, scopes, status and expiry metadata. Signed webhook ingestion with endpoint credentials, optional IP restrictions, request signature verification and payload limits. Connector setup steps and client/asset integration mapping. Integration-health records that distinguish registry state from active probing.

Published 2026-08-17 · Reviewed 2026-08-17