# SAMPLE: AI Observation Findings Report

> **SYNTHETIC SAMPLE. ILLUSTRATIVE LAYOUT.**
>
> - Customer, people, devices, vendors marked fictional, and all figures are invented.
> - This is not a Behavry product export. Behavry does not generate this report.
> - A provider prepares it by hand, from the connected sources' list views, audit export and alerts.
> - Use it as a starting structure, and replace every value.

| | |
|---|---|
| Customer | Northwind Example Co. (synthetic) |
| Service stage | Observation |
| Observation window | 2026-11-02 to 2026-11-12 (synthetic) |
| Prepared by | [Provider name], [analyst] |
| Reviewed with customer | [name, role, date] |
| Coverage statement | See *Coverage and limitations*, version [x] |

## 1. Summary

During the window, the connected sources showed **six AI services or integrations**:

- **One** was on a governed path, where individual actions were recorded.
- **Five** were not governed.
- **Two** showed observed usage.
- **Three** were detected only through licensing, grants, or deployment. Usage is not established for these three.

> Write the summary so a non-technical reader can see what was found, what was not looked at, and what you recommend. Do not describe licensed or granted services as "in use".

## 2. What we looked at

| Source | Connected? | What it can show | What it cannot show |
|---|---|---|---|
| Microsoft 365 admin API (`microsoft_365` connector) | Yes | Copilot licensing and enablement, enabled user counts | What users asked or did |
| Entra ID OAuth grants (`azure_ad`) | Yes | Third-party apps with granted scopes and principals | Whether the app was used, or sign-in history |
| Managed browser extension | Yes, on 38 of 412 devices (synthetic) | AI site visits, paste and input events, and DLP findings on those browsers | Unmanaged browsers, personal devices, and native apps |
| Desktop agent (Warden) | Yes, on 6 devices (synthetic) | LLM API call metadata and MCP configuration exposure | Devices without the agent |
| Citizen-code platforms (Replit) | Yes | Deployed apps and creator metadata | Platforms not connected |
| Governed MCP path for the helpdesk agent | Yes | Each tool call on that path, with the policy decision | Calls that bypass the configured path |
| Network, DNS or firewall logs | **Not a Behavry source** | | |

## 3. Findings

| ID | Finding | Detection level | Evidence | Risk (analyst) | Recommendation | Owner |
|---|---|---|---|---|---|---|
| F-01 | Copilot for Microsoft 365 enabled for the Finance pilot group (40 of 412 users) | Service detected | Licensing and enablement from the M365 admin API | Medium | Confirm the business owner and approved data scope. Review sensitivity labels on finance SharePoint sites before wider enablement. | Customer IT |
| F-02 | Fictional meeting-notes app holds mail and calendar read scopes for one user | Service detected | Entra OAuth grant | High | Confirm whether the app is approved. If it is not, the customer decides whether to revoke the grant. The provider does not revoke during observation. | Customer security |
| F-03 | ChatGPT web used with pasted content that triggered DLP findings | Usage observed | Browser extension events on managed browsers | High | Agree an acceptable-use position and decide whether to monitor DLP findings as an alert in the monitoring stage | Customer + provider |
| F-04 | Claude Desktop with two MCP servers configured on a developer machine | Usage observed | Warden metadata and configuration exposure | High | Identify what the MCP servers can reach. Consider placing them on a governed path. | Customer engineering |
| F-05 | Replit app with an AI agent and an external API, ungoverned for 10 days | Service detected | Citizen-app discovery | Medium | Review with the creator. A 30-day ungoverned alert would fire if it remains unreviewed. | Customer app owner |
| F-06 | Helpdesk agent's ticket tool calls recorded on the governed path | Action recorded | Signed audit events on the configured path | Low | Keep under observation. Candidate for monitoring alerts on write actions. | Provider |

## 4. Not established by this report

- That any listed service is the only AI in use. Coverage is limited to the connected sources in section 2.
- Usage of services detected only through licensing, grants or deployment.
- What content users entered, beyond DLP pattern findings on managed browsers.
- Any action outside a configured governed path.

## 5. Recommended next step

These are options, and nothing changes until the customer decides:

1. Remain in observation and repeat the review at an agreed cadence.
2. Move to **monitoring**: agree the alert signals and the review cadence, and who reviews, recommends, approves and responds (see *Monitoring handoff*). Nothing is blocked in monitoring.
3. Discuss **protection** for specific actions only, through the customer's change process.

## 6. Sign-off

| Role | Name | Date |
|---|---|---|
| Provider analyst | | |
| Customer reviewer | | |
