Information Systems Security Manager

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO etc. The posting includes: intro paragraph about SOSi, role description. Then "Essential Job Duties:" list. Then "Qualifications" with Minimum Requirements and Preferred Qualifications. Then "Additional Information" with Work Environment and Working at SOSi (EEO statement). We need to map to sections. We need to decide which sections to include: About the role (intro). Responsibilities (Essential Job Duties). Requirements (maybe Minimum Requirements). Qualifications (maybe Preferred Qualifications? Actually they have both Minimum Requirements and Preferred Qualifications; could combine under Requirements? But we have separate sections: Requirements, Qualifications, Skills. We need to follow instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we must decide which to include based on content. We have content for About the role (intro). Responsibilities (Essential Job Duties). Requirements (Minimum Requirements). Qualifications (Preferred Qualifications). Skills maybe could be extracted from qualifications (e.g., strong communication skills, knowledge of tools). Could put under Skills. Benefits: not mentioned except maybe "Working at SOSi: All interested individuals will receive consideration..." that's EEO, not benefits. No explicit benefits, pay, schedule. So we should NOT include Benefits, Pay, Schedule sections because no specific content. Also we should not include empty headings. Thus output sections: About the role, Responsibilities, Requirements, Qualifications, Skills (maybe). But we need to see if Skills section has content: we have "Strong communication skills and ability to coordinate tasks across functional groups." Also "Practical knowledge of JIRA and Confluence." "Experience with compliance tools such as Tenable Nessus and SCAP." Those could be skills. So we can create Skills section. We must preserve all substantive info; do not invent or summarize away detail. Must not omit any substantive info. So we need to include all details from the posting: intro paragraph, essential duties list, minimum requirements list, preferred qualifications list, work environment info (maybe under About the role or a separate section? There's no heading for Work Environment but we could include under About the role or maybe under Additional Information? But we only allowed headings list; we could put work environment under About the role as a paragraph. Or we could create a separate section like "Working Conditions" but not allowed. So we fold into About the role or Responsibilities? Probably About the role can include the work environment description. We must not include EEO statement (Working at SOSi: All interested individuals will receive consideration...). That's boilerplate; remove. Also remove duplicated lines. Now craft HTML. Structure:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Skills

• ...
...

Make sure to preserve all details. Let's extract details. Intro paragraph: "🚀 Join SOSi at the Forefront of Cyber Defense! SOSi is on the hunt for a seasoned Information Systems Security Manager to lead cutting-edge security initiatives at Joint Base Pearl Harbor Hickam in Honolulu. In this pivotal role, you’ll architect and maintain robust cybersecurity frameworks that safeguard DoD networks and systems. Collaborate with a dynamic mix of customers, partners, and stakeholders to implement mission-critical security protocols that keep our nation's digital infrastructure secure.Ready to make an impact where it matters most? Let’s build the future of defense technology—securely." We need to keep that but maybe remove the rocket emoji? It's part of text; we can keep but it's not substantive? It's okay. We'll keep as is. Now Essential Job Duties list (each sentence starts with a verb). Let's list them: - Assist the Cyber Security Compliance Team Lead in formulating and upholding an organized information system security program and policies that are applicable to their assigned area of responsibility. - Establish and maintain secure computer systems and networks for classified processing, and take responsibility for the administration, maintenance, and security auditing of such systems. - Develop and supervise the implementation of guidelines and policies for operational information systems security. - Manage assigned eMASS (Enterprise Mission Assurance Support Service) packages containing all security authorizations for information systems under their supervision. - Coordinate inspections, tests, and reviews of information system security. - As a key member of the team, you will be responsible for contributing your expertise and skills to help ensure the team's success in responding to security incidents and protecting organizational assets. - Practical understanding of the Assured Compliance Assessment Solution (ACAS) to support the execution of the information system patch and vulnerability management program. - Thorough understanding of Security Technical Implementation Guidelines (STIG) and ensure they are reviewed, maintained, and updated on a quarterly basis. - Ensure compliance with Configuration Management policies and procedures for authorizing the use of hardware and software on an information system. - Engage with external stakeholders to facilitate the coordination of interconnection requests and ensure that such requests are processed and approved in an efficient manner. - Maintain current knowledge of system functions, security policies, technical security safeguards, and operational security measures. - Manage, maintain, and execute the information security continuous monitoring plan. - Keep records of all security-related vulnerabilities POA&Ms and ensure that serious or unresolved violations are reported to the AO/DAO. - Evaluate any changes to the system, its environment, and operational requirements that could impact security authorization. Now Minimum Requirements (under Qualifications heading but we will put under Requirements): - An Active in-scope SECRET clearance. - Compliant with DoD 8140 DCWF 722 Advanced, Information Systems Security Manager. - Masters or PH.D in Computer Science, Cybersecurity, Data Science, Information Systems, Information Technology, or Software Engineering // OR // CISM, CISSP, CISSP-ISSMP, FITSP-M, GCIA, GCIH, GICSP, or GSLC. - Ten (10) years of experience supporting cybersecurity, information assurance, systems engineering, or RMF-related activities. - Knowledge of NSA’s Commercial Solution for Classified (CSfC) solution and Cross Domain Solutions (CDS). - Thorough understanding of NIST Publication 800-53r5, Risk Management Framework, Executive Order 14028, and OMB Mandate M-22-09. - Prior experience with eMASS. - Strong communication skills and ability to coordinate tasks across functional groups. Now Preferred Qualifications: - An Active in-scope TOP SECRET clearance with SCI Eligibility. - Recent experience in the assessment and authorization of systems. - Practical knowledge of JIRA and Confluence. - Experience with compliance tools such as Tenable Nessus and SCAP. - Experience in program policy and process creation and oversight. Now Work Environment (under Additional Information): - Working conditions are normal for an office environment. - Fast paced, deadline-oriented environment. - May require periods of non-traditional working hours including consecutive nights or weekends. We could include this under About the role or maybe a separate section but not allowed headings. We'll add a paragraph under About the role after the intro. Now Skills section: we can pull from Minimum Requirements and Preferred Qualifications that are skill-like: Strong communication skills, ability to coordinate tasks across functional groups, practical knowledge of JIRA and Confluence, experience with compliance tools such as Tenable Nessus and SCAP, experience in program policy and process creation and oversight. Also maybe knowledge of NSA CSfC, CDS, NIST 800-53r5, RMF, EO 14028, OMB M-22-09, eMASS, ACAS, STIG, Configuration Management, etc. But those are more knowledge requirements. Could still be skills. However we already have Requirements and Qualifications sections covering those. To avoid duplication, we should not repeat same content in multiple sections. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication but better to avoid redundancy. We can assign each piece to appropriate section: Requirements (minimum), Qualifications (preferred), Skills (specific abilities like communication, coordination, JIRA/Confluence, Tenable Nessus/SCAP, program policy creation). However some items like "Strong communication skills and ability to coordinate tasks across functional groups" appear in Minimum Requirements; we could move that to Skills and remove from Requirements to avoid duplication. But then we would be omitting it from Requirements, which would lose substantive info if we don't include elsewhere. We'll include it in Skills and not duplicate in Requirements. Similarly, "Practical knowledge of JIRA and Confluence" and "Experience with compliance tools such as Tenable Nessus and SCAP" and "Experience in program policy and process creation and oversight" are in Preferred Qualifications; we could move them to Skills and not duplicate in Qualifications. But then Qualifications would be left with only clearance, education/certifications, years experience, knowledge of NSA CSfC/CDS, NIST 800-53r5, RMF, EO 14028, OMB M-22-09, prior experience with eMASS. That's still substantive. Thus we need to decide: Keep Requirements as minimum requirements (excluding communication skill etc). Keep Qualifications as preferred qualifications (excluding the skill-like items). Keep Skills as the skill items. Let's list: Requirements (Minimum Requirements): - Active in-scope SECRET clearance. - Compliant with DoD 8140 DCWF 722 Advanced, Information Systems Security Manager. - Masters or PH.D in Computer Science, Cybersecurity, Data Science, Information Systems, Information Technology, or Software Engineering OR CISM, CISSP, CISSP-ISSMP, FITSP-M, GCIA, GCIH, GICSP, or GSLC. - Ten (10) years of experience supporting cybersecurity, information assurance, systems engineering, or RMF-related activities. - Knowledge of NSA’s Commercial Solution for Classified (CSfC) solution and Cross Domain Solutions (CDS). - Thorough understanding of NIST Publication 800-53r5, Risk Management Framework, Executive Order 14028, and OMB Mandate M-22-09. - Prior experience with eMASS. Qualifications (Preferred Qualifications): - Active in-scope TOP SECRET clearance with SCI Eligibility. - Recent experience in the assessment and authorization of systems. Skills: - Strong communication skills and ability to coordinate tasks across functional groups. - Practical knowledge of JIRA and Confluence. - Experience with compliance tools such as Tenable Nessus and SCAP. - Experience in program policy and process creation and oversight. Now we need to ensure we didn't lose any substantive info: we omitted "Masters or PH.D in Computer Science, Cybersecurity, Data Science, Information Systems, Information Technology, or Software Engineering // OR // CISM, CISSP, CISSP-ISSMP, FITSP-M, GCIA, GCIH, GICSP, or GSLC." That's in Requirements. Good. We omitted "Prior experience with eMASS." That's in Requirements. We omitted "Knowledge of NSA’s Commercial Solution for Classified (CSfC) solution and Cross Domain Solutions (CDS)." That's in Requirements. We omitted "Thorough understanding of NIST Publication 800-53r5, Risk Management Framework, Executive Order 14028, and OMB Mandate M-22-09." That's in Requirements