Information System Security Engineer (ISSE)

We need to output HTML fragment with sections: About the role? Actually the posting includes description: "At Accenture Federal Services, nothing matters more..." That's about the company. Then "Job Description Accenture Federal Services is looking for an Information System Security Engineer (ISSE) to design..." Then "What You'll Own", "What You'll Deliver", "Here's What You Need", "Bonus Points If You Have", "Security Requirements", "Compensation" (pay range), maybe "Benefits" (they mention benefits but no specifics). According to rules: include a section only when posting has real, specific content for it. Benefits: they say "Accenture Federal Services offers a wide variety of benefits. You can find more information on benefits here." That's not specific content; it's generic. So we should NOT include Benefits section because no specific benefits listed. Pay: they give pay range for certain locations: "$103,200—$196,400 USD". That's specific, so include Pay section. Schedule: not mentioned, so omit. Skills: maybe we can include under Requirements? But we have sections: About the role (maybe company overview), Responsibilities (What You'll Own + What You'll Deliver?), Requirements (Here's What You Need), Qualifications (maybe Bonus Points?), Skills (maybe technical skills?), but we need to follow headings: 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 preserve all substantive info. We need to decide mapping: - About the role: could be the introductory paragraph about Accenture Federal Services mission and the role overview. Could combine first paragraph and job description sentence. - Responsibilities: "What You'll Own" and "What You'll Deliver" both are responsibilities/deliverables. Could combine into Responsibilities section with bullet list. - Requirements: "Here's What You Need" (mandatory). Could be Requirements. - Qualifications: maybe "Bonus Points If You Have" could be Qualifications or Skills? Actually qualifications often include preferred qualifications. Could treat Bonus Points as Qualifications (preferred). Or Skills: maybe list technical skills from requirements. But we have to avoid thin sections. We could combine Bonus Points into Qualifications section as preferred qualifications. - Skills: maybe we could extract specific technical skills from requirements (e.g., NIST 800-53, RMF, SIEM Splunk, etc.) but that's already in Requirements. Might be redundant. Better to not create Skills if not distinct. - Pay: include pay range. - Benefits: omit as no specifics. - Schedule: omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. Must not include boilerplate like EEO, legal, accommodation, etc. Must remove those. We need to include the company mission paragraph, the job description sentence, maybe the "Join us to drive positive, lasting change..." That's part of About the role. Let's extract substantive content: Intro paragraph: "At Accenture Federal Services, nothing matters more than helping the US federal government make the nation stronger and safer and life better for people. Our 13,000+ people are united in a shared purpose to pursue the limitless potential of technology and ingenuity for clients across defense, national security, public safety, civilian, and military health organizations. Join Accenture Federal Services, a technology company within global Accenture. Recognized as a Glassdoor Top 100 Best Place to Work, we offer a collaborative and caring community where you feel like you belong and are empowered to grow, learn and thrive through hands-on experience, certifications, industry training and more. Join us to drive positive, lasting change that moves missions and the government forward!" Then job description: "Accenture Federal Services is looking for an Information System Security Engineer (ISSE) to design, implement, and maintain the security architecture and controls for cloud-based client systems supporting the program. You'll build and operate the security tooling — SIEM, vulnerability management, automation — that keeps systems compliant and secure, and provide the technical engineering input that supports RMF/JSIG authorization activities." That's also part of About the role maybe. Then "What You'll Own" list: - Design and implementation of security controls across cloud-based systems — identity and access management, encryption, and network security - Security tooling engineering and administration — SIEM (Splunk), vulnerability management (Nessus/ACAS), and STIG compliance tools - Security-as-code automation for deploying and configuring security tooling (Ansible, Terraform, PowerShell, Bash, or Python) - Technical input into RMF authorization artifacts — SSP, SCTM, POA&Ms, and Risk Assessment Reports — supporting the authorization package - Incident detection engineering — developing detections, tuning alerts, and improving telemetry to support incident response - Technical compliance review of new and existing systems against IA directives, including protection of data across classification levels Then "What You'll Deliver": - Security architecture and controls implemented and functioning across supported cloud environments - Working SIEM and vulnerability management tooling that gives the security team real visibility into risk - Accurate, engineering-grounded inputs to RMF documentation that hold up under authorization review - Detections and alerting that measurably improve incident response time and coverage - Automated, repeatable deployment and configuration of security tooling, not manual one-off setups Combine these into Responsibilities (maybe both Own and Deliver are responsibilities). Could list bullet points. Then "Here's What You Need": - 3+ years of experience implementing NIST 800-53 controls and the Risk Management Framework (RMF), including at least 1 year of hands-on experience administering security tooling such as SIEM (Splunk), vulnerability management (Nessus/ACAS), or security automation (Ansible, Terraform, PowerShell, Bash, or Python) - 2+ years of experience with virtualization or cloud environments (AWS or Azure) - DoD 8570 IASAE Level II certification (e.g., CISSP, CASP+), or DoD 8140 equivalent - Bachelor's or Associate degree in Computer Science, Cybersecurity, or a related technical field, or 4+ years of relevant job or military experience in lieu of degree Then "Bonus Points If You Have": - AWS or Azure technical certifications, or Splunk-specific certifications (e.g., Splunk Certified Architect, Splunk Enterprise Security Certified Admin) - Experience with a security incident response team (NOC/SOC) - Familiarity with container security (Docker, Kubernetes, ECS/EKS/AKS) - JSIG or ICD 503 compliance knowledge - Experience working in a DevSecOps project environment - Familiarity with National Security systems and air-gapped environments Then "Security Requirements": "Active TS clearance required; SCI preferred" Also there is a paragraph about compensation ranges for certain states, and then the pay range: "$103,200—$196,400 USD". Also statement: "Compensation for roles at Accenture Federal Services varies depending on a wide array of factors, including but not limited to office location, role, skill set, and level of experience." That's generic but we can include as part of Pay section prose. We must not include boilerplate like "As required by local law, Accenture Federal Services provides reasonable ranges of compensation for hired roles based on labor costs in the states of ..." That's actually substantive because it lists states where the range applies. It's part of pay info. We should keep that? The rule: preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that sentence as part of Pay section. However we must not include fluff like "Accenture Federal Services offers a wide variety of benefits. You can find more information on benefits here." That's benefits but not specific; we omit Benefits section. We also need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must cut out the large EEO statements, accommodation, other employment statements, etc. Thus final HTML:

  About the role

  At Accenture Federal Services, nothing matters more than helping the US federal government make the nation stronger and safer and life better for people. Our 13,000+ people are united in a shared purpose to pursue the limitless potential of technology and ingenuity for clients across defense, national security, public safety, civilian, and military health organizations. Join Accenture Federal Services, a technology company within global Accenture. Recognized as a Glassdoor Top 100 Best Place to Work, we offer a collaborative and caring community where you feel like you belong and are empowered to grow, learn and thrive through hands-on experience, certifications, industry training and more. Join us to drive positive, lasting change that moves missions and the government forward! Accenture Federal Services is looking for an Information System Security Engineer (ISSE) to design, implement, and maintain the security architecture and controls for cloud-based client systems supporting the program. You'll build and operate the security tooling — SIEM, vulnerability management, automation — that keeps systems compliant and secure, and provide the technical engineering input that supports RMF/JSIG authorization activities.

  Responsibilities

  • Design and implementation of security controls across cloud-based systems — identity and access management, encryption, and network security
  • Security tooling engineering and administration — SIEM (Splunk), vulnerability management (Nessus/ACAS), and STIG compliance tools
  • Security-as-code automation for deploying and configuring security tooling (Ansible, Terraform, PowerShell, Bash, or Python)
  • Technical input into RMF authorization artifacts — SSP, SCTM, POA&Ms, and Risk Assessment Reports — supporting the authorization package
  • Incident detection engineering — developing detections, tuning alerts, and improving telemetry to support incident response
  • Technical compliance review of new and existing systems against IA directives, including protection of data across classification levels
  • Security architecture and controls implemented and functioning across supported cloud environments
  • Working SIEM and vulnerability management tooling that gives the security team real visibility into risk
  • Accurate, engineering-grounded inputs to RMF documentation that hold up under authorization review
  • Detections and alerting that measurably improve incident response time and coverage
  • Automated, repeatable deployment and configuration of security tooling, not manual one-off setups

  Requirements

  • 3+ years of experience implementing NIST 800-53 controls and the Risk Management Framework (RMF), including at least 1 year of hands-on experience administering security tooling such as SIEM (Splunk), vulnerability management (Nessus/ACAS), or security automation (Ansible, Terraform, PowerShell, Bash, or Python)
  • 2+ years of experience with virtualization or cloud environments (AWS or Azure)
  • DoD 8570 IASAE Level II certification (e.g., CISSP, CASP+), or DoD 8140 equivalent
  • Bachelor's or Associate degree in Computer Science, Cybersecurity, or a related technical field, or 4+ years of relevant job or military experience in lieu of degree

  Qualifications

  • AWS or Azure technical certifications, or Splunk-specific certifications (e.g., Splunk Certified Architect, Splunk Enterprise Security Certified Admin)
  • Experience with a security incident response team (NOC/SOC)