Visible prompt-like text
Instructions addressed to an AI can sit inside ordinary sections, footnotes or appended content.
Document security for recruitment
Scan CVs before they influence AI-assisted screening.
Check candidate files before they enter an AI-assisted screening workflow. Follow each version’s decision and retrieve the current Approved copy, with candidate assessment kept human-led.
- Outside exact versionCandidate file
- Organise the recordChoose a Collection for the workflow
- Completed Standard ScanCheck and route
Three destinations
- ApprovedLibrary → current eligible version → Review workflow
- Needs reviewInvestigate, replace or recheck
- QuarantineKeep this exact version out
The Collection keeps all three outcomes organised. Membership does not grant approval or retrieval.
No decision: The scan could not complete, so no security decision was made. Retry is available and no new scan credit is consumed.
The recruitment problem
Candidate content can become input and instruction.
A CV is supposed to describe a candidate, but an AI tool may also respond to instruction-like text inside the file. Hidden or visible instruction-like content may influence a downstream summary, comparison or what a reviewer sees next.
Review the document before AI processing, then assess the candidate through your normal human-led process.
Understand document prompt injectionCandidate-file intake
Protect the integrity of the review workflow.
Use a consistent scan across the files an AI may summarise, organise or compare.
Content a reviewer may not notice
Supported hidden or machine-readable layers may be extracted even when they are difficult to see on the page.
Downstream influence
A manipulated summary or comparison can shape what a human reviewer sees and investigates next.
Your document workflow
Review the file before the AI reviews the candidate.
Keep document security separate from candidate assessment and apply it consistently.
- 1Receive the CV or candidate file through the normal channel.
- 2Choose the Collection for the hiring workflow, then check the supported exact file before AI-assisted summarisation.
- 3Follow Approved, Needs review or Quarantine; findings concern the document, not candidate merit.
- 4Keep the record organised in its Collection while you resolve a Needs review or Quarantine decision; membership never grants retrieval.
- 5Retrieve only the current eligible Approved exact version from the Library for authorised later review.
- 6Submit an updated CV as a replacement that needs its own scan, and keep candidate decisions human-led.
An accepted replacement supersedes the earlier version immediately, with no fallback while it is pending or held. Both versions remain in history. .mdSiren does not assess candidates, rank suitability or make employment decisions.
Before screening
Separate document integrity from candidate merit.
The scan should answer questions about the file and its supported content—not about whether a person should progress.
- Apply the same intake process to equivalent candidate files.
- Scan the exact file that will enter the screening workflow.
- Review supported findings independently of candidate assessment.
- Check coverage and retain appropriate human oversight.
- Follow applicable recruitment, privacy and data-retention rules.
This page describes a document-security checkpoint, not a recruitment recommendation or compliance guarantee.
Related resources
Before documents become AI context
Put a document check before AI-assisted screening.
Check incoming candidate files, follow the document decision and retrieve current Approved copies for authorised AI-assisted review.