Security
Security starts in the data model, and every layer is built to hold if another one fails.
- Row-level
- Tenant isolation
- SSO
- Via your identity provider
- Audit trail
- On sensitive actions
- Least privilege
- Access by default
How we protect student data: tenant isolation, least-privilege access, and defence in depth.
Last reviewed 26 October 2026
Security starts in the data model. Every record carries its institution, and Postgres row-level security filters every query, so the database itself keeps each university's data apart. Access runs through your single sign-on, and sensitive actions go to an append-only audit trail. A daily automated sweep checks the database's access controls. See every control in our Trust Centre.
Defence in depth
No single control is trusted on its own. Each layer is built to hold even if another fails.
Isolate every tenant
Each institution's data is fenced off in the database with row-level security. A query can only ever see its own tenant's rows.
Authenticate through your IdP
Access runs through your identity provider. First Six links a sign-in to a known person and never creates one, and sessions can be revoked.
Grant the least access that works
Staff access can be limited to particular cohorts, degrees or campuses, and every privileged function re-checks the permission in the database.
Record what matters
Sensitive actions are written to an audit trail that can't be quietly edited, so activity stays traceable after the fact.
The controls, one by one
The specific measures that protect student data.
Tenant isolation in the database
Every tenant-owned row carries its institution and is filtered by Postgres row-level security, so separation never depends on application code.
Single sign-on
Authentication runs through your identity provider over OpenID Connect, with a documented Microsoft Entra ID walkthrough.
Session control
Your admin can revoke a person's sessions from the Team page, and staff sessions end after 8 hours of inactivity.
Hardened endpoints
Machine endpoints use bearer tokens compared in constant time, with rate limits and payload caps to blunt abuse.
Append-only audit log
Sensitive actions and reads are written to an append-only trail that cannot be edited or deleted, so you can see who did what, and when.
FAQs
Can't see your question? Ask us, or email security@firstsix.com.au.
How is one university's data kept separate from another's?
Every record carries its institution ID, and Postgres row-level security filters every query to the signed-in tenant. Because the database enforces it, an ordinary bug in app code can't read across tenants.
Can we get your security documentation for a vendor review?
Yes. Under NDA we share our HECVAT-Lite self-assessment and our security and data-handling document, and we'll complete your own questionnaire. Our subprocessor list is public.
Do you encrypt data in transit and at rest?
Yes. Traffic is served over HTTPS with HSTS, and data at rest in the managed database and file storage is encrypted by the platform.
How do you handle secrets and credentials?
Secrets live in environment configuration and a password vault, never in source control. A register records what each one can reach, and they're rotated quarterly or immediately on any suspected exposure.
What happens to access when a staff member leaves?
Removing someone at your identity provider blocks any new sign-in straight away, and an admin can revoke a live session instantly from the console.
Reviewing First Six for procurement?
Request our security pack, including HECVAT responses and the subprocessor list.
