Skip to main content

StackJack 0.1.0.13683+01bae8c

StackJack 0.1.0.13683+01bae8c

This release adds watch sweeps for prospects. A watch sweep is a short, time-limited observation period that shows which AI apps and sites a prospect's staff use. Exposure scans can also now use Microsoft Entra Internet Access traffic, and Rewst connections no longer fail on the first call.

New features

  • Watch sweeps for prospects. A prospect's page now has a "Watch sweep" panel. It lets you run a short, watch-only observation of AI use on the prospect's computers and browsers before they become a client.
  • Starting a sweep:
    • Choose a length of 7, 14 or 30 days. The default is 14.
    • Tick the agreement statement and type your name to start.
    • For prospects in the EU or UK, a staff notice must also be recorded before you can start.
  • While a sweep runs, the panel shows:
    • The end date.
    • How many computers and browsers are reporting.
    • Instructions for removing the endpoint agent and the browser extension.
    • The deploy panels for the agent and extension, available directly on the prospect's page.
  • Watch-only behavior: during a sweep, nothing is blocked, warned, coached, masked or captured as text. Only summary facts about which AI apps and sites were seen are recorded. This applies regardless of any other policy settings on the organization.
  • How a sweep ends:
    • Automatically on its end date.
    • When you choose End now, after a confirmation.
    • When you close the prospect.
    • When you convert the prospect to a client.
    • When the prospect is automatically deleted.
  • What ending a sweep does: it turns off the agent and extension and revokes their access. Computers can be enrolled again later with a new enrollment key, for example after the prospect becomes a client.
  • Permissions: only tenant-wide Administrators can start or end a sweep. Auditors can view sweep details.
  • A help page explaining watch sweeps is included.
  • Watch sweep results in exposure scans and reports.
  • When an organization has had a watch sweep, its exposure scan and report include the following, shown as counts and dates only, with no individual people or devices identified:
    • The AI apps and AI sites seen by the endpoint agent.
    • The AI sites seen by the browser extension.
    • How many computers and browsers reported.
  • New "AI seen on staff computers" finding (Medium, shadow AI). It includes a table, a key number, and a summary of the sweep: its length, dates, the recorded agreement, and the computers and browsers that reported.
  • A sweep that is still running is labeled "so far." If no computer reported, the report says so rather than suggesting no AI was found.
  • Reports never count activity after the sweep's agreed end date.
  • A prospect that has had a sweep but has no other connections can now be scanned. Previously, such a scan failed because there was nothing to scan.
  • Microsoft Entra Internet Access as an exposure source.
  • Exposure scans can now read Global Secure Access traffic to see which AI sites were reached through Entra Internet Access. For each site, the scan shows the request count, the number of distinct people and computers, and the last day seen.
  • No individual user, device or address details appear in results.
  • New "AI sites reached" finding (Medium, shadow AI), with its own table and key number.
  • Very large data sets are capped. When this happens, the figures are shown as minimums.
  • The Microsoft consent page lists the additional read-only permission this source needs. If the tenant doesn't have an Entra Internet Access license, the scan reports this source as unavailable and does not raise a blind-spot finding.

Improvements

  • The AI assistant's answers about a prospect now include the prospect's watch sweep status.
  • The scan panel's automatic-deletion date now accounts for sweeps. A prospect is deleted 30 days after its most recent scan or sweep, whichever is later.

Bug fixes

  • Fixed Rewst connections failing on the very first call and being reported as a gateway error. Requests to Rewst now send the content type that Rewst expects.

UI & UX changes

  • Prospects no longer appear in the organization picker on the Deploy page. To deploy the agent or extension for a prospect, start a watch sweep and use the deploy panels on the prospect's own page.
  • Confirmation messages after starting or ending a sweep now stay visible on the prospect's page instead of disappearing when the page refreshes.