Built so one compromised laptop can’t take the fleet.
IT operations software can reach every machine and every person in your organization, which makes it a target. Every Ogni product is designed around that fact. This page describes how, and is just as clear about what is still on the way.
How OgniView is put together.
Two separate trust domains
Machines and people authenticate in completely different ways. An agent’s credential can never be turned into a console login, so stealing one from a laptop gives an attacker nothing to administer the fleet with.
A credential per machine
Each agent receives its own credential when it enrolls, issued by a certificate authority on your server. One machine can be revoked without touching the others.
Encrypted in production
In production mode the server refuses unencrypted agent connections and refuses to start with placeholder secrets. You cannot accidentally run it insecurely.
Least privilege
Granular role-based permissions decide who can see and do what, down to which machines a person may act on. Accounts are created by invitation only.
Single sign-on
Sign in through Microsoft Entra ID, Google Workspace, Okta or any OpenID Connect provider, so your existing account policies apply. A local administrator login is kept as a break-glass path.
Everything is recorded
Every action in the console lands in an activity log, with who did it and when, and log retention you control.
Your data stays yours
All of it lives on your server. OgniTech has no access to your installation and receives no telemetry. Support sessions happen only when you invite us.
What we are still completing.
These items are committed before OgniView is generally available. Founding customers see the results first, including the penetration test report.
Multi-factor login
For local accounts. Accounts using single sign-on already inherit your provider’s MFA.
Penetration test
An independent test of the server, console and agent.
Signed releases
Every release and license file signed, and verified before it is applied.
Automated backups
Built-in database backups with a tested restore procedure.
How OgniDesk protects tickets and requesters.
Nothing open by default
Every page and every interface requires sign-in. The only exception is knowledge-base articles an administrator has chosen to publish. Automated tests check every route on each change.
Permissions checked every time
A person’s role and permissions are re-read on every request, so removing access takes effect immediately, including on connections already open.
Requesters see only their own
The help center shows a requester only their own tickets, only public replies and files, and never an operator’s email address.
Fixes need a person
Scripts run on a requester’s computer through a least-privilege OgniView account and wait for an operator’s approval by default.
Reporting a vulnerability.
If you believe you have found a security problem in any OgniTech product, email [email protected] with the version, a description and steps to reproduce. We will acknowledge your report, keep you informed while we fix it, and credit you if you would like.
Please do not test against a customer’s installation without that customer’s permission. Ask us and we will provide a test environment.