Do you recognize a good idea when you see one? We want to hear from you!
Header Image

I suggest you ...

Source IP restriction for website / paths

Please implement the ability to restrict access to specific paths on a website to defined source IP's. Usually this has been done on the webserver, but NAT'ting of the Webserver Protection breaks this feature on webservers (sees the internal IP of UTM instead of public source IP).

Usage Examples:

a)
Website globally allowed
path /administrator only allowed to defined source IP's

b)
Partner hosts a private company Website - should anly be accessible from Company public IP's
path / only allowed to defined source IP's

32 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Sascha ParisSascha Paris shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    3 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Anonymous commented  ·   ·  Flag as inappropriate

        Hello,

        I also need to restrict access to a single (or range of) host(s).

        That's useful for outsourced *********** tests in order to enable
        that company to perform tests under real conditions before a
        portal get's productive.

        Best regards, Uwe

      • Sascha ParisSascha Paris commented  ·   ·  Flag as inappropriate

        Hello Bob
        Only partly. The idea behind the feature is just, that you don't have to do IP filtering on the webserver(s) itself, but on the UTM's WAF ;o)

      Feedback and Knowledge Base