Security built in, not bolted on.
What the software does, what we check, and what we do not claim.
Your data stays on your server
Both products are self-hosted. Tickets, documentation and credentials live in your own database, not with us.
Signed webhooks with replay protection
Outgoing webhooks can be signed (HMAC) with a timestamp so receivers can verify the sender and reject replays. Verification snippets come in five languages.
SSO that keeps local safeguards
Agent sign-in with company SSO is off by default, limited to linked agents, excludes administrators, still requires local two-factor and leaves the credential vault locked.
Loop guard and rate limits on rules
Event rules have rate limits and a loop guard, and a test drawer shows what a rule would do without side effects.
Audit trail and a last-administrator guard
Changes are audited, and the last administrator cannot be removed by accident.
Webhook URL policy
Private and internal addresses are blocked for webhooks by default; you add trusted networks explicitly.
What we check, in the open
Automated code review and scanning
Our code is also run through Aikido Security, Semgrep and CodeRabbit. These are tools we use, not certifications.
Checked on every change
Rivet Core runs secret scanning, dependency audits and static analysis on every push and pull request. A failed check fails the build.
See the checksDependencies kept current
Dependabot is set up for RivetIT and Rivet Core, so known-vulnerable packages are flagged.
Written security reviews
Rivet Core publishes its threat model and security reviews, including what was and was not run.
Read the reviewsISO 27001 control mapping
RivetIT maps all 93 ISO/IEC 27001:2022 Annex A controls to what it does, and what it does not. It is a gap analysis, not a certification.
Read the control listSelf-assessed. We have not undergone a third-party SOC 2 or ISO 27001 audit.
We build Rivet IT Ops with AI. Most of the code is written by Claude, directed by a person. Changes go to a beta environment and are tested there before release, and automated tools (CodeRabbit, Semgrep, Aikido) scan the code. People do not review every line.
Security features
Two-factor & passkeys
TOTP and passkey sign-in, with unusual sign-in alerts.
OpenID Connect sign-in
Company SSO through Authentik, Keycloak or Ory Hydra.
Roles & department access
Read, write or full access per module and department, with an audit trail.
Hardened deployment & backups
fail2ban, ufw and hardened PHP and database settings, with encrypted backups.
Self-hosted means you keep it patched
You run the server, so you control updates and backups. Take a backup, then update in Administration or by script. Found a vulnerability? Use the security policy, not a public issue. Company policies are on FoleyIT LLC.