Khasm · PROGRAM ROADMAP

A phased, fully-funded program from core attack library to fleet-wide AI coverage

Khasm is scoped as a multi-phase build, not a single release. Each phase below carries its own investment, team, budget breakdown, and exit-criteria milestones, sequenced so that later phases draw directly on the attack-library and compliance work completed earlier — no phase starts until its dependencies are met.

SAR 9,000,000
Total program investment
12 months
Total program duration
3
Sequenced phases

Core attack library & findings register

Planned

Phase 1 — core platform buildout

4 monthsSAR 3,200,000

Resources

Attack-library engineers3 FTE

Build the initial prompt-injection and jailbreak attack suites against representative LLM architectures.

Platform engineers2 FTE

Build the campaign runner, findings register, and transcript-capture pipeline.

Compliance lead1 FTE, part-time

Aligns reporting to OWASP LLM Top 10, SAMA FEER, and NCA ECC-2 patterns.

Program manager1 FTE

Owns cross-workstream sequencing, reporting, and design-partner readiness.

Budget breakdown

Engineering & platform development

Attack-library engine, campaign runner, findings register, and transcript-capture pipeline.

SAR 2,000,000
Compliance & reporting alignment

OWASP LLM Top 10, SAMA FEER, and NCA ECC-2-aligned reporting formats and documentation.

SAR 500,000
Design-partner pilot readiness

Onboarding tooling and integration test rigs against representative LLM copilots and agents.

SAR 500,000
Contingency

Reserve against attack-library and integration-timeline risk.

SAR 200,000

Plan of action

  1. 1
    Build the initial prompt-injection & jailbreak attack suiteAttack-library engineering · 6 weeks

    Cover the OWASP LLM Top 10 bypass categories against representative LLM architectures.

  2. 2
    Build the campaign runner and findings registerPlatform engineering · 8 weeks

    Every successful bypass captured as a reproducible transcript, not a severity score alone.

  3. 3
    Align reporting to OWASP LLM Top 10, SAMA FEER, and NCA ECC-2Compliance lead · 6 weeks

    Produce report formats regulators and design partners already recognize.

  4. 4
    Sign first 2-3 design-partner letters of intentProgram manager · 10 weeks

    Confirm the LLM copilots and agents the first live campaigns will run against.

Activities

Prompt-injection & jailbreak attack library

Planned

Continuously updated adversarial prompt suites testing the latest bypass techniques.

Owner Attack-library engineering

Findings register with transcript proof

Planned

Every successful attack captured as a reproducible transcript.

Owner Platform engineering

Depends on Prompt-injection & jailbreak attack library

OWASP LLM Top 10, SAMA FEER & NCA ECC-2 alignment

Planned

Reporting formats and evidence trail aligned to recognized frameworks.

Owner Compliance lead

Sovereign hosting for attack transcripts

Planned

Attack transcripts and model outputs hosted and retained inside the Kingdom by default.

Owner Platform engineering

Depends on Findings register with transcript proof

Exit-criteria milestones

  • ✓Prompt-injection and jailbreak attack suite validated against representative LLM architectures
  • ✓Campaign runner and findings register live with transcript capture
  • ✓OWASP LLM Top 10, SAMA FEER, and NCA ECC-2-aligned reporting formats approved
  • ✓2-3 design-partner letters of intent signed

Pilot deployment & hardening

Planned

Phase 2 — pilot deployment & hardening

4 monthsSAR 3,000,000

Depends on Core attack library & findings register

Resources

Agentic security engineers2 FTE

Build and validate tool-misuse attack campaigns against agents with real tool/function access.

Integration engineers2 FTE

Connect design-partner LLM copilots and agents into continuous attack campaigns.

Pilot lead1 FTE

Owns pilot success criteria and design-partner relationships end to end.

Program manager1 FTE

Continues cross-workstream sequencing and pilot reporting.

Budget breakdown

Agentic tool-misuse & data-leakage engineering

Tool-misuse attack campaigns and data-exfiltration probes for agentic systems.

SAR 1,400,000
Design-partner integration

Connecting production LLM copilots and agents into continuous campaigns across pilot sites.

SAR 900,000
Pilot operations & customer success

Pilot-cohort account management and findings-remediation support.

SAR 500,000
Contingency

Reserve against integration and remediation-timeline risk across the pilot cohort.

SAR 200,000

Plan of action

  1. 1
    Deploy continuous campaigns against the first design-partner systemIntegration engineering · 4 weeks

    Connect the first production LLM copilot or agent and go live with continuous attack campaigns.

  2. 2
    Ship agentic tool-misuse and data-leakage attack campaignsAgentic security engineering · 10 weeks

    Extend the attack library from text-only jailbreaks to tool-calling agents and data-exfiltration probes.

  3. 3
    Harden remediation SLA and automatic re-test workflowPlatform engineering · 6 weeks

    A fix ships, a re-test runs automatically, and the finding only closes once it passes.

  4. 4
    Run a structured pilot review cyclePilot lead · 12 weeks

    Track finding volume, time-to-fix, and re-test turnaround against baseline.

