Skip to main content
Regulaxy
Prove

Roles, audit, and no outbound calls.

Three questions every security review asks, and three answers you can show rather than assert.

The artifact

An audit log row

The problem

"Hidden in the UI" is not a permission.

A button that is not rendered still exists on the server. A penetration test finds it in ten minutes, and the audit team asks about it before that.

How it works
  1. 01

    Two roles

    Administrator and operator. An operator sees the calendar, the inventory and the dashboard, sets event status and fills in checklists. Creating, editing, cancelling and settings — no.

  2. 02

    Enforced server-side

    The separation is enforced at the endpoint, not in the interface. Hiding a button is a convenience; the server-side check is the permission.

  3. 03

    Sign-in

    Authentication against Active Directory. Session length and attempt limits are editable, and every rejection is logged with its reason in its own file.

  4. 04

    Audit

    Every change is recorded. Permanently deleting an event removes what derives from it — but not the audit log, which is the record that the deletion happened.

Figure — mapping to Directive 364

What it looks like

An audit row

Who, when, what changed, and what it was before. It is what §98 asks for, and it is what remains after the event itself is gone.
Your network

Regulaxy

Application server and database, on your side

  • Active Directory — authentication and roles
  • Your database — all application data
  • System logs — split by function
no link
The public internet
Figure — the network boundary
What it connects to

No external identity provider and no dependency on a cloud service.

  • Active Directory / LDAP
  • Local system logs
  • Your database

Show us your worst window.

Bring the one that keeps slipping. Thirty minutes, your estate, no slides.