Content assurance and quarantine

Nothing crosses unchecked

Before anything moves, every file passes two separate stages: deterministic validation, then inspection by engines. A check answers only yes or no, and every answer is recorded with the version that gave it. ARP treats file names, extensions, declared types, archive structure and engine output as hostile input, and it checks only the bytes it hashed when it admitted the file, never the source file, which lies outside its trust boundary.

2: Separate stages: validation, then inspection
17: Deterministic validation rules
4: Inspection engines: data-leak detection, ClamAV, YARA and the AI model
0: Bytes altered in the delivered file

Seventeen validation rules

Group	Protects against
Naming	Names that break, mislead or escape the destination file system, including reserved device names and path traversal.
Type	Content that is not an accepted type, or whose detected type contradicts its extension.
Size	Files larger than the route and the appliance are provisioned for.
Archives	Archive bombs, entries that escape extraction, links pointing outside, and encrypted contents that cannot be inspected.
Active content	PDF and Office documents carrying embedded script or macros.

An encrypted archive is not judged malicious. It is content no engine can look inside, and a route that accepts one has made a deliberate choice.

From evidence to outcome

What was found	Outcome
A critical, high or medium finding	Quarantine
The AI model judges the file malicious or out of place	Quarantine
Only low or informational findings	Pass
No findings, and every required engine completed	Pass
A required engine did not complete or was unavailable	Failed as a fault of the mechanism, never quarantined

Quarantine is final

A quarantined file is never delivered. This holds in several independent places, so one mistake cannot open it. The appliance's processing has no way out of quarantine, the interface has no way to release it, the permission list has no release permission, and the quarantine page has no release button.

An operator can see every contained item with its route, its reason and its full evidence, export a report of its metadata, and dispose of it early with an audited reason. An operator cannot read, download, release or reprocess it. A wrongly quarantined file is settled with the owner of the system that produced it and, if the policy was wrong, by an audited change to the policy; the source then sends again.