The harness normally installs its own rather permissive security manager in self-defense to prevent tests from interfering with each other. The harness' security manager is designed to prevent changes to the JVM's state that would impact other tests. Most tests will not find the standard harness security manager a hindrance.
A test which must install its own security manager will always need to run
in its own separate JVM. To do this, add the othervm
option to the
main
action in the test description.