Evidence that never leaves your control

On your infrastructure

Sentinel is delivered as an appliance that runs on your own infrastructure or in your own cloud account. You decide where it runs and who can reach it.

Evidence gathered from Oracle stays there.

Read-only, through Oracle’s own interfaces

Sentinel reads Oracle Fusion through Oracle’s own interfaces: BI Publisher reports that Sentinel manages, and Oracle’s REST services.

Change requests are read the same way from your change management tool, with an account that only needs read access.

Where Oracle’s APIs have limitations, Sentinel reads through its own BI Publisher reports. They are kept only in Sentinel’s own user account, so the rest of Oracle Fusion stays as it is: Sentinel Core and Compare change none of your data, setup or reports.

Deploy, when it comes, is the one exception: it will apply setup changes using only the permissions you grant, and it will never touch transactional data.

Supported connectors

Data protection and privacy

Sentinel keeps what it needs to explain activity and to evidence control, in a database inside the appliance you run. Sensitive values are masked where people do not need to see them.

You set how long people and monitoring data is kept, and older data is deleted every night.

Sentinel has a privacy notice for the people it monitors, which you can publish for them.

Signed updates and licences

Updates and licences are signed, and the appliance checks the signature before it accepts them.

Its own audit trail

Every configuration change made in Sentinel is recorded in Sentinel’s own audit trail: what changed, who changed it, and when. The tool that checks control is itself under control.

Open-source notices

Sentinel uses open-source components. Each release carries a bill of materials and the third-party notices for those components, and the notices can be read in the product under Help, About Sentinel.