Skip to main content
HonestMOS
InvestigationsHow EUCOM shelved a tax break for 9,000 troops in Poland — for five years.
Back to CTM Cryptologic Technician (Maintenance) — overview, pay, training, civilian translation, reviews
CTME5

Cryptologic Technician (Maintenance)

E-5 (Sergeant) · Navy

HEADS UP

CTM2 (E-5) is the independent-maintainer paygrade and the DoD 8140 / 8570 certification inflection point. The TEMPEST and EMC compliance evaluations that were supervised at CTM3 are now your technical authority. The section's COMSEC accountability records are the ones the COMSEC Responsible Officer calls first when the audit schedule comes out. If you do not hold a current IAT Level II or III certification for your billet, fix that before anything else — the IA officer's workforce-compliance report goes to the commanding officer monthly.

The Honest MOS Read
Petty Officer Second Class CTM2 is the working senior cryptologic maintenance technician. The community is small enough that 'CTM2' and 'the LPO on duty' are often the same sentence — even when the watchbill does not yet say LPO, the CTM3s in your section are already treating you as the authority in the space. The Chief is mentoring you toward anchors he expects to pin. The officer-in-charge of the detachment calls you by name when there is a hard equipment problem at 0200. That is not flattery — it is the job description. You run a section or a maintenance cell: on an Afloat Collection Element (ACE) or Cryptologic Direct Support Element (CDSE) detachment, a shore-based SIGINT collection facility, a Navy Special Reconnaissance element, or a Fleet Intelligence Organization's cryptologic equipment maintenance shop. The section includes two to four CTM3s and CTMSNs who you train, qualify, evaluate, and mentor toward advancement and NEC pipelines. The CSMP for your section's assigned systems, the NSA-accountable equipment inventory, the PMS training plan, and the section's contribution to the material readiness reports that go to the commanding officer — those are your accountability, not your supervisor's. The maintenance technical authority at CTM2 has expanded materially from CTM3. The complex multi-system fault — the one that traces through a receiver chain, a signal processor, a COMSEC hardware interface, and the antenna distribution system simultaneously — is yours to troubleshoot without calling the LPO for the first three steps. You have been in the equipment long enough to know the failure modes; the TM fault-isolation procedure is the documented method, not a safety net. When the fault isolates to a finding that requires the engineering chain — an anomaly that needs NSA field-activity input, a TEMPEST compliance question that requires a waiver, a COMSEC hardware malfunction that triggers NSA notification — you understand what you are escalating and why, and the LPO does not have to translate your discrepancy report before forwarding it. TEMPEST compliance work is the technical differentiator at CTM2. TEMPEST — Telecommunications Electronics Material Protected from Emanating Spurious Transmissions — is the NSA program governing the protection of classified information from unintentional electromagnetic emanation. The CTM2 who understands the TEMPEST framework beyond the 'do not connect unapproved test equipment' rule — who can run a TEMPEST evaluation of a re-installed or modified classified system, document the baseline measurements, identify deviations from the certified configuration, and route the findings to the engineering chain in the format the NSA field activity accepts — is the CTM2 the LPO trusts with the pre-inspection system lineup. The CTM2 who treats TEMPEST compliance as an NSA problem rather than a technical maintenance function has not grown into the paygrade. MIL-STD-461 is the published standard; TEMPEST is the classification-specific application of that standard's emanation-control principles to cryptologic and classified systems. At CTM2 you are writing the findings, not just reading the test limits. The CSMP discrepancy entry for an EMC or TEMPEST finding needs to be specific enough that an NSA engineer reading it six months later understands exactly what was measured, what the deviation was, and what TM or TEMPEST guidance it deviates from. The DoD 8140.03 / DoD 8570.01-M workforce qualification framework is a section-level administrative responsibility at CTM2. Your billet almost certainly requires an IAT (Information Assurance Technician) Level II or Level III certification under the current approved baseline. CompTIA Security+ (CE) is the most common IAT II certification; CompTIA CASP+, ISC2 CISSP, or GIAC GCED are common IAT III pathways. Beyond your own billet, you track the DoD 8140 compliance status of every CTM3 and CTMSN in your section: which billets require which work-role designations, which sailors hold current certifications, and which are in the pipeline ahead of their qualification deadlines. The IA officer's monthly workforce-compliance report to the commanding officer pulls from the section-level tracking you maintain. If the report has a gap under your section's numbers, the IA officer calls you first. The NSA/CSS Policy Manual 3-16 accountability authority at CTM2 is the accountability record the COMSEC Responsible Officer audits when an accountability discrepancy is found anywhere in the section. Your section's log is the one the NSA periodic inspector reads first. One unexplained gap in the log history under your tenure as section leader generates a review of the entire log back to the date of your section accountability assumption. The accountability discipline you built at CTM3 and CTMSN is now the standard you enforce in the CTM3s and CTMSNs below you. The CTM1 NWAE and the Chief's Mess are both closer than they feel at CTM2. The eEVAL trait average against your peer CTM2s is the FMS component the advancement slate cares most about after the exam score. The Chief who is already mentoring you knows the FMS math — ask him which eEVAL blocks read as Chief-competitive and which read as adequate-petty-officer. The difference is in whether the bullets cite measurable outcomes with named results, or describe functions performed without documented impact.
Career Arc
  • 01CTM2 pin-on via NWAE — exam score, eEVAL trait average and ranking against peer CTM2s, time-in-rate.
  • 02Section or maintenance-cell ownership: accountability for CTM3s and CTMSNs under your section — training, PQS sign-offs, NEC pipeline mentoring, eEVAL input.
  • 03TEMPEST compliance evaluation authority — run TEMPEST baseline measurements on re-installed or modified classified systems, document findings in NSA-accepted format.
  • 04DoD 8140 section-level compliance tracking: your billet cert current, every CTM3 and CTMSN in the pipeline ahead of their qualifying deadline.
  • 05NSA-accountable equipment accountability as the senior section petty officer — your log is the one the COMSEC Responsible Officer calls first.
  • 06CTM1 NWAE prep documented on the Chief's timeline — eEVAL profile building toward EP/MP recommendation with measurable outcomes named.
  • 07Chief Petty Officer selection board on the horizon — the packet begins at CTM2, not CTM1. The Chief mentoring you now is reading the eEVAL blocks you are writing, not the ones you will write at CTM1.
