Onboarding sequence
Create the client entity first. This provisions an isolated tenant with its own device inventory, risk list, audit log, and report scope. Nothing from one client is visible from another.
Then invite the operators who will manage that client and assign them roles. With the entity in place, agent rollout and rule configuration can proceed against a clean, scoped environment.
Three-tier hierarchy
Secuno uses a Global Admin, Partner, Client hierarchy. The Global Admin sees the whole estate. A Partner sees the clients assigned to it and can manage operators and policy within that scope. A Client scope is a single managed organisation.
Isolation is enforced by the database itself, not just by application code: a query that forgets its tenant filter returns nothing, so a Partner cannot read another Partner's clients even by manipulating a request. This is what lets one Secuno instance manage hundreds of clients without cross-tenant leakage.
Agent rollout
Deploy the agent to the client's devices using your existing software distribution, such as an RMM, GPO, or Intune. The agent registers itself, generates its Ed25519 keypair, and reports its first full inventory.
Once the first inventory lands, CVE correlation runs and the client's initial risk posture appears. There is no separate scan step to schedule. Correlation is continuous from the first report.
SLA configuration
Set remediation windows per severity for each client. Critical, High, Medium, and Low each get a configurable deadline. The SLA engine surfaces overdue risks immediately rather than letting them slip silently.
Because SLAs are per client, you can run a stricter policy for a regulated client and a lighter one elsewhere from the same console. Auto-escalation can raise severity if a risk stays open past a threshold.