Secure file uploads by keeping new documents in private holding storage until the required validation and content checks pass. Release only that checked version, and authorize each person who tries to retrieve it. For an IT manager approving a customer portal, that means designing receipt, inspection, and access as separate steps.
A customer should be able to see that a document arrived while it is still being checked. Employees and other customers should receive access only when the application's release conditions are satisfied. This distinction lets background scanning take time without making an unreviewed file available in the meantime.
Follow a customer drawing from receipt to use
Consider a hypothetical fabrication business introducing a portal for customers to submit PDF drawings. Its estimator needs to open each drawing and prepare a quote. The proposed design accepts the upload, immediately creates a download link, and schedules a malware scan afterward.
That sequence leaves a gap: the estimator can open the file before the result arrives. Deleting a file after a harmful finding cannot undo an earlier download. The better sequence is receive privately → validate and scan → release for authorized use.
Microsoft's ASP.NET Core upload guidance describes this pattern: a background scanner checks files held in quarantine, and passing files move to normal storage with their status tracked. It also recommends a dedicated upload area, application-generated filenames, and disabling execution there. These are application-design examples, not capabilities automatically supplied by a web firewall.
For the fabrication portal, give each submission a unique internal identity. Keep the customer's filename as a display label rather than using it to choose a storage path. Show “Received—checking document” while the original remains inaccessible to ordinary download and preview functions.
Put the gateway and application checks in the right places
The public upload request needs protection before the application accepts it. Network Box USA's managed Web Application Firewall (WAF) service provides request inspection, application policy, rule tuning, monitoring, and reporting. Its WAF+ overview documents granular policies by user, path, and web address. Managed tuning helps apply the agreed request policy while keeping legitimate portal use working.
Include the upload route in that scope discussion. Confirm supported file sizes, request-body inspection limits, and treatment of the actual upload format. If the browser uploads directly to separate cloud storage, identify which control sees those bytes; protecting the portal page does not automatically put that storage transfer through its WAF.
The application team still implements storage permissions, scanner integration, and the release decision. The managed WAF scope does not establish an included object-storage scanner, quarantine workflow, or particular cloud integration.
Start the portal's acceptance policy with the formats the business needs. The OWASP File Upload Cheat Sheet recommends permitted extensions, file-type validation, size limits, and protected storage. It warns that the sender-supplied content-type label can be spoofed. Check that the contents match an allowed document type rather than trusting the PDF filename. Keep document-processing libraries maintained and constrain their permissions. A completed scan reduces risk; it cannot guarantee that every harmful file will be identified.
Capacity is another requirement. Bound both individual uploads and the work waiting for inspection. Our API rate-limiting guide explains the separate roles of request frequency, concurrent work, and usage quotas.
Make delayed and failed scans part of the workflow
Suppose the fabrication company's scanner becomes unavailable after a customer uploads a drawing. The proposed operating rule is to keep the document in holding storage, preserve its status, and notify the responsible operator. The estimator sees a processing delay instead of receiving an unchecked download link.
Show the customer whether to wait or contact support, and give the support team a submission reference. Agree when a stalled job is investigated, retried, or removed under the retention policy. A deadline for producing the quote should trigger escalation through that process, rather than silently changing the release condition.
Distinguish an incomplete scan from a completed result. For example, Amazon GuardDuty's documented scan outcomes separate no threats found, a detected threat, unsupported content, denied scanner access, and an internal failure. Those are AWS-specific statuses. In any chosen platform, map its actual outcomes to explicit application behavior; a skipped or failed check should remain unresolved.
AWS also documents storage access policies based on scan-result tags, including protection against unauthorized changes to those tags. The useful design principle is that the release state must be enforced by the system serving the file. Hiding the download button alone leaves other retrieval paths to consider.
Bind release to this version and this reader
Now suppose the customer replaces the drawing while the first scan is still running. Our recommendation is to create a new submission identity or immutable version and start its checks separately. A late result for the first drawing must apply only to that first version. It must not release whatever file currently happens to have the same display name.
After the replacement passes the required checks, the estimator assigned to that customer's quote may retrieve it. A different customer's account must still be denied. OWASP's authorization guidance calls for permission checks on every request, including access to static resources. A scan result and a reader's permission answer different questions.
For this portal, the IT manager can give engineering one concrete acceptance requirement:
Serve a drawing only when the requested version has passed the required checks and the requester is authorized for that customer's quote. Keep pending, failed, unsupported, and rejected submissions unavailable to ordinary readers. Replacing a drawing starts a new review.
Demonstrate that behavior in an authorized test environment with harmless documents: delay a scan, replace a pending file, and try retrieval through a second test customer's account. Include direct download and preview routes. This exercises the sequence that matters without introducing real malware.
To plan the gateway portion, contact our team with the upload route, permitted document types, expected workload, and the application owner's proposed release process. Those details let the WAF and application teams agree where their responsibilities meet.