Common Screwups
  • ×Letting a CTM3 close a CSMP discrepancy as repaired without verifying system operability post-repair. Your sign-off on the section's maintenance record is the standard — if the system fails the next operational check, the department head comes to you first. 'The CTM3 closed it' is not an answer that holds up.
  • ×Accepting a verbal exception to PMS from the officer in charge without logging it in the 3-M coordinator's record. When the inspection team asks why a quarterly PMS was deferred for six months, verbal authorization from an officer you cannot contact because he PCS'd is not a defense. Log the exception the day it is granted.
  • ×Running an EMC measurement on a classified system with equipment not on the approved test-equipment list for that accreditation boundary — even to 'check something quickly.' The unauthorized instrument that adds an RF path to a TEMPEST-controlled system is a TEMPEST incident report regardless of the measurement outcome.
  • ×Going around the LCPO to the department head or the commanding officer when you disagree with a maintenance decision. The disagreement happens in the LPO's office; you walk out aligned. The Chief's Mess hears about the shortcut the same watch, and the CTM2 who bypassed the chain of command is the CTM2 the LCPO does not put on the NEC school nomination.
  • ×Treating the CTM1 NWAE as something to prepare for after the cycle opens. The BIB for CTM1 covers a reference list that takes six months to absorb. The CTM2 who starts studying the week the cycle opens and the CTM2 who has been studying for six months are not comparable exam candidates. The FMS that advances to CTM1 is built across the entire tour, not in a sprint.

A Day in the Life

  • 0530-0600Wake up. Check the maintenance data system and any overnight system event reports before PT. The CTM2 who arrives at 0800 and discovers the SIGINT collection system went down at 0200 without knowing about it has already missed the morning brief.
  • 0600-0700Command PT. The CTM2 sets the standard for the section — arriving at PT formation and executing the workout at the standard the OPNAVINST 6110.1 PRT requires, without the excuses the junior sailors are watching for.
  • 0700-0800Hygiene, uniform, chow. Review the overnight duty log and the current CSMP for any new discrepancies that affect the day's maintenance priorities. Arrive at quarters with the section's operational status current.
  • 0800-0830Quarters — the CTM2 is at the LPO's left and the section's spokesman for material status if the LCPO asks. The daily plan from the LPO is your section's work order for the day; any conflict between the plan and the section's current maintenance posture gets surfaced at quarters, not at 1100.
  • 0830-1100Maintenance work center — corrective maintenance on deadlined systems, supervisory oversight of CTM3-executed PMS, COMSEC log review for any overnight duty-section entries that need CTM2 review before the COMSEC Responsible Officer's next walkthrough. Complex fault diagnosis runs during this block when the equipment spaces are staffed.
  • 1100-1130Section status review — CSMP current, parts-order status checked with the supply petty officer, any material-condition changes that affect the afternoon's work brief. The LPO's 1130 check-in on material status should hear the same numbers the commanding officer hears at the afternoon brief.
  • 1130-1230Chow. Not skipped — the CTM2 who skips chow because 'something came up' is modeling a work pattern the junior sailors will emulate until it becomes a section-level problem.
  • 1230-1430Afternoon maintenance block, section training evolution, or NEC mentoring sessions with CTM3s. DoD 8140 compliance review — check the tracking spreadsheet against any certification expiration dates in the next 90 days.
  • 1430-1530CTM1 NWAE study — current BIB reference, 45-60 minutes. The Chief who passes the equipment space during this block and sees the CTM2 with the study materials is the Chief who adds a data point to the Chief-board discussion. The Chief who never sees the CTM2 studying is the Chief who asks whether the packet is real.
  • 1530-1630End-of-day section review — CSMP current, COMSEC log current, any material status changes documented before the duty section assumes the watch. Brief the incoming duty section senior petty officer on anything that changed during the day that they need to know at 0200.
  • 1630-1800Released most garrison days. Duty sections, afloat periods, exercises, and field operations change this block completely.
  • 1800-2200Personal time — family, gym, additional NWAE study. The CTM2 married with family is balancing the professional preparation load against the family readiness that the Chief is also watching. The deployment or exercise cycle that catches the family financially or emotionally unprepared is the cycle that shows up in the CTM2's OPSEC posture and the CTM1 application.
  • On-call (most CTM2 billets, not formal duty section)When the duty section hits a complex fault that exceeds the CTM3's authorization level, the phone call comes to the CTM2. The response expected is: available within 15 minutes, in the equipment space within 30, and a brief diagnosis or escalation decision within the first hour. The commanding officer who calls the CTM2 at 0130 about a COMSEC hardware fault that is affecting the collection mission is testing whether the CTM2 can function at 0130. The answer the commanding officer needs is a timeline and a next action, not a status update.
  • NSA periodic inspection weekThe week before an NSA periodic inspection, the CTM2's schedule is the inspection preparation plan. Every accountability log pre-audited, every CSMP current, every deferred MRC documented with an authorization and an EDD, every DoD 8140 certification current in the tracking spreadsheet. The inspection team that finds no discrepancies under the CTM2's section is the result of months of daily discipline — not a week of pre-inspection theater.

