DevSecOps Security Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must preserve all substantive info, no invented or summarizing away detail. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. We need to parse the posting. Key content: - Description: Leidos is seeking a DevSecOps Security Engineer ... (intro). This is about the role. - About the role: The description includes details: supporting development of L-CAP, hybrid cloud data mesh, AI-first engineering, SAFe/Agile, ART, hybrid position requiring 3 days onsite 2 days WFH if within commutable distance from Gaithersburg, MD; Eagan, MN; Egg Harbor Township, NJ; else 100% remote. Also mentions U.S. citizenship required, ability to obtain and maintain Public Trust, meet government background investigation, must meet FAA facility and info system access requirements, continuous US residency for at least 3 of prior 5 years. - Responsibilities: list of what you'll do: implement and maintain automated security controls in CI/CD pipelines (SAST, DAST, SCA, container scanning, IaC scanning); enforce security gates, artifact signing, provenance verification, SBOMs; drive container vulnerability remediation and hardening; implement Kubernetes security controls; secure workloads via secrets management, mTLS, service mesh policies, Linux/container hardening; build/maintain policy-as-code and infrastructure guardrails using OPA/Rego, Kyverno; produce security evidence supporting authorization and continuous monitoring; partner with platform and application teams to triage vulnerabilities, remediate findings, support security incident response and root cause analysis; leverage AI-assisted development, automation, modern engineering practices. - Requirements: Core Technical Qualifications: Bachelor's degree in Cybersecurity, CS, IT, or related field with 4+ years relevant experience (additional experience may be considered in lieu of degree). Hands-on experience integrating SAST, DAST, SCA, container scanning into CI/CD pipelines. Experience securing Kubernetes and container environments, including pod security, network policies, RBAC, admission controls, hardened/minimal base images. Experience with vulnerability scanning and remediation using tools such as Nessus, Trivy, Grype, or Qualys, including CVE triage and tracking. Experience with secrets management (HashiCorp Vault or equivalent) and security automation using Python, Bash, or Go. Experience with Git-based workflows and CI/CD tooling, such as GitLab CI, GitHub Actions, or Jenkins. Working knowledge of NIST 800-53, automated security evidence, and AWS or Azure cloud security. Understanding of network security, including segmentation and default-deny policies. U.S. citizenship required, with ability to obtain and maintain a Public Trust and meet government background investigation requirements. Must meet FAA facility and information system access requirements, including continuous U.S. residency for at least 3 of the prior 5 years. - Preferred / Desired Qualifications: Security+ CE, CySA+, or equivalent DoD 8570 IAT Level II certification. Certified Kubernetes Administrator (CKA) or Certified Kubernetes Security Specialist (CKS). Knowledge of software supply chain security, including SLSA, Sigstore/cosign, in-toto, and FIPS 140-3. Experience with policy-as-code (OPA/Rego, Kyverno) and infrastructure-as-code security scanning (Terraform, CloudFormation). Experience securing Kubernetes/OpenShift environments, including service mesh security (Istio, Linkerd) and security context constraints. Experience with GitOps deployment using ArgoCD, Flux, or equivalent. Experience in aviation, FAA, or other safety-critical environments. Experience with SAFe or large-scale Agile delivery. - Skills: Not explicitly listed separate; but many technical skills are in qualifications. Could combine under Skills? The instruction: Use sections only when posting has real specific content. We have content for Responsibilities, Requirements (Core Technical Qualifications), Preferred/Desired Qualifications (could be Qualifications). Also we have Pay: Pay Range $87,100.00 - $157,450.00. Also note: "The Leidos pay range for this job level is a general guideline only and not a guarantee..." We should include that as part of Pay section. - Benefits: The posting includes "Why Leidos?" paragraph about mission, AI, etc. Also "Pay And Benefits" section: Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. More details at link. Also "About Leidos" paragraph about company. Also "Securing Your Data" etc (boilerplate to remove). Also "Commitment to Non-Discrimination" (EEO) to remove. We need to include Benefits section if there is real specific content. The posting mentions: "Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement." That's specific enough. Also "Pay and benefits are fundamental..." but that's generic. We'll include the list. - Schedule: The posting mentions hybrid position requiring 3 days onsite and 2 days working from home, if within commutable distance; else 100% remote. That's schedule info. So we can include Schedule section. - About the role: we need a section heading About the role. The intro paragraph can go there. We must not repeat job title as heading. Not include Job ID/requisition numbers. We must not include filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

... (intro paragraph plus maybe hybrid schedule? but schedule separate)

Better to keep schedule separate. Thus About the role: description of role, mission, L-CAP, AI-first, SAFe/Agile, hybrid position details? Actually schedule details could go under Schedule. But About the role can include the role purpose. We'll include:

