Controls summary: what runs today and what does not yet
Updated: August 2026 · written for a review team, and meant to be read in one page
This English text is a convenience translation. If it differs from the Hebrew version, the Hebrew prevails.
Two tables. The first is what runs in the code today and can be demonstrated. The second is what does not yet, and what stands in its place until it does. A control that is not in operation appears in the second table rather than going missing from the page.
What runs today
| Control | What exactly |
|---|---|
| Encryption in transit | TLS 1.2 and above. The database is never published beyond the machine that runs the system |
| Separation between matters | Every matter is an ethical wall: default-deny, and access is granted on a need-to-know basis |
| Administrator access to content | Taking access creates a recorded, visible event in the firm's own log. There is no silent access |
| Multi-factor authentication | Hardware security keys (WebAuthn / FIDO2) and TOTP. A physical key cannot be copied and cannot be relayed by a phishing site. Making it mandatory for users is the firm's own policy |
| Audit log | Every login, access denial, permission change, settings change and model call. Retained at least 24 months, with a review screen for the administrator |
| Tamper detection on the log | Every entry is hashed together with the one before it, by a database trigger. Update, delete and truncate on the log are refused, and a nightly check names the first row that no longer matches. What we do not claim: a database superuser can edit a row; what they cannot do is leave the log looking untouched |
| A lawyer's approval before analysis | Analysis runs only after a named lawyer has approved the settings of the matter, and that approval is logged with the user and the time |
| Quote verification | Every quote is checked letter by letter against the document. A quote not found verbatim is flagged, and the fact that rested on it is downgraded |
| Local processing | Scan OCR, metadata extraction and image descriptions run on the machine itself, with no external call and no model cost |
| Running with no external call | Ingest, triage, Hebrew search, quote verification and rendering the deliverables all work with no external call at all. It can be chosen for a particular matter |
| A read-only interface for AI assistants | A token belonging to a named lawyer, the same permission check the web interface runs, nothing generative, and a quote re-verified at read time. An administrator can switch individual tools off, and every read is logged. What we do not claim: authentication against the firm's identity provider |
| Statutory retention and deletion | The retention period is computed when a matter closes and enforced in the database itself, so it holds for a maintenance script too. The classification is a suggestion a lawyer confirms in their own name, and any override carries a reason that is recorded |
| Backup | Nightly backup of the database and the document store, verified after each run, with a copy off the machine and at a second provider |
| Backup encryption | Every copy that leaves the machine is encrypted to a key whose private half is on no server. The off-box copy is locked against deletion for seven days, including against that provider's own root account |
| Restore test | Performed and documented with dates, including a restore out of the second provider and documents verified against the fingerprint on record. Not yet rehearsed: a restore onto clean hardware |
| Encryption at rest | On a private server we operate: in place, with the key served at boot from a separate machine and never stored on the machine it unlocks. On the firm's own infrastructure: full-disk encryption is your setting, and the onboarding runbook asks for it before any material lands. In both: encryption at rest protects against physical theft of the disk, not against someone who already holds privileges on a running machine |
| Export and continuity | A full export of the database, the deliverables and a list of every source file with its fingerprint. The installation makes no call back to us, the licence is checked locally, and after expiry the system moves to read-only, where viewing and export keep working |
What does not yet, and what stands in its place
| Subject | The position, and what stands in its place |
|---|---|
| ISO 27001 and SOC 2 | Not held, and we will not hang a badge we do not have. The route is written and its trigger is a firm that requires it. Until then: this page, a data processing addendum in Hebrew, and a full response to your questionnaire |
| ISO 42001 | Not held and not currently planned. In its place we completed the CSA AI Controls Matrix self-assessment |
| External penetration test | Planned before the first firm-wide deployment, and annually after that. You receive the attestation letter with scope, dates, findings by severity, and confirmation that the severe ones were remediated and retested |
| Cyber and professional indemnity insurance | Bought before signature, and the certificate is an item in the signature round |
| Full segregation of duties | We are a company of at most three people, so it is not achievable and we do not claim otherwise. Compensating controls operate in its place: automated test suites that must pass before every release, version control with a changelog handed to the customer, additive-only migrations so that going back a version needs no restore, an update tool that backs up before it touches anything and stops if it cannot, and the fact that the customer pulls the release themselves. The full list of the limits is given to a review team on request |
| Continuous integration | There is no system today that runs the tests automatically on every change. The suites are run before every release, and the running version is reported by the system itself so you can confirm what is installed |
| External code audit | None. In its place, the automated gates above and source-code escrow, which allows an independent review on the terms set in the agreement |
| Round-the-clock support | Support is in business hours, Sunday to Thursday, with a phone number for a production-down incident. We would rather say so up front than promise a rota we cannot staff |
| Availability commitment | On a private server we operate: 99.5% monthly. On the firm's own infrastructure availability is a property of your estate, so we make no commitment about a server, a network and power we cannot see |
| Background checks | Planned: a police clearance certificate, identity verification, and signed confidentiality and IP assignment for everyone with access |
| Audited financial statements | There are no audited accounts. In their place: a Companies Registrar extract, an accountant's letter and source-code escrow |
| Key-person dependency | A real dependency at this size. It is reduced by source-code escrow, a full operations runbook delivered at go-live, and the fact that the installation keeps working with no dependency on us. A named successor contractor is not yet in place |
Questions, and the full documents
This page is a summary. The full detail is on the Security and trust, and the list of providers and locations is on the Subprocessors page. A data processing addendum, the incident response procedure, a data-flow diagram and the EU AI Act classification memo are sent on request to security@makor-ai.com.