CIPHER
Resources

Practical guidance on protecting open documents.

Short guides on screen-capture risk and on planning an integration.

Guide 01

Why access controls stop at the screen

Access controls decide who may open a document. They say nothing about what happens once it is open in front of someone entitled to see it.

  • A phone can photograph a screen in seconds, without writing a log or breaking a permission.
  • The organisation usually learns of it only when the information appears somewhere it should not.
  • By then there is rarely any way to establish how it left.
  • Treat the open-document moment as part of your threat model, alongside storage, transit and access.

Guide 02

Reducing the risk of photographed screens

No single measure removes the risk, but layered measures reduce it and make attempts visible.

  • Limit who can open the most sensitive documents, and review that list regularly.
  • Make clear in policy and training that photographing confidential screens is prohibited.
  • Add technical detection and blurring where a platform displays confidential documents.
  • Make sure capture attempts are logged somewhere your security team will actually look.

Guide 03

Rolling out CIPHER in your firm

A rollout goes smoothly when the groundwork is done before the first confidential document is uploaded.

  • Decide which documents and teams move into CIPHER first, and who administers the workspace.
  • Choose the security policy: phone detection, its sensitivity, screenshot protection and session timeout, and who reviews alerts.
  • Tell staff and guests that camera-based protection is active, and why the browser will ask for camera access.
  • Run a pilot with non-sensitive sample documents before moving client files in.