Senior Information Systems Security Manager (ISSM)
KBR Careers · Beavercreek, OH · 3 wk ago
Information TechnologyFull-time
We need to produce HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the posting.
Title: Senior Information Systems Security Manager (ISSM) Belong. Connect. Grow. with KBR! (but we ignore title heading).
First paragraph: "KBR’s National Security Solutions team provides high-end engineering and advanced technology solutions to our customers in the intelligence and national security communities. In this position, your work will have a profound impact on the country’s most critical role – protecting our national security." That's about the role.
Then "Why Join Us?" with bullet points: Innovative Projects..., Collaborative Environment..., Impactful Work... This could be part of About the role or maybe separate but we can include under About the role.
Then "Position Summary" paragraph: "The Information System Security Manager will provide system authorization support, risk management and business continuity expertise, threat detection and prevention methods, incident response and management methods, auditing, vulnerability management support, and system security documentation for the NIL. This position will be responsible for all NIL activities for the Digital Infrastructure program in ABMS." That's also about role.
Then "Key Responsibilities" list: many bullet points. We'll put under Responsibilities.
Then "Work Environment" with Location, Travel Requirements, Working Hours. That could be under Schedule? Actually location and travel and hours. Could be under Schedule (working hours) and maybe Benefits? Not exactly. The instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map.
- About the role: includes intro, why join us, position summary.
- Responsibilities: key responsibilities list.
- Requirements: maybe qualifications required? The posting has "Qualifications Required:" list. That could be under Requirements or Qualifications. The headings include both Requirements and Qualifications. We need to decide. Usually Requirements = required qualifications. Qualifications = desired? But we have both Required and Desired sections. So we can put Required under Requirements, Desired under Qualifications. Or we could combine. The instruction: "Use
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the posting.
Title: Senior Information Systems Security Manager (ISSM) Belong. Connect. Grow. with KBR! (but we ignore title heading).
First paragraph: "KBR’s National Security Solutions team provides high-end engineering and advanced technology solutions to our customers in the intelligence and national security communities. In this position, your work will have a profound impact on the country’s most critical role – protecting our national security." That's about the role.
Then "Why Join Us?" with bullet points: Innovative Projects..., Collaborative Environment..., Impactful Work... This could be part of About the role or maybe separate but we can include under About the role.
Then "Position Summary" paragraph: "The Information System Security Manager will provide system authorization support, risk management and business continuity expertise, threat detection and prevention methods, incident response and management methods, auditing, vulnerability management support, and system security documentation for the NIL. This position will be responsible for all NIL activities for the Digital Infrastructure program in ABMS." That's also about role.
Then "Key Responsibilities" list: many bullet points. We'll put under Responsibilities.
Then "Work Environment" with Location, Travel Requirements, Working Hours. That could be under Schedule? Actually location and travel and hours. Could be under Schedule (working hours) and maybe Benefits? Not exactly. The instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map.
- About the role: includes intro, why join us, position summary.
- Responsibilities: key responsibilities list.
- Requirements: maybe qualifications required? The posting has "Qualifications Required:" list. That could be under Requirements or Qualifications. The headings include both Requirements and Qualifications. We need to decide. Usually Requirements = required qualifications. Qualifications = desired? But we have both Required and Desired sections. So we can put Required under Requirements, Desired under Qualifications. Or we could combine. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have both Requirements and Qualifications sections.
Thus:
- Requirements: list of required qualifications (BS degree, 9+ years, DoD 8570 IAT/IAM Level I/II cert, understanding of OS, knowledge of client/server/storage/networking, understanding of cloud security requirements, familiarity with DevSecOps and SSDLC, ability to troubleshoot, innovative with strong analytical..., understanding of ABMS Digital Infrastructure program, active TS/SCI clearance, experience with SAPs).
- Qualifications: desired qualifications (Advanced degree, 9+ years of IT/security-related experience with recent ISSM experience, Sec+/CASP/CISSP certification or NIL experience, Software Development in Java, Python, Ruby and/or C++, Linux Expertise (RedHat/RHEL or CentOS preferred), prior experience with software scanning/static code analysis, prior experience with cloud and container security tools).
- Skills: maybe we can extract skills from responsibilities? But we have no explicit skills section. Could we create Skills from required/desired? The instruction says include a section only when posting has real, specific content for it. There's no explicit "Skills" heading. However we could infer skills from responsibilities? But better not to create a Skills section if not explicitly present. The posting does not have a separate Skills section. So we omit Skills.
- Benefits: posting includes "KBR Benefits KBR offers a selection of competitive lifestyle benefits which could include 401K plan with company match, medical, dental, vision, life insurance, AD&D, flexible spending account, disability, paid time off, or flexible work schedule. We support career advancement through professional training and development." That's benefits. So include Benefits.
- Pay: not mentioned. So omit Pay.
- Schedule: we have Working Hours: Standard, Travel Requirements: 35%, Location: Dayton, OH. That's schedule-ish. Could be under Schedule. The posting includes "Working Hours: Standard" and "Travel Requirements: 35%". That's schedule info. So we can include Schedule section with location, travel, hours.
Now we need to format.
We must not include boilerplate like "Belong. Connect. Grow."? That's part of tagline but maybe considered boilerplate? It's part of the intro but not essential. However we can keep it as part of About the role? It's a tagline; but it's not navigation/legal/EEO. It's okay to keep.
We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is "KBR is an equal opportunity employer..." and "R2130583". Those are EEO and Job ID. Remove them.
Also remove "Ready to Make a Difference?..." paragraph? That's a call to action, maybe considered application instructions? It's encouraging to apply. Might be considered boilerplate? The instruction says remove application instructions. That paragraph is encouraging to apply, so we should remove it.
Also remove "Belong, Connect and Grow at KBR" paragraph? That's about culture but maybe considered boilerplate? It's not legal/EEO but it's a generic culture statement. Could be considered part of About the role? It's somewhat generic but still substantive? It's about company values. Might be okay to keep but it's somewhat fluff. However we need to preserve ALL substantive information; do not invent or summarize away detail. This paragraph is substantive about company culture. It's not boilerplate like EEO. So we could keep it under About the role.
But we must also remove duplicated lines. There's "Belong. Connect and Grow." repeated? At start: "Belong. Connect. Grow. with KBR!" and later "Belong, Connect and Grow at KBR". Slight variation. We'll keep both? Might be duplicate. Safer to keep only one instance? The instruction: remove duplicated lines. So we should deduplicate. We'll keep the first tagline maybe.
Now produce HTML.
Structure:
About the role
About the role
... combined paragraphs.
Maybe we need- for lists.
For About the role we can have paragraphs.
Then
Responsibilities
- ... each responsibility.
Requirements
- ... each required qualification.
Qualifications
- ... each desired qualification.
Benefits
- ... each benefit.
Schedule
Location: Dayton, OH. Travel Requirements: 35%. Working Hours: Standard.
We must not include empty sections. Now extract content precisely. About the role content: - "KBR’s National Security Solutions team provides high-end engineering and advanced technology solutions to our customers in the intelligence and national security communities. In this position, your work will have a profound impact on the country’s most critical role – protecting our national security." - "Why Join Us?" bullet points: - Innovative Projects: KBR’s work is at the forefront of engineering, logistics, operations, science, program management, mission IT and cybersecurity solutions. - Collaborative Environment: Be part of a dynamic team that thrives on collaboration and innovation, fostering a supportive and intellectually stimulating workplace. - Impactful Work: Your contributions will be pivotal in designing and optimizing defense systems that ensure national security and shape the future of space defense. - Position Summary: "The Information System Security Manager will provide system authorization support, risk management and business continuity expertise, threat detection and prevention methods, incident response and management methods, auditing, vulnerability management support, and system security documentation for the NIL. This position will be responsible for all NIL activities for the Digital Infrastructure program in ABMS." We can combine into paragraphs. We might keep "Why Join Us?" as a heading? Not allowed; only those headings. So we incorporate into About the role. Now Responsibilities list (Key Responsibilities): List items: 1. Coordinating, executing, and managing cybersecurity assessment & authorization (A&A) related activities supporting IT hardware, software, and connectivity capabilities in support of intelligence data management and analysis requirements 2. Provide advice and assistance on all things cyber security for customer-acquired development and systems maintenance projects, driving and monitoring system authorization status of segment components, authoring and coordinating related documentation 3. Facilitate, perform, and manage actions necessary to maintain system and capability accreditation status consistent with DoDI 8510.01 (Risk Management Framework (RMF) for DoD Information Technology (IT)), including scanning, auditing, and authoring/coordinating security accreditation-related documentation 4. Review and advise on security aspects of contracted maintenance deliverables and proposals 5. Perform requirements analysis, design, and integration for complex software applications and collaboration infrastructures 6. Participate in the change management process, including reviewing Change Requests and assisting in the assessment of security impact of proposed changes 7. Write implementation and design documents describing how security features are implemented 8. Create and maintain information system security documentation, Standard Operating Procedures (SOP), and provide guidance on active Plans of Action and Milestones (POA&M) 9. Present system maintenance, authorization status, and potential issues to various intelligence and acquisition community audiences 10. Keep leadership aware of any roadblocks, issues, or concerns with system authorization status We need to preserve exact wording. Now Requirements (Qualifications Required): List: - BS degree in information systems or related technical field - 9+ years' technical experience in cybersecurity or information technology - DoD 8570 IAT/IAM Level I/II certification - Understanding of common operating systems (Windows, Linux/Unix, Cisco IOS/NX-OS) - Knowledge of client, server, data storage, and networking technologies - Understanding of the requirements and standards for Cloud security - Familiarity with DevSecOps principles and Secure Software Development Lifecycle (SSDLC) - Ability to troubleshoot, assess root cause, and resolve technical issues - Innovative with strong analytical, problem-solving, organization and interpersonal skills - Understanding of ABMS Digital Infrastructure program - An active TS/SCI clearance is required - Must have experience working with Special Access Programs (SAPs) Now Qualifications (Desired): List: - Advanced degree in a technical field - 9+ years of IT/security-related experience with recent ISSM experience - Sec+/CASP/CISSP certification or NIL experience - Software Development in Java, Python, Ruby and/or C++ knowledge - Linux Expertise (RedHat/RHEL or CentOS preferred) knowledge. - Prior experience with software scanning/static code analysis (e.g. Fortify, SonarQube) - Prior experience with cloud and container security tools (e.g. Prisma Cloud/Twistlock, StackRox, Anchore) Note there is a duplicate "knowledge." after Linux Expertise line; we keep as is. Now Benefits: List from "KBR offers a selection of competitive lifestyle benefits which could include 401K plan with company match, medical, dental, vision, life insurance, AD&D, flexible spending account, disability, paid time off, or flexible work schedule. We support career advancement through professional training and development." We can break into items: - 401K plan with company match - medical - dental - vision - life insurance - AD&D - flexible spending account - disability - paid time off - flexible work schedule - professional training and development (career advancement) Now Schedule: - Location: Dayton, OH -