Security that follows the process
What a person can do comes from the business processes in their roles. Sign-in, approvals, sessions and every security event are designed to stand up to an audit.
Sign-in
Single sign-on with OpenID Connect (for example Microsoft Entra ID), or passwords with an authenticator-app second factor. Lockouts, re-authentication for sensitive changes and server-side sessions.
Roles from processes
Roles are sets of business processes; a person is trained on a process before it is in their role. Separate workspaces keep teams' data apart.
Two people, not one
Basis changes, rule changes, privileged roles, password resets and weaker sign-in settings each wait for a second person.
Tamper-evident log
Every sign-in, change, download and approval in a hash-chained security log, exported to your SIEM and anchored outside the application.
Keys and data
Pseudonymisation keys per workspace, wrapped under a master key; authenticator secrets sealed; database connections over verified TLS.
Browser hardening
Secure cookies, a strict content security policy with no inline script, spreadsheet-formula neutralisation on every export.
Talk to us about security
We'll walk your security team through sign-in, roles, approvals and the security log, and share the assessment.
Or email hello@autoimpact.co.uk · Ask for the brochure