™Scan the staged content
Apply customer-selected malware scanning, file inspection, and content analysis before a batch is eligible for release.
+Roadblock™
Staging, Inspection & Release
Apply customer security controls to a staged batch. Release only after clearance and verified outside teardown.
03YOUR INSPECTION. YOUR RELEASE POLICY.
Staging is a decision point.
Arrival does not mean approval.
The outside worker can deposit a batch into staging. It cannot authorize that batch to enter Hawkeye. Customers apply their security scanning and inspection in the staging zone; Roadblock permits internal delivery only after the configured controls have cleared the batch.
Validate the data
Check file types, schemas, allowed content, and the batch manifest. Preserve the link between source records, the diff, and the staged objects.
Enforce release policy
Define the checks that must pass and when human review is required. A pending or failed result keeps the batch held and the inside path closed.
Keep the transfer history
Retain job IDs, source identifiers, acquisition timestamps, batch hashes, worker lifecycle events, inspection results, release decisions, and delivery receipts under your policy.
Uncertain state means no release.
A failed scan, pending review, unknown connection state, or unconfirmed worker teardown keeps the transfer blocked. Additional scheduled jobs wait for the same protected transfer boundary to become available.
Carry provenance from intake to evidence review.
Preserve the original downloaded batch and record its source, collection time, and hash baseline in staging. Verify transfer integrity when the cleared batch reaches the private data lake, and retain those records for the evidence workflow. Supported forensic images can later be exported as EWF (.E01) with verification and custody documentation; native files retain their original format. Security clearance permits a transfer—it does not by itself authenticate evidence or establish a forensic acquisition.
Explore EWF evidence export