Weekly Cadence

The CTM2 week runs off the LCPO's plan of the week, which reflects the command's readiness cycle, any NSA or command inspection timelines, and the collection schedule that drives equipment availability requirements. Monday morning quarters is when the CTM2 brings the section's status to the LPO in specific, current terms — not 'about the same as last week' but: systems up, systems deadlined, parts on order with EDDs, deferred MRCs with authorizations, CTM3 and CTMSN training progress, and any NEC pipeline or certification timeline items that need the LPO's action. The LPO who receives a specific, accurate section brief on Monday morning can run the week without daily material-status inquiries. Tuesday through Thursday are the production core. Complex corrective maintenance, scheduled PMS execution, CTM3 training evolutions, and DoD 8140 compliance activities run simultaneously. The CTM2 who keeps these threads distinct and visible to the section — maintenance log current, training records updated, compliance tracking current — is the CTM2 who can give the LPO a clean status brief at any point in the week, not just at the scheduled sync times. Technical training blocks, when the command schedules them, are where TEMPEST compliance scenarios and multi-system fault isolation exercises run — the CTM2 who prepares a real-equipment scenario for the section's training block rather than a whiteboard diagram is the CTM2 whose CTM3s retain the material. Friday is the plan-of-week review and the Chief's counseling check-in if that is the command's counseling cadence. The LCPO walks the spaces for the weekly readiness check; the CTM2 meets that walkthrough with the week's maintenance production, the section's advancement and certification status, and the pipeline items that are moving. The Chief who passes the spaces and asks 'how is the section tracking?' should hear a specific answer, not a summary. Deployed, afloat, and exercise tempos collapse the Mon-Fri rhythm into whatever operational windows exist — the COMSEC accountability discipline and the TM-based fault-isolation standard do not change with the tempo, and the CTM2 who maintains both in high-tempo environments is the CTM2 the commanding officer recommends for the next leadership billet.

