Documents
Documents lets you author, version and publish documents — policies, procedures, charters, records, meeting minutes — directly inside CyberGuard, so the text of your governance programme lives where the rest of your GRC data lives. Every document carries revision history, a lifecycle, and links to the objects it governs.
Where to find it
Section titled “Where to find it”Operations → Documents in the sidebar.
Key concepts
Section titled “Key concepts”Document containers, language versions and revisions
Section titled “Document containers, language versions and revisions”A document container is the language-independent identity of a document: it holds the type, domain, classification and links. Under it sits one managed document per language — one language is the default, the others are translations — and each language version is a chain of revisions (v1, v2, …): every saved change produces a new revision instead of overwriting the previous text. The Version history sidebar lets you read any past revision and diff two of them.
Document types and content sources
Section titled “Document types and content sources”Every document has a Document type — Policy, Procedure, Charter, Record, Meeting minutes or Other — used to group the catalogue and scope the template picker. Its content comes from one of three sources, chosen at creation:
- Authored — written in the in-platform Markdown editor with a formatting toolbar and live preview; the published version is rendered to a PDF snapshot.
- Uploaded — an existing file (for example a signed PDF) carried through the same lifecycle and history.
- Linked — a pointer to a document living in another system; readers open it in place.
Lifecycle
Section titled “Lifecycle”Each language version moves through Draft → In review → Change requested → Validated → Published → Deprecated. A French translation can still be in draft while the English original is published.
Working with documents
Section titled “Working with documents”Create a document from the add button, pick its type, domain and source, and optionally start from a document template — the picker offers templates matching the document’s type and language.
When you link one document to another from inside the editor (Link to document), CyberGuard records the edge automatically: each document shows References (what it points to) and Referenced by (what points at it), computed from the content itself.
A document can also be linked to the objects it governs — policies, applied controls, task definitions, processings. The link is associative and bi-directional: the linked object shows a Documents panel listing what’s attached. And a document can carry a Classification level from an object-classification scheme such as TLP; the level shows as a coloured badge and is stamped on every page of the exported PDF.
Read view
Section titled “Read view”The Documents page itself is a read-oriented catalogue: published documents shown as tiles, grouped by type, with search and type filters — the place to browse and read the published corpus, separate from the authoring workflow.
Related
Section titled “Related”- Applied controls — attach a document to the control it describes.
- Tasks — link procedures to the recurring work that follows them.