Information Systems Technician
Installs and operates information technology and communications systems aboard ships and at shore installations. Manages networks, maintains servers, and ensures information systems are available and secure.
“You'll manage Navy network infrastructure and information systems — routers, switches, servers, and the communication architecture that connects ships and shore installations to each other and to the broader naval network. The shipboard IT environment is hard on equipment and harder on the people maintaining it under operational pressure, which means IT veterans who've managed Navy networks have a problem-solving resilience that enterprise IT employers recognize. Security clearance plus CompTIA Security+ and Network+ plus operational Navy IT experience is a competitive federal IT contractor profile. Government IT organizations and managed services providers recruit Navy IT veterans consistently and the clearance is a meaningful differentiator in the federal market.”
You are the person who resets passwords for people who swear they didn't change anything, aboard a ship where going home after work is not an option because the ship is the home. The Navy's IT infrastructure ranges from modern and well-maintained at major shore installations to 'this router is from when this ship was commissioned and we can't update the firmware because the one critical application only works on the old firmware,' and you will experience both in the same career. NMCI — the Navy Marine Corps Intranet — is the enterprise network you will support ashore, and it is a massive IT infrastructure managed by HP/DXC on contract, which means you will learn to navigate both Navy bureaucracy and contractor bureaucracy simultaneously. Shipboard systems include ADNS (Advanced Digital Network System) and SCI networks that require clearance to touch and patience to maintain. CompTIA Security+ is mandatory. CCNA is common. The Help Desk tickets will range from 'my CAC reader isn't working' (it's upside down) to 'the entire ship's network is down and the XO is asking why.' The six-figure civilian IT job is real. The Security+ is real. So is earning it.
MOS Intel
- 1Your Security+ is required for most DoD IT positions — get it in A School and keep it current.
- 2Volunteer for shore duty at NCDOC, NAVCYBERFOR, or fleet cyber commands. The experience and networking opportunities dwarf what you get on a ship.
- 3Learn cloud (AWS/Azure), scripting (Python/PowerShell), and automation. The Navy teaches you legacy systems but the job market wants modern skills.
Navy IT is a solid, reliable path to a civilian tech career. The recruiter will tell you it's like being an IT professional — and it largely is, just on ships and submarines sometimes. What they won't emphasize: sea duty is the deal-breaker for many. You will spend 3-4 years on a ship, and IT on a ship means being on call 24/7 when systems go down. The server room is hot, the equipment can be outdated, and you are responsible for everything from email to satellite communications. Shore duty is much more like a normal IT job. The civilian translation is strong — Security+ and military IT experience get you hired — but you have to supplement with modern certifications because the Navy still runs a lot of legacy systems.
Execute the Job — By Rank
How you actually run this job at each rank — what you do, what you drill, which manuals you own, and what good looks like. Written for the soldier, sailor, airman, Marine, or Guardian currently in the seat. Each rank deeplinks into the full Playbook deep-dive: time-blocked schedules, unit-type variations, career decisions, and the read on the next rank.
You are the new IT — the tier-one ticket queue and the cable-tracer the LPO sends to whichever space stopped working in the last hour. The crow is not on the sleeve yet; the network does not care.
Fresh out of A-school at Information Warfare Training Command Corry Station, you check aboard a ship, a NCTS / NCTAMS shore command, a Marine MEF G-6 if you are on green-side detached duty, or whatever afloat platform the detailer cut you for. Pre-rate strikers may show as SN on the muster sheet until the rating designator is set. You reimage workstations, reset CAC PINs, replace dead patch cables, run the help-desk ticket queue (Remedy / ServiceNow / the platform-specific equivalent), and you escort the contractor through the SCIF or comm spaces when the LCPO does not have an HM2-equivalent senior to spare. You stand watch in dungarees or the watchbill the platform runs — afloat ITs stand network watch in the IT-21 / ONE-Net spaces; shore ITs run the help-desk floor and the IA / cyber compliance ticket queue. You study for PQS, the 301-series watch quals the platform requires, and the next NWAE cycle. Whether you end up blue-side (afloat — carrier strike group, surface combatant, amphib), shore (NCTAMS / NCTS / fleet cyber shore command), or SUB (Naval Submarine School Groton, IT-8404 pipeline) depends on orders, your LPO, and how visibly you carry yourself in the first 90 days.
- 01CAC enrollment, PIN reset, DEERS lookup, and account creation in Active Directory in your sleep — this is 30-40% of the daily ticket queue.
- 02Image a workstation off the Navy / ONE-Net gold image and rejoin it to the domain without breaking the GPO stack the LPO maintains.
- 03Trace a CAT-5/6 run from the wall jack to the patch panel to the switch port — punch a 568B if the cable diagram says you have to.
- 04Operate the VTC stack — Cisco TelePresence, Polycom, the unit's DCS / DVS-G equivalent — and run pre-brief checks 30 minutes early, every time.
- 05Open, work, and close a help-desk ticket cleanly — categorization, resolution notes, customer signoff that the LCPO can defend at the next inspection.
- 06Lock down a workstation against the current DISA STIG checklist before you push it to a user; know what ACAS is scanning for before it scans.
- —SECNAVINST 5239 series — Department of the Navy Cybersecurity / IA Program (the umbrella that every Navy IT reg inherits from).
- —OPNAVINST 5239 series — Navy Cybersecurity Program (pull the current version from Navy Doctrine Library before quoting it).
- —DoDD 8140 / DoDM 8140.03 — Cyberspace Workforce Qualification (the chart that gates which billets you can sit and which certs you need to keep them).
- —DISA STIGs — public.cyber.mil — Windows, Active Directory, Cisco IOS, the platform-specific STIGs for whatever you administer.
- —NIST SP 800-53 — Security and Privacy Controls (the parent document under every Navy cyber accreditation).
- —CompTIA Security+ exam objectives (current SY0 cycle) — the IAT-II floor for most IT billets under DoDM 8140.
- —CompTIA Security+ certification by your first-year mark — IAT-II is the floor for most production IT billets; the LCPO will not slot you on the watchbill without it.
- —A+ and Network+ if you did not arrive with them — Navy Credentialing Opportunities On-Line (Navy COOL) pays the voucher; do not leave it on the table.
- —All NWAE-eligible PQS and 301-series watch quals signed off on the LCPO's timeline — the slow ITSN becomes the slow IT3 candidate.
- —PRT Good Low or higher; BCA in standard. The senior ITs notice who carries the cable bag and who falls out on a damage-control drill.
- —Annual cyber awareness training (DoD CYBER AWARENESS) completed before the deadline. You will be the IT whose lapse locks the command out of the network.
- —Plugging a personal USB into a government workstation. The CIRT ticket lands on the LCPO's desk that afternoon and your name is on the OPREP.
- —Sharing a CAC PIN over the phone, in chat, or anywhere else. Even once. The information assurance officer runs spot checks and the goat locker hears the same week.
- —Closing a ticket as "resolved" without confirming with the user. The next morning the senior officer reopens it as "you did nothing," cc to the LCPO and the MEDO of the wardroom.
- —Imaging a machine off a personal USB instead of the Navy gold image. The trust-level mismatch surfaces on the next ACAS / STIG audit and your name is on the finding.
- —Telling a senior officer "I cannot do that" without offering the workaround. Always have the next step ready; the wardroom remembers which IT solves problems and which IT lists them.
The good ITSN is the sailor the LPO sends to the XO's laptop problem because it will come back fixed and the XO will not bring it up at the next 8 o'clock report. By month nine the Sec+ is on the cert sheet, PQS is done, and the LCPO is asking which C-school pipeline you want — submarines (IT-8404 at Naval Submarine School Groton), the network administration NEC stack, or staying blue-side on a CSG for the next cycle.
You are a petty officer now. The crow on the sleeve says you own a shift on the help desk or a watch in the IT spaces, and at least one ITSN is watching how you wear it.
You own a shift in the ship's IT spaces, the NCTS / NCTAMS help-desk floor, the comm shop on a sub if you came out of Groton with the 8404 / submarine NEC, or the MEF G-6 IT bench if you are detached green-side. You run the day-to-day account administration, you push the WSUS / SCCM patch cycle on the workstations you own, you train the ITSNs on PQS line items, and you execute the LPO's training plan instead of just attending it. You sit on the watchbill as a qualified network operator on the IT-21 / ONE-Net spaces your platform runs, you run ACAS / SCAP scans on your scope, and you start the harder NEC conversation: the submarine pipeline (IT-8404) if you are blue-side and want it; the network systems administration NECs (the IT-27xx / IT-33xx series — pull the current NEC source-rating message before you fall in love with a code); the CTN conversion if cyber-warfare-side is where you actually want to go. Pull the current NAVADMIN for IT advancement quotas and current NEC source ratings — do not quote what your buddy told you last year.
- 01Manage Active Directory users, groups, and OUs inside your delegated scope — no shared admin accounts, no sloppy group nesting, every change logged.
- 02Run a SCCM / WSUS / Tanium patch deployment cycle on the published maintenance window with reporting back to the LCPO that the inspector can read.
- 03Stand up a tactical / shipboard network segment — VLAN, DHCP, internal DNS, switch port config — with a diagram and an IP plan printed for the relief.
- 04Operate the platform comm stack — IT-21 / ONE-Net afloat, NCTAMS / NCTS infrastructure shore, the sub's comm suite if you came through Groton — and troubleshoot a downed circuit inside the watch.
- 05Run ACAS and SCAP scans against your scope, read the report, and close findings before the IA officer asks twice.
- 06Walk a senior officer through a phishing remediation without making him feel stupid — and document the CIRT ticket cleanly enough that Fleet Cyber Command does not call back.
- —SECNAVINST 5239 series — DON Cybersecurity / IA program.
- —OPNAVINST 5239 series — Navy Cybersecurity Program (current version; pull from the Navy Doctrine Library, not the stale folder on the share).
- —DoDM 8140.03 — Cyberspace Workforce Qualification (this is the chart the LCPO checks against your cert sheet at every watch turnover).
- —DISA STIGs you actually administer: Windows 10/11, Server, AD, Cisco IOS, Office 365 — public.cyber.mil.
- —NIST SP 800-53 — Security and Privacy Controls; NIST SP 800-181 — NICE Framework (the work-role map under DCWF).
- —NAVPERS 18068 Vol II + the current NEC source-rating NAVADMIN — read the entries for IT-8404 submarine, IT-2735 / IT-2779 / IT-3389 (verify current codes before quoting) before you talk to the career counselor.
- —IAT Level II compliance maintained at all times (Sec+ continuing education or CCNA-Security equivalent).
- —CCNA before the IT2 NWAE if you are network-side; AZ-900 / AZ-104 if your platform runs Microsoft cloud workloads — Navy COOL funds the voucher.
- —PRT Good Medium or better; BCA in standard. Submarine ITs are held to the platform's additional medical screening on top.
- —NWAE for IT2 prep documented on the LCPO's timeline; pull the current Bibliography for Advancement (BIB) and own it — the BIB is the test, the test is the BIB.
- —At least one NEC pipeline packet in motion (IT-8404 submarine, network administration NECs, CTN conversion if applicable) or a documented reason you are still building the next one.
- —Using shared admin accounts. Every domain-controller action is logged and ownership-by-shared-account ends petty officer careers at the next CIRT review.
- —Patching outside the maintenance window. You will brick the ship in the middle of a brief or take the shore command off the network in the worst possible hour.
- —Building a network segment without printing the diagram and the IP plan. When you go on leave the relief cannot inherit your stack and the watch falls apart.
- —Treating a cyber-incident-response ticket as a help-desk ticket. A phishing campaign or a STIG drift gets reported to CIRT / Fleet Cyber Command inside the timeline or the LCPO is on the phone with the wardroom.
- —Posting OPSEC-relevant photos from the spaces — racks, screens, unit insignia, deployment timing. The OPSEC officer and adversary collectors both read social media.
The good IT3 is the petty officer the LPO trusts with the XO's VTC problem and the IT-21 / ONE-Net circuit outage on the same watch, because both come back working and the wardroom does not have to ask twice. He has CCNA on the cert sheet, an IT-8404 / submarine or NEC packet in his folder if he wants it, and the LCPO is already mentioning his name for the next IT2 slate.
You are the working senior IT — section LPO in fact even when the title is unofficial. The IT3s call you LPO whether the watchbill posts the rotation that way or not, and the chief is mentoring you toward anchors he expects to pin in two boards.
You run a section — a watch section in the ship's IT spaces, an NCTS / NCTAMS help-desk team, the comm shop on a sub as the senior IT aboard (if there is no senior rate in the billet), a MEF G-6 IT cell, or a specialty cell at a Fleet Cyber Command shore command. You train and qual-sign two-to-four IT3s and ITSNs, build the section's training plan, manage your slice of the IT-21 / ONE-Net infrastructure, write the network-status portion of the daily SITREP or department-head sync, and own the IA / cybersecurity compliance work the LCPO does not have time to do himself. NEC-coded billets define the seat: IT-8404 submarine on a boat, network administration NECs at a shore enterprise IT command, advanced comm / cryptographic NEC stack if you went down that pipeline, or a CTN conversion if the cyber-warfare side is your endgame. The NWAE for IT1 is no longer abstract; the eEVAL trait average against your peer IT2s actually starts to matter for the next slate.
- 01Run a section watchbill on the IT-21 / ONE-Net spaces or the shore help-desk floor as the senior enlisted on shift — incident triage, escalation to CIRT / Fleet Cyber, clean handoff to the LCPO without the chief rewriting your turnover.
- 02Brief a network status update to the department head / LCPO / executive officer — uptime, ticket SLAs, STIG / ACAS compliance, IA findings, ongoing risk — in five slides the wardroom will not rewrite.
- 03Run an IA vulnerability / IAVA-equivalent closure cycle inside the published timeline — track, patch, validate, report — and own the spreadsheet that defends the close-out.
- 04Conduct a real change-management board for a section-level network change — risk, rollback, validation, sign-off — on the ship or shore command's ECP / change-control process.
- 05Onboard a new IT3 or ITSN and have them productive on the watch in two weeks, including STIG familiarity, ticket discipline, and platform-specific PQS / 301 line-item sign-offs.
- 06Write a CIRT-quality incident-response report on a real phishing or compromise event — timeline, indicators, containment, eradication, recovery, lessons-learned — clean enough that Fleet Cyber does not call back.
- —SECNAVINST 5239 series; OPNAVINST 5239 series — current versions of the DON / Navy Cybersecurity Program.
- —DoDI 8530.01 — Cybersecurity Activities Support to DoD Information Network Operations.
- —DoDM 8140.03 — Cyberspace Workforce Qualification (the IAT / IAM / cyber work-role chart you sign your IT3s and ITSNs against).
- —NIST SP 800-61 — Computer Security Incident Handling Guide (the IR playbook the Navy quietly maps to).
- —NAVPERS 18068 Vol II + current NEC source-rating NAVADMIN — you mentor packets off this and not off the version on the share from two years ago.
- —CCNA, CompTIA CySA+, Cisco CCNP path, AZ-104 / AWS SAA — the credentials Navy COOL funds and the next slate board reads.
- —IAT Level II or III compliance (Sec+ minimum, CCNA-Security / CCNP / CASP+ trending up) — tracked in the command training database and on the LCPO's tickler.
- —NWAE for IT1 prep on the LCPO's timeline; EAW (Enlisted Advancement Worksheet) clean and BIB study log defensible.
- —PRT Good High or better; BCA in standard; warfare device pinned where the billet allows (SS / SW / AW / EXW / FMF as platform requires).
- —Section certification rates — IAT compliance, STIG closure, ticket SLA, IAVA closure — at or above the command average, every cycle, no caveats.
- —eEVAL trait average and ranking that supports EP / MP recommendation; your LCPO knows your number before the EVAL board reads it.
- —Letting an IT3 sit a watch as an IAT-II or IAT-III billet when they are not certified. The DoDM 8140 audit catches it and the finding is on you, not on the junior.
- —Skipping the after-action on a real CIRT event because "we closed the ticket." The next event repeats the same indicator and your section is the one named in the Fleet Cyber report.
- —Bypassing the LCPO to talk to the wardroom or the cyber officer directly. The medical chain runs through the chief and the IT chain runs through the LCPO; the goat locker hears about it the same day.
- —Accepting a verbal change request from a senior officer without a ticket. The change blows up at 0200 and there is no paper to defend either of you.
- —Loaning gear without a sub-custody chit. Property accountability is the line the Navy does not let any petty officer cross twice and the IG inspector loves a custody mismatch.
The good IT2 is the petty officer the LCPO names when the wardroom asks who is running the IT spaces at 0200. The section's STIG / IAVA numbers brief without caveat, his IT3 has a network-administration NEC packet on the table, and his eEVAL bullets read action-result-impact instead of generic IT filler. He sits the IT1 NWAE on a study log the chief can defend, and the warfare device on his blouse is current.
You are the LPO. The chief is editing your Chief packet; the wardroom calls you by name; the IT2s and IT3s watch how you carry the department the way you used to watch your chief.
You are LPO of an IT division — ship's information systems division, NCTS / NCTAMS production cell, submarine medical-equivalent IT shop if your billet is the senior IT aboard, MEF G-6 detachment, or a Fleet Cyber Command shore element — running 10-25 ITs and a piece of the command's network and cyber readiness. You write four-to-six eEVALs per cycle for IT2s and IT3s that pick the next NWAE slate. You build the department training plan, defend the network and cyber readiness brief at department-head sync, manage IAT / DoDM 8140 work-role compliance at the department level, and mentor at least one IT a year into a Cyber Warrant (170-series — verify the current accession path before quoting), a commissioning program (Seaman to Admiral / STA-21, MECP, LDO / CWO IT-side), CTN conversion if cyber-warfare is the calling, or the senior NEC pipelines (submarine, advanced network engineering, the IT side of the CWE / cyber workforce). The Chief board packet conversation is no longer abstract — your LCPO is editing your record, your eEVAL profile is being built across the year, and the warfare device on your blouse matters more than any single cert you have ever earned.
- 01Run a department-level network architecture conversation — VLAN scheme, IP plan, redundancy, growth roadmap on the platform's IT-21 / ONE-Net infrastructure — without hiding behind the LCPO or the cyber officer.
- 02Defend a CCRI / CORA or equivalent Navy cyber readiness inspection at the department level — own the gap, present the closure plan, hit the milestone the inspection team published.
- 03Build and execute a six-month training and certification plan that produces a CCNP-grade or CISSP-trending IT and two Sec+ / CCNA-grade junior petty officers.
- 04Operate as the senior IT on a deployment, patrol, MEU, or contingency — including the call to wake the CO at 0200 when the network posture has actually shifted.
- 05Translate cyber and network risk to the CO / XO / department head in language the wardroom will repeat without rewording, and brief Fleet Cyber Command / NAVIFOR liaisons on enlisted execution at your unit.
- 06Mentor an IT2's NWAE / NEC / Warrant / commissioning packet from idea to selection — and counsel honestly when the path is wrong for the sailor.
- —SECNAVINST 5239 series; OPNAVINST 5239 series — current Navy / DON Cybersecurity Program.
- —DoDI 8500.01 — Cybersecurity; DoDI 8510.01 — RMF for DoD IT.
- —NIST SP 800-37 — Risk Management Framework; 800-53 — Controls; 800-171 — CUI in Nonfederal Systems.
- —DoDM 8140.03 — Cyberspace Workforce Qualification (you are auditing the department against it).
- —NAVPERS 18068 Vol II + the current NEC source-rating NAVADMIN — you build the pipeline off the current cycle, not the stale folder on the share.
- —Cisco CCNP path, CISSP (the Chief / Warrant differentiator), SANS GIAC short-courses for currency, AWS / Azure architect tracks where the platform runs cloud.
- —Chief board packet under construction with the LCPO's eye on every line; eEVAL profile defensible at wardroom / command level; warfare device pinned and current.
- —Department-level IAT / 8140 compliance, STIG / ACAS posture, and IAVA closure defensible at department head and CO level — every cycle, no caveats.
- —IAT Level III maintained (CCNP-Security, CASP+, or CISSP) with continuing-ed credits banked.
- —Pipeline output — IT-8404 submarine, network NECs, CTN conversion, Warrant Officer accession, commissioning, NWAE — producing at least one selectee per year from your department.
- —NWAE for Chief is replaced by the Chief Petty Officer selection board; the package is built across the year, not the week before submission. The LCPO defines the cadence.
- —Briefing STIG / ACAS / IAVA numbers you have not personally validated. The cyber officer catches it once and your Chief packet feels it permanently.
- —Letting a senior IT2 carry the change-management / configuration-control board because "he is your guy." When he transfers, the gap surfaces and the LPO's name is on the JAG.
- —Confusing seniority with current technical depth. The senior IT2 may know the new platform better than you do — let him brief it and stand by him; the LCPO sees who is honest about the gap.
- —Going around the LCPO to the cyber officer, the wardroom, or NAVIFOR / Fleet Cyber liaisons. The chiefs talk; the next Chief board sees the pattern.
- —Treating the Warrant / commissioning / CTN mentoring conversation as transactional. The sailors you put through these accessions at this rank build the bench the Navy cyber workforce depends on for the next decade — counsel honestly about ADSO, OCS, and the seat they actually want.
The good IT1 is the LPO the LCPO trusts to run the department for a week without daily check-ins. His network and cyber readiness numbers brief without caveat; his eEVALs pick ITs above expectation; his pipeline produces submarine, Warrant, commissioning, and NEC packets the wardroom signs without rewriting. He sits the Chief selection board with a record that reads itself.
You are a Chief. The gold-fouled anchors mean the goat locker is yours, the wardroom asks you by name, and the entire department reads the command's mood off how you stand at quarters.
The job changes more between IT1 and ITC than at any other promotion in the rate. As LCPO of an IT department — ship's information systems division on a CSG / ESG / amphib, NCTS or NCTAMS production element, submarine COB-adjacent senior IT on a boat, MEF G-6 enlisted lead, or a Fleet Cyber Command / NAVIFOR shore staff cell — you run 15-40 ITs and you own enlisted execution from the deckplate up. You write Chief-quality eEVALs that pick the next IT1 and ITC slate; you sit at department head sync as the senior enlisted IT voice; you walk the spaces during a real-world contingency, network outage, or cyber readiness inspection (CCRI / CORA / equivalent) and identify the broken systems before the inspector does. You build the next LPO. You mentor the next CTN conversion, submarine, Warrant Officer, or commissioning candidate. You enforce the standard, in uniform, every day, while the deckplate watches whether your liberty habits match your at-sea posture.
- 01Run an LCPO's mess of ITs — accountability, training, readiness, discipline, family, finance — with weekly cadence the wardroom and the department head can predict.
- 02Defend the department's network architecture, cyber readiness, DoDM 8140 work-role compliance, controlled-cryptographic-equipment accountability, and inspection posture at command-level synch without your numbers being rewritten.
- 03Walk a real-world CIRT event, contested-network exercise, or CCRI / CORA inspection as the senior enlisted IT voice on scene — your AAR is what the wardroom briefs up the chain to NAVIFOR / Fleet Cyber.
- 04Mentor four-to-six IT1s into Chief-board-competitive candidates; mentor at least one Warrant Officer (170-series), CTN conversion, submarine, or commissioning packet to selection per year.
- 05Operate as the senior enlisted IT during a deployment, patrol, MEU, or fleet contingency — including the call to wake the CO at 0200 when the network or cyber posture has actually shifted.
- 06Translate Fleet Cyber Command / NAVIFOR / Type Commander cyber strategy into deckplate decisions the ITs rehearse without rewording the message.
- —OPNAVINST 5239 series — current Navy Cybersecurity Program.
- —SECNAVINST 5239 series — DON Cybersecurity / IA program (you are quoted from it more often than you quote it).
- —DoDI 8500.01, 8510.01, 8530.01 — Cybersecurity, RMF for DoD IT, Cybersecurity Activities (you live inside this stack).
- —DoDM 8140.03 — Cyberspace Workforce Qualification (you defend department-level compliance every cycle).
- —MILPERSMAN — fluent in the articles that govern enlisted personnel actions (advancement, retention, separation, NJP) at ITC-level visibility.
- —CPO 365 / CPO Initiation guidance, Senior Enlisted Academy reading list — the goat locker and the wardroom hold you to it, even after the anchors are pinned.
- —Chiefs Mess transition / CPO 365 cycle complete; standing as a Chief in the mess at the deckplate level — not a Chief in title alone.
- —Department-level cyber readiness inspection (CCRI / CORA / equivalent) passed without senior-NCO-attributable CAT-I findings during your tenure as LCPO.
- —CISSP or CCNP-Security maintained; CCE / SANS GIAC credentials where the billet justifies (submarine IT chiefs especially, Fleet Cyber shore-side chiefs without exception).
- —Pipeline producing 1+ Warrant (170-series), CTN, submarine, or commissioning selectee per year — and the wardroom can name them.
- —Zero Chief-level integrity incidents — fraternization, financial, OPSEC, classified handling, HIPAA-equivalent. One ends the career permanently.
- —Mistaking the goat locker for a private club. The mess is a working leadership platform; chiefs who treat it as social will be the ones the department reads as off-mission inside the same patrol cycle.
- —Stopping personal PT, BCA, and technical study because "I am a Chief now." Sailors read the deckplate harder when the anchors go on, not less, and the cyber world does not stop changing because you stopped reading.
- —Letting an IT1 LPO run a bad division because he is "your guy" or "almost a Chief." The wardroom and the CMC see the climate first and the next slate gets read against the gap.
- —Going public with disagreement with the cyber officer, the department head, or the CO. The disagreement happens in the office; you walk out aligned. The goat locker enforces this without the wardroom asking.
- —Treating the Warrant / commissioning / CTN mentoring as a checkbox. The careers you build at this rank shape the Navy's cyber and IT enlisted bench for the next decade and beyond.
The good ITC is the LCPO the CO calls by name and the goat locker defends in the mess. His department briefs without caveats, his IT1s pick up Chief, his CCRI / CORA inspection findings are closed before the inspector asks, and his deckplate posture matches his liberty posture. He is on the Senior Chief slate before the CMC has to ask, and the contractor on the next pier already has his card.
You are the senior enlisted IT and cyber voice in a department, command, or staff. The CO names you in the slide. NAVIFOR and Fleet Cyber know your name on the slate. The deckplate watches whether you still walk the line.
As ITCS or ITCM you run the senior enlisted IT / cyber posture for a CSG / ESG / MEU / Type Commander staff, an NCTAMS or NCTS production command, a Fleet Cyber Command / NAVIFOR enlisted directorate, a submarine squadron senior enlisted IT cell, or you sit as a Command Master Chief (CMC) or Chief of the Boat (COB on submarines) where the path opens. You write fewer eEVALs but they are the ones that pick the next Chief and Senior Chief slate. You sit at command-team synch as the senior enlisted voice on every enlisted IT / cyber decision — accession, training, retention, credentialing, discipline, CTN conversion approvals, Warrant accession pipeline. You translate Fleet Cyber Command / NAVIFOR / Surgeon-General-equivalent strategy into command-level talent decisions. You build the next CMC / COB / SEA selectee. You start the post-Navy market plan 24-36 months out — credentialing translation to the cleared IT contractor space (Booz Allen, Leidos, SAIC, CACI, MITRE, ManTech, Peraton, BAE), federal civilian at DISA / NSA / DoN, or commercial enterprise IT — because the bench you leave behind decides whether the goat locker remembers your name.
- 01Run a senior-enlisted command climate across an IT / cyber department or command that produces certified ITs, Warrant / CTN / submarine / commissioning selectees, and enlisted retention at rates above the type-command average.
- 02Brief the CO, cyber officer, TYCOM, NAVIFOR, or Fleet Cyber Command on enlisted IT and cyber readiness and risk in language the flag officer can defend at the next echelon — without rewriting.
- 03Sit on Chief selection board panels, command CMC / COB slates, Warrant Officer accession boards, and senior-enlisted credentialing panels with the discipline and confidentiality the convening authority requires.
- 04Translate NAVIFOR / Fleet Cyber Command / OPNAV-led cyber strategy into enlisted talent management decisions at the unit and across the rate.
- 05Run a real-world contested-network event, deployment cyber posture, or fleet-level CCRI / CORA response as the senior enlisted IT voice — and your AAR is what NAVIFOR reads in the lessons-learned.
- 06Run a Red Cross / casualty notification or a serious-incident response with the dignity it requires. You are the face the family and the deckplate see.
- —OPNAVINST 5239 series; SECNAVINST 5239 series — full Navy / DON cybersecurity program library; you are quoted from it more than you quote it.
- —DoDI 8500.01 / 8510.01 / 8530.01 — Cybersecurity, RMF for DoD IT, Cybersecurity Activities — the umbrella the wardroom inherits.
- —DoDM 8140.03 — Cyberspace Workforce Qualification (you defend command-level compliance and you sit on accession panels off it).
- —MILPERSMAN — fluent on enlisted personnel actions at the senior-enlisted threshold; you are in the room for NJP, separation, and high-visibility cyber-clearance cases.
- —Senior Enlisted Academy (SEA, Naval War College Newport RI) reading list and CMC / COB Symposium materials — you consume doctrine and translate it down.
- —NAVIFOR / Fleet Cyber Command / Type Commander policy memos and NAVADMINs — current; pull each one as it drops, not from a stale folder.
- —SEA fellowship or equivalent senior-enlisted PME complete before competing for command CMC / COB slate.
- —Command-level cyber readiness inspection (CCRI / CORA / Fleet Cyber assessment) passed without senior-enlisted-attributable findings during your tenure.
- —Warrant Officer (170-series), CTN, submarine, and commissioning accession pipeline producing 1+ selectee per year from your command — and the wardroom can name them.
- —eEVAL profile that the senior rater can defend at command and TYCOM level — your rated chiefs are picking up Senior Chief and Master Chief on schedule.
- —Zero senior-enlisted-level integrity incidents — financial, fraternization, classified-handling, OPSEC. One ends the career permanently and there is no recovery at this paygrade.
- —Pretending to be the senior technical voice on a topic where you are out of date. Senior ITs lose authority by faking depth — the cyber officer and the JOs see it inside the same brief.
- —Letting a Chief-led division drift on STIG / ACAS / IAVA compliance because "the wardroom will catch it." You own the enlisted execution at the unit roll-up; the inspection finds it under your name.
- —Treating the Warrant / commissioning / CTN conversion mentoring conversation as transactional. The careers you support at ITCM build the enlisted IT and cyber bench the Navy depends on for the next decade.
- —Going public with disagreement with the CO, the cyber officer, NAVIFOR, or Fleet Cyber leadership. Take it in the office. Walk out aligned. The goat locker and the wardroom both enforce it.
- —Confusing the warm-up to retirement with the job. Until you walk out of the formation for the last time, the formation is your job, and the deckplate reads which one you are working.
The good Master Chief IT is the senior enlisted cyber and IT voice the CO, the cyber officer, NAVIFOR, and Fleet Cyber Command all name without thinking. His command's enlisted IT slate is the one NAVIFOR quotes in policy memos; his Warrant / CTN / commissioning accession rate is in the upper third of the rate; his rated chiefs pin Senior Chief and Master Chief on schedule. When he retires, the cleared contractor space and federal civilian hiring managers at DISA / NSA / DoN have his number, and the goat locker remembers the standard he left behind — not the position he held.
What this actually is in the real world
Your skills translate. Here's what civilian employers call this job — and what they pay.
Network and Computer Systems Administrators
Strong matchComputer, Automated Teller, and Office Machine Repairers
Strong matchNetwork and Computer Systems Administrators
Strong matchSoftware Developers
Related fieldComputer and Information Systems Managers
Related fieldSalary data from the U.S. Bureau of Labor Statistics Occupational Employment and Wage Statistics program, retrieved Feb 2026. BLS.gov cannot vouch for the data or analyses derived from these data after the data have been retrieved from BLS.gov.
How exposed is the civilian version of this job to AI?
Not a measurement of this MOS. Published labor-market research on the closest civilian occupation in our crosswalk — treat it as a signal, not a verdict.
Closest civilian match: Network and Computer Systems Administrators (close match)
Documentation, scripting, and config-file work sit squarely in LLM territory (51% exposure). The 2013 model — filed under this occupation’s old SOC number, 15-1142, since renumbered 15-1244 in 2018 — rated it almost automation-proof (3%), because hands-on server-room work didn’t fit that era’s model.
This describes exposure for the civilian occupation, not a rating of this MOS, your unit, or your actual day-to-day duties. The matched civilian job is a close or related crosswalk, not exact.
Exposure research: Eloundou et al., "GPTs are GPTs" (arXiv preprint) (2023); Eloundou et al., Science 384(6702):1306-1308 (DOI 10.1126/science.adj0998) (2024); Eloundou et al. published occupation-level data (occ_level.csv) (2023); Frey & Osborne, "The Future of Employment" (Oxford Martin School / Technological Forecasting and Social Change 114:254-280) (2013).
Read the full methodology and see how much of the MOS catalog is scored so far on the AI/Automation Displacement Risk tool.
MOS Pulse
Anonymous · One tap · No accountThree seconds of your time, zero of your identity. This is how the honest picture of IT gets built — one tap at a time.
Knowing what you know now — would you pick IT again?
Did your recruiter describe this job accurately?
Hours per week this job actually takes in garrison?
That tap took 3 seconds. A full review takes 10 minutes — and does about 100x more for the next person staring at this contract.
Write the Full Review →Nobody’s gone first. Yet.
Zero reviews for IT. Not because nobody has opinions — anyone who’s actually done Information Systems Technician is carrying a full magazine of them — but because nobody’s put theirs on the record.
So here’s the deal: the first approved review of every MOS becomes its Founding Review. Permanently badged, permanently first. Every person who looks up IT from now on reads it before anything else — including the recruiter’s version.
We could fill this page with fake reviews tonight. Plenty of sites do. We never will — which means this space stays exactly this empty until someone who lived it goes first.
Anonymous by default — no name, no unit, fuzzy timestamps. Your chain of command never knows it was you.
IT Information Systems Technician — FAQ
Q01What does a IT do in the Navy?
Q02How long is IT training and where is it held?
Q03What security clearance does a IT need?
Q04What does a day in the life of a IT look like?
Q05What are the most common career-ending mistakes for a IT?
Q06What civilian jobs does IT translate to?
Q07What's the career progression for a IT?
Q08How often do IT soldiers deploy?
Q09What's the recruiter not telling me about IT?
Sources:Branch MOS catalog · DTMO pay tables · DoD/.gov benefits references · O*NET civilian career mapping · verified service-member reviews