What this solves#
Files coming in from outside, or going out to a partner, have to be scanned. Usually that means:
- Transfer in one place, scanning in another, with a person moving files between them
- Extra hops, uploading to a scanning server and back
- Evidence of the scan living apart from the transfer record
INNORIX attaches the security tool you already run to the transfer step. Files are scanned where they move, a detection is handled the way you decided beforehand, and the result lands in the same run record.
Who this is for#
| Role | When |
|---|---|
| Security | Scanning inbound and outbound files is mandatory |
| System administrator | You want the antivirus or EDR you already run wired into transfers |
| Audit | Evidence of scanning has to come from the transfer record |
The tools you can attach#
Pick them under Security, inside the Integrations group in the left menu. There are 18 in all, and the count beside Available integrations counts only the ones not yet connected: connect one and it moves up into Connected providers, leaving 17 below.
| Kind | Tools |
|---|---|
| Antivirus and malware | McAfee ENS, Avast Antivirus, AVG AntiVirus, Clam AntiVirus, Kaspersky KES, Symantec Norton |
| EDR | CiscoAMP, CrowdStrike Falcon, Fortinet FortiEDR, Palo Alto Cortex, Bitdefender GravityZone, Trend Micro Apex One, SOPHOS, Microsoft Defender |
| Content scanning and sanitization | OPSWAT MetaDefender |
| DLP and content | Vitrium Security, Microsoft Purview |
| CASB and DLP | Skyhigh Security SSE |
Each tool advertises what it can do. The badges on its card are Antivirus, EDR, DLP, Malware, Content scanning, File sanitization, Threat intel, CASB and WildFire, and the filter above the list narrows to tools with a given one.
If your tool is not listed, a transfer step can call an external API as a follow-up job instead. See Add File Transfer Capabilities to Web, App, and Business Systems.
Connecting it and attaching it#
Step 1. Connect the tool#
- Integrations → Security in the left menu. The panel has two parts: Connected providers at the top ("Nothing is connected yet" until you add one) and Available integrations below. Each heading carries a count: there are 18 tools in all, and connecting one moves it up, so the lower count drops to
17(it has not gone missing). The lower part has anAll categoriesfilter that narrows by what a tool does -Antivirus,EDR,DLPand so on, the same tags the cards carry. - Press the card for the tool you run. A detail panel opens with two tabs.
- On the Connection tab, enter the connection details. They differ per tool, and fields such as URLs and keys are format-checked.
- On the Scan policy tab, set the three options described below. The screen order is
Scan timing, thenScan scope, thenWhen a threat is detected. APolicy summaryat the bottom reads your choices back in one sentence, such as "Scan all files before transfer. Block the transfer if a threat is detected." - With the connection details in, Test connection checks them first. Finish with Connect - beside it there is only
Cancel, and no Save button. The tool then moves up into Connected providers. To change a tool you already connected, press Manage on its card.
The card up top summarises what you set —
Scan timing,On detection,Scan scope, andLast checkedfor when it last ran.One setting carries two names. Where you set it, on the
Scan policytab, it readsWhen a threat is detected; on the summary card it readsOn detection. They are the same setting.A value showing
Not setis not a fault. It means the connection was saved with no scan policy, which is what a connection created by a Flow looks like. Fill it in on theScan policytab.
Step 2. Attach it to a transfer step#
- Flows → pick the Flow → Edit flow.
- Select a step and find the What's next group in the panel on the right. Its header counts what you have set (
0 configured) and a card you have not set yet readsNot added. There are six cards:Security,Post to app,Monitoring,Calendar,EmailandRun. - Add the Security card. The only choices are the tools you connected in step 1. With nothing connected there is nothing to pick, so finish step 1 first.
- Change anything that should differ for this step alone. Connection details are folded away under
Connection; what stays open is what this step does with the tool. - Save & activate.
The three settings live in two places. What you set when connecting the tool (
Integrations→Security→Scan policy) is the baseline; attaching it to a step lets you differ for that step. Most teams set it once at connection time.
The settings, and how to choose#
Scan timing — when it scans#
| Option | Meaning | When |
|---|---|---|
Before transfer at source |
Before sending, at the source | The default. A bad file never leaves |
After transfer at target |
After arrival, at the destination | When evidence must be destination-side |
Before and after transfer |
Both | When inbound and outbound are both controlled |
Scanning at the source saves bandwidth, because a bad file is never sent. Scanning at the target gives you "we scanned what we received". Under regulation, Before and after transfer is the safe choice.
When a threat is detected#
| Option | Meaning | When |
|---|---|---|
Block transfer |
The transfer is stopped | The recommended setting for inbound control |
Alert only |
Notify, but still send | While you are only observing |
Admin confirm |
Wait for an administrator | When a false positive must not block the business |
When first adopting this, run Alert only for a week or two to see the false-positive rate, then switch to Block transfer.
A connected tool's summary card may read
QuarantineorRemove. Those are values left in older data, and the editor now offers only the three above. If you see one, save the policy again to land on one of the three. Do not leave it unread --Removedeletes the file.
Scan scope — what gets scanned#
| Option | Meaning |
|---|---|
All files |
Everything |
Executable files only |
Executables only |
Custom extensions |
Extensions you name |
Scanning everything on a Flow that moves millions of small files daily adds a lot of transfer time. If the risk is concentrated in executables, narrowing to Executable files only is a reasonable trade.
There is no field for files to leave out. The only way to narrow what gets scanned is the three
Scan scopevalues above, and pickingCustom extensionsdid not reveal a field for naming extensions (checked on screen, 2026-11-15). If one particular set of files must be left out, the way to do it is to split the Flow so that step carries no Security card.
Worked settings#
| Situation | Scan timing | When a threat is detected | Scan scope |
|---|---|---|---|
| Design files received from partners | After transfer at target |
Block transfer |
All files |
| Inbound to an air-gapped network | Before and after transfer |
Admin confirm |
All files |
| Distributing internal build output | Before transfer at source |
Block transfer |
Executable files only |
| Collecting inspection data, millions of small files | Before transfer at source |
Alert only |
Custom extensions |
| Customer portal uploads | After transfer at target |
Block transfer |
All files |
| The first two weeks of adoption | unchanged | Alert only |
All files |
Reading the result#
Scan results land in the same run record as the transfer. There is nowhere else to look.
Assurance records two different things:
| Name | Code | Meaning |
|---|---|---|
Malware detected |
SEC-05 | Malware was found. The most serious severity |
Malware scan incomplete |
SEC-15 | The scan did not finish. Not the same as finding nothing |
They are different. Malware scan incomplete means "unknown", not "clean". It happens when the scanning service did not answer or the scan was cut short. It does not resolve itself, so a person has to look.
The Assurance report shows the security outcome as a condition row:
✓ Security & evidence no violations PassedThis row ends three ways, not two. It is where the two issues above part company.
| Marker | What the row reads | Row verdict | Contract Status |
When |
|---|---|---|---|---|
✓ |
no violations |
Passed |
Satisfied |
It scanned and found nothing |
✕ |
Malware detected |
Failed |
Violated |
SEC-05. It scanned and found something |
! |
not verified: Malware scan incomplete |
Not verified |
Indeterminate |
SEC-15. The scan did not run, so nothing is known |
The third one is the point. A scan that did not happen is not a violation; it is "not verified". The bar is yellow rather than red, the conditions header reads 1 condition not verified rather than 1 condition failed, and the run summary becomes Recovery: Needs Attention with Contract: Indeterminate. It counts as neither a pass nor a failure, so a report that only counts failures will not show it.
What happens on Malware detected is set in the Handled by INNORIX group under Error handling:
Malware detected Follows the security integration settingThat is, it follows the When a threat is detected value you chose above. There is nothing separate to set on the Assurance side.
Errors and exceptions#
| What you see | Meaning | What to do |
|---|---|---|
Malware scan incomplete (SEC-15) |
The scan did not finish | Check the scanning service. Do not read it as clean |
Malware detected (SEC-05) |
Something was found | Handled per When a threat is detected. Quarantine and review happen in the security tool |
| The card stays in a needs-setup state | Connection details are incomplete | Fill the required fields. URLs and keys are format-checked |
| Transfers got noticeably slower | The cost of scanning everything | Narrow Scan scope, or scan on one side only |
| A false positive blocked the business | Block transfer fired |
Move to Admin confirm temporarily and clean up the exclusion list |
| You cannot tell whether it was scanned | No Security card on that step | Check What's next in the Flow editor |
Operating notes#
- Never read
Malware scan incompleteas a pass. It is the most dangerous misreading. The scan did not happen; the file is not known to be clean. - Do not start with
Block transfer. One false positive can halt an entire overnight rollout. Observe withAlert onlyfirst. - There is no exceptions field. You cannot excuse one file that keeps tripping the scanner, so give
Alert onlya long enough observation period before moving toBlock transfer. - Scanning cost scales with file count. Scanning everything on a Flow with millions of small files lengthens the run and collides with deadline conditions.
- It attaches per step. In a multi-step Flow, check which step carries the card. Scanning the collection step but not the distribution step is only half the job.
- Destination-side scanning is the stronger audit story, because "we scanned what we received" is in the record.
By industry#
| Industry | How it is used |
|---|---|
| Finance | Before and after transfer for both directions, with Admin confirm so a false positive does not stop work |
| Public sector and defense | Mandatory for air-gapped inbound: Block transfer and full scope, with the record as audit evidence |
| Manufacturing | Destination scanning for partner design files, source scanning for executables going to equipment |
| Healthcare | Destination scanning for inbound imaging, with Scan scope tuned for size |
| Media | Destination scanning for partner masters, scanning on one side only because files are large |
| Retail | Executable files only for software going to store terminals |
See also#
- Scan Received Files with Microsoft Defender and Perform Follow-up Processing — one tool in depth
- Decide in Advance What Happens When a Transfer Goes Wrong —
Malware detectedandHandled by INNORIX - Securely Importing and Exporting Files in Air-Gapped and Network-Segmented Environments
- Define Transfer Success with an Assurance Contract — the
Security & evidencecondition