Key Skills — How to Drill Each

  1. 01
    Troubleshoot a multi-system cryptologic equipment casualty — fault tracing through a receiver, signal processor, and COMSEC hardware interface simultaneously — using TM fault-isolation procedures and your own system knowledge, without calling the LPO for the first three steps.
    Multi-system faults at the CTM2 level require building a mental model of the signal path across system boundaries before opening the TM. Start with the symptom: what specific function failed, at what point in the collection chain, under what operational conditions. Map the symptom to the block diagram that spans the relevant systems. The TM fault-isolation tree may not address cross-system faults directly — your job is to apply the single-system fault isolation methodology from multiple TMs simultaneously and isolate the boundary where the signal chain breaks. Document each measurement step with its result before advancing to the next. The LPO you call after three steps should hear a crisp summary of what you have eliminated, what remains, and what you need authorization to do next — not 'it might be the [component] but I am not sure.'
  2. 02
    Run a work-center PMS review: current CSMP status, deferred MRCs with reasons, parts on order, upcoming inspection liabilities — presented to the department head in a format the commanding officer can brief without rewriting.
    The work-center PMS review is a recurring brief, not an ad-hoc status update. Structure it the same way every time: systems by operational status (up, down-but-operational-with-workaround, deadlined); deferred MRCs with reason, LPO acknowledgment date, and expected resolution date; parts on order by NSN with due-in date and the system they support; upcoming inspection liabilities by date and type. The department head should be able to read the brief and brief it up without calling you. The CTM2 who walks into the weekly sync without a prepared, accurate PMS review is the one the LPO has to rebuild on the fly before the brief.
  3. 03
    Conduct a TEMPEST / EMSEC evaluation of a re-installed or modified classified system — document the baseline, identify deviations, route findings in the format the NSA field activity accepts.
    A TEMPEST evaluation at the CTM2 level follows the system's certification documentation and the applicable NSA TEMPEST standards for the system type. Before you run any measurement on a classified system for TEMPEST evaluation purposes, verify the test equipment against the command's approved test-equipment list — not the general CTM approved list, the list specific to that system's accreditation boundary. Document the baseline measurements at the test points specified in the system's TEMPEST certification documentation, record any deviations with the measured value and the certified limit, and route the finding to the engineering chain with the system's TEMPEST certification number, the specific test point affected, and the deviation magnitude. The NSA field activity does not accept 'it looked okay' as a finding; they accept numbers, test conditions, and equipment identifiers.
  4. 04
    Run the section's DoD 8140 / 8570 compliance tracking: which CTM3s and CTMSNs hold which IA technical certifications, which billets require which work-role designations, and which sailors are in the certification pipeline ahead of their billet-qualifying deadline.
    Build a simple tracking sheet: sailor name, billet, required DoD 8140 work-role designation, required certification, current certification and expiration date, status if in pipeline. Review it monthly against the IA officer's workforce-compliance spreadsheet. Any gap between your tracking and the IA officer's record needs to be resolved before the commanding officer's monthly workforce-compliance brief — not after. The CTM2 who hands the IA officer accurate, current section-level compliance data is the CTM2 the IA officer references when the commanding officer asks how the section is tracking.
  5. 05
    Mentor a CTM3's NEC pipeline packet from idea to submission — and be honest about the school pipeline commitment, deployment implications, and what the NEC actually does to the next advancement slate.
    The CTM3 who wants an NEC packet needs two things from the CTM2 mentor: accurate information about the school pipeline and billet reality, and honest assessment of whether the NEC timing makes sense given the sailor's current eEVAL profile and advancement slate position. Pull the current NAVADMIN and NAVPERS 18068F NEC entry for the CTM3 before the mentoring conversation, not during it. The CTM3 who submits an NEC packet based on what the CTM2 remembers from his own tour is building a plan on a potentially outdated data set. The mentor's job is to help the sailor build the plan on current documents — and to say clearly if the timing is wrong.
  6. 06
    Write the maintenance readiness section of a detachment or unit SITREP input that is specific enough that the commanding officer can defend it at the next echelon without calling you to explain.
    The maintenance readiness section of a SITREP reads: systems affected by name (or system-designation-equivalent that is releasable at the classification level of the SITREP), operational status, downtime if applicable, cause, expected restoration date, and mission impact. 'All systems operational' is acceptable when true. 'System A deadlined for [fault description]; LRU on order, NSN [number], EDD [date]; collection mission [affected/unaffected] per [reference]' is the entry the commanding officer can brief. 'Some systems have maintenance issues that are being addressed' is the entry the commanding officer edits before sending and then calls you to ask what he should have said.

