.mdSiren
Coming soon
Menu

Document security for AI systems

Check documents before they enter your AI systems.

Check incoming versions and keep approved copies ready for your agents and workflows. Inspect results in your private workspace, or connect your systems through Pro for document submission and approved retrieval.

Coming soonSee how it works

Five Standard Scans, once per account. No card required.

  • Checks before RAG ingestion
  • Clear handling decisions
  • Five scans, once per account

Illustrative product view

Check. Decide. Retrieve.

  1. Outside documentReference guide.md
  2. CheckStandard Scan
  3. DecisionApproved
  4. RetrieveApproved copy for your workflow

Other possible decisions

  • Needs reviewCheck the concern before use
  • QuarantineKeep this version out of AI work
Illustrative product view · Synthetic example

Why check first

A document can carry more than the words you see.

A document can contain hidden, active or instruction-like material alongside the words you see. .mdSiren helps you check it first and decide what should happen next.

Create one controlled boundary between outside documents and the systems that may reuse them.

Learn about prompt injection in documents
  1. ReceiveOutside document
  2. CheckStandard Scan
  3. DecideApproved, Needs review or Quarantine
  4. RetrieveApproved copy for your workflow

How it works

Check. Decide. Retrieve.

Scan the incoming version, follow its handling decision and retrieve the current Approved copy. Collections keep sources organised by project.

Illustrative workflow · Synthetic example

  1. 01

    Check the incoming version

    Choose a Collection for the client or project.

    Upload the source for scanning, then choose a Collection to keep related records together. An exact version means the file actually checked.

  2. 02

    Follow the decision

    Approved, Needs review or Quarantine.

    Use an Approved version, investigate a review finding or keep a blocked version out of your workflow.

  3. 03

    Retrieve the Approved copy

    Find it in your private Library.

    Download the current Approved file for your AI workflow, or use the Pro API for scoped document submission and eligible exact-version retrieval.

Three possible destinations

Supported checks clear

Approved

Required supported checks completed without a blocking or review finding. This version is added to your Library.

Retrieve the current Approved copy while its checks remain valid.

A next decision is needed

Needs review

A finding or coverage gap needs your attention before this version enters AI work.

Review it, replace it or retry.

In Quarantine

Quarantine

A blocking finding keeps this version out of normal reuse.

Keep it out of AI work and follow the finding.

Technical failure: If a scan cannot complete, no decision is made. You can retry without using a new scan credit.

Explore the workflow in detail

Collections and Library

Keep current Approved sources ready for retrieval.

Find current Approved copies in your private Library, ready for knowledge bases, agents and other document workflows. Organise sources into Collections and handle files needing attention in the workspace.

  • Collections keep every document status together without changing its decision.
  • Approval stays with the exact version that was checked.
  • When a revised file arrives, check the new version before using it.

Pro API. Submit documents, act on their decisions and retrieve eligible Approved exact-version copies for agents and automated workflows.

Explore the Library
Your Library

Reference guide.md

Approved · Supported checks clear

Collection
Knowledge-base sources
Checked copy
Current exact version
Next step
Retrieve for your workflow
Illustrative Library record · Synthetic example

Use cases

One checkpoint for knowledge bases and agents.

Check sources before RAG ingestion or agent access, then apply the same boundary to research, client work and other document-based applications.

Explore use cases

What it scans

See beyond the visible page.

Standard Scan checks supported visible and machine-readable content, then shows what completed and where coverage was limited.

  • Prompt-injection signals
  • Hidden and instruction-like content
  • Supported sensitive-information patterns
  • Links and active document surfaces
See what .mdSiren scans
  • Visible pageWhat you read
  • Machine-readable layerWhat software may extract

From the blog

Make document and AI decisions deliberately.

Practical guidance on prompt injection, document security, information handling and AI governance.

Read the blog

Common questions

The essentials, clearly.

What is .mdSiren?

.mdSiren is a document security checkpoint for AI systems. It checks each supported incoming version, gives it an Approved, Needs review or Quarantine decision, and keeps eligible Approved copies available for people and authorised Pro integrations.

Can I use it today?

Yes. Free and Pro access are available now. Start with five Standard Scans, once per account, with no payment card required.

What do Approved, Needs review and Quarantine mean?

Approved means required supported checks completed for the exact version without a finding that blocks approval or needs review. Needs review means a finding needs attention or required coverage is missing. Quarantine keeps a version with a blocking finding out of normal reuse. Manual approval override is not available.

All product questions

Before documents become AI context

Build your checked document Library.

Five Standard Scans, once per account. No card required.

Coming soonSecurity and scope