Cloud Security Engnieer - Intermediate

We need to output HTML fragment with sections: About the role? Actually the posting includes Position Summary, Key Responsibilities, Required Qualifications, Preferred Qualifications, About The Company, Benefits. Also maybe "Location: Remote", "Education: Bachelor's Degree", "Experience: 5+ years", "Work Authorization: U.S. Citizen". Those are metadata; we should fold minor metadata into a short

or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short paragraph with location, education, experience, work auth. We need headings:

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use only those headings if content exists. We have Position Summary (maybe "About the role")? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map sections accordingly. We have Position Summary: could be "About the role". We'll output

About the role

then

with summary. Key Responsibilities:

Responsibilities

then

• each. Required Qualifications: maybe

  Requirements

  or

  Qualifications

  . The list includes both required and preferred. We could have

  Requirements

  for required qualifications, and

  Preferred Qualifications

  maybe as a separate heading? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid extra headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples, but we should stick to those categories. However we have both required and preferred qualifications; we could combine under "Requirements" and note preferred within same list? But we must preserve all substantive information; we could have two sub-sections: maybe under Requirements we list required, then a note "Preferred:" but that might be okay. Or we could have "Qualifications" heading for required, and "Preferred Qualifications" maybe not in the list but could be considered a subsection; but instruction says prefer a few substantive sections over many thin ones. Could combine required and preferred under "Qualifications" with subheadings? But we cannot use headings other than those? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Safer to stick to those. We'll have: - About the role (position summary) - Responsibilities - Requirements (required qualifications) - Qualifications (maybe we could treat as skills? but we have many technical skills; maybe we put them under Qualifications) - Benefits We need to avoid Pay and Schedule sections because not specified. We also have About The Company; could be part of About the role? Or we could add a section "About the company" but not in list; maybe we can incorporate into About the role paragraph. We'll include a short paragraph for metadata: location remote, education bachelor's, experience 5+ years, work authorization US Citizen. Now we need to ensure we don't include boilerplate like EEO, equal opportunity, etc. Remove those. We must preserve all substantive information: responsibilities list, qualifications list, preferred qualifications list, benefits list, about company details. Let's extract. Position Summary: "We are seeking a Cloud Security Engineer Intermediate to provide hands-on cloud security support for a 24x7 FedRAMP High AWS GovCloud environment. The role will support vulnerability management and patching, hardened cloud images, CI/CD security, continuous monitoring and threat detection, backup and data protection, and cloud security compliance." Key Responsibilities list: - Coordinate vulnerability management and patching activities across cloud environments within required federal SLA timelines. - Analyze Tenable Nessus scan results, map CVEs to NIST SP 800-53 Rev. 5 controls, and manage POA&M entries for open findings. - Execute Ansible-based AMI patching and perform regression scans to validate remediation. - Implement and maintain security scanning within GitLab CI and Jenkins pipelines, including SAST, SCA, DAST, container, IaC, and secrets scanning. - Maintain hardened baseline AMIs aligned with DISA STIG and CIS benchmarks. - Support security tools including Trivy, Grype, SonarQube, OpenSCAP, and Syft. - Monitor CISA KEV and other authorized threat intelligence sources. - Correlate Splunk SIEM and CrowdStrike Falcon EDR security events and support CloudWatch monitoring and alerting. - Respond to and escalate security events within required response timelines. - Support AWS Backup, cross-Region replication, backup testing, and recovery activities. - Support Data Loss Prevention (DLP) operations. - Support AWS IAM and least-privilege access controls. - Maintain Infrastructure-as-Code configurations using Terraform and Ansible. - Support AWS Control Tower and Service Control Policies. - Maintain audit logs and security documentation in accordance with NIST SP 800-53, FedRAMP, FISMA, and applicable policies. Required Qualifications list: - Bachelor's degree. - 5+ years of AWS cloud security engineering experience, including IAM, Security Hub, GuardDuty, AWS Config, CloudTrail, KMS/CloudHSM, Control Tower, and Service Control Policies. - FedRAMP High or AWS GovCloud experience. - 5+ years of vulnerability management experience using Tenable Nessus or equivalent, including CVE triage, POA&M management, and remediation. - 5+ years of experience securing CI/CD pipelines using SonarQube, Trivy, Grype, IaC scanning, secrets detection, and DAST in GitLab CI or Jenkins. - 4+ years of experience with Terraform and Ansible, hardened AMIs, and DISA STIG or CIS benchmarks. - 5+ years of experience with Splunk or equivalent SIEM, including log analysis, threat correlation, and alert tuning. - 3+ years of experience with CrowdStrike Falcon or equivalent EDR. - 5+ years of experience with NIST SP 800-53 Rev. 5 and FISMA/FedRAMP controls. - Proficiency with Microsoft Excel and Word. - Excellent verbal and written communication skills. Preferred Qualifications list: - Experience securing containers and Kubernetes environments on AWS EKS, Red Hat OpenShift, or ROSA. - Experience with SBOMs using CycloneDX and Syft. - Experience with DLP solutions in federal cloud environments. - Experience with AWS Backup and immutable recovery capabilities. - Experience with AIOps security triage tools. - Experience producing OSCAL evidence and integrating with RegScale. - Experience implementing Zero Trust network controls. - Experience with federal cloud security processes, continuous monitoring, or similar environments. About The Company: - Headquartered in Leesburg, Virginia, Zenius Corporation is a HUBZone-certified small business. - Zenius specializes in providing Grants Management, IT Modernization, Acquisition Management, and Financial Management services to Federal agencies. - Zenius is selected by Inc 5000 as one of the fastest-growing companies in the DC Metro Area, awarded in 2025, 2024, 2021, and 2020. - Zenius is also listed by Financial Times as one of the fastest-growing companies in the Americas in 2021. - Zenius is an awardee of 2019 Best of Leesburg winner (Business Management Consultant category). Benefits: - Competitive benefits package that includes paid holidays and paid time off, medical insurance including health, vision, dental insurance, 401K matching, Flexible Spending Account and flexible schedules, as per business needs. - We also work with our employees on training and professional certification plans that benefit the employee. We should not include EEO etc. Now produce HTML. We need a short paragraph for metadata: maybe

  Location: Remote | Education: Bachelor's Degree | Experience: 5+ years | Work Authorization: U.S. Citizen

  But we should avoid using ? Not prohibited. Could just plain text. We'll output:

  About the role

  We are seeking a Cloud Security Engineer Intermediate to provide hands-on cloud security support for a 24x7 FedRAMP High AWS GovCloud environment. The role will support vulnerability management and patching, hardened cloud images, CI/CD security, continuous monitoring and threat detection, backup and data protection, and cloud security compliance.

  Location: Remote | Education: Bachelor's Degree | Experience: 5+ years | Work Authorization: U.S. Citizen

  Then Responsibilities. Then Requirements (required qualifications). Could be

  Requirements

  then

  . Then Qualifications (maybe we could put preferred under Qualifications? But we have both required and preferred; maybe we split: Requirements for required, Qualifications for preferred? But Qualifications heading is ambiguous. Could do Requirements for required, and Qualifications for preferred? Or we could combine both under Requirements with a note "Preferred:" inside list items. But we need to preserve all info; we could have two lists: one for Required Qualifications, another for Preferred Qualifications, each under its own heading. The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid using both Requirements and Qualifications headings. So we can have:

  Requirements

  for required qualifications.

  Qualifications

  for preferred qualifications. That seems okay. Then Benefits. We also might include About the company under About the role? Could add another

  About the company

  but not in list; maybe we can incorporate into About the role paragraph after summary. But we have to preserve all substantive information; we could add a separate section "About the company" but not in the prescribed headings; risk of violating instruction? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." implies those are examples, not an exhaustive list; we could still use other headings but better to stick to those. We could treat About the company as part of About the role (since it's about the company). We'll add a paragraph after the role summary. Thus final HTML:

  About the role

  We are seeking a Cloud Security Engineer Intermediate to provide hands-on cloud security support for a 24x7 FedRAMP High AWS GovCloud environment. The role will support vulnerability management and patching, hardened cloud images, CI/CD security, continuous monitoring and threat detection, backup and data protection, and cloud security compliance.

  Headquartered in Leesburg, Virginia, Zenius Corporation is a HUBZone-certified small business. Zenius specializes in providing Grants Management, IT Modernization, Acquisition Management, and Financial Management services to Federal agencies. Zenius is selected by Inc 5000 as one of the fastest-growing companies in the DC Metro Area, awarded in 2025, 2024, 2021, and 2020. Zenius is also listed by Financial Times as one of the fastest-growing companies in the Americas in 2021. Zenius is an awardee of 2019 Best of Leesburg winner (Business Management