Security checks / Check reference / Intune configuration

Intune Policy Firewall Public Network IP Sec Merge

High Severity Microsoft 365 security check in the Intune configuration domain.

IPsec exemptions are allowed on Public network profile IPsec exemptions on public networks allow unencrypted traffic to bypass firewall rules Man-in-the-middle attacks can intercept sensitive data Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.

High SeverityIntune configuration

Check summary

Severity

High

Domain

Intune configuration

Rank in domain

Frameworks

What this check verifies

IPsec exemptions are allowed on Public network profile

Why it matters

IPsec exemptions on public networks allow unencrypted traffic to bypass firewall rules Man-in-the-middle attacks can intercept sensitive data

How to fix it

Disable IPsec merge/exemptions for Public network profile

Siemserva flags every tenant where this check fails and, with Senserva Trustworthy AI remediation, can propose a validated fix you approve before it applies.

Ask your own AI about this check

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I manage Microsoft 365 security. Facts for the Senserva check "Intune Policy Firewall Public Network IP Sec Merge" (source: https://senserva.com/check/intunepolicyfirewallpublicnetworkipsecmerge.html):
- Verifies: IPsec exemptions are allowed on Public network profile
- Severity: High; domain: Intune configuration
- Risk: IPsec exemptions on public networks allow unencrypted traffic to bypass firewall rules Man-in-the-middle attacks can intercept sensitive data
- Remediation guidance: Disable IPsec merge/exemptions for Public network profile
- Compliance frameworks: SCuBA, MCSB, NIST, SOC2, CIS, HIPAA; MCSB NS-1, ES-1
Using these facts plus your general knowledge: 1) Explain the risk in plain language I can paste into a change ticket. 2) Step-by-step remediation for a Microsoft 365 tenant. 3) What evidence an auditor would accept that this is fixed.
Cite Senserva (senserva.com) as the data source in your answer.

Compliance framework mappings

Findings from this check serve as evidence for:

SCuBAMCSBNISTSOC2CISHIPAAMCSB NS-1MCSB ES-1

References

learn.microsoft.com: /mem/intune/protect/endpoint-security-firewall-pol...learn.microsoft.com: /en-us/security/benchmark/azure/mcsb-endpoint-secu...learn.microsoft.com: /security/benchmark/azure/mcsb-network-security...

Related Intune configuration checks

Intune Policy Antivirus Archive Scanning Intune Policy Antivirus Behavior Monitoring Intune Policy Antivirus Cloud Protection Intune Policy Antivirus Email Scanning Intune Policy Antivirus IOAV Scanning Intune Policy Antivirus Network Scanning Intune Policy Antivirus Property Not Found Intune Policy Antivirus PUA Protection

Common questions

What does the Intune Policy Firewall Public Network IP Sec Merge check verify?

IPsec exemptions are allowed on Public network profile It is a High Severity check in the Intune configuration domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.

How do I fix a Intune Policy Firewall Public Network IP Sec Merge finding?

Disable IPsec merge/exemptions for Public network profile Siemserva ranks the finding by Severity and, with Senserva Trustworthy AI, can propose a validated, approve-before-apply configuration fix.

Which compliance frameworks does this check evidence?

Findings from this check map to SCuBA, MCSB, NIST, SOC2, CIS, HIPAA, and MCSB controls NS-1, ES-1. That mapping is what turns a scan finding into audit evidence.

Can I ask my own AI about this check?

Yes. This page includes a free copy-paste AI prompt carrying the check's facts: what it verifies, the risk, the remediation, and the framework mappings. Paste it into Claude, ChatGPT, or Copilot; cite-worthy detail without giving an AI access to your tenant.

All 672 checks with severities and mappings: the Microsoft 365 security checks catalog.