Book a demo

Itzal Lens

Find out what you have, and where it is

Nearly every company that asks us for a policy cannot yet answer what have we got, and where. Lens answers it from the devices you already manage, and reports what it found rather than copying it out.

Book a demo See pricing

  • 4places it looks
  • 8frameworks mapped
  • 0data copied out

What you get

The answer to what have we got, and where

A policy written without this is a guess about your own company. Lens is how you stop guessing.

  1. 01

    A map of where regulated data actually sits

    By device, by location and by framework, so you can see that the PCI problem is in one team's downloads folder rather than everywhere.

  2. 02

    A list of the AI tools already in use

    Reported by hostname, never by content. It is how you find out which tools to sanction and which to have a conversation about.

  3. 03

    A starting policy you can defend

    Thresholds and actions chosen against what you found, which is a much shorter conversation with a works council than a policy chosen against a template.

Where it looks

The places data quietly accumulates

Everything is read on the device or through an account you already own. Nothing is copied to us.

  • Laptops

    Downloads, desktops and local folders on the machines you already manage, read by the agent that is already there.

  • Cloud drives

    The folder somebody shared with the whole company three years ago and nobody has looked at since.

  • Chat and collaboration

    Slack and Teams, where documents get dropped instead of filed.

Frameworks

Every framework brings its own thresholds and its own action

A finding is not just a kind of data, it is a kind of data under an obligation. Each framework carries its own thresholds and its own action, which is what lets one laptop block for HIPAA and only warn for Internal.

  • HIPAA

    Health records

    Patient names, record numbers and clinical detail, under the identifiers the rule lists.

  • PCI DSS

    Card data

    Card numbers validated by Luhn and BIN, so a test number next to the word example does not fire.

  • GDPR

    EU personal data

    Names, addresses, identifiers and the context that makes them a record rather than a mention.

  • CCPA

    California residents

    The same personal data, under the obligations that apply in California.

  • GLBA

    Customer financials

    Account and routing numbers, balances, and the material non-public information around them.

  • FERPA

    Education records

    Student records and anything that identifies a student inside them.

  • SOX

    Financial reporting

    Unreleased results, forecasts and the working papers behind them.

  • Internal

    Your own rules

    Your patterns and your own kinds of thing, in your words: project codename, claim handler, deal name.

Plans

How it is sold across the editions

Lens is included in Itzal Enterprise and sold as an add-on on the other three editions. It answers what you already have and where it is, which is a different question from what is leaving right now.

  • Guard Essentials Add-on

    Available on its own, priced per device like the edition.

  • Guard Pro Add-on

    Available on its own, priced per device like the edition.

  • Itzal Business Add-on

    Available on its own, priced per device like the edition.

  • Itzal Enterprise Included

    AI tools in use, and where sensitive files sit on the fleet.

See the full comparison and prices

What it finds

The things nobody knew were there

Three findings from a first run, in the order people are usually surprised by them.

  1. Before a policy

    You need to know whether HIPAA, PCI or GDPR is your real problem.

    Lens maps findings to frameworks, so the first rule you write is aimed at the data you actually hold.

  2. Before a renewal

    Somebody asks which AI tools the company is already paying for, or using for free.

    Discovery reports the hostnames in use across the fleet, which is usually a longer list than the one procurement has.

  3. Before an audit

    An auditor asks where regulated records live outside the systems of record.

    A per-device, per-location answer, with counts and types, and no copy of the content anywhere.

When it finds something

You choose what happens next

Three settings, chosen per compliance framework rather than per person, so HIPAA can block on the same laptop where Internal only warns. Most companies spend the first couple of months on the first one.

  1. Quietest

    Make a note of it

    Nobody is interrupted. You get a picture of what is happening before you change anything about how people work.

  2. In the middle

    Tell the person

    A banner before the send, saying what was spotted. They decide, and the decision is recorded.

  3. Firmest

    Stop it going

    Held until the data is taken out. Only where you have decided it is worth it, so the rule does not push people somewhere worse.

Set it to watch for a month, then decide. That is how almost everyone starts.

Book a demo How the rollout works

What Lens does not do

The limits, said plainly

Every product on this site has a boundary. Ours are worth knowing before you buy rather than after, and the console reports them the same way.

It does not copy your data anywhere.

Lens reports what it found and where. The content stays where it was, and there is no field in the record that holds it.

It is not a backup, an archive or a remediation tool.

It tells you what exists. Moving it, deleting it or locking it down is your decision and your tooling.

It is a picture, not a live feed.

Lens tells you what was there when it looked. The moment-by-moment control is Guard, Shield and Mail.

Questions

What people ask before they book

Short answers. The longer versions are in the pages linked from each one.

Does Lens send our files anywhere?

No. It reports the finding, the kind of data, the count, the location, and the content stays where it was. The same device boundary Guard works under applies here.

How long does a first run take?

Most companies have a usable picture within a week of the agent reaching the fleet, because it reports as it goes rather than waiting for a complete pass.

Do we need Guard first?

No, but it is the same agent. If Guard is already deployed, Lens is a licence change rather than a new rollout.

Does it read employees' personal files?

It reads the locations you point it at on the devices you manage. Personal devices are outside a device-based control entirely, and we would rather say so than imply otherwise.

What do we do with the result?

Usually two things: sanction the AI tools worth sanctioning, and set your first thresholds against the frameworks that actually turned up.

The rest of the family

Everything else is a licence, not another rollout

It answers what you have and where before you write a single rule, which makes the rest of the decision a much shorter conversation.

See Lens on your own laptops.

Lens is usually the first thing people run. Half an hour, your hardware, and a straight answer on what it would cost.

Book a demo See pricing