The system security officer or database owner should be aware of possible security issues.
For example, alice is a user in the Accounting database and has no access to the payroll data. She could create the procedure alicep that selects name and salary from Accounting.dbo.payroll, and then grant execute on alicep to public. If the system security officers accidentally changes the ownership of alicep to bill, a privileged user with access to the payroll data with preserve permissions option, all users can access the payroll information by executing the malicious procedure alicep because all the permissions are set to be preserved after the ownership change.
To avoid unauthorized usage, the system security officers or database owner can check existing permissions on an object using sp_helprotect.
