Data Sources
Sync Model
How data-source syncs run, fail, retry, and produce evidence in Noru.
Sync model
Data-source syncs collect provider records, normalize them, and attach the results to Noru objects such as evidence, assets, personnel, risks, findings, and controls.
Lifecycle
The user connects a provider and grants the documented scope, role, token, or API key.
Noru stores the integration configuration and schedules syncs, daily by default unless the integration supports a different cadence.
The provider collector calls read endpoints and converts provider records into normalized entities and evidence.
Noru maps useful evidence to controls and leaves unknown evidence available for review.
Future syncs update the same normalized records, mark stale evidence, and surface failures.
Sync outputs
Prop
Type
Failure modes
What sync can and cannot prove
Sync can prove configuration, access, inventory, finding, training, or activity facts exposed by the provider API at the time of collection.
Disconnect behavior
Disconnecting a data source stops future syncs and prevents Noru from using the stored provider credential for collection. Previously collected evidence remains part of the workspace history unless removed through your retention or deletion workflow.