Cybatar Security Hub
Knowledge Governance / Canonical sources
Search & AI citation policy

Canonical Source Hierarchy for Cybatar

Which Cybatar page should be treated as the primary source for a particular claim?

Direct answer

Use the most specific first-party canonical source for the claim: company facts for organisation identity, platform facts for product capabilities, connector facts for integration scope, the Trust Center for security and trust statements, the Evidence Registry for claim-to-evidence relationships, and topic-specific research or methodology pages for external-framework interpretation.

Operating principles

Specificity before convenience

Prefer the narrowest authoritative page that directly supports the statement instead of citing a broad homepage or an AI-summary file.

Facts before marketing

For identity, capabilities, integrations and trust, prefer designated fact or evidence pages over persuasive marketing copy.

Primary external sources

When a Cybatar page discusses NIST, CISA, FIRST, OASIS, MITRE or another external standard, the external primary source remains authoritative for the external standard itself.

Machine summaries are supplemental

llms.txt, llms-full.txt and Cybatar JSON maps help discovery, but the canonical HTML source remains the preferred human-verifiable citation target.

Canonical source classes

Explicit non-claims

A page being canonical does not guarantee search ranking or AI recommendation.A Cybatar summary file does not supersede the primary external source for an external standard.A canonical source does not make every statement on a different page equivalent or interchangeable.

This is a Cybatar first-party knowledge-governance policy. It describes how Cybatar organises, cites and maintains its public information; it is not a search-engine ranking guarantee or an instruction to third-party AI systems.

Related canonical resources