Information System Security Officer

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

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We must not include Job ID etc. We must include sections only when posting has real specific content. We need to parse the posting. Content: - Intro paragraph: "Join the Cyber Team in Paradise 🌴 SOSi is looking for a seasoned Information Systems Security Officer (ISSO) ready to lead the charge in securing mission-critical IT operations at Joint Base Pearl Harbor Hickam, Honolulu. As part of a dynamic team supporting over 5,000 users across the Pacific theater, you’ll be at the forefront of solving complex technical challenges that drive real-time Command and Control (C2) strategies. This isn’t just a job — it’s a mission. You’ll own the full Risk Management Framework (RMF) lifecycle, from identifying vulnerabilities to engineering resilient security controls. If you're fluent in DoD protocols, thrive in high-stakes environments, and can deliver executive-level insights with clarity and precision, this is your opportunity to make a strategic impact where it matters most." That's about the role. So we can have

About the role

then a

with that paragraph. - Essential Job Duties: list of duties. That's responsibilities. So

Responsibilities

then

• each duty. List items: - Assist the ISSM (Information System Security Manager) 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. That's many items. We'll list them. - Qualifications: Minimum Requirements and Preferred Qualifications. Could be under Requirements or Qualifications. The instruction says we can have sections like Requirements, Qualifications, Skills. We need to decide. Probably "Qualifications" section includes both minimum and preferred. Could split into Requirements (minimum) and Preferred Qualifications. But we should avoid thin sections. Maybe combine into one Qualifications section with subheadings? But we only allowed

  for section headings, not

  . So we could have

  Minimum Requirements

  and

  Preferred Qualifications

  as separate sections if they have content. That's okay. But we need to avoid filler like "commensurate with experience". Not present. We have Minimum Requirements bullet list: - An Active in-scope SECRET clearance. - Compliant with DoD 8140 DCWF 722 Intermediate, Information Systems Security Manager. - Bachelors Degree in Computer Science, Cybersecurity, Data Science, Information Systems, Information Technology, or Software Engineering // OR // GMON, SecurityX, CCISO, CCSP, CGRC, CISSO, Cloud+, GCSA, GSEC, Security+, or SSCP. - Six (6) years of experience supporting cybersecurity, information assurance, systems engineering, or RMF-related activities. - 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. Preferred Qualifications: - An Active in-scope TOP SECRET clearance with SCI Eligibility. - Knowledge of NSA’s Commercial Solution for Classified (CSfC) solution and Cross Domain Solutions (CDS). - Experience in an agile work environment - 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. We also have Additional Information: Work Environment and Working at SOSi (EEO). We should remove EEO boilerplate. Work Environment: "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." That's specific content about schedule/working conditions. Could be placed under Schedule or maybe Benefits? There's no explicit Pay or Benefits. So we could create a Schedule section with that info. Or we could put under "Work Environment" but we only allowed headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use Schedule for work hours info. Also maybe Benefits? Not present. Pay? Not present. Skills? Could be extracted from qualifications but we already have Qualifications. Could also have Skills section but maybe redundant. We'll stick to sections we have content: About the role, Responsibilities, Minimum Requirements (maybe as Requirements), Preferred Qualifications (maybe as Qualifications), Schedule. But we need to follow instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if we have content. So we could map: - About the role: intro paragraph. - Responsibilities: duties list. - Requirements: maybe Minimum Requirements. - Qualifications: maybe Preferred Qualifications? But we already used Requirements for minimum; Qualifications for preferred? Or we could combine both under Qualifications and not have Requirements. But we need to avoid thin sections. Let's decide: Use Requirements for minimum, Qualifications for preferred. That seems logical. - Schedule: work environment info. We should not include Skills, Benefits, Pay. Now ensure we preserve all substantive information. We must not drop any duty or qualification. Also we must not include boilerplate like "All interested individuals will receive consideration and will not be discriminated against for any reason." That's EEO, remove. Also remove "Working at SOSi:" line? Actually that line is part of EEO boilerplate. Remove. Now produce HTML fragment. Structure:

  About the role

  Join the Cyber Team in Paradise 🌴 SOSi is looking for a seasoned Information Systems Security Officer (ISSO) ready to lead the charge in securing mission-critical IT operations at Joint Base Pearl Harbor Hickam, Honolulu. As part of a dynamic team supporting over 5,000 users across the Pacific theater, you’ll be at the forefront of solving complex technical challenges that drive real-time Command and Control (C2) strategies. This isn’t just a job — it’s a mission. You’ll own the full Risk Management Framework (RMF) lifecycle, from identifying vulnerabilities to engineering resilient security controls. If you're fluent in DoD protocols, thrive in high-stakes environments, and can deliver executive-level insights with clarity and precision, this is your opportunity to make a strategic impact where it matters most.

  Responsibilities

  • Assist the ISSM (Information System Security Manager) 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.

  Requirements

  • An Active in-scope SECRET clearance.
  • Compliant with DoD 8140 DCWF 722 Intermediate, Information Systems Security Manager.
  • Bachelors Degree in Computer Science, Cybersecurity, Data Science, Information Systems, Information Technology, or Software Engineering // OR // GMON, SecurityX, CCISO, CCSP, CGRC, CISSO, Cloud+, GCSA, GSEC, Security+, or SSCP.
  • Six (6) years of experience supporting cybersecurity, information assurance, systems engineering, or RMF-related activities.
  • 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.

  Qualifications

  • An Active in-scope TOP SECRET clearance with SCI Eligibility.
  • Knowledge of NSA’s Commercial Solution for Classified (CSfC) solution and Cross Domain Solutions (CDS).
  • Experience in an agile work environment
  • 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.

  Schedule

  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.

  Check for any leftover boilerplate: