Policy creation
Policy creation turns a blank page into a signed, published, acknowledged policy without leaving CyberGuard. You pick a template aligned to a recognised standard, the platform fills in your organization’s details, you edit the text in the built-in document editor, a domain manager signs it, and everyone who needs to read it is notified and tracked until they acknowledge it.
Where to find it
Section titled “Where to find it”Governance → Policy Creation in the sidebar.
Generating a document
Section titled “Generating a document”Press Create Policy and complete the four sections of the form.
-
Template selection — choose a Policy Template from the built-in library of compliance-aligned templates.
-
Company information — enter the Company Name that will replace the placeholders throughout the document, pick the Domain the policy belongs to (your own domain, unless you are a Global Administrator, in which case any domain), assign a Policy Owner, and type the name and title of the person shown as Approved By. Drag a Company Logo onto the drop zone to brand the cover page, header and footer (PNG, JPG, GIF or WebP, up to 5 MB).
-
Document details — set the Version, the Publish Date, the initial Status (Draft or Archived), and the Introduction Text that replaces the template’s introduction section.
-
Options — leave Save to Library ticked to keep a copy of the generated document in your policy library, then press Generate Document.
CyberGuard substitutes your details into every placeholder in the template — company and product names, dates, owner, approving authority, version — and swaps the logo into the header, footer and title page.
Editing
Section titled “Editing”Generated documents are not frozen. Edit Document opens the file in the built-in editor, where authorized administrators can rewrite control language, add organization-specific requirements, adjust roles, responsibilities and scope, and bump the version. Edits save automatically; close the editor when you are done.
Signature and publication
Section titled “Signature and publication”Documents move through four states, shown as badges in the Status column and selectable in the status filter: Draft, Pending Signature, Published and Archived.
How a draft reaches Published depends on your role:
- Domain Managers and Global Administrators get Review & Sign. You sign the policy digitally, and the signed policy auto-publishes — it goes live immediately.
- Everyone else gets Request Signature. That notifies the domain manager, who reviews and signs; the policy auto-publishes on their signature. You are notified once it has been signed and published.
Signing is handled through an integrated digital-signature provider, which produces a cryptographically verifiable signature and a signed PDF. The detail page records Signed By and Signed At alongside the owner, creator, publish date, creation date and file size. Publishing a generated document also creates the matching entry on the Policies page, so the published corpus and the action plan stay in step.
Acknowledgement tracking
Section titled “Acknowledgement tracking”When a policy is published, CyberGuard emails the users who need to acknowledge it. The notification carries the policy name, version and creation date, a direct link to review it securely, and instructions for acknowledging.
Opening a published policy from that link, or via View & Acknowledge in the list, shows the document and a prompt to review and acknowledge. Once a user acknowledges, the page confirms it and the acknowledgement is recorded permanently — each user can acknowledge a given document exactly once.
The Acknowledged column tells you where each policy stands at a glance: a badge for your own acknowledgement (done, or pending your action) and a count of how many users have acknowledged in total. The document’s detail page lists every acknowledgement with the User and the Date, so gaps are obvious and can be chased.
