OSArmor installs 2 drivers: osadevprotect.sys and OSArmorDevDrv.sys. See
this. The drivers are signed by Microsoft so SecureBoot should remain enabled to install OSArmor, like any other legit software. When OSA very first came out as a beta product, it was necessary to disable SecureBoot in order to install it because the developer had to wait for Microsoft's approval. This was a little over a year ago already--time flies, right?