Enterprise option
Secure deployment
For utilities with strict information-security requirements: the protections every utility has today, what the secure option adds, and what can be arranged beyond it.
What every utility already has
Each utility runs in its own environment on AWS. Nothing is shared between utilities except the public website.
- Its own database, in a private network with no route to the internet. Only the utility's own functions can reach it.
- Its own data storage, with public access blocked, encryption at rest and encrypted connections only.
- Its own sign-in system. Accounts are invite-only. Microsoft single sign-on carries your own multi-factor rules, or users can add an authenticator app.
- Its own API. Every request needs a signed-in user, and what each person can see depends on their role.
- A record of activity. Sign-ins, page views, exports, uploads and administrator changes are written to an audit trail.
- You control data use. Administrators choose whether data helps improve detection or appears in combined public statistics, and can replace meter numbers with substitute IDs before upload.
- Upload-only connector keys, which can send files but never read data, and which administrators can revoke at any time.
The secure deployment option
Available with the Enterprise plan. It is chosen when your environment is created, and your environment is built with it from the start.
Authenticator-app sign-in, required
Every password account must register an authenticator app at first sign-in and enter a code each time. Passwords must be at least 14 characters. Accounts that sign in with your Microsoft account follow your own multi-factor rules.
An encryption key made for you
Your database and data files are encrypted with a key created for your utility only. It rotates every year automatically.
A key switch you control
Name up to five of your own administrator accounts. They can disable the key, which makes all of your data unreadable immediately, and enable it again. They can turn the key off but cannot use it to read your data.
Built automatically
Your environment is created from our setup page by the same automated process as every other utility, with no manual build steps.
| Benefit | Trade-off to know about |
|---|---|
| Every password sign-in has a second factor, so a stolen password alone is not enough. | People need an authenticator app. A lost phone means an administrator resets that user's sign-in. |
| A key dedicated to you, with a switch you can pull to cut off all access to your data. | If the key is disabled, the service stops for your users until it is enabled. Deleting it is permanent and takes at least 30 days, with a cancel window. |
| Encryption keys are separate from every other utility. | Fixed when the environment is created. Moving an existing utility onto it means building a new environment and loading the data again. |
| Automatic and repeatable. | Delivery by SFTP is not part of this option. Files are uploaded on the Data Imports page or sent by the connector over HTTPS. |
Further options, by arrangement
These need design work with your network and security team. They are scoped and quoted for each utility and are not part of the standard offering.
| Option | What it gives you | What it costs you |
|---|---|---|
| Private connectivity Site-to-site VPN or Direct Connect between your network and your environment. | Traffic between your network and ours does not cross the public internet. | Fixed monthly network cost, setup effort on both sides, and someone to maintain the tunnel. If it is down, the connection is down. |
| Private-only access The site and API answer only inside your network. | Nothing about your environment is reachable from the public internet. | Needs the private connectivity above. Staff outside your network, including our support staff, cannot reach the service without it. |
| Allowed network addresses Sign-in only from your office or VPN address ranges. | Stolen credentials are useless from anywhere else. | Remote and travelling staff must use your VPN. Address changes need an update from us. |
| A dedicated AWS account Your environment in its own AWS account. | The strongest separation, with billing and access you can audit on their own. | The highest cost and the longest setup. Updates are rolled out account by account. |
| A key held in your own AWS account Your AWS account owns the encryption key. | You hold the key itself, not only a switch for it. | Needs your AWS account and your key policy to be maintained. A misconfigured key policy stops the service. |
Not sure what you need? We are happy to complete your security questionnaire and talk it through with your security team.
Talk to us about a secure deployment
Tell us your requirements and we will say what is included and what would be scoped.