Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Advanced Malware Threat Protection is an AI-powered inspection capability for Azure Firewall Premium. It analyzes supported files in outbound internet and east-west traffic to detect potentially unknown, obfuscated, or polymorphic malware. It adds file analysis to the firewall's existing signature-based protections.
This article shows you how to create a security profile group that contains a malware profile, and apply the group to application rules. Start in Alert only mode to evaluate inspection before you select Alert and deny.
For the shared prerequisites and profile/group/rule model, see Azure Firewall AI Security concepts. For request-based analysis of application exploit attempts, see Configure Advanced Application Threat Protection.
Important
Advanced Malware Threat Protection is currently in PREVIEW. See the Supplemental Terms of Use for Microsoft Azure Previews for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
Prerequisites
- Azure Firewall Premium with a license for the AI Security add-on, in a region where the preview is available. See Azure Firewall AI Security concepts.
- The AI Security add-on enabled on all firewalls associated with the firewall policy.
- An Azure Firewall Policy with application rules covering the outbound or east-west traffic that you want to inspect.
- For HTTPS traffic, working TLS inspection and client trust in the inspection certificate authority. For certificate and Key Vault requirements, see Azure Firewall Premium certificates.
- An authorized test environment with a benign control file and a safe, approved malware-test artifact for validation. Don't use live malware or production data.
During the preview, configuration is available only in the Azure portal.
Inspection scope
Advanced Malware Threat Protection inspects supported file uploads and downloads over HTTP or HTTPS. Traffic must traverse Azure Firewall and match an application rule associated with the malware security profile through a security profile group.
For HTTPS traffic, TLS inspection must successfully decrypt the content before file inspection can occur. Traffic selected for bypass skips malware inspection.
Inbound traffic is outside the initial release scope. Don't assume that every file transfer or protocol is inspected.
Configure Advanced Malware Threat Protection
Create a security profile group that contains a malware profile, and then associate the group with the application rules that select traffic. Creating a profile or group alone doesn't enable inspection for a traffic flow.
Create a security profile group with a malware profile
- In the Azure portal, open your firewall policy.
- Select Settings > Security Profile Groups (preview) > Create security profile group.
- On the Basics tab, enter a configuration name and select Advanced malware threat protection (preview). Select other protections to include in the same group.
- Select Next.
- On the Configure protections tab, create a new malware profile or select an existing one:
- To create a profile, enter a profile name.
- To reuse a profile, turn on Use existing Advanced malware threat protection security profile and select the profile.
- For Mode, select Alert only for the initial evaluation. The other options are Disabled and Alert and deny.
- Under Risk threshold, set the Alert percentage for the risk scores that you want to review.
- Select Next, review the settings, and then select Create.
An action is triggered when the file's risk score is greater than the configured threshold. A lower threshold triggers the action at lower risk scores.
A security profile group can contain at most one profile of each type. Other protection profiles are optional.
Apply the group to application rules
Before changing a rule, check whether a matching network rule allows the same traffic. Azure Firewall processes network rules before application rules, so that traffic might not reach the application rule that applies the malware profile. For more information, see Azure Firewall rule processing.
- In the firewall policy, select Rules > Application rules.
- Create or edit the application rule for the traffic that you want to inspect.
- Scope the rule's sources and destinations to the intended traffic.
- Select the security profile group that contains the malware profile.
- Configure the protocol for the traffic:
- For HTTPS, use HTTPS:443 and enable TLS inspection on the rule.
- For HTTP, use HTTP:80. TLS inspection isn't required for unencrypted HTTP traffic.
- Save the application rule.
Verify inspection in Alert only mode
Use a controlled test before applying blocking to a wider scope.
- Confirm that the test traffic traverses the firewall and matches the intended application rule.
- Check the rule's security profile group, the selected malware profile, the Alert only mode, and the alert threshold. Check that a bypass entry doesn't exclude the test traffic.
- For HTTPS, confirm that TLS inspection succeeds and that the client trusts the inspection certificate authority.
- Transfer a benign control file and a safe, approved malware-test artifact through the same scoped inspection path.
- Review the alerts and recorded actions for the test transfers. Compare the observed risk scores with the configured alert threshold.
A successful transfer alone doesn't prove that malware inspection occurred. Confirm the inspection result before enabling blocking. For existing firewall monitoring guidance, see Monitor Azure Firewall.
Enable blocking after evaluation
After reviewing the results in Alert only mode:
- In the security profile group, edit the malware profile and change Mode to Alert and deny.
- Set both the Alert and Deny risk thresholds for your requirements.
- Repeat the approved tests in the authorized test environment.
- Confirm that a transfer is denied when its risk score exceeds the deny threshold. Repeat the benign control test and review the recorded actions before widening the rule's scope.
If inspection doesn't produce the expected result
Check the following items before changing thresholds:
- The traffic traverses the firewall and matches the intended application rule.
- A network rule doesn't match the traffic before the application rule.
- The application rule references the intended group, and that group contains the correct malware profile.
- The profile mode, thresholds, and bypass entries match the test.
- HTTPS traffic is successfully decrypted, and the client trusts the inspection certificate authority.
Don't interpret an absent alert as proof that a file is safe or that inspection occurred.
Limitations
- HTTPS content can't be inspected without successful TLS decryption.
- Inspection applies to supported files in scoped application traffic, not to every file or protocol.
- Risk verdicts are probabilistic and can produce false positives or false negatives. A verdict isn't proof that a file is benign or malicious.