It would be nice if the java.security.debug option were specified in the main security documentation pages (that is, somewhere under http://java.sun.com/products/jdk/xxx/docs/guide/security). Currently, it is documented only in the context of RMI, JSSE, Certpath, and Plugin, as a search in /usr/web/work/j2se/1.4 shows:

./docs/tooldocs/solaris/rmid.html: "-Djava.security.debug=*";
./docs/tooldocs/solaris/rmid.html:next permission allows the <code>java.security.debug</code> property to be
./docs/tooldocs/win32/rmid.html: "-Djava.security.debug=*";
./docs/tooldocs/win32/rmid.html:allows the <code>java.security.debug</code> property to be used by an
./docs/tooldocs/win32/rmid.html%: "-Djava.security.debug=*";
./docs/tooldocs/win32/rmid.html%:allows the <code>java.security.debug</code> property to be used by an
./docs/guide/security/jsse/JSSERefGuide.html:<code>java.security.debug</code>, while the JSSE-specific dynamic
./docs/guide/security/certpath/CertPathProgGuide.html:<code>java.security.debug</code> property to <code>certpath</code>. For
./docs/guide/security/certpath/CertPathProgGuide.html: java -Djava.security.debug=certpath BuildCertPath
./docs/guide/plugin/developer_guide/faq/troubleshooting.html:<p><b>A: </b>You can enable the <tt?java.security.debug>/tt> property to enable
./docs/guide/plugin/developer_guide/debugger.html: <li><a href="#jsdp">java.security.debug property</a></li>
./docs/guide/plugin/developer_guide/debugger.html:<h2><a name="jsdp"></a><code>java.security.debug</code> property</h2>
./docs/guide/plugin/developer_guide/debugger.html: domains in context, set <code>-Djava.security.debug=access:stack </code>in the