Published

Keep a password-protected submission in a restricted intake state until the workflow can inspect the content or apply an approved exception. Give the sender a clear choice: provide an accepted replacement through the secure intake channel, or use the organisation's approved password-handling process. Record the outcome against the actual file received.
This matters when an application, claim, or supplier file contains a protected PDF or archive. Staff need to know why processing stopped, what the submitter should do next, and which resulting documents may enter review. The password, the inspection result, and the business acceptance decision each need their own handling.
A password prompt can mean different things. Adobe distinguishes a Document Open Password from a Permissions Password that restricts actions such as printing or editing. Check the file's protection and the chosen tool's behaviour before asking for credentials or changing its handling.
| Observed condition | Appropriate next decision |
|---|---|
| Opening the file requires a password | Hold it for the approved secret-handling path or request a permitted replacement. Record which inspection could not be completed. |
| The PDF opens but has permission restrictions | Determine which authorised operations the workflow may perform. Follow the content owner's instructions and configured processing policy. |
| The format or encryption is unsupported | Request an accepted format or route to a named exception owner. Keep the original and the reason for the request connected. |
| A scan times out, exceeds a limit, or reports a threat | Retain the specific result and follow its recovery or security-response path. A request for a password may be irrelevant to that failure. |
ClamAV documents separate encrypted-archive and encrypted-document heuristics. An enabled heuristic can flag encryption as a detection outcome. Interpret that result with the deployed scan configuration; it does not, by itself, identify malicious payload content. Confirm what was actually inspected before making a release decision.
Document intake does not always need a decryption service. Define the formats the business process accepts, the sensitivity of the content, and the available inspection route. Then give staff and submitters an actionable next step.
Use an approved portal or transfer channel to obtain an accepted document format. Tell the sender which file needs replacement and why. The replacement gets its own identity and inspection result.
Where protected submissions are expected, use a controlled password channel and an isolated, supported decryption process. Inspect the resulting content before releasing it under the intake policy.
An authorised evidentiary or archival workflow may retain the original without opening it. Record that decision, restrict access, and keep it outside normal searchable or review-ready content.
Assign an owner and an expiry or follow-up date to unresolved submissions. A reviewer should be able to distinguish awaiting a replacement, awaiting credentials, inspection failed, and ready for business review without reading a long support conversation.
Use an approved protected channel for the password, bound to the submission and authorised recipient or service. Avoid filenames, metadata, comments, email chains, ordinary ticket bodies, URLs, and notification text. The person reviewing the business evidence usually needs the inspection outcome, not access to the secret.
The OWASP Secrets Management Cheat Sheet covers restricted access, lifecycle management, and auditing. For this workflow, record that credentials were provided, which authorised process used them, and when access expired. Keep secret values out of logs and case notes; retire them and temporary material under the approved policy.
Set a bounded retry policy for a wrong password. Return a useful request to the verified submitter without echoing the supplied value. Staff should follow the same controlled path when helping someone complete a submission.
Keep the source, submission reference, document version or checksum, protection result, and selected handling route.
Use the approved credential and tool in an isolated worker. Validate the actual resulting files and record inspection outcomes.
Link permitted outputs to the original and move only the eligible versions into the business review workflow.
A decrypted or extracted file is a derived artifact with its own identity and content type. Record its parent reference, checksum, processing time, and relevant tool/scan details. Keep the original under its access and retention rules. A later replacement must receive a new inspection decision.
The OWASP File Upload Cheat Sheet recommends layered controls, including accepted formats, constrained storage, limited permissions, and checks on expanded size. For archives, bound total expanded bytes, entry count, nesting, processing time, and memory. Reject paths that escape the extraction area and file types the process does not accept. Give the worker only the filesystem, network, and secret access required for the job.
A clean malware result is one input to release. The file also needs to satisfy the configured format, processing, and business rules. For submissions arriving as attachments, see secure email document intake; the same release decision should apply across supported channels.
This fictional design accepts PDF evidence and permits credential-assisted inspection of supported archives. Submission SUB-00041 contains a protected evidence.zip for application CASE-2026-00041. The configured release policy holds the entire pack when a prohibited entry is found.
Intake records the received archive's reference and checksum. It reports that inspection requires an opening password and holds the file outside ordinary retrieval and processing. The verified submitter receives the approved replacement or credential-submission options.
The submitter uses the controlled credential form. The workflow binds the secret reference to SUB-00041 and limits retrieval to the inspection worker. The application record shows that credentials arrived, without showing their value.
The isolated worker opens the supported archive and applies its expansion and path limits. It identifies two PDFs and an executable. The executable is prohibited by this workflow's allowed-format policy, regardless of its malware result.
The pack stays held, including the two PDFs, and the submitter is asked for an accepted replacement. The decision retains entry-level results and the original archive reference. Another workflow could permit individual-file release, but it would need its own explicit rule and evidence.
The submitter uploads an accepted replacement. It gets a new reference and inspection results before release to the case reviewer. The file history connects both submissions, the reason for replacement, and the accepted versions. Credential access expires and temporary material follows the cleanup policy.
This example separates receipt, inspection, release, and the later business decision. The upload-confirmation guide covers the earlier question of whether the submitted bytes arrived.
Identify why inspection stopped, offer a permitted next step, and keep credentials separate from the document file. Controlled inspection and version-specific release decisions let the business review proceed with usable evidence and a clear history of how it arrived.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.