Saudi Arabia
In the Kingdom: your environment, your regulators, your language.
Inlinea runs the same platform in every region; in the Kingdom of Saudi Arabia that means single-tenant environments on Saudi soil, a Workspace that follows the Digital Government Authority standard in Arabic, and controls mapped to the frameworks Saudi buyers name.
- environment per customer
- 1
- Single-tenant: your own server, Control Center, Workspace, gateway and session engine.
- cities worldwide
- 147
- The same platform, in the Kingdom and in any other region you choose.
- languages, full RTL
- 2
- Arabic and English across the Workspace and the sign-in pages.
Residency
What stays in the Kingdom
- Identity and configurationUsers, groups, Access Rules and settings, on your tenant's own disk.
- Logs and evidenceAudit, Traffic, ZERA Access and Browser Security logs and Session Evidence, kept for the retention you set.
- Application trafficOn the agent path, encrypted end to end between devices and never readable by Inlinea; through ZERA, terminated by the gateway in your tenant.
- Internet egressSovereign Outlinks send a group's traffic out from your own data center, from your own addresses.
Government standard
A Workspace a ministry can publish
- KSA Government presetThe Digital Government Authority design foundations: second navigation bar, official bands and ribbons, Arabic first.
- Arabic and EnglishFull right-to-left layout, every visible string translatable, a typeface per script, previewed before publishing.
- Your domainThe Workspace and every Protected Service on the ministry's own domain, certificates issued automatically.
Frameworks
The frameworks Saudi buyers name
| Framework | Why it matters | Controls mapped |
|---|---|---|
| NCA Essential Cybersecurity Controls (ECC) | The Kingdom's baseline for government and critical sectors | Identity-based access, least privilege, privileged access, logging, residency |
| NCA Cloud Cybersecurity Controls (CCC) | Required for cloud services to Saudi government entities | Single tenancy, residency, logging, administrator controls |
| CST cloud service provider registration | The Kingdom's regulatory framework for cloud services | Service facts and residency published per tenant |
| Personal Data Protection Law (PDPL) | Personal data of people in the Kingdom | Residency, access by role, retention you set, deletion on exit |
| SAMA Cyber Security Framework | Banks and insurers | Privileged access, third-party access, logging, network security |
| Digital Government Authority standards | Digital government platforms | The KSA Government Workspace preset |
Inlinea's own formal status for each framework is published in the Trust Center and never rounded up.
Questions buyers ask
Where exactly is the data?
In your own tenant in the Kingdom, on its own persistent disk, with daily snapshots. The Platform page in your Control Center states the region and the residency facts.
Can Inlinea staff see our data?
The Trust Center states what Inlinea can and cannot see. Application traffic on the agent path is unreadable by Inlinea; the ZERA gateway in your tenant terminates TLS to enforce your policy.
Do you offer a mapping to NCA ECC?
A control mapping pack is available on request through the Trust Center's document request.