Security
Controls you can test, evidence you can produce
Recondora is built for institutions that are inspected. Its controls are part of the product, not a policy document, and they produce their own evidence.
Segregation of duties
Force matches, closures, write-offs and record changes are proposed by a maker and approved by a different checker. The rule is enforced in the database transaction, so no screen or API call can bypass it.
Tamper-evident audit log
Every action is appended to a log in which each entry carries the hash of the one before. Administrators verify the whole chain in one click; any edit or deletion breaks it.
Write-once evidence
Every input file is fingerprinted with SHA-256 on arrival and kept on write-once object storage with retention, so the file behind a result can always be produced and proved unchanged.
Card data kept out
Card numbers are masked on ingestion and full card numbers are never stored, which keeps Recondora out of most of your card data scope.
Identity and roles
Single sign-on through OpenID Connect; users can hold several roles; control roles (audit, compliance, risk, security) cannot change operational data. Enforced MFA, finer roles, recertification and dormancy rules arrive in R1.
Tenant isolation and residency
Each customer's data is kept apart and never meets another tenant's in a query. Residency is chosen per tenant: your region, your cloud account or your data centre.
Repeatable results
Every run records the hash of the configuration that produced it, so a result can be tied to the exact rules, packs and company settings in force.
Secure delivery
Automated tests and dependency checks on every change, a software bill of materials (CycloneDX) for every build, chiseled container images that run as non-root, and an independent penetration test before every major release.
See it with your own files.
Book a walkthrough: we load sample files from two of your rails, run them through Recondora and show you every match, break and approval.