...
An organization that signs its own code should not vouch for code acquired from a third party without carefully auditing the third-party code. When signing privileged code, ensure that all of the signed code is confined to a single jar file (see ENV01-J. Place all security-sensitive code in a single jar JAR and sign and seal it for more information) and also that any code invoked from the privileged code is also contained in that jar file. Non-privileged code must be left unsigned, restricting it to the sandbox. For example, unsigned applets and JNLP applications are granted the minimum set of privileges and are restricted to the sandbox. Finally, never sign any code that is incomprehensible or unaudited.
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="cabc51932e4960c7-e68ddb43-48c74668-891b8b76-25392888f2c2aba57068948d"><ac:plain-text-body><![CDATA[ | [ISO/IEC TR 24772:2010 | http://www.aitcnet.org/isai/] | "Adherence to Least Privilege [XYN]" | ]]></ac:plain-text-body></ac:structured-macro> |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="baa5520ef95f0b11-d69fc327-42e34498-b3f68376-6efa0f3e89e2474475a6bcf9"><ac:plain-text-body><![CDATA[ | [[Dormann 2008 | AA. Bibliography#Dormann 08]] |
| ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="ac7c3d9c7c58181b-1f1bf0a6-4a4d448a-89439e8e-964fa67fed74601e34878d36"><ac:plain-text-body><![CDATA[ | [[McGraw 1999 | AA. Bibliography#McGraw 99]] | Appendix C: Sign Only Privileged Code | ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="99a79f7af61a7a25-22660e00-4f1641a0-b432bf19-f3c78d3dac1ddc3ff1ea7722"><ac:plain-text-body><![CDATA[ | [[Schneier 2000 | AA. Bibliography#Schneier 00]] |
| ]]></ac:plain-text-body></ac:structured-macro> |
...