---
schema_version: "1"
id: ff22b8dadab1d4b78c5a61df2459f65623c89091b3ae3e5eb2e29df43e5465fb
title: Migrating the Security Filters
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mule-runtime/4.3/migration-security-filters.md
canonical_url: https://docs.mulesoft.com/mule-runtime/4.3/migration-security-filters
source_site: docs.mulesoft.com
content_type: documentation
content_hash: c2aad58c3e77e5cfe50a98e8d0702c128a6e7b3b3994911a851029a4875aa682
description: MuleSoft Documentation Site
release: "4.3"
latest: false
---
---
product: Mule Runtime
version: 4.3
---

# Migrating the Security Filters

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

In Mule 3, the Security Filters where part of the Mule Module Security. In Mule 4, this where
migrated to the [Mule Validation Module](https://docs.mulesoft.com/validation-connector/latest/).

## IP filters

In mule 3 we had three different options to filter by IP: \* `<filters:filter-by-ip>` \*
`<filters:filter-by-ip-range>` \* `<filters:filter-by-ip-range-cidr>`

### Filtering By one IP

Example: Filtering by one IP in Mule 3

```xml
<filters:filter-by-ip regex="127.0.0.1"/>
```

This will filter those IPs that matches the regex. In mule4:

Example: Filtering by one IP in Mule 4

```xml
<validation:is-blacklisted-ip blacklist="iplist" ip="#[vars.ip]">
<validation:ip-filter-list>
	<validation:ips>
		<validation:ip value="127.0.0.1"/>
	</validation:ips>
</validation:ip-filter-list>
```

Where is necessary to set that `ip` variable (or whichever variable suits).

### Filtering by range of IPs

In mule 3, we had two ways of defining subnet mask to filter with:

Example: Filtering by IP range in Mule 3

```xml
<filters:filter-by-ip-range net="127.0.0.1" mask="255.255.255.0"/>
<!-- or -->
<filters:filter-by-ip-range-cidr cidr="127.0.0.1/24"/>
```

Both are replaced by:

Example: Filtering by IP range in Mule 4

```xml
<validation:is-blacklisted-ip blacklist="iplist" ip="#[vars.ip]">
<validation:ip-filter-list>
	<validation:ips>
		<validation:ip value="127.0.0.1/24"/>
	</validation:ips>
</validation:ip-filter-list>
```

Where is necessary to set that `ip` variable (or whichever variable suits).

1.  _Are there other similar validations added in mule 4?_

    Yes, there is also a WhiteList validation, which only allows IPs from a IP Filter List.

## Time Expiration Filters

In mule 3 we could filter the message if it had elapsed some defined time from a starting date. For
example:

Example: Filtering by elapsed time in Mule 3

```xml
<filters:filter-expired dateTime="#[vars.startingTime]" expiresIn="1000"/>
```

In Mule 4, this validation is in the validations module:

Example: Filtering by elapsed time in Mule 4

```xml
<validation:is-not-elapsed time="1" timeUnit="SECONDS" since="#[vars.startingTime]"/>
```

1.  _Are there other similar validations added in mule 4?_

    Yes, there is also a Time Elapsed validation, which validates if the time elapsed has exceeded a
    certain amount of time.

## See Also

[Validation Connector Technical Reference](https://docs.mulesoft.com/validation-connector/latest/validation-documentation)