Information Systems Security Officer (ISSO) (Onsite)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must remove boilerplate: date posted, country, location, position role type, etc. Also remove navigation, legal, EEO, etc. Keep substantive info: description of role, responsibilities, qualifications, preferred qualifications, benefits, pay range. We need to preserve all substantive info, not invent or summarize away detail. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading (the page already shows it). No Job ID/requisition numbers as headings. We need to decide sections: About the role (maybe intro paragraph about RTX/Collins). Responsibilities (list of duties). Requirements (mandatory qualifications). Qualifications (maybe split into Required and Preferred? The instructions say use headings like Qualifications, Skills, Benefits, Pay, Schedule. Could combine required qualifications under "Requirements" and preferred under "Qualifications" or "Skills". But we need to follow instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Possibly Skills if we have skill list. We must not create sections with filler like "not specified". So only include if content. Let's extract content: About the role: The paragraph starting "At RTX, the world's largest aerospace and defense company..." and "Collins Aerospace is a leader..." and "Join us and help shape the future..." and "This is onsite position in Cedar Rapids, IA". Also later paragraphs about mission etc. We'll combine into About the role. Responsibilities: The bullet list under "What YOU will do:" includes many items. Need to capture each as

• . Also later "Experience collaborating with IT or engineering teams to support investigation and remediation activities." appears as part of responsibilities? It's after the list but seems like a responsibility. We'll include it. Requirements: Mandatory qualifications: "Typically requires a University Degree and minimum 2 years of prior relevant experience or an Advanced Degree." "U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance." "Active DoD Secret Security Clearance required on day one." "IAM Level I certification compliant with DoD 8570 / DoD 8140 (e.g., Security+, GSEC, GSLC)." "Experience performing cybersecurity monitoring, detection, and analysis activities in an enterprise or DoD environment." "Working knowledge of cybersecurity principles, including network security, system logging, access controls, and incident detection." "Experience analyzing security alerts, logs, and network traffic to identify anomalous or malicious activity." "Ability to document findings, audit results, and response actions according to established procedures." "Familiarity with cybersecurity tools such as SIEMs (Splunk preferred), IDS/IPS, endpoint protection, vulnerability scanning, and network monitoring platforms." "Ability to follow established incident response, escalation, and continuous monitoring procedures." "Willingness to work collaboratively in a team-based cybersecurity operations environment" Also "U.S. Citizen, U.S. Person, or Immigration Status Requirements: Active and transferable U.S. government issued security clearance is required prior to start date. U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance Security Clearance Type: DoD Clearance: Secret Security Clearance Status: Active and existing security clearance required on day 1". This is similar. We'll combine. Qualifications (Preferred): The "Qualifications We Prefer:" list. Skills: Could be derived from both required and preferred but maybe we treat skills as separate? The instruction says we can use Skills heading if we have skill list. Could list technical skills: SIEM (Splunk), IDS/IPS, endpoint protection, vulnerability scanning, network monitoring, network protocols, etc. But we might just put them under Qualifications or Skills. To avoid duplication, maybe put required under Requirements, preferred under Qualifications, and skills under Skills (maybe combine both). However we must not create thin sections. Let's see if we have enough for Skills: we have familiarity with tools, network protocols, etc. Could be a separate Skills section. Benefits: The "What We Offer:" list includes many items. We'll capture as
  • . Pay: The salary range: "The salary range for this role is 68,900 USD - 131,100 USD." Also mention that it's a good faith estimate. We'll include that. Schedule: Not mentioned besides onsite. No schedule details like full-time, shift. So we should not create Schedule section. Now we need to output only HTML fragment, no /, no markdown fences. We'll structure:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Requirements

    • ...
    ...

    Qualifications

    • ...
    ...

    Skills

    • ...
    ...

    Benefits

    • ...
    ...

    Pay

    The salary range for this role is 68,900 USD - 131,100 USD. The salary range provided is a good faith estimate representative of all experience levels.

    We need to ensure we don't include boilerplate like "Learn More & Apply Now!", "Do you want to be a part of something bigger?" etc. Those are promotional but maybe considered substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The motivational paragraphs might be considered application instructions? They are more like marketing. Safer to remove them. Keep only the core description. Thus About the role: include the RTX description and Collins Aerospace description and the onsite location sentence. Also maybe the later mission paragraph? That seems promotional. Might be considered boilerplate? It's describing the team mission. Could keep as part of About the role? It's not boilerplate but it's still marketing. The instruction says remove application instructions, not necessarily marketing. However to be safe, we could keep the initial RTX and Collins description and the onsite line. The later paragraphs about mission, "Are you up for the challenge?" etc are likely application encouragement; better to remove. Thus About the role paragraph: "At RTX, the world's largest aerospace and defense company, 185,000 great minds are united by purpose and inspired to make a difference solving the world’s most complex problems. With our three market leading businesses, world-class operations and investments in research and development, we offer capabilities and opportunity no one else can. Together, we push the boundaries of known science and find new ways to connect and protect our world. Collins Aerospace is a leader in technologically advanced, intelligent solutions that help redefine the aerospace and defense industry. With a comprehensive portfolio and deep technical expertise, we help customers meet the demands of the global market. Join us and help shape the future of aerospace and defense. This is an onsite position in Cedar Rapids, IA." We need to preserve all substantive information; we removed some motivational fluff but kept core. Now Responsibilities list: Let's extract each bullet from "What YOU will do:": - Support cybersecurity implementation and maintenance for assigned information systems under the guidance of the ISSM or senior ISSOs. - Process and review data transfer requests, ensuring security controls are applied and authorization requirements are met. - Assist with user account and access requests, verifying approvals and adherence to role-based access control policies. - Execute continuous monitoring activities, including reviewing security logs, validating security controls, and identifying anomalies. - Conduct system auditing and log reviews to detect policy violations, compliance issues, or potential security events. - Develop, maintain, and update cybersecurity documentation, security plans, and authorization artifacts to support audit-ready operations. - Track and assist in closure of Plans of Action and Milestones (POA&Ms) resulting from audits, assessments, or monitoring activities. - Report identified security issues, audit findings, or system anomalies to the ISSM or senior cybersecurity personnel. - Collaborate with cross-functional teams (IT, Facilities, Industrial Security) to ensure cybersecurity requirements are applied consistently. - Support preparation for inspections, audits, and assessments by providing required documentation, evidence, and operational insight. - Experience collaborating with IT or engineering teams to support investigation and remediation activities. Note: The last one seems like a qualification but it's phrased as experience; we can keep as responsibility. Now Requirements list: Let's list each distinct requirement: - Typically requires a University Degree and minimum 2 years of prior relevant experience or an Advanced Degree. - U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance. - Active DoD Secret Security Clearance required on day one. - IAM Level I certification compliant with DoD 8570 / DoD 8140 (e.g., Security+, GSEC, GSLC). - Experience performing cybersecurity monitoring, detection, and analysis activities in an enterprise or DoD environment. - Working knowledge of cybersecurity principles, including network security, system logging, access controls, and incident detection. - Experience analyzing security alerts, logs, and network traffic to identify anomalous or malicious activity. - Ability to document findings, audit results, and response actions according to established procedures. - Familiarity with cybersecurity tools such as SIEMs (Splunk preferred), IDS/IPS, endpoint protection, vulnerability scanning, and network monitoring platforms. - Ability to follow established incident response, escalation, and continuous monitoring procedures. - Willingness to work collaboratively in a team-based cybersecurity operations environment. Also maybe "Active and transferable U.S. government issued security clearance is required prior to start date." Already covered by active DoD Secret clearance. Now Qualifications (Preferred) list: - Hands-on experience with SIEM platforms such as Splunk for log analysis, alert triage, and event correlation. - Exposure to vulnerability scanning tools and review of findings, with basic remediation knowledge. - Familiarity with DoD or other regulated environments, including RMF, NIST, JSIG, NISPOM, or DAAG guidance. - Experience supporting inspection, assessment, or audit readiness activities. - Working knowledge of network protocols, architectures, and common attack techniques. - Ability to identify trends or recurring issues in security events and communicate findings to senior analysts. - Experience collaborating with IT, Facilities, or Industrial Security teams to apply cybersecurity requirements consistently. Now Skills: Could list technical skills derived from both required and preferred: SIEM (Splunk), IDS/IPS, endpoint protection, vulnerability scanning, network monitoring platforms, network protocols, etc. But we might avoid duplication. Perhaps we can put skills under Qualifications and not have separate Skills. However the instruction allows Skills heading; we could create a Skills section listing: SIEM (Splunk), IDS/IPS, endpoint protection, vulnerability scanning, network monitoring, network protocols, etc. But we need to ensure we don't repeat content already in Requirements/Qualifications. It's okay to repeat? The instruction says preserve ALL substantive information; repeating is okay as long as we don't lose info. But better to avoid duplication to keep concise. However we could keep Skills as a summary of technical proficiencies not covered elsewhere. But many are covered. Given the instruction to prefer a few substantive sections over many thin ones, maybe we combine Required and Preferred into Qualifications, and have Skills separate for technical tools. Let's think. We have Requirements (mandatory) and Qualifications (preferred). That's two sections. Skills could be separate but might be thin. However we have a decent list of skills: SIEM