Palo Alto Integration Engineer, MID

We need to output HTML fragment with sections: About the role (position summary), Responsibilities, Requirements (maybe combine required qualifications), Skills? The posting includes many details. We must not repeat job title. Use

for section headings. Use

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

  for prose. We must include sections only when posting has real specific content. We have location, schedule, employment type, clearance, salary range. Those are metadata; we can fold minor metadata into a short

  or drop it. We should not create Pay/Schedule/Benefits sections unless posting actually states them. It does state Salary Range, Work Schedule (Full-Time, Remote, On-site on occasion). So we could include a "Compensation" section for salary range, and maybe a "Work Schedule" section? The instruction says: Prefer a few substantive sections over many thin ones. Also: 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 combine location, schedule, employment type, clearance into a brief

  maybe under "About the role" or separate "Job Details". But we must not create Pay/Schedule/Benefits sections unless posting actually states them. It does state salary range and schedule, so we could have a "Compensation" section for salary, and maybe a "Work Schedule" section for schedule. However that might be thin. Better to combine them into a "Job Details" paragraph. We need sections: About the role (position summary), Responsibilities, Requirements (maybe combine required qualifications and preferred qualifications?), Skills? The posting includes "Core Competencies" which could be Skills. Also "Preferred Certifications". Could be under "Preferred Qualifications". We can have sections: About the role, Responsibilities, Required Qualifications, Preferred Qualifications, Core Competencies (Skills). Benefits? Not mentioned besides maybe none. So we omit Benefits. We must not include boilerplate like EEO, etc. We need to preserve all substantive information. So we need to include all responsibilities bullet points, required qualifications bullet points, preferred qualifications bullet points, core competencies bullet points, and also mention location, schedule, employment type, clearance, salary range. We need to format using

  headings,

  • for lists,

    for prose. We must not repeat job title as heading. So no heading for "Palo Alto Integration Engineer, MID". We'll just start with maybe

    About the role

    then a

    containing position summary plus location, schedule, employment type, clearance, salary? Or we could separate. Better:

    About the role

    Position summary ...

    Then maybe

    Job Details

    Location: Washington, DC – On-Site; Work Schedule: Full-Time, Remote, On-site on occasion; Employment Type: Full-Time; Clearance: Suitability Determination and ability to obtain and maintain the required Government background investigation and IT access; Salary Range: $110,000 – $140,000 annually.

    But "Job Details" might be considered a thin section but it's substantive. Could be okay. Alternatively we could embed those details in the About the role paragraph. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." So we can fold location, schedule, etc into a short

    . So we can have About the role paragraph that includes position summary and those details. Thus:

    About the role

    Digital Global Connectors (DGC) is seeking a Palo Alto Integration Engineer, MID to support the engineering, implementation, administration, and continuous improvement of enterprise Palo Alto Networks security infrastructure in a federal government environment. The Palo Alto Integration Engineer will work as part of a network and cybersecurity engineering team supporting Palo Alto Networks Next-Generation Firewalls (NGFW), Panorama, Prisma Access, GlobalProtect, Prisma Cloud, and Cortex XDR capabilities. The engineer will work closely with senior security engineers, network engineers, cloud operations personnel, and Government stakeholders to maintain secure, reliable, and compliant network security services. The ideal candidate has hands-on Palo Alto Networks experience, strong enterprise networking fundamentals, and experience supporting cybersecurity operations in environments governed by Federal security and compliance requirements. Location: Washington, DC – On-Site; Work Schedule: Full-Time, Remote, On-site on occasion; Employment Type: Full-Time; Clearance: Suitability Determination and ability to obtain and maintain the required Government background investigation and IT access; Salary Range: $110,000 – $140,000 annually.

    Then Responsibilities: we have many bullet points grouped under headings like "Palo Alto NGFW Engineering & Administration", "Panorama & Centralized Management", etc. We need to output a list of duties. Could combine all responsibilities into a single
    with
    • items, preserving the detail. We should not lose any duty. We'll need to parse the responsibilities section. Let's extract responsibilities bullet points: From text: Palo Alto NGFW Engineering & Administration - Engineer, implement, configure, administer, and troubleshoot Palo Alto Networks Next-Generation Firewall infrastructure across perimeter, internal segmentation, data center, and cloud-connected environments. - Develop and maintain firewall security policies using Palo Alto Networks App-ID, User-ID, and Content-ID capabilities. - Configure and maintain threat prevention capabilities, including antivirus, anti-spyware, vulnerability protection, URL filtering, file blocking, WildFire, and DNS Security. - Assist with the implementation and maintenance of SSL/TLS decryption policies. - Perform firewall rule reviews, rule-base optimization, shadow-rule identification, and security policy lifecycle management. - Troubleshoot firewall connectivity, performance, routing, and security policy issues and perform root-cause analysis. - Analyze NGFW traffic, threat, and security logs to support troubleshooting, security monitoring, and incident investigations. Panorama & Centralized Management - Administer and maintain Palo Alto Networks Panorama centralized management capabilities. - Configure and maintain Panorama device groups, templates, shared policies, pre-rules, and post-rules. - Support onboarding and configuration management of Palo Alto Networks firewalls through Panorama. - Monitor Panorama platform health, device connectivity, synchronization, and policy deployment. - Support Panorama upgrades, patches, configuration changes, and operational maintenance. - Generate operational, security, and compliance reports through Panorama. Prisma Access & GlobalProtect - Support the administration and maintenance of Palo Alto Networks Prisma Access capabilities. - Configure and troubleshoot GlobalProtect remote-access services, gateways, agents, and authentication integrations. - Monitor Prisma Access availability, connectivity, performance, and security effectiveness. - Maintain and optimize cloud-delivered security policies, URL filtering, and threat prevention configurations. Security Operations & Threat Prevention - Monitor and analyze Palo Alto Networks threat prevention logs, WildFire results, and security events. - Assist with tuning threat prevention profiles and firewall policies to improve security effectiveness and reduce false positives. - Support cybersecurity incident response activities through firewall log analysis, traffic investigation, policy analysis, and containment support. - Assist with Cortex XDR monitoring, alert triage, prevention policy administration, and detection-content tuning. - Support the use of MITRE ATT&CK concepts in security monitoring and detection activities. Cloud Security - Assist with the administration and monitoring of Palo Alto Networks Prisma Cloud capabilities. - Monitor and triage cloud security posture and compliance findings. - Support Prisma Cloud policy configuration, alerting, reporting, and remediation tracking. - Assist with integration of Prisma Cloud findings into SIEM and vulnerability-management processes. - Support cloud security operations within AWS and/or Microsoft Azure environments. Change Management & Documentation - Prepare firewall and security-platform changes for Change Advisory Board (CAB) review. - Develop implementation plans, technical impact assessments, testing procedures, and rollback plans. - Execute approved configuration changes in accordance with established change-management procedures. - Develop and maintain technical documentation, including SOPs, runbooks, troubleshooting guides, configuration records, and operational procedures. - Maintain accurate configuration, change, and operational records. Federal Cybersecurity Compliance - Support configuration and operation of Palo Alto Networks technologies in accordance with applicable Federal cybersecurity requirements and security baselines. - Support NIST SP 800-53, FISMA, FedRAMP, NIST SP 800-207 Zero Trust Architecture, OMB Zero Trust requirements, and applicable DISA STIG requirements. - Assist with Authorization to Operate (ATO) activities, including security-control implementation documentation, SSP contributions, continuous-monitoring evidence, and audit artifacts. - Support configuration-compliance assessments and remediation of security baseline or STIG deviations. - Monitor applicable Palo Alto Networks vulnerabilities and vendor advisories and support vulnerability-remediation activities. We need to output these as list items. Could group under subheadings? The instruction says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using other headings? It says use

      for section headings (list). Likely they expect only those headings. So we should not create subheadings like "Palo Alto NGFW Engineering & Administration". Instead we should just have a single Responsibilities section with a list of all duties. That's okay; we lose the grouping but preserve all duties. That's acceptable. Thus

      Responsibilities

      with each duty as
      • . Now Requirements: we have Required Qualifications and Preferred Qualifications. Could combine into Requirements section? The instruction says use headings like Requirements, Qualifications, Skills. We could have

        Required Qualifications

        and

        Preferred Qualifications

        . That's okay because they are in the list. Or we could have a single Requirements section with both required and preferred. But better to follow the list: we can have Required Qualifications and Preferred Qualifications as separate headings. Thus:

        Required Qualifications

        list each required qualification. Similarly for Preferred Qualifications. Then Skills: we have Core Competencies. Could map to Skills section. So

        Skills

        with list of core competencies. We also have Preferred Certifications. Could be under Preferred Qualifications or maybe a separate Certifications section, but not in the list. Could add under Preferred Qualifications as part of that list. We must not invent or summarize away detail. So we need to include all required qualifications bullet points, all preferred qualifications bullet points, all core competencies bullet points, and preferred certifications bullet points. Let's extract required qualifications bullet points: From text: Required Qualifications - Bachelor's degree in Computer Science, Information Technology, Cybersecurity, Network Engineering, or a related field. An equivalent combination of education and directly relevant professional experience may be considered. - 3–5 years of hands-on experience in network security engineering, firewall administration, or a closely related discipline. - At least 2–3 years of hands-on experience with Palo Alto Networks NGFW platforms in an enterprise environment. - Demonstrated experience developing and administering Palo Alto Networks firewall security policies and threat prevention profiles. - Hands-on experience with Palo Alto Networks Panorama. - Strong knowledge of enterprise networking concepts, including: - Routing and switching - VLANs - Network segmentation - Firewall zones - IPsec and SSL VPNs - TCP/IP and network troubleshooting - Experience troubleshooting firewall connectivity, performance, and security-policy issues. - Experience analyzing firewall, traffic, and threat-prevention logs. - Familiarity with Federal cybersecurity requirements, including NIST SP 800-53, FISMA, and applicable DISA STIGs. - Experience working within formal change-management processes. - Strong written and verbal communication skills. - Ability to develop