Information System Security Manager (ISSM) (Onsite)
or drop it." So we can include a short p for date posted, location, etc. But we need to preserve all substantive information. The substantive info includes: Position Role Type: Onsite, U.S. Citizen requirement, security clearance needed, etc. Also description of Collins Aerospace, role description, responsibilities, qualifications, preferred qualifications, benefits, pay range. We need to decide sections: About the role (maybe summary), Responsibilities (What You Will Do), Requirements (Qualifications You Must Have), Qualifications (maybe Qualifications We Prefer?), Skills (maybe not separate), Benefits (What We Offer), Pay (salary range), Schedule (maybe not given). There's no explicit schedule info besides onsite. Could include Schedule as Onsite? But schedule not given; we could omit Schedule section if no specific content. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we should not create Schedule if no explicit schedule details. However we have Position Role Type: Onsite. That could be considered schedule? Might be considered work arrangement. But the instruction says use h3 for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. If we have Onsite info, we could put under About the role or maybe a separate section? Probably include under About the role: "Onsite position in Richardson, TX". Or we could add a Schedule section with "Onsite". But the posting does not give hours, just onsite. Might be okay to include Schedule with Onsite. However the instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Position Role Type: Onsite, which is a schedule type. So we can include Schedule with content "Onsite". But we need to ensure not filler. It's specific. We also have Pay: salary range given. So include Pay section. Benefits: detailed list. Now we need to strip out fluff: The long paragraphs about Collins Aerospace mission etc. Might be considered About the role content. We'll keep a concise summary but must preserve ALL substantive information; do NOT invent or summarize away detail. That means we cannot omit details; we must keep all substantive info. However we can rephrase? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Summarizing away detail is not allowed. So we need to keep the details, but we can format them. We cannot remove any substantive info. That means we need to keep all sentences that convey info about the role, responsibilities, qualifications, etc. We can't drop any of those details. However we can remove boilerplate like "Learn More & Apply Now!" etc. Also remove duplicated lines. Also remove EEO etc. Thus we need to keep the descriptive text about Collins Aerospace, the role description, responsibilities, qualifications, preferred qualifications, benefits, pay, etc. We'll need to include them in appropriate sections. We must not repeat the job title as a heading. The job title is "Information System Security Manager (ISSM)". We'll not use that as heading. We'll produce something like:
Date Posted: 2026-09-28
Location: Richardson, TX (US-TX-RICHARDSON-461 ~ 3200 E Renner Rd ~ RENNER BLDG 461)
Position Role Type: Onsite
U.S. Citizenship required; Active Secret security clearance required after day 1.
Then sections:About the role
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. Our team in Richardson, Texas is seeking an Information System Security Manager (ISSM). The Information Systems Security Manager is responsible for compliance oversight, assessment, and operations of systems under their purview. They may be assigned to a single large-scale program or oversee multiple programs. Must have knowledge regarding National Industrial Security Operating Manual (NISPOM) and related documentation such as: Baseline Technical Security Configuration Standards, Defense Counter-Intelligence Security Agency (DCSA) Assessment and Authorization Process Manual (DAAPM), Customer/contract specific Cybersecurity regulations, Joint Special Access Program Implementation Guide (JSIG). This is an onsite position in Richardson, TX.
But note we already mentioned onsite in metadata; we can still include. Responsibilities: from "What You Will Do:" list. We need to convert bullet list into- . The text includes sentences separated by periods. We'll need to parse them into list items. Let's extract: - ISSMs are required to maintain IAM Level III certification commensurate with their role as required by DoDD 8140 (8570). - Complete all DCSA and Collins Aerospace required training within 6 months of appointment (annual requirements thereafter). - Accountability for all systems under their assigned purview. - Maintaining a working knowledge of all CIS functions, security policies, technical security safeguards, and operational security measures. - Interactions with DCSA SCA/ISSP to track items including, but not limited to, upcoming authorizations (ATO), new technologies solutions (i.e., new SIEM, OS, etc.), policy interpretations (in conjunction with Site ISSM), and onsite A&A. - Developing, maintaining, and updating, in coordination with all system stakeholders (CS Manager, ISO, DT, etc.), applicable site POAM(s) to identify system weaknesses, mitigating actions, resources, and timelines for corrective actions. - Coordinating DCSA SVA preparation activities for assigned CAGE in conjunction with Site ISSM. We'll put each as
- .
Requirements: "Qualifications You Must Have:" list. We need to keep all details. The text is a paragraph with multiple sentences separated by periods. We'll need to break into list items? The instruction: Use
- for any list of duties/requirements/benefits. So we should treat each distinct requirement as a list item. Let's parse:
- Typically requires a University Degree and minimum of 10 years prior relevant experience or an Advanced Degree in a related field and minimum 7 years of experience
- U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance.
- Experience supporting cybersecurity compliance as stipulated by DCSA Assessment and Authorization Guide (DAAG), Joint SAP Implementation Guide (JSIG), and/or National Industrial Security Program Operating Manual (NISPOM) regulations
- Past direct leadership or project/program management experience
- IAM Level III certification (CISSP, CISM or other)
- Cybersecurity, systems security or hardening
- Compliance-based auditing using the Risk Management Framework (RMF) and/or non-defense regulations such as FAA, Payment Card Industry (PCI), ISO 9001 Quality Management standards, or HIPPA
- Experience working with and/or supporting computer technologies (such as: databases, operating systems, computer network hardware, software programs, hardware troubleshooting or electronics)
- Physical security/security, policework/criminal justice, investigations, or Border Patrol
- Project or program management, office management, senior administration, or account management
Note some items are combined; we can keep as separate bullet points as above.
Qualifications We Prefer: list.
- Master’s degree in computer science, Information Systems, Information Technology, Cyber Security, Criminal Justice, Business or other relevant degrees
- Experience with various information system security tools that address vulnerability analysis and mitigation. These may include Splunk, Forcepoint, Ivanti, Tenable, ACAS, HBSS, etc.
- Experience in the oversight and execution of the Assessment & Authorization processes (Certification & Accreditation), as defined in JSIG/RMF
- Experience in the execution and management of Information System’s (IS) incident response and administrative inquiries/investigations in collaboration with the Investigations department
We could put these under a section "Qualifications" (maybe split into Required and Preferred). But we have only one h3 for Qualifications. Could we have two subsections? Not allowed; only h3 headings. We could combine Required and Preferred under Qualifications with maybe separate paragraphs. But we need to preserve all info. We'll do:
Qualifications
Required:
- ...
Preferred:
- ...
- . Pay: salary range: "The salary range for this role is 107,500 USD - 204,500 USD. The salary range provided is a good faith estimate representative of all experience levels." We'll keep that as
. Schedule: we have Position Role Type: Onsite. We'll put
Schedule
Onsite
. We also need to include metadata like date posted, location, citizenship, clearance. We'll put those in a shortat top. We must not include boilerplate like "Learn More & Apply Now!", "Do you want to be a part...", "Please consider the following role type definitions...", "As part of our commitment...", "RTX is an Equal Opportunity Employer...", "Privacy Policy and Terms...". Also remove duplicated lines: there may be duplicate sentences about U.S. citizenship etc. We'll keep only one. Now produce HTML fragment. Check that we didn't miss any substantive info: The description of Collins Aerospace, role responsibilities, qualifications, preferred qualifications, benefits, pay, schedule (onsite). Also the requirement to maintain IAM Level III certification etc. Already in responsibilities. Also note: "Must have knowledge regarding National Industrial Security
- . Pay: salary range: "The salary range for this role is 107,500 USD - 204,500 USD. The salary range provided is a good faith estimate representative of all experience levels." We'll keep that as
- for any list of duties/requirements/benefits. So we should treat each distinct requirement as a list item. Let's parse:
- Typically requires a University Degree and minimum of 10 years prior relevant experience or an Advanced Degree in a related field and minimum 7 years of experience
- U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance.
- Experience supporting cybersecurity compliance as stipulated by DCSA Assessment and Authorization Guide (DAAG), Joint SAP Implementation Guide (JSIG), and/or National Industrial Security Program Operating Manual (NISPOM) regulations
- Past direct leadership or project/program management experience
- IAM Level III certification (CISSP, CISM or other)
- Cybersecurity, systems security or hardening
- Compliance-based auditing using the Risk Management Framework (RMF) and/or non-defense regulations such as FAA, Payment Card Industry (PCI), ISO 9001 Quality Management standards, or HIPPA
- Experience working with and/or supporting computer technologies (such as: databases, operating systems, computer network hardware, software programs, hardware troubleshooting or electronics)
- Physical security/security, policework/criminal justice, investigations, or Border Patrol
- Project or program management, office management, senior administration, or account management
Note some items are combined; we can keep as separate bullet points as above.
Qualifications We Prefer: list.
- Master’s degree in computer science, Information Systems, Information Technology, Cyber Security, Criminal Justice, Business or other relevant degrees
- Experience with various information system security tools that address vulnerability analysis and mitigation. These may include Splunk, Forcepoint, Ivanti, Tenable, ACAS, HBSS, etc.
- Experience in the oversight and execution of the Assessment & Authorization processes (Certification & Accreditation), as defined in JSIG/RMF
- Experience in the execution and management of Information System’s (IS) incident response and administrative inquiries/investigations in collaboration with the Investigations department
We could put these under a section "Qualifications" (maybe split into Required and Preferred). But we have only one h3 for Qualifications. Could we have two subsections? Not allowed; only h3 headings. We could combine Required and Preferred under Qualifications with maybe separate paragraphs. But we need to preserve all info. We'll do: