Cyberspace Effects Operations Officer

You are the junior SF cyber officer — fresh out of the 17S Initial Skills Training pipeline, TS/SCI badge around your neck, zero operational credibility yet. Space Delta 6 has been defending the SF's space mission systems since before you were commissioned; your job for the next two years is to earn the right to stand mission without someone checking every decision you make.

You commissioned through USAFA, AF ROTC, OTS, or direct SF accession, received 17S designation, and passed through 17S Initial Skills Training (the cyber officer schoolhouse integrating AF and SF training elements) before reporting to one of three primary first-unit tracks: Space Delta 6 at Schriever SFB or Peterson SFB (mission systems defense, Cyber Mission Force team integration, or the Mission Defense Team aligned to a specific space mission area), a USCYBERCOM Cyber Mission Force team as an embedded SF element (Combat Mission Team, Cyber Protection Team, or Cyber Support Team under USCYBERCOM mission authority), or a joint / IC partner billet at NSA, DIA, or a CCMD J39 cyber staff. At Delta 6 your daily work is the MDT or CMF team mission cycle — planning operations under the team chief, executing defensive or effects missions per the assigned mission authority, documenting the operational timeline and the actions taken, and working the post-mission review with the senior officers who grade the execution. Outside the ops floor there is the OPR cycle, the professional development stack (JP 3-12 study, STARCOM foundational education, unit-level training events), and the clearance-maintenance reality that runs under continuous evaluation. The unglamorous version: a lot of learning the team's specific mission set, a lot of asking questions in the debrief rather than the brief, and the slow accumulation of certified mission hours that make you operationally credible.

• 01Plan and execute cyberspace operations missions within the team's assigned mission authority — offensive or defensive — per JP 3-12 (Cyberspace Operations) and the unit's governing operational orders, with full documentation and mission debrief on standard.
• 02Operate within the Cyber Mission Force team structure: understand the team's position in the Cyber Mission Force enterprise (Combat Mission Team / Cyber Protection Team / National Mission Team / Cyber Support Team), the mission-assignment chain through USCYBERCOM or SF service component, and the deconfliction requirements with other joint forces in the same operational environment.
• 03Defend space mission systems through the MDT framework — understand the specific satellite C2 architecture, ground station network, or mission data processing system you are defending, including the system's technical topology, the threat model the MDT operates against, and the incident-response procedures the team uses when indicators of compromise appear.
• 04Maintain TS/SCI clearance discipline at the operational level: self-report foreign contacts, financial changes, and potential security incidents through the continuous evaluation system without waiting to be asked. DoDD 8140 (Cyber Workforce Framework), the relevant CFETP, and unit security operating instructions are not optional reading.
• 05Write clear, sourced, and complete mission documentation — operational logs, incident reports, after-action summaries — in the format the unit's mission record requires. Cyber operations generate a documentation trail that senior leadership and legal review; inaccurate records are an integrity problem, not a typo.
• 06Complete Mission Commander Initial Qualification Training (or equivalent position certification) within the timeline the unit publishes. Lapsed certification means you are not on the operational roster; the DO reads the qual card.

• —JP 3-12 — Cyberspace Operations (the foundational joint doctrine for cyberspace operations; read chapters II and III on offensive and defensive cyberspace operations before your first mission planning cycle).
• —USSPD 1 — U.S. Space Force Doctrine Publication 1, "The Spacepower Doctrine" (the SF institutional frame that contextualizes the 17S mission within the broader Space Force warfighting function).
• —DoDD 8140.01 — Cyberspace Workforce Management (the DoD-wide cyber workforce framework that establishes position coding, qualification requirements, and continuous development requirements for 17S officers).
• —DAFMAN 36-2406 — Officer and Enlisted Evaluation Systems (the OPR / PRF / Stratification system; read before your first rater-ratee initial counseling, not after).
• —EO 12333 — United States Intelligence Activities; DoDM 5240.01 — Procedures Governing the Conduct of DoD Intelligence Activities Affecting US Persons (the legal framework for operations that touch US-person data or US critical infrastructure — non-negotiable reading in the first 90 days).

