Case #1: Filtering rules based on distinguished user profiles

Problem: How to provide multiprotocol, firewall filtering based on user’s ID, not only based on computer IP addresses?

Solution: EdenWall provides per user filtering: any organization with distinguished user profiles will find interest in this. Access permissions enforced by EdenWall are very strict: no insecure IP/Mac = User binding is ever performed.

For example, universities typically distinguish two distinct types of users:

Before using EdenWall, access lists on the firewall could only use the IP address of the computer opening a connection as criteria: A teacher trying to connect to the teacher’s server from a student workstation was therefore rejected.

Now that EdenWall is in use, the firewall knows which user tries to open each connection, and can use that strict ID criteria to decide whether access should be granted or denied. A teacher is granted access to the teacher’s server, even when connecting from a student’s workstation, even if several users are working at the same time on that same workstation.

Conclusion: Access permissions depend on the user’s ID, not only on their computer’s IP address. EdenWall relies on the exclusive NuFW® technology, which has no equivalent on the market.

Next case : EdenWall VPN - Typical use