By default, clients are hosted at Hetzner's main data centre in Johannesburg with a standby micro instance at Microsoft Azure. Hetzner's data centres are all equipped with CCTV cameras and access is granted to Hetzner employees via biometric access. We try our absolute best to secure your data and prevent unauthorised access while keeping your data accessible whenever it is needed.
Clients can opt to host in Microsoft Azure's data centre in the South Africa North region by paying an extra monthly fee. Azure has more regions than any other cloud provider and they provide complaint and resilient solutions. Backups are handled by Azure and they ensure that all servers remain accessible.
Clients can opt to host TaskFlow on premises if there is a very good reason for wanting to do so. In this case it is the client's responsibility to provide us with a server and to ensure that access is restricted to the server. Clients also have the responsibility to perform daily backups and maintenance.
Our server infrastructure will improve over time. At the time of writing we are able to provide a 99.9% uptime to our clients. This excludes the on premise clients since we cannot control all the variables, such as power supply to the server and network uptime.
|Availability %||Downtime per year|
We keep 7 days full backups for each TaskFlow database. Backups are replicated via a secure channel between regions as well as to a physical location. Backups are made at 02:00 every day. Backups are not sent across the boarder - i.e. the data remains in South Africa.
Servers are constantly monitored and TaskFlow system administrators are notified whenever crucial events occur.
Your database is only accessible via your TaskFlow URL (e.g. demo.taskflow.co.za). Although all clients' databases run on one cluster there is no data sharing between clients' databases what so ever. Your database is replicated over a secure connection using key pair authentication.
Direct database access (read-only) can be provided to clients who wish to mine their data with BI tools. An email can be sent to firstname.lastname@example.org to request access. We will follow the necessary steps to ensure that the person requesting access is authorised to do so.
Login details are hashed using industry standard hashing techniques. Not even TaskFlow staff has access to your passwords. In the event that a client loses their password, the only option is to send password reset instructions. When logging into TaskFlow, your data is always transmitted via HTTPS. You can verify this from within the browser by making sure that a "lock" icon is present.
TaskFlow employees have access to the administrator account on your TaskFlow instance. We may log on from time to time in order to assist with support requests. We use our discretion to only access data that relates to the support request and we have policies in place to ensure that TaskFlow employees do not copy data without authorisation from the client.
Only a select few TaskFlow engineers have access to the server clusters. The only means of logging in is using secure key pair authentication via SSH. We only allow TaskFlow engineers access to the server clusters from our office's location (i.e. no access is granted to any IP address other than our static IP at our office).
We use a hardened Linux distribution as our operating system and have configured our firewall to only allow access on certain ports. Our servers are also resilient against DDoS attacks. We make every best effort to adhere to best practice / standards when securing our network, infrastructure and data.
TaskFlow as a framework is designed in such a way that it prevents all of the most common types of attacks:
All code changes made to the TaskFlow framework is evaluated and reviewed by TaskFlow engineers through a peer review process. In addition, our automated testing platform performs unit tests and code auditing and provides our engineers with reports that are used to determine if changes introduce any bugs or regressions.
Changes are carefully written up and compiled in a new version release document which is distributed to clients prior to deploying new versions. Opportunity for feedback is given and our engineers ensure that upgrades always result in a better product for the user.