No new browser to roll out. Nothing new to learn.
LayerT arrives through the tools you already run: your MDM installs it, your directory tells it who’s who, and your people keep using the browser they know. An administrator approves each new browser before it gets any rules or shared accounts.
Rolled out through the tools you already run.
- Your directoryJumpCloud, over SCIM 2.0
LayerT consoleRules, shared accounts, Inbox- Signed policy to the extensionChrome, pushed by your MDM
- The pageWhere LayerT blocks, asks or fills in
Requests, sign-ins and sessions flow back to the Inbox and audit log.
Deploy
Your MDM pushes a Chrome policy that installs LayerT and pins it to the toolbar. People sign in once with their company identity. Each new browser then waits for an administrator’s approval.
macOS and WindowsSet policy
Write rules and add shared accounts in the console. Build a rule by pointing at the page.
Signed before it shipsEnforce
The extension reads only what your rules name. It acts in the page on form submissions, pastes, typed text and files, and fills in shared-account sign-ins.
Fails closed on stale policyDecide and prove
Requests land in the Inbox, and reach approvers by email or Slack too. Every block, approval, sign-in and session goes into one audit log, in plain words.
Kept 365 days by defaultReviewing LayerT for your company?
The architecture pages cover every component, data flow and limit, written for your security team.
Questions a good security lead asks.
Straight answers. If yours isn’t here, ask us in the demo.
Do people have to switch browsers?
No. LayerT is an extension in Chrome, the browser they already use. Your MDM rolls it out, and people sign in once with their company identity. Every new browser then waits for an administrator’s approval before it gets any rules or shared accounts.
Does LayerT read everything people do in the browser?
No. LayerT reads only the fields your rules name. When a rule matches, LayerT records what matched, and for a typing rule the text of the field, so an auditor can check the decision. A rule can mask or hide its values. Tell your people what your rules record. Session recording is a separate thing: it’s off by default, needs your company to confirm a lawful basis, and tells people on the page when it’s on.
What happens if LayerT can’t reach its servers?
The extension keeps working from its last signed policy. If that policy gets too old, LayerT fails closed: it blocks the actions your rules cover and tells the person why, until it can sync again. A block that people can continue past with a reason stays a block while LayerT is offline, because the reason has to be recorded first.
Can people see or copy a shared password?
Not while they sign in. LayerT fills the sign-in form for them, and the password never shows on screen or lands in the browser’s password manager. If someone really needs to see it, they can ask: two other people must approve, one of them an Owner or Compliance Officer. They see it once, it’s logged, and the account’s owner is asked to change it.
Which identity providers does it work with?
LayerT is built for JumpCloud, over SCIM 2.0 and OpenID Connect. Other providers that speak those standards may work, but we haven’t certified them yet.
Is this data loss prevention?
Not in the broad sense. LayerT’s rules act on form submissions, pastes, typed text and files given to a page, by a file’s name or by the text inside a plain-text file of up to 1 MB. LayerT doesn’t read inside PDFs, Office files or images: a rule about a file’s text stops those and says it couldn’t check them. What a site uploads by itself in the background isn’t checked. We’d rather tell you now than in a security review.
Can a vendor allow-list our address?
Yes, one shared account at a time. Send the account through a gateway on a small server you rent, and the vendor sees one address it can allow-list. Routing is off until you switch it on for an account, and the sign-in isn’t opened when its gateway can’t be reached, unless you set the account to go direct. Gateways are in early access: built and tested, and they have run in our test environment only.
Is LayerT SOC 2 or ISO 27001 certified?
Not yet. LayerT is pre-launch. What it does today is produce the evidence your own auditors ask for: approvals, sign-ins and sessions in one readable log.
How much does it cost?
Pricing is on application. It depends on how many people use LayerT and which parts you need, so tell us about your team in a demo request and we’ll put a proposal together.
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.