Leidos is seeking a DevSecOps Security Engineer to join the Air Traffic Business Area within the Homeland Sector, supporting the development of the Leidos Common Automation Platform (L-CAP). L-CAP is a mission-critical, future-ready automation platform built on a hybrid cloud data mesh architecture, enabling next-generation air traffic management capabilities. We are building with an AI-first engineering mindset, embracing emerging AI capabilities and modern development practices to accelerate delivery, improve software quality, and continuously evolve how we design and build mission-critical systems. This role operates within a SAFe/Agile framework as part of an Agile Release Train (ART) delivering iterative value across the program. This position supports government programs and requires the ability to obtain and maintain a favorable Public Trust investigation.

Then Schedule section: hybrid position requiring 3 days onsite and 2 days working from home, if within commutable distance (Less than 1 hour's drive one-way during normal traffic) from Gaithersburg, MD; Eagan, MN; or Egg Harbor Township, NJ. However, if you do not reside within a commutable distance, you may be considered for a 100% remote role. Also mention must meet FAA facility and information system access requirements, including continuous U.S. residency for at least 3 of the prior 5 years. Actually that is more requirement than schedule; but schedule part is hybrid/remote. We'll put schedule details there. Responsibilities:

• ... each bullet. Requirements: core technical qualifications. Qualifications: preferred/desired qualifications. Skills: maybe we can combine technical skills from requirements? But we already have requirements and qualifications. The instruction says use sections only when posting has real specific content. We have content for Skills? Not explicitly separate; but we could still create Skills section summarizing technical skills like SAST, DAST, SCA, container scanning, Kubernetes, secrets management, policy-as-code, etc. However that would be somewhat duplicative. Safer to omit Skills section if not explicitly present. But we have many skill statements in requirements; but those are qualifications. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not mandatory to include all. We should include only those with real specific content. The posting does not have a separate "Skills" heading; but we could infer skills from responsibilities and qualifications. However to avoid inventing, better to omit Skills section unless we can directly map to a list of skills explicitly mentioned. The posting mentions "Hands-on experience integrating SAST, DAST, software composition analysis, and container scanning into CI/CD pipelines." That's a skill. Also "Experience securing Kubernetes and container environments..." etc. Could be considered skills. But the instruction says "Prefer a few substantive sections over many thin ones." So we could combine skills into Requirements or Qualifications. I think we can omit Skills section. Benefits: we have specific list. Pay: we have range. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We need to ensure we preserve all substantive info. Let's extract each piece precisely. About the role: we already captured intro plus maybe mention of supporting government programs and Public Trust. That's fine. Responsibilities: list each bullet from "What You’ll Do". Let's copy exactly: - Implement and maintain automated security controls in CI/CD pipelines, including SAST, DAST, software composition analysis, container scanning, and infrastructure-as-code scanning. - Enforce security gates, artifact signing, provenance verification, and SBOMs (CycloneDX/SPDX) to prevent vulnerable or unverified deployments. - Drive container vulnerability remediation and hardening, including hardened minimal base images and elimination of critical/high findings. - Implement Kubernetes security controls, including pod security, network policies, RBAC, admission controls, and security context constraints. - Secure workloads through secrets management, mutual TLS (mTLS), service mesh policies, and Linux/container hardening. - Build and maintain policy-as-code and infrastructure guardrails using OPA/Rego, Kyverno, or equivalent tools. - Produce security evidence supporting authorization and continuous monitoring requirements. - Partner with platform and application teams to triage vulnerabilities, remediate findings, and support security incident response and root cause analysis. - Leverage AI-assisted development, automation, and modern engineering practices to improve security, code quality, productivity, and delivery speed. We should keep the exact phrasing. Requirements (Core Technical Qualifications): list each bullet: - Bachelor’s degree in Cybersecurity, Computer Science, Information Technology, or related field with 4+ years of relevant experience. (additional experience, education and training may be considered in lieu of degree) - Hands-on experience integrating SAST, DAST, software composition analysis, and container scanning into CI/CD pipelines. - Experience securing Kubernetes and container environments, including pod security, network policies, RBAC, admission controls, and hardened/minimal base images. - Experience with vulnerability scanning and remediation, using tools such as Nessus, Trivy, Grype, or Qualys, including CVE triage and tracking. - Experience with secrets management (HashiCorp Vault or equivalent) and security automation using Python, Bash, or Go. - Experience with Git-based workflows and CI/CD tooling, such as GitLab CI, GitHub Actions, or Jenkins. - Working knowledge of NIST 800-53, automated security evidence, and AWS or Azure cloud security. - Understanding of network security, including segmentation and default-deny policies. - U.S. citizenship required, with the ability to obtain and maintain a Public Trust and meet government background investigation requirements. - Must meet FAA facility and information system access requirements, including continuous U.S. residency for at least 3 of the prior 5 years. Qualifications (Preferred / Desired Qualifications): list each bullet: - Security+ CE, CySA+, or equivalent DoD 8570 IAT Level II certification. - Certified Kubernetes Administrator (CKA) or Certified Kubernetes Security Specialist (CKS