Manuals & References — What Chapters Matter

  • MIL-STD-461 — Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems and Equipment
    At CTM2 you are writing TEMPEST compliance findings against this standard — not citing it to explain why test equipment is restricted, but applying the emissions and susceptibility framework to real measurements on real systems. Know the difference between conducted and radiated emission limits, understand the test method categories that apply to the equipment types in your work center, and be fluent in the documentation format an NSA engineer expects to read in a TEMPEST deviation finding. The LPO who calls you with a TEMPEST compliance question at 0200 expects the CTM2 answer, not the CTM3 answer.
  • OPNAVINST 2201.3 — Navy SIGINT Operations and Reporting
    The collection posture brief to the commanding officer traces to this instruction. When the CTM2 reports a system's operational status, the commanding officer is calculating the collection mission impact. OPNAVINST 2201.3 is the framework the commanding officer uses for that calculation; if you do not understand the policy, you cannot brief the impact accurately. The section CTM2 who understands the collection and reporting framework is the section CTM2 who briefs 'mission-affecting' or 'not mission-affecting' with a defensible basis rather than a guess.
  • NSA/CSS Policy Manual 3-16 — COMSEC Material Control System
    You are the senior accountable petty officer in most CTM2 section configurations. Your section's log is the one NSA reads during periodic inspections. Read the sections governing periodic audit procedures, the documentation requirements for COMSEC equipment operational checks, and the incident reporting chain — not as a refresher, but as the accountable-party who signs the records. The CTM2 whose log entries satisfy the NSA periodic inspector's requirements is the CTM2 whose COMSEC Responsible Officer does not have to remediate before the inspection team arrives.
  • DoDM 8140.03 — Cyberspace Workforce Qualification and Management Program
    This manual defines the work-role designations and approved certification baselines that gate which billets your section members can fill and how long they can fill them before the certification lapses. At the CTM2 level you track section-level compliance — know the work-role designations for the billets in your section, the approved certifications for each, and the renewal cycle. The IA officer who finds a compliance gap during the commanding officer's monthly review asks the section CTM2 first. Have the answer before the question is asked.
  • NAVPERS 18068F and current NEC source-rating NAVADMIN — the NEC catalog and current pipeline availability
    Mentor packets off the current documents, not the version of NAVPERS 18068F that was current when you went through your own pipeline two years ago. Pull the current cycle's NAVADMIN before every NEC mentoring conversation. The CTM2 who can tell a CTM3 'the current NAVADMIN shows [X] slots for that NEC in the next cycle and the pipeline runs [Y] weeks with [Z] billet implications' is the mentor whose sailors submit competitive packets.
  • NWAE BIB for CTM1 — current cycle from MyNavyHR / NETC
    Build the CTM1 study plan before the cycle opens and put a monthly review cadence on the references that anchor the exam. The BIB for CTM1 covers maintenance procedures, COMSEC policy, DoD 8140 framework, personnel policy, and leadership doctrine — a broader reference base than the CTM3 BIB. The CTM2 who has been working through the CTM1 BIB for six months before the cycle opens walks into the exam with a materially different preparation baseline than the one who starts with the cycle announcement.

Standards — How to Hit Each

  • NWAE for CTM1 prep documented on the LCPO's timeline; eEVAL Enlisted Advancement Worksheet (EAW) clean and the BIB study log defensible when the Chief asks.
    The Chief who is mentoring you toward anchors reads the EAW, the eEVAL blocks, and the study log as a unified picture. An EAW that shows college credits, an active certification, a clean PRT record, and a documented NWAE study log in conjunction with eEVAL blocks that cite measurable outcomes is the package the Chief can advocate for at the selection board. Build each component independently and bring them together — not as a check-the-box exercise, but as the accurate record of a sailor who is performing at the next paygrade before the next paygrade arrives.
  • DoD 8140 / IAT Level II or III certification current for your billet and tracked for every CTM3 and CTMSN in the section.
    Verify your own billet's current DoD 8140 work-role designation and the approved certification baseline for that role on the DoD Cyber Exchange. If your certification is within 90 days of expiration, schedule the renewal examination before it expires — not after. For the section, build the tracking spreadsheet described in keySkillsDeep and review it monthly against the IA officer's workforce-compliance data. Any discrepancy between your tracking and the IA officer's record gets resolved before the commanding officer's brief, not during it.
  • Section COMSEC accountability records 100% accurate at every command audit and NSA periodic inspection.
    Before every quarterly COMSEC Responsible Officer audit, walk the section's accountability log yourself. Every entry should reconcile with the physical inventory: serial numbers, quantities, holders, action types, TPI signatures. Any reconciliation discrepancy found during your own pre-audit review is a correctable finding; any reconciliation discrepancy found by the COMSEC Responsible Officer during the official audit is an investigation. The thirty minutes you invest in the pre-audit self-check is the thirty minutes that determines which of those two scenarios plays out.
  • PMS completion rate defensible at commanding officer level — your section's numbers in the monthly maintenance readiness report brief without caveats.
    The commanding officer's monthly maintenance readiness brief reads the numbers, not the narratives. If your section's PMS completion rate has a caveat — 'we had two sailors on leave' or 'the system was down for a parts delay' — the commanding officer needs to hear a rate that already accounts for those constraints, not a rate that requires the caveat to be defensible. Track the completion rate weekly and manage the deferred MRC documentation in real time, not at month's end. The number that goes into the readiness report is the number you have been maintaining all month.
  • eEVAL trait average and ranking that supports EP/MP recommendation; the LCPO knows your ranking weeks before the EVAL board reads it.
    The eEVAL blocks you write for your CTM3s set the standard the Chief uses to evaluate your own eEVAL input. Blocks that cite measurable outcomes — 'led section COMSEC audit that resolved 4 outstanding discrepancies; zero COMSEC findings on subsequent NSA periodic inspection' — are the blocks the Chief builds EP/MP recommendations around. Blocks that describe functions — 'performed maintenance on assigned systems and trained junior sailors' — are the blocks the Chief rewrites because they do not distinguish the sailor from the job description.

