Malware scanning
Scan files using maintained antivirus signatures.
Safeput receives uploads into private temporary storage, verifies the actual file contents, scans for malware, and makes only clean files available for retrieval.
Private by default. Fail closed before retrieval.
What Safeput verifies
Every upload is inspected against the file itself—not just what the client claims it is.
Scan files using maintained antivirus signatures.
Determine format from the file’s contents and compare it with its extension and declared MIME type.
Compare declared and received byte counts and enforce the project limit.
Reject encrypted archives, PDFs, and Office documents that cannot be inspected safely.
Detect macros in supported Office formats and apply the project’s upload rules.
Limit archive depth, entry count, expanded size, compression ratios, and unsafe paths.
How Safeput protects files
Safeput keeps untrusted files private through upload, inspection, and retrieval.
Files go directly into private temporary storage. They do not need to pass through your application server.
Safeput gives the scanner temporary access to one specific object and validates it before and during inspection.
Only files with a clean verdict become temporarily available to your application.
Infrastructure & data protection
API, upload, and retrieval traffic use HTTPS.
Uploaded objects are not publicly accessible.
Inspection runs separately from the public application layer.
Administrative and service access is limited to what is operationally required.
Malware scanning and file validation substantially reduce the risk of accepting untrusted files, but no scanner can guarantee that a file is harmless. Applications should continue to process uploaded content defensively.
Ready when you are
Secure the files entering your application without operating the scanning infrastructure yourself.