Implementation guide
OWASP AISVS v1.01
Monitoring, Logging & Anomaly Detection · Training Data & Model Lifecycle Audit
Tag documents with source and writer
Verify that every ingested document is tagged at write time with source, writer identity, and timestamp.
OWASP AISVS v1.01, requirement 12.5.4
In plain English
Tag every document, at the moment it is ingested into a knowledge base or memory, with its source, the identity that wrote it in and the time. When bad content is found, these tags tell you where it came from and what else arrived by the same route.
What good looks like
- Source, writer identity and timestamp are set at write time on every document.
- The tags are set by the ingestion service from its own verified context.
- The tags cannot be changed afterwards (see 8.1.2).
- Retrieval, filtering and investigations can use them.
How teams usually do it
- The ingestion service stamps the tags from the authenticated caller and the connector in use. It never reads them from the document or from fields the client supplies.
- Storing the tags as metadata on every chunk made from the document.
Suggested evidence
- Ingestion code.
- Sample metadata.
- A query listing everything written by one identity in a time window.
Common mistakes
- Letting the uploader fill in the source field.
- Tagging the document and not the chunks.
- One shared service identity as the writer for everything, which tells you nothing.
Not sure which requirements apply to your system? Take the assessment, or browse every guide in this chapter.
Requirement text from the OWASP AI Security Verification Standard, licensed under CC BY-SA 4.0. This guidance is shared under the same licence.