Being in the Air Force, the job was mostly like any civilian IT job. We worked off a ticket system to resolve computer issues, dealt with “customers” (other military members), managed servers, satellites, networks, etc. The specifics depended on the exact job; it seemed like every base I was assigned to had different equipment or mission requirements, so I was always learning some new system to manage.
Probably the biggest difference from the civilian sector was that military networks were severely locked down. There were approved software lists that were managed from much higher levels in the Air Force and only that software was allowed to be installed on computers. Half the time, even us administrators at the base level couldn’t mess with installed software.
There were software scans that would detect unauthorized software and boot computers off the network until it was resolved. Most places I worked, you couldn’t bring CDs or flash drives with your own programs on them. USB devices would be flagged instantly and get your account kicked off the network until you completed remedial training through your local IT office.
Our web browsing was severely limited too. Some bases only allowed official military website access; others would allow access to the web but only from an approved white list of sites. It depended on the job and the classification of the network.
Also, they believed that the best security was older systems that had been thoroughly tested for vulnerabilities, so we were usually a step or two behind the civilian sector in terms of operating systems and software/hardware. They preferred that new systems were thoroughly tested in the civilian sector first, most vulnerabilities identified and remedied, and then we would trust it. So I rarely got to learn about modern IT technologies unless I researched it myself in my own free time.
EDIT: In terms of harassment, there was sometimes a lack of respect for the IT guys. Lots of higher-ranking officers made unreasonable demands, expecting us to make some impossible network requirement magically work because “that’s your job.” Or just getting mad when things were broken, because “Why do we have IT guys if things are always broken?” Or the same if things work: “Why do we have so many IT guys when nothing ever breaks?” We had our own leadership in the IT field whose job was to explain to other leaders exactly what we did and how it benefits them, so the rest of us could focus on the job.
Being in the Air Force, the job was mostly like any civilian IT job. We worked off a ticket system to resolve computer issues, dealt with “customers” (other military members), managed servers, satellites, networks, etc. The specifics depended on the exact job; it seemed like every base I was assigned to had different equipment or mission requirements, so I was always learning some new system to manage.
Probably the biggest difference from the civilian sector was that military networks were severely locked down. There were approved software lists that were managed from much higher levels in the Air Force and only that software was allowed to be installed on computers. Half the time, even us administrators at the base level couldn’t mess with installed software.
There were software scans that would detect unauthorized software and boot computers off the network until it was resolved. Most places I worked, you couldn’t bring CDs or flash drives with your own programs on them. USB devices would be flagged instantly and get your account kicked off the network until you completed remedial training through your local IT office.
Our web browsing was severely limited too. Some bases only allowed official military website access; others would allow access to the web but only from an approved white list of sites. It depended on the job and the classification of the network.
Also, they believed that the best security was older systems that had been thoroughly tested for vulnerabilities, so we were usually a step or two behind the civilian sector in terms of operating systems and software/hardware. They preferred that new systems were thoroughly tested in the civilian sector first, most vulnerabilities identified and remedied, and then we would trust it. So I rarely got to learn about modern IT technologies unless I researched it myself in my own free time.
EDIT: In terms of harassment, there was sometimes a lack of respect for the IT guys. Lots of higher-ranking officers made unreasonable demands, expecting us to make some impossible network requirement magically work because “that’s your job.” Or just getting mad when things were broken, because “Why do we have IT guys if things are always broken?” Or the same if things work: “Why do we have so many IT guys when nothing ever breaks?” We had our own leadership in the IT field whose job was to explain to other leaders exactly what we did and how it benefits them, so the rest of us could focus on the job.