Information Assurance Compliance Specialist - 30427

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to parse the job posting. Key info: - Requisition Number: 30427 (metadata, not heading) - Required Travel: 11 - 25% (but later says Expected travel up to 10-15% of time for approx one week per trip. There's some inconsistency. We'll include travel info maybe in Schedule? Actually travel is separate. Could be part of Schedule? Not exactly. Could be part of "Schedule" heading if they mention travel percent. But we only create Schedule section if posting actually states schedule (like work hours, shift, remote, etc). There's mention: Ability to work onsite at Dam Neck, Virginia Beach, VA hybrid schedule. Remote/telework is at the discretion of the government. So schedule info: hybrid schedule, onsite, remote possible. So we can include Schedule section. - Anticipated Salary Range: $91,072.00 - $130,104.00. So Pay section. - Security Clearance: Secret Level (but we can include maybe in Requirements? Not a heading. Could be part of Requirements. We'll include in Requirements or Qualifications. - Level of Experience: Senior. - Mission Technologies description: about the role? There's a summary: "HII's Mission Technologies division is currently seeking an Information Assurance Compliance Specialist to support Naval Surface Warfare Center Dahlgren Division (NSWCDD) Dam Neck Activity (DNA) cybersecurity programs for Shore-Based Training Systems." That's about the role. - Key Job Responsibilities: list of duties. - What You Must Have: requirements. - Preferred Qualifications: qualifications. - Physical Requirements: maybe include as part of Requirements? Could be separate but not a standard heading; we could include under Requirements. - Benefits: later: "We offer competitive benefits such as best-in-class medical, dental and vision plan choices; wellness resources; employee assistance programs; Savings Plan Options (401(k)); financial planning tools, life insurance; employee discounts; paid holidays and paid time off; tuition reimbursement; as well as early childhood and post-secondary education scholarships. Bonus/other non-recurrent compensation is occasionally offered..." So we have benefits content. - Pay: we have salary range. - Schedule: hybrid schedule, onsite, remote possible. We must not include boilerplate like EEO, legal, etc. Remove duplicated lines. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings. We must preserve all substantive information. We must not invent or summarize away detail. We must only include sections when posting has real specific content. Thus sections: About the role (maybe from summary), Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We need to decide what goes where. About the role: Could be the summary paragraph: "HII's Mission Technologies division is currently seeking an Information Assurance Compliance Specialist to support Naval Surface Warfare Center Dahlgren Division (NSWCDD) Dam Neck Activity (DNA) cybersecurity programs for Shore-Based Training Systems. This position will provide senior-level compliance and auditor support for Risk Management Framework (RMF) Assessment & Authorization (A&A) processes supporting approximately 80 cloud and shore-based training systems across PMS339, DRPM SUBS (SEA07TR), and RRL sponsors." That seems appropriate. Responsibilities: The list under "Key Job Responsibilities". We'll capture each bullet as

. Requirements: "What You Must Have" includes education/experience combos, advanced specialized experience, knowledge, tools, certification, clearance, ability to work onsite hybrid schedule, strong communication skills. Also physical requirements maybe. Qualifications: "Preferred Qualifications" list. Benefits: the paragraph about benefits. Pay: salary range. Schedule: hybrid schedule, onsite, remote possible, travel percent maybe? Travel is separate but could be part of Schedule? The instruction says use Schedule heading for schedule info. Travel is not schedule but could be included under Schedule? Might be better to include travel under Schedule? However they said "Schedule" heading for schedule info like work hours, shift, remote, etc. Travel is separate but not a standard heading. Could we include travel under Schedule? Might be okay but risk of misinterpretation. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." They gave examples but not limited to those. They said include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we could create a "Travel" heading if there is specific travel content. But they didn't list Travel as example; but we could still use it if we think it's appropriate. However they said "e.g." meaning examples, not exhaustive list. So we could add Travel heading. But they also said "Prefer a few substantive sections over many thin ones." So maybe combine travel into Schedule? But schedule is about work schedule, not travel. Travel is separate but could be considered part of Schedule? Might be okay. Better to create a separate "Travel" heading if we have specific travel content. The posting includes: "Required Travel: 11 - 25%" and later "Expected travel up to 10-15% of time for approximately one week per trip". So we have travel specifics. So we can include Travel section. But they didn't list Travel as example; but we can still use it. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are typical but not exclusive. So we can add Travel. We must not create sections with filler. Travel has real content. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule, Travel. But we need to check if we have Skills section? Not explicitly; we could embed skills in Requirements/Qualifications. No need. Now we need to output only HTML fragment, no /, no markdown. We'll produce something like:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Benefits

...

Pay

Anticipated salary range: $91,072.00 - $130,104.00.

Schedule

Hybrid schedule with onsite work at Dam Neck, Virginia Beach, VA; remote/telework at the discretion of the government.

Travel

Required travel 11‑25% of time, expected up to 10‑15% for approximately one‑week trips to support authorization briefings, stakeholder coordination, or senior‑level meetings.

We need to preserve all substantive information. Let's extract details precisely. About the role: The summary paragraph plus maybe the mission technologies description? The mission technologies description is more about the company; but could be considered "About the role"? The instruction says "About the role" heading for section headings e.g. About the role. Usually that is a brief description of the role and team. The mission technologies description is more about the company; but could be considered part of About the role? Might be better to include only the summary that directly describes the role. The mission technologies description is generic about the division; could be considered boilerplate? It's not boilerplate but it's about the division. However the instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines. This is not that. It's substantive about the division. Might be okay to include in About the role. But to be safe, we can include both the summary and the mission technologies description as part of About the role. Let's capture: "Mission Technologies’ Global Security (GS) group comprises live, virtual, constructive (LVC) solutions; fleet sustainment; nuclear and environmental; and Australia business. As a trusted partner to our military customers, HII designs, develops and operates the largest LVC enterprise that prepares warfighters for cross-domain battle. With advanced technologies to enable mission readiness, HII understands that preparation requires full coordination—not readiness in piece-parts. For more than 40 years, the U.S. Navy has entrusted HII to maintain and modernize the vast majority of its fleet. With a holistic approach to life-cycle maritime defense systems—from small watercraft to submarines, surface combatants and aircraft carriers—HII ensures a high state of readiness. HII supports the Department of Energy’s national security mission through the management and operation of its sites, as well as the safe cleanup of legacy waste across the country. HII meets clients’ toughest nuclear and environmental challenges." That's a lot; but it's about the division, not the role. Might be considered "About the company". Could be omitted? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. But where to put? Could be under About the role as context. It's not duplicated. So we include. Thus About the role paragraph(s) will include that block plus the summary. We need to ensure we don't repeat content elsewhere. Now Responsibilities: list each bullet from "Key Job Responsibilities". Let's extract them exactly: - Oversee, evaluate, and support documentation, validation, and accreditation processes necessary to ensure information technology (IT) systems meet the organization's information assurance (IA) and security requirements. - Provide senior Auditor support for RMF packages and continuous monitoring purposes as needed in RMF Steps 0-6 for PMS 339 and DRPM SUBS (UWS TR) systems. - Provide security controls risk assessments and validations. - Lead annual security reviews and annual testing of security controls; validate control implementation and effectiveness. - Independently assess quality of security control implementation against NIST SP 800-53 requirements and Navy cybersecurity policies. - Review, validate, and approve security artifacts including System Security Plans (SSP), Security Assessment Plans (SAP), Security Assessment Reports (SAR), and Plan of Action and Milestones (POA&M). - Develop and maintain objective quality evidence (OQE) documentation for security control validation and continuous monitoring. - Conduct comprehensive reviews of STIG compliance results, ACAS vulnerability scan outputs, and remediation activities; provide recommendations for risk mitigation. - Assess POA&M entries for accuracy, completeness, and appropriate risk categorization; track vulnerability remediation timelines. - Lead continuous monitoring activities by analyzing security control compliance status, identifying systemic issues, and recommending corrective actions. - Coordinate with Information System Security Managers (ISSM), Technical Area Experts (TAE), Security Control Assessors (SCA), Functional Authority Officials (FAO), and Authorizing Officials (AO). - Review and approve technical documentation including engineering change proposals, baseline descriptions, and configuration management artifacts for security compliance. - Prepare and deliver briefings to senior leadership at TAE, SCA, and FAO/AO checkpoint and authorization signing meetings on system security posture and risk acceptance recommendations. - Develop cyber policies, procedures, compliance reports, and risk analysis documentation. - Ensure appropriate treatment of risk, compliance, and monitoring assurance from internal and external perspectives across multiple systems and sponsors. - Provide expert guidance on Navy cybersecurity policies, instructions, RMF processes, and FISMA reporting requirements. - Utilize Enterprise Mission Assurance Support Service (eMASS) to manage authorization packages, track system status, and maintain compliance artifacts. - Support cross-sponsor activities for PMS339, SUBS, and RRL programs; coordinate