Technical Mistakes — Concrete Consequences

  • Letting a CTM3 close a CSMP discrepancy as repaired without verifying system operability post-repair.
    When the system fails the next operational check and the chain traces the fault back to the 'repaired' discrepancy, the department head does not ask the CTM3 why the verification was skipped — he asks the CTM2 who signed off the section's maintenance record. Your signature covers the section's output. The CTM3 who did not verify gets counseled; the CTM2 whose section's standard allowed the unverified close gets the eEVAL entry.
  • Accepting a verbal exception to PMS from the officer in charge without logging it in the 3-M coordinator's record.
    The inspection team that finds six months of missed PMS on your section's record has one question: where is the documentation authorizing the deferral? The OIC who authorized it verbally has PCS'd; the email he sent is in a mailbox that was wiped when his account closed. The log entry that documents the exception, the date, and the authorizing officer's name is the only defense the section has. The CTM2 who did not log it wears the inspection finding.
  • Running an EMC measurement on a classified system with equipment not on the approved test-equipment list for that accreditation boundary.
    The instrument does not need to malfunction or record anomalous data. The connection of a non-approved instrument to a TEMPEST-controlled system is itself the TEMPEST incident. The IA officer generates the report; NSA reviews the system's TEMPEST certification; the re-accreditation timeline is measured in months. The maintenance log entry that shows the unauthorized instrument connection is your name, your date, your tool list. The approved-test-equipment list for each system is in the accreditation package for that system — it takes five minutes to check before the measurement.
  • Treating the CTM3's COMSEC accountability log entry as a formality — skimming the signature rather than verifying the entry against the physical inventory.
    The log entry the CTM3 signs is the entry NSA reads during the periodic inspection. The CTM2 who countersigns without verifying is the CTM2 whose co-signature appears on the discrepant entry. The COMSEC Responsible Officer who finds the discrepancy during the audit asks both signatories to explain. 'I trusted the CTM3' is not an answer that holds up at a COMSEC investigation.
  • Going around the LCPO to the department head or commanding officer when disagreeing with a maintenance decision.
    The Chief's Mess hears about the bypass the same watch. The CTM2 who circumvents the chain of command — even with good technical justification — is the CTM2 the LCPO does not put on the Chief board nomination, does not recommend for the NEC school slot, and does not advance as an LPO candidate. The disagreement happens in the LCPO's office and you walk out aligned, or you walk out with a documented, leadership-acknowledged objection. There is no third option that does not cost the CTM2 career capital.

Career Decisions at This Rank

  • Chief Petty Officer selection — is the packet actually competitive, and what does the timeline look like honestly?
    The Chief board packet is a multi-year product, not a document assembled before the board convenes. The board reads the entire service record: eEVAL trend across the CTM2 and CTM1 paygrades, the EP/MP recommendations in the eEVAL blocks, the awards record, the educational achievements, the warfare qualifications, the NEC depth, the pipeline output. The Chief who is mentoring you toward the board is not doing you a favor — he is evaluating whether your record is actually competitive against the pool. Ask him directly: 'Is my record a Chief packet or does it need another cycle?' The honest answer may be uncomfortable but the alternative is submitting a packet that does not advance and spending another 18 months wondering why. The CTM2 who builds toward Chief the right way — one defensible eEVAL block, one measurable outcome, one production result at a time — is the CTM2 whose packet the board reads in thirty seconds.
  • Limited Duty Officer (LDO) — Cryptologic or Information Warfare side — versus staying enlisted
    The LDO program is the primary commissioned officer pathway for senior enlisted sailors in the Navy's technical ratings. The CTM community produces LDOs in the Information Warfare Officer (IWO) and Limited Duty Officer Cryptologic (LDO-Cryptologic) designations. The LDO application process is competitive: application timeline, service record quality, physical readiness record, interview, and commanding officer endorsement. The honest tradeoff: LDO extends the career commitment significantly, changes the daily job from technical maintenance execution to leadership and staff functions, and moves the sailor into an officer culture that is different from the Chief's Mess. The CTM2 who wants to stay close to the technical work is generally better served by the Chief's Mess and a strong NEC pipeline than by commissioning. The CTM2 who wants the administrative and leadership track should talk to LDOs in the command about what the post-commissioning career actually looks like — not the brochure version.
  • DoD 8570 / 8140 advanced certification — CASP+, CISSP, or GIAC-family at the IAT III level
    The transition from IAT Level II (Security+ CE) to IAT Level III (CompTIA CASP+, ISC2 CISSP, GIAC GCED, or equivalent) opens senior billet gates in the CTM community and the broader Navy cryptologic workforce, and substantially increases the post-service salary floor in the cleared-contractor and federal-civilian markets. The CTM2 paygrade is when the investment makes sense — enough technical depth to study meaningfully, enough remaining career to capture the billet-access benefit. CISSP requires five years of qualifying professional experience in two of eight CISSP domains before you can sit the exam; CompTIA CASP+ does not have a formal experience requirement. Map the certification pathway against the DoD 8140 approved baseline for the senior CTM billets you want access to before choosing which exam to prioritize.
  • Remaining in the Navy through 20 years versus separating with the package the CTM2 paygrade has built
    The CTM2 at 8-12 years of service is in the highest-value separation window from a cleared-contractor market perspective: TS/SCI clearance, COMSEC and TEMPEST maintenance credentials, DoD 8140 certification, and enough seniority to be credible but not so senior that the transition to a junior IC or defense-contractor role feels like a step backward. The 20-year retirement benefit under the legacy High-3 system or BRS is real and growing; the CTM2 who is competitive for Chief and wants the retirement benefit should stay. The CTM2 who is not tracking toward Chief and has a concrete civilian offer on the table should run the full compensation comparison — base pay, BAH, BAS, TSP, TRICARE, and the retirement value at 20 versus the immediate civilian salary, 401k matching, and career trajectory. The decision is math, not loyalty. Run the numbers with real figures from the civilian job offer, not estimates.

