Taking a peek, this looks like you're attaching a JVM Agent and instrumenting JDK classes as they're loaded, calling into the jguard controller? This is probab

Taking a peek, this looks like you're attaching a JVM Agent and instrumenting JDK classes as they're loaded, calling into the jguard controller? This is probably how the SecurityManager should have been designed in the first place.