Skip to content

Scattered facts.One truth you can prove.

Assertor sits above all your systems, whoever made them. Ask who can do what. Get one answer, with proof.

One question. Every system.

Every system knows a piece.

Here, four systems prove one sentence about one person. Point at a card to see which words it proves.

Maria Lopez can change employees' bank details and release payments.

Two powers in one hand. Her request was approved for payroll only.

Framed from 4 systems

ERP Core banking Identity Service desk

Each fact comes from the system that knows it. Together they frame one sentence.

Illustration with a made-up person.

One layer above every system you run.

Each kind of system knows its own part. Assertor reads them all and frames the whole, whoever made them.

AssertorOne question. One answer you can prove.
ERPRoles and powers: who can pay and approve
HRPeople: who they are, where they work
IdentityAccounts: which are active, and for whom
Core bankingPayments: who can release them
Service deskRequests: what was asked, what was approved
CloudData: who can open what

Whoever made them

  • Oracle
  • SAP
  • Workday
  • Salesforce
  • Microsoft
  • Temenos
  • ServiceNow
  • Atlassian

What an answer looks like

Talk about security with your own data.

Plain wordsAsk the way you would ask a colleague, in English or Arabic.

One finished sentenceThe model sees the question and this sentence. Never a table.

Question

Who can change employees' bank details and also release payments?

Answer

Maria Lopez can do both. Her request was approved for payroll only.

The path

  1. PersonMaria Lopez
  2. RolePayroll Manager
  3. PowerChange bank details
  4. Whose recordsEmployees' bank details

What this answer read

ERP Core banking Identity Service desk Cloud: not read yet

Illustration with a made-up person.

The pathFrom the person, through each role, down to whose records.

Its marksOne mark lights for each system the answer read.

No guessingWhat is not read yet is named, never filled in.

How it works

  1. Connect each system, read-only

    A guide walks your team through it, step by step. Assertor only reads.

  2. Ask in plain words

    In English or Arabic, the way you would ask a colleague.

  3. The facts come together

    Each system answers for what it knows. Assertor frames the whole.

  4. See the path

    From the person, through each role, down to whose records.

  5. Take the report

    The full check, ready for the auditor.

Built to be trusted

Read-only

Assertor never writes to your systems. It reads, and it shows what it read.

The model never sees a table

It sees the question and the finished sentence. The numbers come from fixed queries.

Isolated tenant per customer

Each customer gets its own isolated tenant, kept where you agree.

Not read yet, said plainly

If a system is not read yet, Assertor says so. It never fills the gap with a guess.

For the auditor

The full check, ready for the auditor.

Take it all as one full-check report. The same answers and the same proof, with what was read and what was not.

Glass data cards from many systems stream along gold light into one lit frame.

One truth you can prove.

Assertor, by Nessort. Shown here with made-up people.

Talk to us

For business, audit and IAM teams

If your teams answer to auditors about who can do what across your systems, we would like to show you Assertor on your own questions, read-only, and hear how you prove access today.

For investors and partners

Assertor grows out of Nessort's work in identity architecture and assurance, beside Ordivor and Authivor. If you would like to follow it or build with it, write to us.

Write to Nessort info@nessort.com
AssertorThe evidence layer: who can do what, since when, and who says so.You are here
OrdivorChange access across every system. One AI helps you write the plan, another checks it, a person decides.
AuthivorWho gets into Oracle EBS, and why.

All products · nessort.com/products

ASSERTOR A Nessort product Nessort