Every session, live first
Every time someone used a shared account, with live sessions at the top. Recorded sessions offer Watch.
Session governance
Know who did what.
Every use of a shared account is a session you can see, and end. For the accounts that need more, record sessions and watermark the page, with privacy built in from the first setting.
From the Sessions list to a signed-out browser, and out through your gateway
Session governance
Know who did what.
Every shared-account session in one list. Recording is off until you turn it on.
Session governanceWatch, with typing masked
Watching needs a reason and is logged against your name. It’s a replay of the page, not a video. What people typed is masked where they typed it. The replay still shows what the page shows back.
End it remotely
An admin ends Alice’s live session from the console.
Her browser signs out
Within about a minute, LayerT signs Alice out of the vendor site. She’s told an administrator ended it, not who or why.
DemoThe admin console
Session governance
Through your gateway.
Early access Send a shared account through a gateway on a server you rent, so the vendor sees one address it can allow-list.
Session governanceOpened from the launcher
Alice presses Sign in on Vendor Cloud operations. The account is set to go out through London 1, a gateway on a server Acme Corp rents. LayerT switches the account’s sites to the gateway before the sign-in page loads.
The vendor meets the gateway first
The sign-in page loads through the gateway, so the vendor’s first sight of the session is the gateway’s address. LayerT fills the sign-in there and says, once, where the session goes out.
The chip names the address
The session chip reads via London 1 · 203.0.113.7: the gateway, and the address the vendor sees. The address can be copied from the chip’s card. Everything else in her browser goes direct.
The address to give the vendor
Routing is off for every account until an Owner or IT Admin picks its home gateway and switches it on. The account’s page shows the IPs to give the vendor for its allow-list.
No gateway, no sign-in
Later, London 1 can’t be reached. The sign-in isn’t opened and Alice is told why, unless the account is set to go direct. Gateways are in early access: built and tested, and run in our test environment only.
DemoEarly accessThe LayerT launcher
Oversight that respects the people doing the work
- Every session, live first Who used which account, when, for how long and how it ended, in one list.
- End a session remotely An Owner or IT Admin ends it with a reason. The person’s browser signs out within about a minute, and they’re told an administrator ended it.
- Recording, off until you choose Off by defaultSwitched on per account, after your Owner attests to a lawful basis. What people type is masked where they type it, in form fields and rich-text editors, and sign-in fields are left out entirely. A recording still shows what the page shows back, such as a sent message.
- Encrypted on the device Each recording gets its own key, made in the browser. Chunks are encrypted before they leave, and storage holds only ciphertext.
- Watching is on the record Only the Owner, IT Admins and Compliance Officers can watch. Each viewing needs a reason and is logged.
- Deleted on schedule Recordings are kept 90 days by default, from 7 to 365, then deleted automatically.
- A watermark with the person’s name Off by defaultDeters and attributes screenshots. It can’t stop a phone camera, and we say so.
- Evidence you can hand over Filter the audit log to a person, account or period and export it as CSV or JSON Lines. Quarterly access reviews add a report of who kept access and who lost it, with a SHA-256 checksum.
- One address a vendor can allow-list Early accessSend a shared account through a gateway on a small server you rent, with a static IP, so the vendor sees one address it can allow-list. The gateway installs with one pasted command, and LayerT checks it from outside, shows the addresses to give the vendor, and keeps it updated and its certificate current. Routing is off until an Owner or IT Admin switches it on for an account, and it covers only that account’s own sites, while someone has a session on it. Built and tested; it has run in our test environment only.
- The session starts at the gateway Early accessLayerT switches the account’s sites to the gateway before the sign-in page loads, so the vendor’s first sight of the session is the gateway. A chip on the page names the gateway and the address the vendor sees, for example “via London 1 · 203.0.113.7”, and the address can be copied. If someone opens the vendor’s page themselves, that first page loads from their own address. When they pick the account there, LayerT doesn’t fill that page: it loads it again through the gateway and fills it there. The gateway sees which host is reached and when, not the content.
- Not opened without its gateway Early accessThe sign-in isn’t opened when its gateway can’t be reached, and the person is told why. You can set an account to go direct instead, which opens it from the person’s own address with a notice.
For your security review
How it works underneath, written for the people who have to sign it off.
Put a layer on the browser.
LayerT is pre-launch and taking demo requests. Tell us what you want to solve, and we’ll show you the product doing it.
