Microsoft 365 security event source
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.
View connector guideCybatar / Connectors
Integration discovery
Security connectors and event-source patterns.
Cybatar can register external systems as security event sources and connect configured data to SIEM, investigation, incident and reporting workflows. These pages describe what the current application can represent without implying unverified vendor-certified connectors.
Canonical integration definition
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.
Source library
Documented connector patterns
Each page separates source-registration capability from deployment-specific authentication, transport, field mapping and vendor support.
Google Workspace security event source
How Cybatar can register Google Workspace as a security event source while preserving source identity, health and operational context for security workflows.
View connector guideWazuh security event source
How Wazuh can be represented as a Cybatar event source for downstream event handling, investigation and security operations when an ingestion path is configured.
View connector guideFirewall security event sources
Cybatar can register firewall systems as security event sources and preserve source, vendor, product, status, health and last-seen context for security operations.
View connector guideEndpoint security event sources
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.
View connector guideCloud log event sources
Cybatar can register cloud logs as event sources and use configured ingestion and normalization workflows to connect cloud telemetry to security operations.
View connector guideSigned webhook ingestion
Cybatar includes a signed webhook ingestion workflow with per-endpoint secrets, optional IP allowlists, payload limits and ingestion-attempt records.
View connector guideCustom API, CSV and event sources
Cybatar event-source registration supports source types including manual, webhook, API, CSV, endpoint, firewall and cloud for deployment-specific ingestion designs.
View connector guide
Developer surface
Implementation guidance
See the public developer guides for signed webhook ingestion, API-key handling, event-source onboarding, connector setup and integration-health evidence.
Open developer guides
Claim boundary
Connector pages are evidence-bounded.
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.
Read connector facts and non-claims →