Otherwise your module could intercept the value of "`Default 403 (access denied) page`" which is modified by the page "`Administer > Site configuration > Error reporting`":

 1. when the module is installed, **copy the existing value** to a secondary variable and **replace the variable by your own** path

 2. **alter the "Error reporting" form** to read from/write to the secondary variable

 3. when the module is uninstalled, **restore the value** from the secondary variable.


----------


And that's it, your module gets notified in a clean way when "Access denied" is triggered.