In an IIS7 web application (ASP.NET) where we don't have control over source code, anyone visiting that application from the internet is presented with the login page.
To comply with security audits, the login page (a specific URL) must be locked down to internal IP network ranges only. In other words, internet users should be able to do everything except get to this login page.
It's easy to block/allow an entire site, but how can security for a specific page or URL be accomplished within IIS configuration?
You can use the "IP Address and Domain Restrictions" feature at the level of folders and virtual directories, as well as sites.
So, put the login page into one of those, and use IIS restrictions. (I mean, redesign the website with that in mind, don't just move it arbitrarily).
See also: https://stackoverflow.com/questions/8147804/ip-restriction-for-a-folder-of-a-web-application-in-iis7
In your web.config, add a section like this:
within the root configuration node.
Even though in the IIS UI it is not possible to apply settings to a single file, the configuration system does support this. The key is the 'path' attribute in the location node. Anything within that node only applies to the path specified.