SaaS and AI discovery

Who in finance just started using ChatGPT?

Rebasoft reads the proxy and DNS logs you already keep, identifies the service and names the person from the proxy login, with nothing to deploy.

Outside services are part of the answer when the board, insurers or customers ask how your critical business services are protected.

SaaS & AI Illustrative
From logs you already keep
Proxy log names the host Catalogue names the service Directory names the person
first use, listed for review
First use No decision
ChatGPT
Finance site Workstation Generative AI
your decision, sent to every collector
Allowed Not allowed
In the console

See what your people really use

Charts show services by type and by policy, with devices and traffic for each service, from generative AI to personal storage.

From a Rebasoft demo estate.
The catalogue

Replace guesswork about AI use with evidence

Surveys and policy statements tell you what staff say they use. Rebasoft shows what your network has actually seen, so you answer boards, insurers and customers with confidence.

485 services

Reports show service names, which ends the work of tracing IP addresses and domains.

97 generative AI services

ChatGPT and its peers sit in their own category, ready for reporting and policy.

14 log sources

Proxy and DNS sources are read directly, alongside dnstap and flow data, so you start from what you already collect.

Your existing logs

Your existing logs deliver the answer, with nothing to deploy

Rebasoft reads Zscaler, Netskope, Cisco Umbrella, Palo Alto, FortiGate, Check Point, Sophos, Forcepoint, Skyhigh, Menlo, iboss, Cloudflare Gateway, ProxySG and Squid, with no agent and no change to how traffic flows. Your team sees which service was used, by whom and how much, and staff prompts and content stay private, because Rebasoft does not read them.

Rebasoft sits beside your proxy, so you gain visibility without touching how traffic flows.
The first ChatGPT use from finance

First use appears on a review list, with a name beside it

  1. 10:12

    A finance workstation reaches ChatGPT

    This is the first time the site has used the service from a workstation, and the proxy log or DNS identifies the host.

  2. 10:12

    The catalogue identifies the service

    The analyst will see ChatGPT, categorised as generative AI, with no policy decision against it, in place of an address or a domain.

  3. 14:00

    It appears on the First use list

    Because the service has no policy decision, it joins the review list and remains there until someone makes a decision.

  4. 14:05

    The person is identified

    The analyst opens SaaS & AI, where the proxy login, matched through your identity directory, provides a name.

  5. 14:10

    A decision is applied

    She marks the service as allowed or not allowed. The policy reaches every collector and the finding is resolved.

A composite. Times are illustrative.

Policy and people

Set policy once and see use person by person

Allowed or not allowed

Set policy by service or by category, and it reaches every collector. Reports separate allowed use from use that is not allowed, so decisions stay visible.

A view by person

Unlike a domain report, this view shows who uses generative AI, busiest first, with the same view for remote access, personal storage, file transfer, file sharing, VPNs and anonymisers.

Alongside the device

SaaS use appears on the device’s asset page, next to its vulnerabilities and owner, so your team sees use in context.

In the console

Decide what is allowed

Set a category or a service as allowed or not allowed. A category decision applies to every service in it that has no decision of its own.

From a Rebasoft demo estate.
Consolidation

Retire the surveys and the separate discovery reports

Staff surveys and AI use spreadsheets
Can replace
Evidence from your logs takes the place of self-reporting.
CASB discovery reports
Consolidates
Rebasoft gives you the who-uses-what view from logs you already have, with no separate discovery exercise.
Common questions
How do we act on a service we do not want?
Your team enforces the decision through the proxy, DNS filter or firewall it already runs. Rebasoft shows what to stop and who it affects, so the action is targeted.
Do we need a proxy?
No. DNS or flow data identifies the service and the device, and a proxy with logins adds the person, so you start with what you have.
When does First use begin?
After seven days of learning what is already in use, so the review list shows what is new to your organisation. It covers generative AI and remote access by default, and your team sets the categories.
Do we need an agent?
No. Rebasoft works from your existing logs and flow data, so there is nothing to roll out to endpoints.
How does this relate to staff monitoring?
It reports on logs your proxy already keeps, with names attached and no prompts or content. Treat it as you would proxy reporting, and cover it in your acceptable use policy and privacy notice.

More questions? See the full Rebasoft FAQ — answers by topic and by role, or how Rebasoft is priced.

See what your logs already show

In thirty minutes on a live console, you will see the catalogue, the First use list and the view by person.