zevOS

01Ebook

The Security & Compliance Pack

Answering the questions procurement will ask

22 pagesPDF, including the model responsesUpdated 16 August 2026

What you get

Takeaways

  • The security questions that come up in every enterprise evaluation
  • What tenant isolation means in practice, and how to demonstrate it
  • Payment scope: what you hold, and what you should never hold
  • Data residency, retention and portability as contract terms

Contents

  1. 01

    The threat model

    Unattended devices in public places, money in motion, and remote control of physical equipment. What each implies.

  2. 02

    Isolation and access

    Tenant scoping in the data layer, role-based access, territory restrictions and separately permissioned financial actions.

  3. 03

    Payments and scope

    Why card data should never touch the platform, and what that removes from your compliance burden.

  4. 04

    Audit and evidence

    What must be recorded, for how long, and what an auditor will actually ask to see.

  5. 05

    Residency and retention

    Where operational data sits, how long it is kept, and how to fix both contractually.

  6. 06

    Answering the questionnaire

    Model responses to the questions that recur — including how to answer honestly when a control is not yet in place.

Or skip the reading

We are happy to work through your own numbers directly — that is usually faster than a document.