Control packs
A control pack is a reading of one regulatory regime, published as data. It carries guardrail and access rules that cite the regime’s controls, a rule suite that proves what those rules decide, and a page naming what it does not cover. pistra pack add copies the rules into your deployment document. After that the document is yours and the pack is not consulted again: there is no pack mode at runtime and nothing reads a pack while a request is being decided.
The identifiers a rule cites ride onto every audit record that rule decides, so a decision can be found by the control it served. The gateway carries them and never reads them: the framework and its taxonomy stay the reader’s.
4 packs ship, citing 27 controls between them. They add 11 rules, and point 12 controls at the mechanism that addresses them, where no rule can.
| Pack | Regime | Controls | Rules | Version |
|---|---|---|---|---|
sa-ndmo |
NDMO data classification | 10 | 4 | 1 |
sa-pdpl |
Saudi Personal Data Protection Law | 5 | 4 | 1 |
sa-sama-csf |
SAMA Cyber Security Framework | 6 | 2 | 1 |
sa-sdaia-ai |
SDAIA AI ethics and generative AI guidelines | 6 | 1 | 1 |
NDMO data classification. Every key carries one of the four national classification levels or is treated as confidential, personal data leaves the Kingdom only through a provider declaring the written approval, and public-classified traffic may carry no personal data. Added after sa-pdpl.
Saudi Personal Data Protection Law. Personal data the pattern tier finds is replaced before it reaches a model, and every request that carried any is recorded against the disclosure, transfer and record-keeping articles.
SAMA Cyber Security Framework. A hybrid or public cloud provider serves a Member Organization only under SAMA’s approval, one outside Saudi Arabia only under explicit approval for that, and the framework’s classification, cryptography and logging considerations are mapped to the trail.
SDAIA AI ethics and generative AI guidelines. A key classified above public, or not classified, does not reach a generative AI provider outside the entity, and the ethics principles a gateway can show are mapped to the redactions and the trail. Added after sa-pdpl, sa-ndmo.
What a pack is not
Section titled “What a pack is not”A pack certifies nothing. It is one reading of a published text, and the reading is the pack author’s rather than the regulator’s. Every control carries the citation it was read from, so a reader can check the reading against the text. Each pack’s page names what it leaves to the entity.
A pack names detectors, guardrail rules and access rules and nothing else. Providers, credentials, keys, models and the tuning of the guardrails block are the deployment’s, so adding a pack cannot change where a request goes or what it costs.
Licence
Section titled “Licence”The packs are licensed under the Apache License 2.0, in packs/LICENSE, and not under the licence the rest of pistra carries. A reading of a law is more useful to everyone if anyone can take it, correct it and publish the correction.
Related: Start from a control pack for the command and what it reports, and Test your rules before they ship for the suite each pack carries.