Smells like BS. At most, the person may have acted as an ISSM (Information Systems Security Manager). Even then, I doubt the &#x27;general purpose&#x27; config used by the majority of the Air Force is created by any one person.<p>By &#x27;general purpose&#x27; I mean the baseline configuration that all non-POR (Program of Record) systems use. Ie, hardened Windows, MS Office, security monitoring, CAC authentication, and DOD certificates. There&#x27;s no chance in hell that the &#x27;general purpose&#x27; configuration will ever be changed to include OSS because it&#x27;s intent is to be the &#x27;lowest common demominator&#x27; of connected systems.<p>This person probably works as a grunt for the AF branch equivalent of G-6.<p>The COTS systems you&#x27;re referring to are POR (Program of Record) systems created and supported by the product development branch. I think for the AF, it&#x27;s the Air Materiel Command. They fall outside the scope of general systems support, therefore they require their own infrastructure for maintenance&#x2F;support.<p><i>Source: I used to support a POR system.</i>