Restrict Umbraco Back Office by IP

Reasons behind IP restriction:

In some cases, having the back office open to the public can be an issue for security, especially for high profile websites as it starts to become an issue for brute force. Not to mention employees accessing the admin interface from home or other unauthorised locations such as libraries etc.

A quick fix for this is to add an IP restriction to the Umbraco directory so that only people in authorised locations can access the service. Employees would then have to use a VPN or wait until they're into the office before they could access the UI.

Applying an IP restriction to the Umbraco back office so that is displays a 404 error:

To apply the restriction, you'll need to create a new web.config file within the Umbraco directory, providing one doesn't already exist, and add the following XML to it, then add/remove/update the IP addresses referenced in the example below so that they match the IP addresses of the office locations you'd like to grant access:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <rewrite>
            <rules>
                <rule name="RequestBlockingRule1" patternSyntax="Wildcard" stopProcessing="true">
                    <match url="*surface*" negate="true" />
                    <conditions>
			<add input="{REMOTE_ADDR}" pattern="123.456.789.10" negate="true" />
                        <add input="{REMOTE_ADDR}" pattern="963.852.741.123" negate="true" />
                    </conditions>
                    <action type="CustomResponse" statusCode="404" statusReason="File or directory not found." statusDescription="The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable." />
                </rule>
            </rules>
        </rewrite>
    </system.webServer>
</configuration>

Once you've implemented that, anyone trying to access the back office that doesn't have one of your defined IP addresses will see a 404 error within the browser.

Other methods:

Other methods of protecting the back office might include changing the directory that it resides in.


Published at

Tags: Umbraco,IIS

Luke Alderton

Comments

Post a comment
Sit tight...
We're adding your comment.
Thank you.
Your comment has been added.
There's been a problem.
Please try again later.
Share with
Tags
Latest Comments
By jack of ass on Replacing the Xamarin Header/Navigation bar with a custom view/template
16 Feb 2019, 03:13 AM
By Zal on Xamarin MasterDetailPage has large margin/padding at top
7 Feb 2019, 12:20 PM
By AndrewEcopE1 on MVC forms in Umbraco
7 Feb 2019, 01:16 AM
By AndrewEcopE1 on MVC forms in Umbraco
4 Feb 2019, 23:53 PM
By Ramachandran on Reducing Umbraco memory usage by enabling 32-bit applications
4 Feb 2019, 17:39 PM
By encoderu9 on MVC forms in Umbraco
4 Feb 2019, 10:51 AM
By AndrewEcopE1 on MVC forms in Umbraco
28 Jan 2019, 19:48 PM
By Luca Ziegler on Xamarin Forms app not updating after deploy
25 Jan 2019, 11:00 AM
Categories
App Development
Event
Game Development
Mapping
Modelling
Programming
Review
Robotics
Tutorial
Web Development