Employee AI investigations3 min readField note 16

Who used an AI tool on a shared Windows PC?

A Claude paste appears under a Finance laptop. Follow the device, time and Windows session evidence before naming an employee in an investigation.

Alex Morgan’s fictional Finance activity report lists observations on an assigned Windows laptop.
The idea in focus

This account view supplies a starting point for a shared-device investigation. Each conclusion must trace back to a particular event.

Field note / 16
In brief

A device assignment identifies whom to ask. A personal attribution needs evidence from the event time.

  • Keep the tenant, device, UTC time and receipt ID together.
  • Check overlapping sessions and shared accounts.
  • Give each unresolved question an owner.
In this article

Start with the hostname on the ticket#

Suppose a help desk reports a possible API key paste on a Finance laptop shared across shifts. The machine is assigned to Alex Morgan in inventory. Open Individual AI usage in the public demo and search for NS-WIN-014. Record the hostname and tenant. If a laptop has been renamed or reassigned, ask IT to verify its enrollment and assignment at the time of the event.

Northstar activity results filtered to NS-WIN-014 show events from several AI tools.
Search the hostname first. The fictional Northstar timeline includes more than one destination and action.

Pin down the exact action and time#

Choose the Claude paste at 09:44:30 UTC on November 18. Keep EVT-1051, the destination and the action together. An earlier Gemini paste on the same device has its own receipt. A search result under a person’s name can be useful for locating both rows, but the inventory assignment alone cannot identify who was at the keyboard.

Claude sample paste shows one API-key pattern match and two email-address matches.
EVT-1051 is the receipt for the Claude paste. Its categories give Security a question to investigate while IT checks attribution.

What if two Windows sessions overlap?#

On a shared workstation a local session may stay signed in while a support technician connects remotely. In the exercise, both logons precede the paste. Review the target device, time zone, target account and logon type in the approved Windows audit source. Microsoft documents interactive and remote-interactive types in event 4624. Network or service logons can also appear in that log.

Illustrative session timeline with a local Finance session and a remote Support session active at the paste time.
These invented sessions are an exercise overlaid on the demo receipt. Windows session history comes from a separately authorized source.

Which account can the records support?#

Where auditing is available, pair the logon and logoff records by logon ID on the same machine within the same boot. Normalize the times and record any clock uncertainty. A missing logoff leaves the interval open. If the browser receipt lacks a trustworthy session identifier, or the team used a shared Windows credential, keep individual attribution unresolved. A known account may still be used by several people.

Worksheet distinguishes device assignment, a session interval and evidence linking the action to that session.
Timing can narrow the candidates. A link between the browser event and a particular session is stronger evidence.

Keep the exposure review moving#

Give the credential owner the event reference, tool, time and detector category. They can evaluate the possible exposure under their existing process. Keep prompt submission, credential validity and individual identity as separate questions. A help desk can route all three without recording the original pasted value.

Browser evidence trail identifies the paste gesture and the local inspection stages.
The browser gesture and its inspection remain useful even while the reviewer checks the account.

Write a ticket the next reviewer can defend#

Record the strongest statement you can support today. For this exercise it is a paste recorded on NS-WIN-014 at 09:44:30 UTC with an API-key pattern match. Route session verification to endpoint IT. Record the source and reason for any later attribution, including corrections, so the next reviewer can see how the conclusion changed.

Worked ticket records the observed Claude gesture, two candidate sessions and the next owners.
The sample handoff preserves what happened on the device and leaves the person field open pending corroboration.
Read the primary sources

Sources & further reading

  1. Open the Northstar device timeline
  2. Microsoft’s Windows logon event reference
  3. Microsoft’s Windows logoff event reference
  4. Employee AI visibility on managed Windows devices
← Back to all articlesBack to top ↑
A CLEAR PLACE TO START

Plan your AI visibility pilot.

Create a brief for your team. Your answers stay in this browser and are included in your download.

AI tools in scope
More supported tools

This creates a planning document. It does not enroll devices or submit a request.