Activities

Agentic tool-misuse testing

Planned

Tests whether an agent with tool or function-calling access can be coaxed into an unauthorized action.

Owner Agentic security engineering

Depends on Prompt-injection & jailbreak attack library

Data-leakage & exfiltration probes

Planned

Tests whether a system can be tricked into revealing its system prompt or another user’s data.

Owner Agentic security engineering

Depends on Prompt-injection & jailbreak attack library

Remediation SLAs & automatic re-test

Planned

Critical and high findings carry a fix-by clock, with re-test scheduled automatically after a fix.

Owner Platform engineering

Depends on Findings register with transcript proof

First design-partner pilots

Planned

Continuous campaigns running against 2-3 design-partner production LLM copilots or agents.

Owner Integration engineering

Depends on OWASP LLM Top 10, SAMA FEER & NCA ECC-2 alignment, Sovereign hosting for attack transcripts

Exit-criteria milestones

  • ✓First design-partner LLM system under continuous attack campaigns
  • ✓Agentic tool-misuse and data-leakage attack campaigns validated in a live pilot
  • ✓Remediation SLA and automatic re-test workflow live
  • ✓Pilot performance report validated against baseline

Fleet-wide expansion & certification

Planned

Phase 3 — fleet-wide expansion

4 monthsSAR 2,800,000

Depends on Pilot deployment & hardening

Resources

Platform engineers2 FTE

Build the multi-system fleet view across an organization’s full AI estate.

Attack-research engineers2 FTE

Track and add emerging jailbreak and tool-misuse techniques to the attack library.

Enterprise account lead1 FTE

Opens and manages expansion into SAMA-regulated and NCA-regulated enterprise networks.

Compliance lead1 FTE, part-time

Owns the ISO 27001 certification audit.

Budget breakdown

Platform engineering (fleet view)

Multi-system fleet dashboard and cross-system findings rollup for a full AI estate.

SAR 1,200,000
Attack-library research & expansion

Continuously updated jailbreak and tool-misuse techniques as new bypass methods appear.

SAR 800,000
Enterprise market development

Expansion into SAMA-regulated and NCA-regulated enterprise networks beyond the pilot cohort.

SAR 500,000
Certification & scale infrastructure

ISO 27001 certification audit and infrastructure scaling for a multi-system fleet.

SAR 200,000
Contingency

Reserve against certification-timeline and enterprise-procurement risk.

SAR 100,000

Plan of action

  1. 1
    Design and deliver the multi-system fleet viewPlatform engineering · 10 weeks

    One rollup view across every registered LLM copilot and agent, for teams running more than one system.

  2. 2
    Stand up the attack-library update pipelineAttack-research engineering · 8 weeks

    A recurring process for tracking and shipping emerging jailbreak and tool-misuse techniques.

  3. 3
    Open first enterprise expansion accountsEnterprise account lead · 14 weeks

    Extend the design-partner model into additional SAMA- and NCA-regulated enterprise networks.

  4. 4
    Complete ISO 27001 certification auditCompliance lead · 12 weeks

    Close out formal certification building on the architecture pre-aligned during phase 1.

Activities

Multi-system fleet view

Planned

A rollup view across every registered LLM copilot and agent for teams running more than one system.

Owner Platform engineering

Depends on First design-partner pilots

Attack-library updates for emerging techniques

Planned

Continuously updated jailbreak and tool-misuse techniques as new bypass methods appear.

Owner Attack-research engineering

Depends on Prompt-injection & jailbreak attack library

Enterprise network expansion

Planned

Extends beyond the pilot cohort into additional SAMA- and NCA-regulated enterprise networks.

Owner Enterprise account lead

Depends on First design-partner pilots

ISO 27001 certification

Planned

Complete formal certification building on the pre-aligned architecture.

Owner Compliance lead

Depends on OWASP LLM Top 10, SAMA FEER & NCA ECC-2 alignment

Exit-criteria milestones

  • ✓Multi-system fleet view live across every registered LLM copilot and agent
  • ✓Attack-library update pipeline shipping emerging techniques on a recurring cadence
  • ✓First enterprise expansion accounts live beyond the pilot cohort
  • ✓ISO 27001 certification achieved

Make AI red-teaming a habit, not an audit

We're selecting design-partner teams running LLM copilots or agentic AI in production for the first pilot cohort. Book a briefing to see the product and discuss fit.