Security
VRS is built so each company’s data stays isolated, access is limited by role, and changes to governed records can be audited. The approach described here is aligned with ISO 27001 principles and the NIST Cybersecurity Framework. It is not a certification claim.
Roles and access
Access is role-based and scoped, including by department. Built-in roles include administrator, department manager, worker and viewer. Permissions take effect immediately; a login needs an active role assignment. Microsoft Entra ID can provide single sign-on and provisioning.
Audit log and sealed approvals
Every governed change is written to an append-only audit trail: who, what, when, and the before and after. A past pay period can be replayed under the rule and policy versions that applied at the time. Approvals freeze the policy snapshot they were taken under.
Customer isolation
Each company’s data is isolated. There are no cross-company reads. If a partner is granted access, they only see what the grant allows, and ownership stays with the customer.
Data residency
When a company is set up, a home region is chosen: Norway, Germany or Switzerland. Norway is the default. Data can be held on the shared platform, or in a dedicated database or a dedicated environment where the engagement requires it. The shared platform is the default.
Privacy and encryption
VRS processes personal data under the GDPR and applicable Norwegian data-protection law, and signs a data-processing agreement when it acts as processor. Data is encrypted in transit and, where appropriate, at rest. Multi-factor authentication is used where applicable. Privacy questions can go to privacy@vrs.no.
AI and sealed pay
The assistant sees only what the user can already see. Writes wait for a person. Sealed pay cannot be altered by a model.