Shadow AI Risk Kit — Software edition · Prepared by Engineering operations lead
0 of 7 sections reviewed by the preparer. Review marks describe the entries, not whether controls are operating.
24 employees and 4 contractors across engineering, support and operations
An enterprise prospect asks about AI in your company and product.
This report summarizes your records. The Full record export preserves complete notes, entries and review coverage.
Confirm the scope and supporting evidence with the owners. Resolve or clearly disclose open conditions. Choose the full record when the recipient needs detailed answers or evidence locations.
Shadow AI Risk Kit — Software edition · Prepared by Engineering operations lead
The five reviewer priorities recorded so far, with the next action already in the register. This page is a briefing for leadership. Respondent names are omitted; review free-text notes and action owners before sharing.
| Risk | Priority | What we are doing |
|---|---|---|
| Customer-data processing and log redaction are not yet verified | Priority | Customer-data processing and log redaction are not yet verified. Support and security owners confirm permitted fields and retention before use · Engineering manager |
| A suggested dependency still needs provenance and license review | Investigate | A suggested dependency still needs provenance and license review. Engineering manager reviews generated code, dependencies and test results before merge · Engineering … |
| Two contractors have not confirmed personal assistants or repository connections | Investigate | Two contractors have not confirmed personal assistants or repository connections. Product owner checks actual behavior and avoids unsupported security or AI claims · E… |
Shadow AI Risk Kit — Software edition · Prepared by Engineering operations lead
Urgent and Priority records appear first; reviewer judgments are not automated. Showing 1–3 of 3 records. Long cells are excerpts; full wording is in the internal working record.
| Use / scenario | Priority | Owner |
|---|---|---|
| U-2 · Customer-data processing and log redaction are not yet verified | Priority | Engineering manager |
| U-1 · A suggested dependency still needs provenance and license review | Investigate | Engineering manager |
| U-3 · Two contractors have not confirmed personal assistants or repository connections | Investigate | Engineering manager |
Shadow AI Risk Kit — Software edition · Prepared by Engineering operations lead
3 recorded uses; 0 record-supported. Groups with missing information appear first. Counts do not establish complete discovery. Showing 1–2 of 2 records. Long cells are excerpts; full wording is in the internal working record.
| Team / source | Responses / coverage | Open gap |
|---|---|---|
| Staff | 24 of 24 / Reviewed | Responses are disclosures, not technical verification. |
| Contractors and associates | 2 of 4 / Partial | Two contractors have not confirmed personal assistants or repository connections |
Shadow AI Risk Kit — Software edition · Prepared by Engineering operations lead
Each record is one reported AI use. File imports and source approval claims do not grant approval. Review permissions and conditions in the full record. Showing 1–3 of 3 records. Long cells are excerpts; full wording is in the internal working record.
| Tool / use | Purpose / information | Owner / status |
|---|---|---|
| U-1 · CodeDraft | Generate test ideas for an internal utility · Synthetic fixtures and public example code | Engineering manager / Restricted |
| U-2 · SupportDraft | Draft responses from customer support tickets · None pending permission review | Engineering manager / Unapproved |
| U-3 · DocsDraft | Draft documentation from public product information · Published release notes and synthetic examples | Engineering manager / Restricted |
Shadow AI Risk Kit — Software edition · Prepared by Engineering operations lead
3 open actions. Open actions first, then earliest recorded due date. Completed entries remain visible. Showing 1–3 of 3 records. Long cells are excerpts; full wording is in the internal working record.
| Next action | Owner | Due / status |
|---|---|---|
| A suggested dependency still needs provenance and license review. Engineering manager reviews generated code, dependencies and test results before merge | Engineering manager | 2026-10-22 / In progress |
| Customer-data processing and log redaction are not yet verified. Support and security owners confirm permitted fields and retention before use | Engineering manager | 2026-10-22 / Blocked |
| Two contractors have not confirmed personal assistants or repository connections. Product owner checks actual behavior and avoids unsupported security or AI claims | Engineering manager | 2026-10-22 / In progress |