Security
Security is a set of enforced boundaries, not an adjective.
This page says what Rygor is designed to enforce, what it deliberately does not claim, how to tell us about a weakness, and how this website itself is built. It describes nothing as safe by assertion; only enforced boundaries and measured results count.
What the platform is designed to enforce
- Customer-hosted, customer-operated. Rygor runs as one compact installation inside the customer's boundary. There is no vendor control plane, no telemetry sent to us and no phone-home. Updates are signed and installed offline by the customer's IT.
- Authority outside the model. A model's output is a proposal or evidence, never an action. Every consequential step, whoever proposed it, passes through one command boundary that checks current permission and the actual network destination.
- Permission at every read. Authorization is checked at every read, search, export and dispatch, and applied before any vector-search limit, so a restricted document cannot appear in a result because it ranked well.
- Separation of concerns. Rules are evaluated by a local helper with no database, network or write credential. Agents are bounded and cannot widen their own authority. Automatic execution needs a separate, revocable grant and is suspended when corrections exceed a limit.
- Honest effects. A timeout is not treated as proof that a write failed. Uncertain external effects are held and reconciled rather than retried, so a connected system is never asked twice because a screen gave up.
- Layered defence against hostile content. Retrieved documents, model output and tool results cannot grant themselves authority. Local classifiers act as signals that hold work or route it for review; a classifier outage holds work rather than letting it through.
- Evidence. Each case closes with a signed evidence pack designed to be verified offline, by someone with no access to the platform.
We use OWASP ASVS 5.0 as our control catalogue and NIST SSDF 1.1 as our development-practice reference. Neither is a conformance claim; both are checklists we work against and report on.
What we do not claim
Rygor is an early engineering build. It has not been independently assessed, penetration-tested by a third party or certified against any standard. None of the design commitments above is a measured result until the status board says so.
- Privileged administrators are trusted. Rygor does not defend against a hostile administrator of the host it runs on, and does not claim root-resistant storage, cryptographic erasure or tamper-proof logs.
- Hosting is not compliance. Running inside the customer's boundary does not by itself satisfy any privacy, security or sector obligation. Those remain the customer's to meet, with Rygor as one controlled component.
- No high availability in the compact profile. Loss of the whole host means restoration by the customer's IT from their backups. Automatic failover is not part of the current design.
- Detection quality is unmeasured. Our content classifiers have passed connection and conversion checks only; their accuracy on Arabic and mixed-language input is not yet qualified.
Reporting a vulnerability
If you believe you have found a weakness in Rygor or in this website, write to bono@abuelnour.com. Please include enough detail to reproduce the issue and, where relevant, the version or page concerned. We acknowledge reports within five business days, keep you informed of what we do, and do not take legal action against good-faith research that respects the privacy of any data it encounters. A machine-readable version of this policy is at /.well-known/security.txt.
We do not currently run a paid bounty programme.
This website
rygor.si is a static site with no server-side code, no accounts, no forms and no third-party requests. It sets no cookies and loads no analytics. It is served with a strict content-security policy, HTTP strict transport security, frame denial and referrer and permissions policies. Its only stored value is your language preference, kept in your own browser. The source of every page is reviewed like any other change to the Rygor repository.