Skip to content

NATO-Style Data Governance Metadata Mapping

This page maps nats-sinks concepts to public, high-level NATO-style data-governance concerns such as discoverability, data-centric security, data quality, lineage, retention, and catalogue integration.

It is not a formal NATO compliance claim. nats-sinks does not implement NCMS, STANAG 5636, a policy authority, an access-control system, or a data catalogue. It can help preserve the metadata and custody evidence that catalogue and governance tools need.

Governance Concern nats-sinks Building Block
Discoverability Stream names, subject patterns, schema profiles, labels, and catalogue manifests.
Accessibility Sink-specific storage, least-privilege credentials, and explicit deployment documentation.
Trust Commit-then-ACK delivery, idempotency keys, hashes, DLQ evidence, and tamper-evident custody.
Policy and regulation Security labels, classification, pre-sink policy checks, retention categories, and reviewable configuration.
Data-centric security Labelled metadata, payload encryption, secret redaction, and least-privilege sink users.
Metadata Mission metadata, data quality metadata, artifact references, lineage fields, and schema profile/version.
Data quality Optional quality scores, confidence, assessed-at timestamps, and quality source fields.
Lineage Source system, source gateway, correlation ID, causation ID, message ID, stream sequence, and payload hash.
Retention Sink table, file path, object prefix, retention category, and deployment-owned deletion policy.
Catalogue integration Data-product manifests generated from reviewed configuration and metadata profiles.

Synthetic Data Product Manifest

{
  "dataset": "synthetic-mission-events",
  "owner": "programme-team-placeholder",
  "nats_subject_patterns": ["mission.synthetic.>"],
  "sink_targets": ["oracle-primary", "file-review"],
  "schema_profile": "mission-event-v1",
  "schema_version": 1,
  "classification": "NATO UNCLASSIFIED",
  "labels": ["synthetic", "mission-support"],
  "security_label_profile": "example-security-label-v1",
  "mission_metadata_profiles": ["normalized-link-event", "tracking-fix-event"],
  "data_quality_profile": "generic-data-quality-v1",
  "artifact_reference_profile": "generic-artifact-reference-v1",
  "retention_category": "programme-defined",
  "lineage_fields": ["event_id", "correlation_id", "source_system"],
  "custody_fields": ["payload_sha256", "stored_at", "sink_commit_id"]
}

Actual catalogue mappings, policy decisions, releasability decisions, and certification evidence must be defined by authorized programme teams.