Senior Aerospace Cybersecurity Architect

We need to output HTML fragment with sections: About the role? The posting includes a description before responsibilities. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We have content for About the role (the description before responsibilities). Responsibilities (list). Required Qualifications and Preferred Qualifications maybe under Requirements/Qualifications. The posting includes "Required Qualifications" and "Preferred Qualifications". We can combine into a Qualifications section with sublists? But we must use

• for any list of duties/requirements/benefits. So we can have a

  Qualifications

  with
  containing both required and preferred? Might be better to separate Required and Preferred as separate sections? The allowed headings list includes Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could use Qualifications for both required and preferred. Or we could use Requirements for required qualifications and Qualifications for preferred? But we must not invent sections with filler. We have content for both required and preferred, so we can include a Qualifications section with two sub-lists? However we must not create extra headings beyond allowed. Could embed paragraphs describing required and preferred within the Qualifications section using

  and

  . That's acceptable. We also have Pay Range And Compensation Package: includes base salary range and benefits. So we need Pay section (maybe also Benefits). The posting mentions benefits: health coverage, flexible PTO, friendly work environment, extra fun perks. So we can have Benefits section with those items. Pay section with salary range. Schedule: Not mentioned. So omit Schedule. Skills: Not explicitly listed; maybe we could infer but we should not invent. So omit Skills. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate: EEO statement, physical requirements? Physical requirements is substantive? It's part of posting but maybe considered boilerplate? It's not EEO/legal but it's about physical demands. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Physical requirements might be considered part of job description; not explicitly excluded. However it's fairly detailed; we could include it under About the role or a separate section? Not in allowed headings. Could embed in About the role as a paragraph. But we must preserve all substantive information; we could include it in About the role paragraph. We also have "Physical Requirements" section; we could incorporate into About the role as a paragraph. We also have "EEO Statement" which must be removed. We also have "Physical Requirements" details; we keep. We also have "While performing the responsibilities..." etc. Keep. Now craft HTML. Structure:

  About the role

  At ICEYE, we design, build and operate the largest fleet of Synthetic Aperture Radar (SAR) satellites in the world. Using advanced technology, our constellation collects topographical data about any location on Earth, day or night, through any weather conditions. Headquartered in Southern California, our customers are society’s heroes – intelligence professionals, warfighters, first responders, and scientific researchers. As a trusted mission partner, the United States and its allies depend on us for critical information when it matters most. The Aerospace Cybersecurity Architect is responsible for defining and advancing the security architecture for ICEYE US satellites, ground infrastructure, mission systems, communications, and supporting technologies throughout their lifecycle. This role serves as the primary cybersecurity architecture partner to aerospace software architecture, satellite operations, mission architecture, and engineering teams, ensuring cybersecurity requirements and security-by-design principles are incorporated into system and mission design from inception through operations. The Aerospace Cybersecurity Architect evaluates cyber risk across space, ground, communications, embedded, cloud, and operational technology environments and develops scalable, risk-informed architecture solutions to mitigate identified threats and vulnerabilities. The role provides technical cybersecurity guidance for system interfaces, trust boundaries, data flows, communications pathways, and mission-critical components while ensuring alignment with applicable customer, contractual, regulatory, and cybersecurity requirements. This position is critical to protecting ICEYE US mission capabilities and establishing resilient security architectures capable of supporting evolving operational and national security requirements.

  Then Responsibilities:

  Responsibilities

  • Define, design, and maintain cybersecurity architectures for satellites, ground stations, mission systems, communications infrastructure, and supporting aerospace technologies.
  • Establish cybersecurity architecture principles, security patterns, technical requirements, and design standards for aerospace and mission environments.
  • Integrate cybersecurity requirements and security-by-design principles into system architecture, software development, DevSecOps, satellite operations, and mission design processes.
  • Perform architecture-level cybersecurity risk assessments, threat modeling, attack-surface analysis, and security design reviews for aerospace and mission systems.
  • Analyze system trust boundaries, interfaces, data flows, communications pathways, authentication mechanisms, and dependencies to identify cybersecurity risks and architecture weaknesses.
  • Identify and assess vulnerabilities affecting embedded systems, operational technology (OT), communications systems, ground infrastructure, mission applications, and supporting cloud environments.
  • Develop architecture-level security controls and mitigation strategies for new aerospace technologies, systems, interfaces, communications pathways, and mission capabilities.
  • Conduct and support technical security assessments, vulnerability assessments, penetration testing, architecture validation, and security testing of aerospace and mission systems.
  • Serve as the cybersecurity architecture partner to software architecture, satellite operations, IT, DevOps, engineering, and cybersecurity teams throughout system design and implementation.
  • Evaluate cybersecurity risks associated with APIs, external interconnections, third-party integrations, supply chain components, hardware, software, and supporting technologies.
  • Define and review security requirements for identity, authentication, authorization, encryption, key management, network segmentation, secure communications, logging, monitoring, and system resiliency.
  • Support implementation and technical validation of cybersecurity controls required by NIST, CMMC, RMF, customer security requirements, and applicable contractual obligations.
  • Develop and maintain security architecture documentation, system diagrams, trust-boundary diagrams, data-flow diagrams, threat models, technical risk assessments, and security design decisions.
  • Provide architecture-level recommendations for remediation of identified security deficiencies and ensure corrective actions align with the broader system and mission architecture.
  • Support cybersecurity incident investigations involving corporate, aerospace, mission, ground, or supporting systems and incorporate lessons learned into future architecture and security design improvements.
  Qualifications: combine required and preferred. We could have a paragraph describing required qualifications then a list? But we must use
  • for any list of duties/requirements/benefits. So we can put required qualifications as a list, and preferred as another list. Thus:

    Qualifications

    Required

    but we cannot use h4 because only allowed headings are h3 for section headings. We cannot add other headings. So we need to embed required and preferred within the Qualifications section using paragraphs and lists without extra headings. Perhaps we can have a

    Required qualifications:

    then
    list. Then

    Preferred qualifications:

    then
    list. That's okay; we are not adding extra section headings, just paragraphs inside the Qualifications section. Thus:

    Qualifications

    Required qualifications:

    • Bachelor's degree in Cybersecurity, Computer Science, Computer Engineering, Electrical Engineering, Aerospace Engineering, Systems Engineering, or a related technical discipline, or equivalent relevant professional experience.
    • 5+ years of professional experience supporting aerospace, satellite, spacecraft, mission, or other complex aerospace engineering systems.
    • 4+ years of experience in cybersecurity architecture, security engineering, systems security engineering, or a related technical cybersecurity discipline.
    • Experience developing or reviewing security architectures for complex distributed systems, embedded platforms, cloud environments, operational technology, or mission-critical systems.
    • Experience performing cybersecurity risk assessments, threat modeling, architecture reviews, vulnerability assessments, or security testing of technical systems.
    • Working knowledge of cybersecurity frameworks and requirements such as NIST SP 800-171, NIST SP 800-53, NIST Risk Management Framework (RMF), CMMC, or comparable security requirements.
    • Experience integrating cybersecurity requirements into system architecture, software development, cloud environments, DevSecOps, embedded systems, infrastructure, or engineering lifecycle processes.
    • Ability to analyze complex technical architectures, interfaces, trust boundaries, data flows, communications pathways, and security controls and translate identified risks into actionable architecture and engineering requirements.
    • Ability to communicate technical cybersecurity risk and architecture recommendations to engineering, cybersecurity, program, and mission stakeholders.
    • Current U.S. Government security clearance or eligibility to obtain and maintain the level of clearance required for the position.

    Preferred qualifications:

    • Experience designing or securing satellite, spacecraft, ground station, ground-segment, command-and-control, or mission-critical aerospace systems.
    • Knowledge of satellite communications, spacecraft command and control, telemetry, tracking and control, ground-segment architecture, or space-to-ground communications.
    • Experience with embedded systems, real-time operating systems, operational technology (OT), hardware security, or specialized aerospace engineering platforms.
    • Experience developing threat models for distributed, mission-critical, embedded, or cyber-physical systems.
    • Experience conducting or supporting penetration testing and security assessments of embedded systems, hardware, wireless technologies, RF communications, or mission systems.
    • Familiarity with secure systems engineering methodologies, systems engineering lifecycle processes, secure-by-design principles, and systems development lifecycle methodologies.
    • Experience supporting U.S. Government, Department of Defense, Intelligence Community, National Reconnaissance Office, or other national security programs.
    • Experience designing and evaluating cloud security architectures within AWS or Microsoft Azure environments.
    • Familiarity with Zero Trust architecture, identity-centric security, network segmentation, cryptographic protections, secure communications, key management, and resilient system design.
    • Familiarity with secure software development, CI/CD, infrastructure-as-code, containers, APIs, microservices, and DevSecOps practices.
    • Experience evaluating cybersecurity implications of third-party technologies, software supply chains, hardware components, APIs, and external system interconnections.
    • Relevant cybersecurity or security architecture certification such as CISSP, ISSAP, CCSP, CSSLP, SABSA, Security+, OSCP, or equivalent.
    Benefits: we have health coverage, flexible PTO, friendly work environment, extra fun perks. Also maybe other benefits? The posting says "Other benefits include health coverage, flexible PTO, a friendly work environment, plus extra fun perks!" So we list those. Thus:

    Benefits

    • Health coverage
    • Flexible PTO
    • Friendly work environment
    • Extra fun perks
    Pay: base salary range $155,000 - $175,000 depending on experience. Thus:

    Pay

    The estimated base salary range for this role is $155,000 - $175,000 depending on experience.

    We should not include Schedule. Now ensure we didn't repeat job title as heading. We didn't. We removed EEO statement, physical requirements? We kept physical requirements? Actually we omitted physical requirements entirely. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.