• —17S Initial Skills Training complete and AFSC 17SX awarded — the pipeline exit credential. SF-specific mission orientation at Schriever SFB / Delta 6 complete before the first operational assignment.
• —TS/SCI clearance with counterintelligence (CI) polygraph maintained current. Clearance loss for a 17S officer is a career exit — the entire operational, joint, and IC assignment slate is built on the clearance stack.
• —Mission Commander or equivalent position certification earned at the timeline the unit publishes — not late, not with a supervised-extension on the record without documented cause.
• —Physical Fitness Assessment under DAFMAN 36-2905 passed on every cycle — small-service visibility means a PT flag reaches the Delta commander faster than in a larger service.
• —OPR initial counseling documented within 30 days of assignment; support form completed before the rater closes the OPR cycle.

• —Operating outside the assigned mission authority. Cyber operations authorities are precisely scoped; an action outside the authority granted by the operational order or the USCYBERCOM / SECDEF approval chain is not a judgment call — it is a legal and operational crisis that lands on every name in the chain.
• —Producing inaccurate or incomplete mission documentation. Cyber mission logs are legal records and operational history; a timeline error, an omitted action, or a summary that does not match the technical record discovered in a review creates an integrity problem that follows the officer's name.
• —Bringing an unauthorized device into the SCIF or the classified mission environment. One event. One investigation. One OPR bullet that answers the next four OPR cycles, and possibly a clearance adjudication.
• —Treating the MDT's space-system knowledge requirement as optional. Mission Defense Teams defend specific mission architectures; the 17S officer who cannot discuss the defended system's topology, the known adversary threat model, or the incident-response procedures with the system engineers loses credibility with the MDT team and the Delta 6 leadership within the first quarter.
• —Posting any unit, mission, or assignment-related content on any open social media platform. Space Force operations and cyber operations are both high-interest OPSEC targets; adversary collection aggregates open-source identifiers against SF cyber personnel specifically.

The good junior 17S is the officer the team chief briefs the Delta 6 commander on at the monthly readiness review — mission certification complete, documentation clean, the adversary TTPs studied on personal time rather than waiting for the mandatory training event. By month eighteen the Mission Commander certification is current, the OPR is already being written by the rater with bullets the O-5 board can read, and the joint billet conversation with the assignment officer has started rather than been deferred.

You are the experienced SF cyber officer the Delta 6 squadron and the joint cyber enterprise both need — Mission Commander on the operational roster, CMF team lead under USCYBERCOM authority, or the SF field-grade in the NSA / CCMD J39 staff seat. The SF cyber community is small enough that your name circulates across every consequential billet in the community before you make Major. That cuts both ways.

By Captain you have a completed operational tour at Delta 6 or on a CMF team, Mission Commander certification, and the functional understanding of the SF's space-domain cyber mission that only comes from running actual operations. The field-grade years are the integration phase: you command a Cyber Mission Force team (Combat Mission Team lead, Cyber Protection Team lead) under USCYBERCOM mission authority, hold a Delta 6 flight-commander or Director of Operations billet building the squadron's operational capacity, serve on the USCYBERCOM J3 / J5 staff at Fort Meade integrating the SF's space-cyber equities into joint operational planning, or hold an IC partner billet at NSA / CSS or a CCMD J39 (cyber and information operations directorate) where the SF's space-domain cyber perspective integrates into the broader IC mission. The DO pipeline at Delta 6 runs: Mission Commander → Instructor / Evaluator → flight commander → Director of Operations → squadron commander (O-5 screen). The joint tour requirement — JPME-II and JDA credit — is explicitly weighted at the O-5 command screen and the O-6 selection board under current SF talent management guidance; do not let the Captain window close without a USCYBERCOM or COCOM J39 tour on the OPR profile. The unglamorous parts: OPR writing for the Lieutenants and NCOs you now rate, the PRF / Stratification cycle (no WAPS — strat by the Delta CC / STARCOM chain), the additional duty stack that comes with every field-grade assignment, and the post-service financial conversation that arrives with full force by the time the IC contractor market starts calling directly.

