Security
Built so your rig data stays yours.
Drilling data is commercially sensitive. Here is how NRG-Drill keeps each organisation separate, accounts for every screen, and makes sure you can always take your data with you.
Found a vulnerability? We want to hear about it.
Responsible disclosureSecurity questionnaire or a call with our team?
security-nrgdrill@alcings.comOrganisations are isolated
- Each organisation’s well data, dashboards and alarms live in its own database schema.
- Every request is scoped to the signed-in organisation; there is no code path that queries across organisations.
- Within an organisation, people only see the wells they have been granted, and the live connection checks the same grants, administrators included.
Rigsite connections
- Each cabin authenticates with a 256-bit random key. We store only its SHA-256 hash, so the key can’t be recovered from our database.
- The Transmitter connects out over HTTPS. No inbound ports are opened at the rigsite.
- Org admins can limit which kinds of source each facility may send. Anything else is refused.
- Revoking a facility key stops that cabin sending at once.
Sign-in and sessions
- Access tokens are short-lived and kept in the browser’s memory, never in local storage. The refresh token is an httpOnly, Secure, SameSite=Strict cookie.
- One active session per person: signing in on a new device ends the old session immediately, live connections included, and tells the old device where the new sign-in came from.
- Accounts lock for 5 minutes after 5 failed attempts, and sign-in endpoints are rate-limited.
- Admin password resets issue a one-time temporary password that must be changed before anything else.
- Platform administrators, who run the service, sign in with an authenticator app and have no access to any organisation’s data screens.
Location restriction
- Sign-ins can be limited to the countries an organisation operates in, checked at sign-in and on every token refresh.
- It can run in report-only mode first, so you see what would be refused before enforcing it. Unknown countries are never refused.
- Individual people, such as travelling staff, can be exempted.
Audit trail
- Sign-ins, failed sign-ins, password resets, session revocations, licence changes and exports are recorded.
- Your organisation’s admins can read your audit log at any time.
Your data
- You own your rig data. We process it to provide the service, under our Data Processing Addendum.
- Export any well’s data as CSV or LAS 2.0 at any time (up to 31 days per export).
- Data is kept for the retention period in your licence and removed a whole month at a time after that.
- If your licence lapses, your rig data keeps being stored through the grace period, so nothing is lost while it’s renewed.
What we record about use
- While the web app is open and visible, it records once a minute that it is being viewed, with the well and dashboard shown. Nothing is recorded while the page is hidden or closed.
- These records produce usage reports for your organisation and are deleted after 90 days; daily totals are kept.
- Wall displays and platform administrators don’t report usage.
Questions from your IT team?
We’ll walk them through the architecture, answer your security questionnaire, and connect a test cabin so they can see the traffic for themselves.