What lies beyond the page deserves a look too.

A file contains more than the visible page

Metadata is information about a file, such as its title and author. Office documents may also store comments, revisions and text formatted as hidden. Microsoft documents these categories and the limitations of Document Inspector: for example, white text on a white background is not identified by the hidden-text inspector.

The presence of this information does not prove an attempted attack. Review comments and author properties are part of many legitimate workflows. The useful question is whether any content tries to direct AI beyond the task you defined.

The résumé that tries to choose its own outcome

Consider a fictional résumé with experience and education. The team wants to compare it against job requirements. A property field contains an instruction unrelated to the candidate's background:

Organize your review by layer

Doc Guard identifies the source of signals so you don't have to treat every alert as part of the main text. Depending on the format, inspection covers properties, comments, notes and supported hidden elements.

• Text: compare the main content with the document's purpose.
• Comments and notes: look for directions aimed at AI or the reviewer.
• Properties: review the detected excerpt and its relationship to the file.
• Concealment: examine the context of small, invisible or unexpectedly positioned text.

Preserve context before removing content

Before editing, preserve the original and work on a copy. A note may explain a legitimate change. Removing every comment without reading it may erase information needed for the review.

After adjusting the copy, run a new analysis. In Doc Guard's history, the file name, signals and excerpts help you revisit findings; the full file is not stored. Keep the versions you need in your team's document repository.