Database documents generated by ClearDB Documenter
represent a precious business and tech asset, storing key data on DB object relations and dependencies, code structure imperfections, security weaknesses, access privileges, etc. But when unprotected, such comprehensive dataset puts a giant target on your forehead and DB documentation becomes a huge security gap on its own. If fallen into the wrong hands, it reveals sensitive data which should only be available to authorized users.
To avoid sad consequences, make sure that database information is only accessible with a password
. In fact, there are certain files, such as DB security audit, that should be protected in a mandatory manner, since they reveal possible weaknesses. When you document an Oracle database using ClearDB Documenter, you have a choice of protecting a complete document with a unique password. If included, protecting a DB Security Audit Report only (mandatory).