You would most likely have to compile a list of any virtualization tools and put them all into Restricted Software titles as already mentioned.
Under the hood, there may be some processes that get called up during virtualization, but that could be tricky to find, and probably unreliable. Not to mention, blocking sub OS processes could be dangerous and cause instability.
As for Boot Camp, the easiest things to do for that is to block the Boot Camp Assistant.app, which is typically needed to create any Boot Camp environment. In the past, when I had to ensure Boot Camp couldn't be used, we also made sure there was a Firmware Password enabled on the Mac, since alternate booting was one potential way around it. You may or may not want to take it that far through. Adding firmware password can sometime introduce some complications down the line.