• 01Lead a Cyber Mission Force team or MDT element through the full mission cycle — planning, legal authority confirmation, execution, documentation, and mission debrief — with all actions within the authorized operational scope and all records complete for IC / legal review.
• 02Operate on the USCYBERCOM J3 / J5 staff or a COCOM J39 at the senior field-grade level — produce joint operational planning products, cyber mission element deconfliction assessments, and space-cyber integration briefs that survive joint staff peer review without the Delta 6 being the credibility backstop.
• 03Brief flag officers on cyber operations: the Delta 6 commander, the USCYBERCOM J3, the USSPACECOM N3/J3, the CCMD J2 / J3. The SF cyber field-grade who hedges every operational brief loses the joint-billet standing that the O-5 command screen reads.
• 04Write OPRs and PRF inputs for the officers and NCOs you rate — measurable bullets, defensible stratification, the honest below-the-line conversation when performance is not competitive. In a small community, inflated OPRs propagate as a rater-credibility liability, not a junior-officer favor.
• 05Translate cyberspace operational requirements into joint planning products: mission-type orders, concept of operations, rules of engagement inputs, deconfliction requests — in the format the USCYBERCOM or CCMD operational chain can execute against.
• 06Maintain and apply the IC partner-agency relationships — NSA / CSS coordination channels, CISA technical collaboration, FBI Cyber Division liaison — at the field-grade level where formal and informal networks both matter.

• —JP 3-12 — Cyberspace Operations (you now teach this doctrine in planning cycles and mission reviews; chapters II-IV are the operational framework the joint staff quotes under pressure).
• —USSPD 1 — U.S. Space Force Doctrine Publication 1 (the SF institutional frame you apply when the joint staff asks how SF cyber equities integrate with space operations).
• —DoDD 8140.01 — Cyberspace Workforce Management (the workforce-credentialing framework your officer-rating decisions tie into at the unit level).
• —DAFMAN 36-2406 — Officer and Enlisted Evaluation Systems (you write OPRs, PRF inputs, and Stratification endorsements at field-grade; understand the DP / PRF system and what the O-5 board reads before the suspense lands).
• —EO 12333; DoDM 5240.01; current IC legal authorities applicable to the mission set (you sign documents against these authorities as a field-grade mission commander; legal literacy at this level is not optional).

• —Documented Mission Commander certification and operational tour credibility — at least one completed CMF team-lead or Delta 6 flight-commander assignment on the OPR profile before the Major's board.
• —Joint duty / JDA credit on the record or actively building. The O-5 SF command screen and O-6 board weight JDA completion; DOPMA mandates it at O-7 consideration. Do not let the Captain window close without a USCYBERCOM J-staff or COCOM J39 billet on the record.
• —JPME-II completion. The SF talent management framework applies JPME-II credit explicitly at field-grade and above; treat it as a planning item, not a career-late discovery.
• —TS/SCI with CI poly maintained current. A clearance event at Captain / Major closes the next joint billet, the NSA / CCMD J39 tour, and the post-service IC contractor market in a single adjudication.
• —Non-rated Line SF O-4 selection — read the SF promotion board results by competitive category. The SF cyber community's promotion rate is distinct from the broader SF officer corps and from the larger AF cyber community.

• —Phoning the CMF team-lead or joint-staff tour. USCYBERCOM J3 leadership and the SF service component leadership both read team-lead and joint-staff performance; weak field-grade execution in the visible joint tour is the OPR profile that does not survive the O-5 command screen.
• —Producing a mission-execution record that cannot survive IC / legal review. Cyber operations at the field-grade level generate records that are reviewed by DoD OGC, NSC staff, and IC oversight; a mission log with factual gaps, timeline errors, or authority-scope ambiguities at this level is a career and legal liability.
• —Missing the joint-tour window. The Captain / Major years are the structural window for the USCYBERCOM J-staff or COCOM J39 tour; field-grade officers who treat joint exposure as deferrable until O-5 discover at the O-5 command screen that the board already decided.
• —Mishandling classified at field-grade. A clearance revocation at Capt / Maj closes the next assignment, the NSA / IC partner billet, and the post-service federal contractor market in one event; the SF cyber community is small enough that the read propagates across every billet by name within the quarter.
• —Writing inflated OPRs for officers who are not competitive. The 17S community is small enough that the senior-rater network knows every name on the ladder; an inflated OPR on a junior officer who underperforms at the next level costs the rater credibility for years.

The good 17S Captain or Major is the officer the Delta 6 DO names first when the USCYBERCOM J3 asks for an SF cyber officer for a short-notice joint planning assignment — mission documentation clean, team-lead tour complete, the joint-staff relationships already built rather than being introduced. By the Major's board, the OPR profile has a USCYBERCOM J-staff or COCOM J39 tour on it, the PRF has a Stratification from the Delta CC or STARCOM chain, JPME-II is done, and the post-service market has already sent the first unreturned LinkedIn message.