FileDNA App
CADR for the messages people actually use.
FileDNA App connects to WhatsApp, Viber, and similar messaging platforms, pulls each incoming attachment, and runs it through FileDNA CADR on Server or Cloud. If the file needed to be disarmed or reconstructed, App replaces it in the conversation with the clean version — if it was already safe, the original stays untouched.
How It Works
App runs as a lightweight connector between a messaging platform’s API and whichever FileDNA engine is doing the analysis.
1
Connect
App registers with WhatsApp Business Platform, Viber, or a similar messaging API, and subscribes to incoming media and attachment events for the accounts you configure.
2
Pull the attachment
When a message with a file attachment arrives, App retrieves it through the platform’s own media API, without altering the original conversation.
3
Run CADR on Server or Cloud
The attachment is forwarded to FileDNA Server or FileDNA Cloud — not processed locally — and analyzed, disarmed, and reconstructed the same way any other file is.
4
Replace only if changed
If reconstruction altered the file, App sends the clean version back into the conversation in place of the original. If the file came back byte-identical, nothing is replaced.
Key Capabilities
Built for messaging platforms where the file has to keep working the same way it did before.
Server or Cloud, never local
App has no analysis engine of its own; every attachment is forwarded to FileDNA Server or FileDNA Cloud for the actual CADR work.
Conditional replacement
A file that comes back unchanged is left exactly as sent — App only swaps in a new version when disarming or reconstruction actually modified something.
Native to the platform’s own media API
Built against WhatsApp Business Platform and Viber’s own attachment and webhook APIs, not a proxy number or a forwarding bot users have to add.
Same verdict, same audit trail
Every attachment gets the same structured verdict and audit log as a file processed anywhere else in the FileDNA line.
Who It’s For
Businesses running customer-facing WhatsApp or Viber channels that accept file uploads — invoices, IDs, claims documents — from people outside the organization.
Security teams who want messaging-app attachments held to the same CADR standard as email and file-share traffic, without asking users to change how they send files.
Organizations already running FileDNA Server or FileDNA Cloud who want to extend the same engine to inbound messaging-app attachments.
App is a connector, not an engine of its own — it depends on FileDNA Server or FileDNA Cloud to actually process a file, the same way FileDNA Relay depends on Desktop, Server, or Cloud for email. Messaging platforms don’t expose a desktop-style local install point, so App only targets the two server-side engines.