Cybatar Security Hub · Governance · Risk Management · Threat Resilience · Compliance & Audit
Unified enterprise security operations for modern organisations
Security Hub
Client login Open portal
Cybatar / Developers / Integration health and evidence
Developer guide

Integration health and evidence

Cybatar includes integration-health records and source health fields, but the current administrative health-check workflow deliberately records connector-registry state rather than fabricating synthetic latency or probe results.

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

Implementation facts

Integration health records store connector name, connector type, status, last-checked time, response metadata and error context. The current health-check workflow maps connector registry states such as connected, active, failed or error into configured, attention or unknown status. The health-check metadata explicitly records active_probe_performed as false for this registry-state check. The workflow does not generate synthetic response latency when no active probe occurred.

Recommended implementation workflow

STEP 1

Identify what evidence should define connector health: registry state, last event received, active probe or a combination.

STEP 2

Use Cybatar source status and last-seen information for telemetry-aware checks where available.

STEP 3

Treat registry-state checks as configuration evidence, not proof of end-to-end event delivery.

STEP 4

Escalate stale, failed or unknown connectors using operational ownership and incident procedures.

Security and claim boundary

Cybatar does not treat a registry-state record as proof of a successful active probe. Deployment teams should validate real data flow and end-to-end behaviour when operational assurance is required.

Frequently asked questions

Does the current Cybatar integration-health workflow perform an active network probe?

The current registry-state workflow explicitly records that an active probe was not performed.

Does Cybatar invent latency values when no probe exists?

No. The current workflow leaves response latency null rather than generating synthetic data.

What is stronger evidence of connector health?

Recent real telemetry, verified end-to-end data flow and deployment-specific active checks are stronger evidence than registry state alone.