How the Seat Varies by Unit Type

  • Afloat CDSE / ACE on a surface combatant (destroyer, cruiser, or amphibious ship)
    The CTM2 on an afloat detachment is the senior maintenance petty officer in an operationally-driven environment where maintenance windows are carved out of the collection schedule and the engineering chain is physically present rather than a phone call away. Sea pay, the ship's operational cycle, and the compressed maintenance environment create a different eEVAL profile than shore — the measurable outcomes are more visible, the operational contribution is more direct, and the CTM2 whose section keeps the collection mission up during a deployment surge is the CTM2 the commanding officer can cite at the next advancement board. Afloat CTM2 billets are the ones that produce Chief-competitive packets when the sailor performs well.
  • Shore-based SIGINT support unit or Fleet Intelligence Organization technical department
    The largest CTM2 peer group, the most formal training infrastructure, and the most predictable schedule for CTM1 NWAE study and DoD 8140 certification pursuit. The tradeoff: the operational differentiation on the eEVAL requires the CTM2 to generate measurable outcomes from maintenance production and section-leadership activities rather than from deployed operational contribution. Shore CTM2 billets are well-suited to NEC pipeline completion, LDO application preparation, and the DoD 8140 advanced certification work.
  • Joint cryptologic element (NSA/CSS or combined-service SIGINT unit)
    The CTM2 at a joint element is operating in the same accountability and TEMPEST compliance environment as the NSA periodic inspection that governs every other CTM billet — because the command authority is NSA/CSS rather than OPNAV. The COMSEC accountability discipline and the TEMPEST compliance standard at a joint element are NSA-directed; the CTM2 who has been operating to that standard develops a compliance depth that the CTM2 at a Navy-only command who treats NSA inspection as a periodic external event does not. Joint-element CTM2 billets produce technically exceptional sailors; the tradeoff is that the Navy administrative chain can be administratively distant.
  • Special Reconnaissance or expeditionary cryptologic element
    Small footprint, high operational intensity, limited peer support. The CTM2 at a special reconnaissance or expeditionary element is the senior technical authority in the maintenance function — there may not be a CTM1 or CTMC in the element. The COMSEC accountability, TEMPEST compliance, and fault-isolation work that the CTM2 at a large shore command has multiple layers of peer review on is the CTM2's individual technical judgment in an expeditionary billet. The standard does not change because the oversight structure is smaller; if anything, the self-enforcement bar is higher because the Navy's inspection framework is not present to catch what the CTM2 misses.

What Good Looks Like at This Rank

The good CTM2 is the petty officer the LCPO names when the officer in charge asks who is running the cryptologic maintenance spaces during the deployment surge. That specific name — not 'whoever is senior' — means the commanding officer has heard this CTM2's name in the material-condition brief often enough to recognize it as the accurate answer, and the LCPO has watched this CTM2's section perform well enough to trust the unsupervised operational period without daily check-ins. That trust is built across months of specific, verifiable performance, not announced. The section's CSMP brief requires no caveats at the weekly sync. Every deadlined system has a documented parts order with a current EDD. Every deferred MRC has a log entry dated the day of the deferral with the authorizing officer's name. The COMSEC accountability log reconciles with the physical inventory before the COMSEC Responsible Officer's quarterly audit begins — because the CTM2 walked it herself the week before and caught the one entry that needed a correction. The NSA periodic inspection that finds zero accountability discrepancies under this CTM2's section tenure is not an accident; it is the output of a daily discipline that the CTM3s in the section have internalized because the CTM2 enforces it without exceptions. The CTM3 under her has an NEC packet on the table — a real one, built off the current NAVADMIN and the current NEC catalog entry, with the school commitment and deployment implications documented and the LPO's endorsement already aligned. The eEVAL bullets for the CTM3 read action-result-impact with specific numbers: 'led COMSEC audit resolving 3 outstanding discrepancies; zero NSA findings on subsequent inspection' rather than 'performed COMSEC duties in a professional manner.' The difference in those two bullet formats is the CTM2's mentoring output made visible. The DoD 8140 certification on her record is current. The tracking spreadsheet for the section's workforce compliance is the document the IA officer uses to populate the commanding officer's monthly brief — because it is accurate and current every time the IA officer pulls it. The CTM1 NWAE study log is on the Chief's desk before the cycle opens, not the week the cycle opens. The Chief who is mentoring her toward anchors does not have to ask what she is working on next — she tells him in the weekly counseling conversation with specific milestones and specific completion dates. The Chief's Mess has already discussed her. The anchors are not guaranteed, but the CTM2 who operates this way is the CTM2 the board reads in thirty seconds.

