A

Apex

Manufactures ESPA-class satellites and bus

Mission Security Engineer

Security Governance, Risk & ComplianceUpdated on Nov 14
Full-timeLos Angeles, CA, USA

About the Job

Requirements

  • U.S. citizenship is required, with the ability to access export-controlled data.
  • Experience with technical tooling, including reading pipeline output, querying an API, and interpreting scanner and configuration state.
  • For entry-level candidates: a bachelor's, master's, or PhD in systems engineering, computer science, cybersecurity, aerospace, or a related field.
  • For entry-level candidates: hands-on building experience through coursework, internships, research code, personal projects, capture-the-flag events, a co-op, or an early role, and/or exposure to RMF, security compliance, cloud, or software engineering.
  • For entry-level candidates: willingness to learn RMF from the ground up and ability to quickly learn a complex technical domain while retaining detailed information.
  • For senior-level candidates: strong experience in embedded or space systems, or cloud infrastructure.
  • For senior-level candidates: multiple systems taken to authorization in national security or DoD environments, with fluency in RMF practice, including categorization under CNSSI 1253, overlay selection, tailoring rationale, assessment coordination, POA&M management, continuous monitoring, and reauthorization triggers.
  • For senior-level candidates: ability to discuss categorization, tailoring, assessment, and authorization concretely, and to design, document, or test a report and determine whether it constitutes evidence that a control is satisfied.
  • For senior-level candidates: direct experience with at least one accredited cloud environment and one non-traditional system such as embedded, weapons, platform IT, industrial, or space.

Responsibilities

  • Build and sustain authorization packages for both system boundaries, including system description, boundary definition, categorization, control selection and tailoring rationale, implementation statements, assessment coordination, and the residual risk picture carried to the Authorizing Official.
  • Engage assessors early on the evidence-generation approach so generated artifacts are trusted before a package depends on them.
  • Own the plan of action and milestones.
  • Maintain the authorization system of record, such as eMASS or an equivalent.
  • Own the authorization boundary determination for the flight segment and develop rationale that withstands assessor scrutiny.
  • Categorize under CNSSI 1253 and defend overlay selection, treating the Space Platform Overlay as a starting point and challenging its assumptions where onboard security capability exceeds the published tailoring.
  • Tailor the control baseline with per-control rationale using Aerospace's Space Segment Cybersecurity Profile (TOR-2023-02161 Rev A) and SPARTA-linked tailoring, including arguing controls back in where onboard capability exceeds baseline assumptions.
  • Define the bus type-authorization and design how each vehicle produced generates its own conformance evidence so fleet growth does not cause assessment labor to grow linearly.
  • Derive verifiable security requirements from threats using SPARTA TTPs as the traceability key, for software and mission integration engineers to build and test against.
  • Translate verification and production artifacts into assessment evidence, and alert engineering early when produced artifacts will not satisfy an assessor.
  • Own continuous monitoring for a fielded fleet, including security audits downlinked across contact windows, configuration drift across vehicles, and on-orbit software updates as recurring authorization events.
  • Define and document the authorization boundary for mission systems in classified cloud, including impact-level scoping and the connection with ground stations and the RF edge.
  • Own the control and evidence story for operator command authority, including identity, role separation, least privilege, two-person integrity, non-repudiation, and complete auditing of every command reaching the vehicle.
  • Build and defend the control inheritance model, and demonstrate the customer-responsible set with live evidence by validating what the cloud service provider and platform satisfy versus what remains the responsibility of mission-unique applications.
  • Implement controls as code so infrastructure-as-code, policy-as-code, and pipeline configuration serve as both implementation and evidence.
  • Make change control and continuous monitoring work at operations tempo without putting a contact window at risk, in preparation for the DoD transition toward the Cybersecurity Risk Management Construct and continuous authorization.
  • Manage security incident reporting and coordination for the boundary.
  • Define the required evidence and its form.
  • Design the OSCAL-based evidence data model and mapping layer that resolves a property assertion to control identifiers across 800-53, CNSSI 1253 baselines, overlays, and program-unique control sets.
  • Build a pipeline that deterministically renders SSP sections, assessment evidence, POA&M items, and continuous monitoring reports from pinned evidence snapshots.
  • Programmatically integrate with the authorization system of record, such as eMASS or an equivalent, so generated artifacts are delivered where assessors look.
  • Use AI-assisted drafting and crosswalk tooling for control narratives, framework mappings, and monitoring summaries, with human review for material read by an Authorizing Official and full traceability from each statement to a source record.
  • Advance controls whose satisfaction is demonstrated by system state rather than narrative.

Desired Qualifications

  • Active Top Secret clearance with SCI access and SAP eligibility is strongly preferred.
  • Experience with OSCAL, eMASS APIs, Xacta, controls-as-code, or continuous-controls-monitoring implementation.
  • Proficiency in Python, Go, or an equivalent language, and experience with CI/CD, infrastructure-as-code, and Git-based workflows.
  • Experience with continuous authorization, ongoing authorization, or cATO.
  • Experience building with AI-assisted development.
  • Understanding of mission operations, including satellite command and control, mission planning, flight dynamics, telemetry processing, or multi-mission ground segments.
  • Embedded or safety-critical background in space, automotive, or industrial control.
  • Experience with SPARTA, NIST IR 8270 or IR 8401, CCSDS security standards, Space Platform Overlay, NASA/Space Force system protection standards, or space-system threat modeling.
  • Experience with classified cloud accreditation at IL5/IL6 or IC equivalents, or accreditation under JSIG or ICD 703.
  • Qualification, or ability to qualify, under DoDM 8140.03 for a systems security engineering, security architecture, or Information Systems Security Manager work role; CISSP, CISSP-ISSEP, CISM, and SecurityX are relevant.

About the Company

Apex

Manufactures ESPA-class satellites and bus

Apex Space designs and builds ESPA-class satellite buses, with the Aries bus as its flagship platform to support space missions. The Archer bus is configurable to host payloads up to 94 kilograms and a total wet mass of 197 kilograms, usable from LEO through deep space, and customers customize payloads for Earth observation, communications, or scientific research. The company differentiates itself with guaranteed on-time delivery, high reliability, and transparent pricing, while offering flexible payload accommodations to aerospace, defense, and research clients. Its goal is to provide reliable, configurable satellite platforms that make it easier for government, commercial, and research customers to access and execute diverse space missions.

Company size
201-500
Company stage
Late Stage VC
Total funding
$718.5M
Headquarters
Los Angeles, CA
Founded
2020

Recently Posted Jobs

Explore more opportunities at Apex

See more jobs