For: Companies Private IT Partner v1.0.816 · Swiss Made
For: v1.0.816 · Swiss Made

Security Policy

Here you write the company security rules and have staff confirm they have read them.

Security-policy editor with employee acknowledgements and versioning.

← All modules
A LOOK INSIDE
Security Policy · Overview Security Policy · Overview
Overview Sample data
Security Policy · Digital acknowledgement Security Policy · Digital acknowledgement
Digital acknowledgement Sample data
Security Policy · Acknowledgements Security Policy · Acknowledgements
Acknowledgements Sample data

Here you write and maintain your company security rules — the binding guidelines for handling devices, data and passwords. Your employees read the policy and confirm that they have taken note of it. This gives you proof at any time of who knows the rules.

The security-policy editor manages the company security policy with versioning and employee acknowledgements. You document binding requirements, publish them to the workforce and collect verifiable acknowledgements — a foundation for audits and legally relevant in case of dispute.

Features
  • An editor for writing and maintaining the company security rules.
  • Employees confirm that they have read the policy.
  • Overview of who has already confirmed and who has not.
  • Older versions of the policy remain traceable.
  • Editor for the security policy with versioning.
  • Publication of the policy to the workforce.
  • Verifiable employee acknowledgements per version.
  • Overview of the acknowledgement status for audits.
How it works
  1. You create the policy or edit the existing version.
  2. You publish the policy to your employees.
  3. Employees read the rules and confirm acknowledgement.
  4. You track in the overview who has not yet confirmed.
  1. You create the policy in the editor or revise the existing version.
  2. You publish the new version to the employees.
  3. Employees confirm acknowledgement in the portal.
  4. You export the acknowledgement status as evidence for audits.

Use it forSet binding rules and prove acknowledgement.

Use it forDocument policies and collect acknowledgements for audits.

In the ICT minimum standard
ID · Identify
  • ID.AM-6Cybersecurity roles and responsibilities for the entire workforce and third-party stakeholders (e.g., suppliers, customers, partners) are established.
  • ID.GV-1Organizational cybersecurity policy is established and communicated
  • ID.GV-2Information security roles and responsibilities are coordinated with internal roles (e.g. those in risk management) and external partners.
PR · Protect
  • PR.AC-2Ensure that only authorised individuals have physical access to ICT assets. Take action (on building security, for example) to ensure that ICT assets are protected from unauthorised physical access.
  • PR.IP-5Ensure that you comply with all (regulatory) requirements and policies concerning your physical assets.
DE · Detect
  • DE.DP-1Define clear roles and responsibilities so that there is no doubt about who is responsible for what, and who holds what authority.