Private quarantine
Keep new files isolated while inspection is pending.
Lupin Security · Staging
Document security and malware protection.
Lupin Security brings private file quarantine, integrity checks, malware inspection and signed verdicts into one shared protection layer for the Lupin ecosystem.
SECURITY
Overview
Scan jobs
Quarantine
Audit trail
Policies
File security workflow
Illustrative workflow · No customer data
Stage 01Quarantine
Stage 02Scan
Stage 03Decision
Example scan decisions
Example clean fileSigned clean
EICAR test fixtureBlocked
Awaiting reviewPending
Illustrative interface. Customer scan submissions are not yet enabled in staging.
The operating outcome
Give every document a verified decision before anyone can use it.
Protect your workflows with a consistent, auditable scan lifecycle. Each consuming Lupin product must separately verify the result and the user's permissions before releasing a file.
Integrity checks
Bind results to a specific file hash and object version.
Malware inspection
Run ClamAV with controlled signature updates.
Signed verdicts
Verify clean and infected results cryptographically.
Organisation isolation
Scope access by verified product and tenant identity.
Audit-ready events
Keep a record of each change in scan state.
How the workflow fits together
01
02
03
04
A clear path from upload to trusted file decision.
Receive
Hold a versioned file in private quarantine. No preview or download yet.
Verify
Confirm the exact storage version and SHA-256 content digest.
Inspect
Run the antivirus engine and record a signed terminal result.
Authorise
Only a valid clean verdict plus the product's own access rules may allow release.
Buyer questions
What organisations ask before they trust a file.
The answers explain the currently validated staging capability and the remaining controls needed for a customer rollout.
How does Lupin Security detect malware?
A dedicated worker reads a versioned quarantined object, checks its hash and inspects its content with ClamAV. A clean verdict must be signed before consuming products consider file release.
What happens if antivirus or storage is unavailable?
The scan fails closed. A pending, infected, failed or unverified document must remain inaccessible; the system does not treat an outage as a successful scan.
Can Lupin products share documents across organisations?
Access to scan jobs is scoped by the authenticated product and organisation. Products must also enforce their own document access controls. Cross-product customer rollout still requires final integration testing.
Is Lupin Security ready for production customer uploads?
No. The core pipeline passed controlled staging tests, but authorised product onboarding, least-privilege credentials and independent production security review remain required. Customer submissions are disabled.
How can we check the service?
Use the public API health check. Health reports process availability; it does not certify that production scanning is enabled.
Talk to the Lupin team
Bring us the information you need to protect.
We'll help shape the right secure intake, scanning and governance process as the shared service progresses through enterprise validation.