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 / Connector setup workflow
Developer guide

Connector setup workflow

Cybatar includes a connector-setup workflow that records named implementation steps, instructions, status and ordering. It is intended to make integration work explicit rather than implying that every source is automatically connected.

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

Implementation facts

Connector setup steps store connector name, step key, step label, status, instructions and sort order. Integration catalogue and integration-connector records can represent connector type, vendor, format, authentication context and connection state. Client integration records can map an integration to organisation or asset context and preserve owner, scope notes, status and health status.

Recommended implementation workflow

STEP 1

Define the connector and the business/security purpose it serves.

STEP 2

Record the required setup stages and their expected outcomes.

STEP 3

Assign credentials, scopes and source-specific settings outside public documentation.

STEP 4

Map the connector to the relevant client, asset or workspace context where applicable.

STEP 5

Record setup status and confirm real data flow before treating the connector as operational.

Security and claim boundary

Setup records describe implementation progress. They do not prove a live third-party connection unless real telemetry or a verified deployment check confirms it.

Frequently asked questions

Does Cybatar have a connector setup workflow?

Yes. The current application includes records for connector setup steps, instructions, status and ordering.

Can integrations be linked to client or asset context?

Yes. The current client-integration model can associate integration records with organisation and asset context.

Does a completed setup step prove a live connection?

Not by itself. Real telemetry or an active deployment-specific check should be used to confirm operational status.