Security

Built to be trusted with your operations.

Your control room runs on this, so you should know where your data is, who can reach it and how you get it back.

Where your data lives.

Your customers will ask you. This is the answer.

Hosted in the EU
Coresent runs on AWS in Frankfurt (eu-central-1). Customer data, backups and logs are stored and processed there.
Yours alone
Every record belongs to one organisation, and every request is checked against it.
Subprocessors
Amazon Web Services hosts the service. The full list is sent on request, and you are told before it changes.

Deployment.

Multi-tenant by default
Your data is kept separate from every other customer's.
Single-tenant available
A deployment of your own, for customers who require it.

Who can get in.

Guards change jobs and contracts end. Access has to follow the same day.

Your sign-in
Single sign-on through your identity provider, with users added and removed from your own directory.
Access by role and site
A guard sees the sites they work. An operator sees the control room. An administrator sets both.
Removed means removed
Take away someone's access and their open session stops on the next click.
Coresent staff
Named engineers only, for a support case you have opened, and written to your audit log.

What is recorded.

Every action in a night can be traced to a person and a time.

Every action
Who did what, to which record, when it happened and when it was recorded.
Tamper-evident
A changed or removed entry is detectable.
Yours to export
Administrators read the log in the console and export it at any time.

How the agent is controlled.

It prepares the work. People decide.

Your permissions
The agent uses the same actions an operator or an administrator uses, with the permissions of the person who asked. It cannot do what that person cannot.
Approval first
Dispatching a rover, moving a round and sending a report to a customer wait for a named person. The proposal shows its reason and its effect on the rest of the night.
Recorded
Who approved, when, and what was proposed are kept in the audit log.

When something fails.

A control room cannot wait for a vendor's office hours.

Backups
The database is backed up continuously, and restores are tested.
Recovery
Recovery targets are agreed in your service-level agreement.
Offline in the field
The guard's phone keeps scanning and recording without a connection, and syncs when it returns.

How we work.

Encrypted
In transit and at rest.
Patched
Dependencies are scanned on every build. Critical fixes ship within 24 hours.
Reachable
Report a vulnerability to security@coresent.io. We answer within two business days.

Your data, your exit.

Nothing about your data depends on staying.

How switching works

Full export at any time
An administrator starts it from the console.
Open formats
CSV and JSON for records, PDF for reports, original files for photos.

For your procurement team.

Write to security@coresent.io.

Data processing agreement
With standard contractual clauses.
Security overview
This page in more detail, with the architecture.
Your questionnaire
Send us yours. We return it completed within a week.

Built to be trusted with your operations.

Bring your security team to the demo.

Pick a time

Open times in the next two weeks.