Technical FAQ

Most frequently asked questions by the IT department

Table of Contents

Introduction

This FAQ is targeted at IT professionals and attempts to answer many of the technical questions or doubts.

Login

Find our iOS app on the app store here: Prescience iOS App

Privacy

We take your privacy seriously.

Please refer to our Privacy Policy for more details on how we manage your privacy.

Software/Hardware Requirements

Prescience is web based and will run in any modern web browser, such as; Chrome, Firefox, Safari or Edge. We recommend Chrome for the optimal experience and performance.

You don’t need any particular hardware to use Prescience.

Prescience is a fully managed service so you need nothing else than a computer or laptop.

Access Management

Prescience uses ASP.NET Identity as the backbone for user identity and access management.

We also use Web- and API key OAuth bearer tokens to secure access. Users obtain a bearer token by authenticating with their email and password.

To establish a high level of password strength, Prescience enforces the following minimum password requirements:

  • At least eight characters
  • At least one upper case letter (ABCDEFGHIJKLMNOPQRSTUVWXYZ)
  • At least one lower case letter (abcdefghijklmnopqrstuvwxyz)
  • At least one number (0-9)

To avoid brute force attacks we monitor failed login attempts and block user accounts after a number of failed attempts.

We will never reset your password for you nor will we send your password to you via email.

Upon user account creation or for password recovery purposes, we will send an email with a password reset link to your email address (username).

We store passwords in a hashed format in an encrypted database with a strict IP whitelist policy.

Passwords will never be sent to users via email.

Upon user creation or password recovery, Prescience will send an email to the email address associated with the user account. The email includes a link that allows the user to create a new password.

Currently, we do not support Single-Sign-On, but if this is a strict requirement please reach out to our our support team here: Contact Support

Currently, we do not support Two-factor authentication, but if this is a strict requirement please reach out to our our support team here: Contact Support

Currently, we do not support alternative authentication sources, but if this is a strict requirement please reach out to our our support team here: Contact Support

Hosting

No, you cannot host Prescience on-premise, nor is it in our roadmap to offer this capability.

To make setup fast and painless all customers run the latest version in the cloud.

We do not operate our own data center. Instead, instead we rely on Microsoft Azure for all our hosting needs.

Prescience is hosted physically in Microsoft Azure’s West Europe data center in Amsterdam, NL.

Some backups are geo-replicated to Microsoft Azure’s North Europe data center in Dublin, IE. 

Uptime and reliability is a primary concern for us. We use Pingdom to measure uptime.

Take a look at the Service Status page to review our historical uptime statistics

We do not operate our own data center. Instead, instead we rely on Microsoft Azure for all our hosting needs.

To learn more about physical security please refer to Microsoft Azure’s guidelines on physical security here: Microsoft Azure data center infrastructure and physical security

We do not operate our own data center. Instead, instead we rely on Microsoft Azure for all our hosting needs.

Please refer to Microsoft Azure’s hosting certification and audit page here: Microsoft Service Trust Portal.

Encryption

Yes!

All communication between web/mobile clients and the Prescience API is forced to use HTTPS/SSL protocol. All attempts to communicate via HTTP will be rejected.

Prescience uses industry-standard Secure Sockets Layer (“SSL”) to encrypt “in-transit” data sent over the Internet using a very strong SHA-256 encryption.

Prescience uses Always-On-SLL (“AOSSL”) to force encryption of all traffic and as a result, there is no non-SSL way for web or mobile clients to exchange data with the Prescience API.

Prescience uses a variety of Microsoft Azure data storage technologies. As data security is a primary concern all data is “at-rest” encrypted using 256-bit AES encryption.

For data stored in SQL databases, Prescience uses the standard built-in Transparent Data Encryption (TDE) to safely encrypt all SQL databases including associated database backups and logs. Please visit the official Microsoft Azure documentation to read more about Transparent Data Encryption.

For NoSQL data stored in CosmosDB we rely on the standard encryption that is offered as part of the CosmosDB database service. Please visit the official Microsoft Azure CosmosDB documentation to read more about at-rest encryption in CosmosDB.

Finally, for data stored in Microsoft Azure Storage Services (such as files, attachments, event data, and log entries) data is encrypted at-rest using Storage Service Encryption (SSE). For more information about SSE please visit Microsoft Azure’s official Storage Service Encryption documentation.

Data Storage

See the hosting section to learn more about with whom and where we store data.

Access to our storage account is managed and granted via our Microsoft O365 AD and further safeguarded by forced two-factor authentication. It is only the CTO and a few trusted key employees that have access to the production storage environment.

We keep point-in-time backups of our SQL databases for 35 days and weekly backups are retained for 12 months after which they are automatically deleted.

Our CosmosDB databases use the following backup policy Azure Cosmos backup policy.

Upon account termination or upon customer request Prescience shall completely remove customer data and content from the production environment. The customer data and content will remain in an encrypted format in Prescience’s historical backups for the period specified in the backup policy.

Logging and Auditing

We use Microsoft Application Insights to log request information, identity, timestamp, and IP addresses for all API requests. Security sensitive requests, such as successful/unsuccessful login, password reset, and password change are stripped of sensitive information before they are logged.

We use our own custom event logging system to log all user and API actions and events, subject to account and workspace partitioning.

Finally, we use Google Analytics to log frontend interactions in order to better understand how users interact with our web/mobile clients.

Request- and event logging files are stored within our Microsoft Azure storage account wither as tables or blob storage.

Google Analytics data is anonymized and stored in Google Analytics.

We mainly use the request logging  and Google Analytics data to identify and troubleshoot bugs and monitor overall system performance to detect and eliminate slow executing code and infrastructure bottlenecks.

We use the custom event logging to provide useful activity timelines to help users understand how data and actions evolve inside the service.

No, currently there is no interface for customers to extract their log files programmatically.

API Integration

Yes, we do!

A distinct advantage over legacy solutions is that Prescience is built API first.

Please refer to the API documentation for further details here: API documentation

API stands for Application Programming Interface.

Our API allows you to programmatically interact with Prescience. This includes the ability to lookup, create, edit, delete data or perform actions in Prescience.

API stands for Application Programming Interface and the API allows you to programmatically interact with Prescience. 

This includes methods and protocols to lookup, create, edit or delete data. In fact, our own web dashboard and mobile app use the API for all communication with our business logic and the data layer.

Customers can leverage the API to make their ERP system or other third-party solutions communicate seamlessly with Prescience. This ensures speedy synchronization and improved data quality while being a real money saver because you avoid manual double keying of data.

Please refer to the API documentation for further details here: API documentation

You have to authenticate with Prescience to receive a Bearer Token. This token can subsequently be used to call the API.

Support

Yes, we do!

All technical support is provided by our own trained staff in English.

Enterprise customers have optional priority support plans. Contact sales to learn more about priority support.

Since we are based in Denmark we offer on weekdays between 8:00 to 16:00 CET.

Support is closed on weekends and Danish bank holidays.

You can send an email to support@prescience.io or use this support contact form to create a support ticket in our Help Desk.

A member of our support team will get in touch with you as soon as possible.

Documentation

Please refer to the following documentation resources :

Help Center for product documentation articles and how-to user guides

API Documentation for developers who need to make systems integration.

Technologies

Our backend is written predominantly in C#.

The frontend (Web app) is written in JavaScript, TypeScript, HTML and CSS.

The native iOS app is using Swift.

We use a mix of different database technologies including CosmosDB, MS SQL, Table Storage, Queues and Blob storage.

Book a Free Demo