Realm in action: a business, its team and its providers

At Brevalt Industries, Emma and her colleague Paul look after IT. The business runs its own servers. Tom and Nina, from Kerwan IT, help them remotely. Marc and Hugo, their software vendors, log in to them too, now and then. Before Realm, nobody knew who connected, colleague or supplier, or when, or to what. Marc's and Hugo's access stayed open, day and night. They passed the same password around, and nobody thought to change it. In an incident, an audit or a dispute, Emma had nothing at hand to show. Emma now uses Prism: Vault for passwords, Realm for access. With Realm, every connection goes through one single point. Kerwan IT, her partner, can run Realm for her. But Emma stays in control: with one button, she can restrict Kerwan IT's access. On the servers, one small program is all it takes: Realm Connect. It reaches out to Realm itself, through an encrypted tunnel. No door needs to be open from outside: the firewall stays shut to incoming traffic. For Emma, there's no VPN to hand out, and no box to maintain. Tom, for his part, needs nothing but his browser to connect. The password comes straight from Tom's Vault, and Realm injects it without ever showing it. What's more, Realm records the whole session by default. Emma sees who connected, to which server, and when. She replays Tom's session, like a video. We see Nina at work, and Emma asks to watch her session. She gives Nina the reason. Nina gets the request first, then accepts it. Emma watches her create an account live, read-only. What Nina is doing is outside her assignment: Emma ends it with one click. In Prism, Emma adds Paul, who can connect right away. Marc, the management software vendor, has no account in Prism. Emma prepares a guest access for him to the production server. First, she selects from her Vault the password Realm will inject when Marc connects. Then she invites Marc and sets his allowed connection hours. Here, Monday to Friday, 8 am to 1 pm. Marc gets the link from Emma, to connect without knowing the server's password. He opens it, asks to connect, and Emma lets him in. Realm injects the password directly: Marc still never sees it. One morning, Paul finds the management software down. He can't get it to start again and needs the vendor's help: he calls Marc. From his session, Paul invites Marc to join him. The link works once, and expires after 15 minutes. Marc joins the very same session. Marc finds the cause, restarts the database, problem solved. Marc's whole fix was of course recorded by Realm, from start to finish. All of these steps are written to the audit log. During sessions, Realm also flags sensitive actions. Months later, an audit asks who created accounts. In the recordings, Emma looks for the user management window. It's Nina's session, several weeks ago, on the domain controller. One click on the event she wants, and the player goes straight to the moment Nina creates the account. Emma exports the video: her NIS2 compliance evidence is ready. Remember: before Realm, Emma had nothing to show, because nothing was really controlled. But today, every access goes through Realm and stays traceable. Designed and hosted in Europe. Emma is back in control: thanks to Realm, she now knows who connects, when, and to what.