Disclaimer: This is one of those posts that unashamedly links off to loads of other clever people.
ELMAH get loads of love, and recently has been the subject of many posts about implementation with ASP.NET MVC. With the recent 1.0 release I thought I would build into a site due to go into production in the near future so obviously needed to protect it from evil doers. First link is a great one for describing the basic implementation of ELMAH on ASP.NET MVC.
So that's it up and running - if it took you more than 10 minutes I would be suprised!
Next to restrict access to the log target. Phil Haack posted a while back about securing ELMAH with ASP.NET which takes very little additional effort to apply up to a secured ASP.NET MVC site (obviously).
The approach is to pass the handler down to a different path by changing the handler config - in this case adding path detail logs (and changing the elmah to exceptions):
<add name="Elmah" verb="POST,GET,HEAD" path="logs/exceptions.axd"
preCondition="integratedMode" type="Elmah.ErrorLogPageFactory, Elmah"/>
Note that this is for IIS7 change the httpHandlers sections for IIS6.
You can then add a location section to the system.web element of the root web.config to deny access to unauthenticated users (or roles whatever...) such as this:
<deny users="?" />
Make sure that the routing ignore rule that you set up originally is also changed to reflect the new path - something like
public static void RegisterRoutes(RouteCollection routes)
//ELMAH exception handling
and that's it. Requests to logs/exceptions.axd will be protected.