What Uninspected means
Uninspected means the sample does not have a completed content inspection. It must not be read as No PII or safe content. The demo includes an encrypted document whose content is unavailable, and a network-only connection for which no document transfer is confirmed.
These examples have different evidence. The encrypted-document example can show Confirmed because the fictional upload was observed, while its contents remain unknown. The connection example shows Inferred because it does not establish that a document was uploaded at all.
Explore an uninspected scenario
In demo mode, select Uninspected content under TRY A SCENARIO, or choose it in Simulate an agent event. Select a fictional endpoint and AI destination, then choose Simulate event. No encrypted file or other document is actually uploaded.
In the resulting drawer, read Inspection, Classification findings and Evidence trail. The notice explains that uninspected content cannot be treated as safe. The source description tells you why coverage is missing in the fictional example.
Compare it with a policy
Open Policies and examine Monitor uninspected content, or create a rule with Data condition set to Uninspected content. Choose an AI destination and Endpoint group, then save the sample policy. Enabled matching rules appear in the event's Evidence trail.
The uninspected scenario is medium risk in the current fixtures. Investigations currently lists high-risk events, so absence from that queue does not mean the coverage gap disappeared. Use AI activity to keep reviewing it.
The preview does not inspect files
All current findings and inspection states are fictional. There is no live parser, OCR service or endpoint classifier connected to the public app. The planned system must report unsupported or unavailable inspection explicitly; the demo is illustrating that distinction, not publishing a verified file-format support list.