Preview — The Next Rank

CTM1 (E-6) is the LPO paygrade — not the informal LPO function that the CTM2 has been filling in for years, but the official watchbill designation that puts your name in the eEVAL chain as the reporting senior for CTM2s and CTM3s in your section. You will write four to six eEVALs per cycle that shape the next advancement slate. The eEVAL blocks you write for junior sailors are the record the board reads when it evaluates whether CTM1 is actually developing the next generation or just occupying the billet. The Chief board is no longer a planning exercise — it is an active event. The packet you submitted or are preparing is built on the service record you created at CTM2 and CTM1, and the board reads the trend, not just the most recent cycle. The CTM1 who is performing at the Chief level before the anchors go on is the CTM1 whose packet the board advances. The Chief who is mentoring you at CTM2 and CTM1 is reading your performance against the standard of a sitting Chief, not the standard of an adequate petty officer. When he tells you the packet is or is not competitive, believe him. The DoD 8140 compliance picture at CTM1 expands to the entire LPO-section's workforce. Every CTM2, CTM3, and CTMSN in your section has a billet-required certification timeline; the CTM1 LPO who presents zero compliance gaps to the IA officer at every monthly brief is the CTM1 whose commanding officer does not have to address workforce-compliance findings at the fleet staff level. The COMSEC accountability authority at CTM1 is the one the NSA periodic inspector names in the audit opening conference as the senior accountable petty officer — your log is the log the inspection starts with.
FAQ

CTM E5 — Frequently Asked Questions

Q01What does a E5 CTM (Cryptologic Technician (Maintenance)) actually do?
You run a section or a maintenance cell — on an ACE or CDSE afloat, a shore SIGINT collection facility, a Navy Special Reconnaissance element, or a Fleet Intelligence Organization cryptologic equipment shop.
Q02What's the most important thing to know as a E5 CTM?
CTM2 (E-5) is the independent-maintainer paygrade and the DoD 8140 / 8570 certification inflection point.
Q03What does a typical day look like for a E5 CTM?
Time-blocked day at the E5 CTM rank tier: 0530-0600 Wake up. Check the maintenance data system and any overnight system event reports before PT. The CTM2 who arrives at 0800 and discovers the SIGINT collection system went down at 0200 without knowing about it has already missed the morning brief, 0600-0700 Command PT. The CTM2 sets the standard for the section — arriving at PT formation and executing the workout at the standard the OPNAVINST 6110.1 PRT requires, without the excuses the junior sailors are watching for, 0700-0800 Hygiene, uniform, chow.…
Q04What mistakes get E5 CTM soldiers fired or relieved?
Letting a CTM3 close a CSMP discrepancy as repaired without verifying system operability post-repair. Your sign-off on the section's maintenance record is the standard — if the system fails the next operational check, the department head comes to you first. 'The CTM3 closed it' is not an answer that holds up; Accepting a verbal exception to PMS from the officer in charge without logging it in the 3-M coordinator's record.…
Q05What career decisions matter most at the E5 CTM rank tier?
Chief Petty Officer selection — is the packet actually competitive, and what does the timeline look like honestly? — The Chief board packet is a multi-year product, not a document assembled before the board convenes. The board reads the entire service record: eEVAL trend across the CTM2 and CTM1 paygrades, the EP/MP recommendations in the eEVAL blocks, the awards record, the educational achievements, the warfare qualifications, the NEC depth, the pipeline output.…
Q06What's next after E5 for a CTM (Cryptologic Technician (Maintenance)) in the Navy?
CTM1 (E-6) is the LPO paygrade — not the informal LPO function that the CTM2 has been filling in for years, but the official watchbill designation that puts your name in the eEVAL chain as the reporting senior for CTM2s and CTM3s in your section.
Q07What manuals and regulations does a E5 CTM need to know cold?
MIL-STD-461 — EMI/EMC requirements; you are now writing the TEMPEST compliance findings, not just reading the test limits.; OPNAVINST 2201.3 — Navy SIGINT Operations; the collection posture brief to the commanding officer traces to this instruction.; NSA/CSS Policy Manual 3-16 — COMSEC Material Control System; you are the senior accountable petty officer in many shop configurations — your log is the one NSA audits.

This playbook has no tips yet. Be the first to share what you know.

Published by the Honest MOS Editorial DeskVerified against DoD/.gov sourcesUpdated May 2026Editorial standards