Information System Security Officer, Senior

We need to output 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 have overview, responsibilities, qualifications (basic and preferred), benefits, pay (salary range), schedule? Not given schedule specifics; only shift: Day, Telework: None. That could be schedule? It says Shift: Day, Telework: None. That's schedule info. So we can include Schedule section with that info. Pay section: Salary Range: $190,000 to $220,000 per year. Also mention starting salary based on education/experience. That's specific enough. Benefits: we have list. Overview: we have overview paragraph; we could put under About the role? The overview is like About the role. We'll use About the role heading for overview paragraph. Responsibilities: list. Requirements: maybe combine basic qualifications? But we have Qualifications section (basic and preferred). Could split into Requirements (basic) and Qualifications (preferred) but instructions: use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills. We need to decide what to put where. We have qualifications (basic and preferred). Could put Requirements = basic qualifications, Qualifications = preferred qualifications. Skills: maybe we can extract skills from qualifications: knowledge of security tools, hardware/software security implementation, communication protocols, encryption techniques/tools, etc. Could make a Skills section. But we must not create thin sections; better to combine. However we have enough content for Requirements (basic qualifications) and Qualifications (preferred). Skills maybe redundant. Could omit Skills if no specific skill list beyond what's in qualifications. But we have "Demonstrated knowledge of and experience with several of the following: current security tools; hardware/software security implementation; communication protocols; encryption techniques/tools." That's a skill list. Could put under Skills. But then we would have Requirements (basic qualifications), Qualifications (preferred), Skills (that list). Might be okay but risk of thin sections. However we have enough detail for each. We also have About WOOD and Why Join WOOD sections; those could be considered About the role? Actually About the role is overview of role; About WOOD is company description. Could be omitted? The instruction: include a section ONLY when posting has real, specific content for it. We have About WOOD content; but we don't have a heading for About the company. Not in allowed headings list. So we might omit that or fold into About the role? Probably better to omit company description as not requested headings. The allowed headings are limited; we should not add extra headings. So we can ignore About WOOD and Why Join WOOD unless we can fit them under About the role (maybe as extra paragraph). But About the role should be about the role, not company. However we can still include a paragraph about company under About the role? Might be stretching. Safer to omit company description as not covered by headings; but we must preserve ALL substantive information. The instruction says preserve ALL substantive information; do not invent or summarize away detail. If we omit company description, we lose substantive info. However we could incorporate it into About the role section as extra paragraph, though it's not strictly about the role but still substantive. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we could also use other headings? Probably we should stick to those given. But we need to preserve all substantive info; we could put company description under About the role as a paragraph, though it's not exactly about the role but still okay. Or we could create a separate heading like "About WOOD" but not in list; risk of violating instruction. Better to incorporate into About the role. Similarly, "Why Join WOOD?" could be folded into Benefits or maybe omitted? It's substantive about company culture; we could put under Benefits? Not ideal. Could put under About the role as additional paragraph. We'll try to include all substantive info within allowed sections. Let's extract: Overview paragraph: "Protect mission‑critical systems at enterprise scale. WOOD is seeking a highly skilled Senior Information Systems Security Officer (ISSO) to lead security oversight across a large, complex software development and systems‑integration environment. In this role, you’ll partner with cybersecurity experts, engineers, and program leadership to safeguard high‑value systems, strengthen security architecture, and ensure compliance with evolving standards. You’ll shape and maintain the security posture of diverse platforms, guiding secure development practices, assessing risks, monitoring vulnerabilities, and driving remediation strategies that protect sensitive data and critical workflows. Your work will span threat detection, incident response, policy implementation, and continuous improvement across multiple technical domains. If you excel in high‑visibility roles, thrive on solving sophisticated security challenges, and want your expertise to directly influence mission success, this is an opportunity to lead at the highest level." That's About the role. Responsibilities: list bullet points. We have many responsibilities lines. We'll put each as

. Requirements: Basic Qualifications list. Qualifications: Preferred Qualifications list. Skills: maybe we can extract from "Demonstrated knowledge of and experience with several of the following: current security tools; hardware/software security implementation; communication protocols; encryption techniques/tools." Also "In-depth experience completing security evaluations of software systems or architectures..." etc. But those are already in qualifications. Might be redundant. Could omit Skills section to avoid thin. But we need to preserve that info; it's already in qualifications (basic). So we can keep it there. Benefits: list. Pay: Salary range. Schedule: Shift: Day, Telework: None. We also have location: Annapolis Junction, Maryland, USA. Could be included in About the role paragraph or maybe as a short p under Overview? Not a heading. We'll add a paragraph after overview maybe under About the role? Or we could add a separate short p before sections? The instruction: do not repeat job title as heading; we can include location as a short p before sections. It's not a heading, allowed. Also Job Type: Full-Time. Could be included in schedule? Or short p. We'll output:

Location: Annapolis Junction, Maryland, USA

Job Type: Full-Time

Then

About the role

Overview paragraph

Responsibilities

...

Requirements

...

(basic qualifications)

Qualifications

...

(preferred qualifications)

Benefits

...

Pay

Salary Range: $190,000 to $220,000 per year. Starting salary is based on minimum education and years of experience and increases based on education and/or experience.

Schedule

Shift: Day. Telework: None.

We must not include boilerplate like EEO, application process, etc. Remove those. Check for any duplicated lines: we have responsibilities list includes some duplicates like "Evaluate security solutions to ensure they meet security requirements for processing information." appears twice; we should keep only one instance? The instruction: Remove duplicated lines. So we need to deduplicate. Let's extract responsibilities lines: - Provide support for implementing and enforcing information systems security policies, standards, and methodologies. - Assist in the evaluation of security solutions to ensure they meet security requirements for processing multiple types of information. - Assist with the Configuration Management for information system security software, hardware, and firmware. - Analyze threats and develop and implement best practice methodologies for incident detection, reporting, and vulnerability remediation. - Maintain records on workstations, servers, routers, firewalls, intelligent hubs, network switches, etc. to include system upgrades. - Evaluate security solutions to ensure they meet security requirements for processing information. (duplicate of second but slightly different wording) - Maintain operational security posture for information systems. - Provide support to the Information System Security Manager (ISSM) for maintaining the appropriate operational IA posture for a system/program/enclave. - Develop and maintain documentation for Certification & Accreditation in accordance with specified policies. - Develop and update system security plans and other IA documentation. - Provide support for Information Assurance Vulnerability Alerts (IAVAs) management (initiating IAVA responses and system security scans, completing remediation, extending IAVA patches and security updates to designated sites, etc.). - Provide CM for security‐relevant information system software, hardware, and firmware. (duplicate of third) - Develop system security policy and ensure compliance. - Administer the user identification and authentication mechanisms of the Information System. We need to deduplicate: remove duplicate lines that are essentially same. We'll keep one each. So final responsibilities list: - Provide support for implementing and enforcing information systems security policies, standards, and methodologies. - Assist in the evaluation of security solutions to ensure they meet security requirements for processing multiple types of information. - Assist with the Configuration Management for information system security software, hardware, and firmware. - Analyze threats and develop and implement best practice methodologies for incident detection, reporting, and vulnerability remediation. - Maintain records on workstations, servers, routers, firewalls, intelligent hubs, network switches, etc. to include system upgrades. - Maintain operational security posture for information systems. - Provide support to the Information System Security Manager (ISSM) for maintaining the appropriate operational IA posture for a system/program/enclave. - Develop and maintain documentation for Certification & Accreditation in accordance with specified policies. - Develop and update system security plans and other IA documentation. - Provide support for Information Assurance Vulnerability Alerts (IAVAs) management (initiating IAVA responses and system security scans, completing remediation, extending IAVA patches and security updates to designated sites, etc.). - Develop system security policy and ensure compliance. - Administer the user identification and authentication mechanisms of the Information System. Now Basic Qualifications: - Must have at least 10 years of experience as ISSO working independently, and/or on teams maintaining secure information system operations in isolated, connected and standalone environments. - Must have at least 5 years of experience using tools to support IAVA management. - Must have at least 5 years of experience using tools to support the preparation, maintenance, and management of SSPs and other security related documentation. - Demonstrated knowledge of and experience with several of the following: current security tools; hardware/software security implementation; communication protocols; encryption techniques/tools. - In‑depth experience completing security evaluations of software systems or architectures to ensure they meet security requirements. - In‑depth experience proposing, coordinating, implementing, and enforcing information systems security policies, standards, and methodologies, preferably on a large software or IT program. - Demonstrated experience performing day‐to‐day security operations of large, complicated information and information processing systems. - Must be committed to developing and adhering to best practices. - Must possess a high level of self‐initiative and must be a solutions‐oriented team player. - Must have excellent interpersonal skills. Preferred Qualifications: - Bachelor's degree in a related field and at least 12 years of relevant experience. - Extensive experience as an Information Systems Security Officer on large software development and integration programs. - DoD 8570 compliance with IAT Level II or higher. - DoD 8570 compliance with IAM Level II or higher. Benefits list: - Health Insurance: Comprehensive medical, dental, and vision coverage. - Retirement Plan: 401(k) plan with company match. - Paid Time Off: Paid vacation, sick leave, and company holidays. - Professional Development: Opportunities for training, certifications, and continued professional growth. - Work-Life Support: Workplace flexibility where permitted by position, customer, security, and mission requirements. - Wellness Resources: Employee assistance and wellness