Case Study · Government

UAE Federal Entity Modernizes SOC with Cortex XSIAM

Legacy SIEM to AI-native in 18 weeks.

How a UAE federal entity replaced its legacy SIEM with Cortex XSIAM in 18 weeks, consolidating telemetry from 30+ sources and aligning to NESA Information Assurance Standards reporting.

UAE federal government entity, NESA-designated critical infrastructure

18 weeks
End-to-end migration
30+
Telemetry sources consolidated
NESA
Aligned reporting
EN/AR
Bilingual delivery
01
The challenge

Legacy SIEM at end-of-cycle and NESA pressure

The federal entity ran a legacy enterprise SIEM that was approaching end of cycle. License costs were rising. Detection content had drifted. The SOC team was firefighting alerts rather than hunting threats. NESA's technical-safeguard requirements had also tightened expectations on logging retention, integrity, and reporting. The legacy SIEM met the controls technically but produced reports the audit team had to massage manually. The entity weighed continuing on the legacy platform, moving to a cloud-native alternative, or modernizing to XSIAM with the rest of the Palo Alto stack already deployed.

"We needed to modernize the SOC and the regulator was going to start asking sharper questions. CWS delivered both at once and the NESA mapping artifact saved our compliance team weeks of work."

Director of Information Security, UAE federal entity

Why CWS

Four reasons CWS won the engagement.

  • Federal-grade engagement experience

    CWS engineers had delivered to federal-entity standards previously, including security-cleared workflows and federally-acceptable documentation in Arabic.

  • Cortex XDR continuity

    Existing Cortex XDR deployment integrated natively into XSIAM. No wasted investment.

  • Senior content authoring

    Detection content migrated from legacy SPL-style queries to XQL with senior-engineer review on every detection rule.

  • NESA mapping as a deliverable

    Compliance artifact produced alongside the technical migration, not as an afterthought.

02
Timeline

Five phases. Defined ownership.

  1. Phase 1

    Discovery and content audit

    Three weeks. Inventoried 30+ telemetry sources, audited existing detection content, mapped NESA control requirements to XSIAM content packs.

  2. Phase 2

    Data source onboarding

    Five weeks. Onboarded each telemetry source into XSIAM with parsing validation. Sources included PA-series NGFW, Cortex XDR, AD, DNS, web proxy, email, and 20+ application logs.

  3. Phase 3

    Content migration

    Five weeks. Migrated 80+ detection rules from legacy SPL to XQL with senior-engineer review. Custom NESA-content pack built. Operations runbooks updated.

  4. Phase 4

    Parallel run

    Three weeks. XSIAM ran in parallel with legacy SIEM. Detection coverage validated. Operations team trained on XQL.

  5. Phase 5

    Cutover and decommission

    Two weeks. Legacy SIEM decommissioned after parallel-run validation. Operations handed over to entity SOC team.

"We needed to modernize the SOC and the regulator was going to start asking sharper questions. CWS delivered both at once and the NESA mapping artifact saved our compliance team weeks of work."

Director of Information Security, UAE federal entity

03
Impact

What changed after the engagement.

  • 30+
    telemetry sources consolidated
    Single XSIAM data lake replaced legacy multi-source SIEM
  • 80+
    detection rules migrated
    Legacy SPL content rewritten in XQL with senior-engineer review
  • NESA
    compliance pack delivered
    Custom NESA-aligned content pack as engagement deliverable
  • 18 weeks
    end to end
    From kickoff to legacy SIEM decommission
  • EN/AR
    bilingual artifacts
    Engineering documentation in EN; executive briefings and audit artifacts in AR
  • Lower
    operational overhead
    AI-native correlation reduced alert volume and freed analyst time for hunting
What's next

Where the engagement is heading.

The entity is now expanding XSIAM coverage to additional federal sub-entities under a federal-wide SOC consolidation initiative. CWS continues to author detection content and run quarterly tuning sessions.

Ready when you are

Modernize your SOC.