Realm for IT providers: all your customers, one tool
For IT providers: onboard a customer, give your technicians access to their machines, and run every customer from one place.
Transcript
This is Tom. Like you, he looks after IT for several companies. He works with Nina at Kerwan IT. Some customers have their own servers. Sometimes the machines are provided by Kerwan IT or other providers. Among them, Brevalt Industries, whose IT manager is Emma. Marc works there too at times: he's the vendor of their management software. Before Realm, to reach those servers, Tom used as many VPNs as he had customers. Each customer had to keep a port open in its firewall so he could connect. Passwords were swapped by instant message, text or otherwise. And nobody really knew who was doing what, or when. Then Kerwan IT set up the Heimlane Prism platform, which handles both passwords and access, with Vault and Realm. With Realm, Tom, Nina, Marc and Emma all use the same tool to connect. Here's how Tom set up Brevalt Industries. He creates Brevalt Industries in Prism: it takes him just a few seconds. Then he installs Realm Connect at Brevalt in a single step: once again, it takes him just a few seconds. Soon, every Brevalt server is online, reachable and auditable. All in all, it took Tom only a few minutes. Realm Connect only uses an outbound connection to Realm, through an encrypted tunnel it sets up by itself, with zero configuration. Brevalt's firewall stays closed: no port had to be opened. For Tom and the Kerwan IT team, no more hassle with VPNs to set up, or boxes to maintain. Tom connects to Brevalt's file server from his favourite web browser. The password comes straight from his Vault: Realm injects it without showing it. And his whole session is recorded. Tom can replay it like a video, and so can Emma at Brevalt. Nina sometimes works at Brevalt: Tom gives her Support L2 rights, with the matching tag. This tag is set to give access to two servers: the production one is out of scope. Nina is carrying out a sensitive operation: Tom asks to watch her session. Realm first asks Nina for her consent, and she gives it. Tom watches Nina change the registry, live, without being able to interact. As for Marc, he has to work at Brevalt in a few hours. He has no permanent account. So Tom prepares an access for him to the production server he has to work on. He first selects from his Vault the password that will be injected when Marc connects. Then he adds Marc's email and his allowed connection hours. Here, weekdays, 8 am to 1 pm. Marc receives a link and opens it. That starts the session, and Tom accepts his request to connect. Realm injects the password automatically. Marc doesn't see it, doesn't receive it, doesn't know it. As for Tom, he has all his customers in one place in Prism, each one fully kept apart. For every session, Realm spots sensitive events and logs them. A few months later, Emma asks Tom who changed the registry. Tom filters Brevalt's sessions on “Registry Editor”. Only one session comes up: it's Nina's, on the domain controller. One click on the event he wants, and the player goes to the moment Nina opened the registry. Emma can check it for herself too. She knows who did what, and when. With the video, her NIS2 evidence is ready and usable as is. Remember: before Realm, access was complicated and nothing was really under control. But today, every access goes through Realm, and stays traceable. Designed and hosted in Europe. Kerwan IT has taken back control and improved security for its customers. Thanks to Realm, Tom now knows who connects, when, and to what.