Security and data

Security and data

Who sees what, who changed what, and what cannot change in a closed month: in KERUVA this is set by rules, not by agreement.

  1. 01

    Role-based access

    Rights are set separately for documents, reference lists, reports and service actions. The server checks every request and denies by default. Cost figures in reports are visible only to users with a separate right.

  2. 02

    Passwords and sessions

    Passwords are stored as strong hashes, and the password policy is based on NIST guidance. All of a user’s sessions can be ended at once, and passwords are reset by email.

  3. 03

    Audit log

    Sign-ins and failed attempts, every data change with its IP address and every refused request are recorded.

  4. 04

    Closed month

    Documents in a closed month cannot be posted, edited or voided. The system will not reopen a month that later calculations already rely on. The accounting policy applies from its effective date, and a backdated record needs a separate right and a reason and is written to the audit log.

  5. 05

    Where the data is stored

    KERUVA is a cloud system with backups. Servers, protection and updates are our job.

  6. 06

    Your data is yours

    If you decide to leave, we will export all your data.