Remove the “master” database in CD environments
In a scaled environment with separate CM and CD servers, the “master” database on the latter is not used; leaving the database accessible may lead to security risks and unnecessary usage of resources. CDs should never write to the “master” database; if the solution does so, it should be refactored to avoid security risk.