
Infrastructure
The robust and scalable infrastructure underpinning Tiller Technolgies SaaS products is hosted entirely within Microsoft Azure, a leading global cloud platform. Our strategic choice allows us to leverage Azure's world-class security capabilities, unparalleled availability, and extensive global network to deliver a highly reliable and scalable service. This section provides information on our infrastructure architecture design and the operational controls implemented to ensure the continuous availability, resilience from data encryption to disaster recovery and monitoring.
How does Tiller host its platforms?
Tiller Technologies leverages the robust, virtualised infrastructure provided by Microsoft Azure data centres strategically located in Dublin, Ireland, and Amsterdam, Netherlands. This choice of infrastructure provides was based on the exceptional quality, security, and resilience provided by Azure, crucial for handling sensitive data and ensuring continuous service availability. Azure's state-of-the-art facilities are designed with multiple layers of physical and digital security, and geo-redundancy for disaster recovery, ensuring that data remains protected and services are resilient against disruptions. Tiller further enhances this by requiring confidential data stored in those data centres to be encrypted both at rest and in transit, and by maintaining comprehensive backup procedures for all cloud-stored data

Tiller Technologies' use of Azure data centres which are certified to the ISO/IEC 27001:2022 international standard for information security, with annual surveillance audits confirming ongoing compliance. Tillers own commitment to data and system integrity is underscored by our own adherence to the rigorous information security standards. We also align with the ISO/IEC 27017 code of practice for information security controls in the cloud and ISO/IEC 27018 for the protection of personally identifiable information (PII) in the cloud. This dedication, combined with our robust availability management policy and incident response plans, ensures that Tiller's infrastructure and services provide a secure, reliable, and highly available environment for our platforms and customer data.
How does Tiller ensure Verify by Tiller can maintain its performance under heavy load?
The Verify by Tiller platform has been specifically designed and developed to be scalable. All our services are hosted on virtualized infrastructure, a core component that enables rapid and dynamic scaling to meet demand. This virtualized infrastructure and architecture allows us to efficiently scale "up" by adding additional performance resources when needed and to scale "out" by expanding the number of concurrent operations, ensuring consistent high performance even during peak loads.

To facilitate seamless and efficient communication across our distributed software services, Tiller Technologies employs an Enterprise Service Bus (ESB) as its middleware communication layer. The ESB is instrumental in enabling data communication in a decoupled, scalable, and reliable manner, preventing single points of failure and allowing individual services to evolve independently without impacting the overall platform.
For database scalability, Azure SQL Server Elastic Pools utilising Database Transactional Unit (DTU) based configuration optimising the database storage, compute and IO usage.
What data loss prevention (DLP) strategies do you employ?
Tiller follows a standard 7 step strategy to appropriately manage the data it holds. This approach to DLP, is designed to prevent sensitive data from leaving our controlled environment without authorization. To do this we have implemented processes that identify, monitor, and protect data at rest, in motion, and in use across our systems.
Our strategy integrates seamlessly with Azure's native security capabilities, leveraging its advanced features to detect anomalous activities, and enforce granular access controls. We continuously refine our DLP measures based on ongoing threat intelligence and regular assessments, ensuring that our defences evolve to counter emerging risks and maintain the confidentiality and integrity of your data.
Our 7-step DLP strategy:
Prioritise data based on sensitivity, ownership, volatility
Categorise data based on type, location, storage, retention
Risk classification based on access, visibility, change control
Review & monitor based on priority, category & risk, review and ensure the data is under appropriate control and management. Establish a review frequency based on the priority & risk
Effect a reporting structure for key stakeholders to communicate current status, risk & incidents effectively
Effect training to both technical and administrative staff on the controls and monitoring procedures and policies
Effect control steps as part of the change and incident management processes, to ensure any changes or incidents are affected in line with the DLP strategy
How do you ensure compliance with the Data Protection Act in regard to information held on hosting platforms like Azure?
Tiller as part of its selection process for host provider took the Data Protection Act requirements into careful consideration. Microsoft has been a leader amongst providers, ensuring its Azure services and the contracts that govern them are fully compliant with UK and EU regulations. The Data Protection Act requires companies using cloud services and the cloud providers themselves, to mitigate for the following:
Implementing retention effectively in the cloud. We ensure that PII data held is only retained in the cloud databases, backups etc. for the period required to perform our services and that data is deleted at the end of that period.
Cloud provider breach response and notification. We have confirmed that our agreements with Microsoft Azure ensure their compliance with regulatory obligations for notification and mitigation support in the event of a breach.
Processing of personal data outside the European Economic Area (EEA). Tiller only uses Azure resources and storage hosted and maintained within the EEA. We currently use Azure datacentres in Dublin & Amsterdam.
Data portability & data ownership. Our Azure agreement (Microsoft Online Agreement Addendum Financial Services) explicitly ensures provision for data export and our services include export to machine readable formats. The addendum also ensures our compliance with the FCA's for firms outsourcing to the 'cloud' and other third-party IT services.
Risk management. Our cloud provider, Microsoft Azure is subject to our Data Protection Impact Assessment process. Also, our agreement with Microsoft Azure ensures there is a right to access independent audit reports on their service available via their Service Trust Portal: https://servicetrust.microsoft.com/ViewPage/PrivacyDataProtection
Security of Privacy. Azure was selected as our cloud provider as they meet all UK and international data protection and security standards, and those standards are regularly assessed and . with the results accessible. https://servicetrust.microsoft.com/viewpage/PenTest
Describe Tiller's Disaster Recovery (DR) plan and its targeted and in case of a primary data centre failure.
Tiller's BCP (Client Product Services DR Plan) outlines contingency planning for the event of a loss of critical service from its Azure cloud hosting provider. For a standard DR situation involving a full failover of all Verify by Tiller services to its secondary data centre at Azure, which is hosted in a separate georedundant region, the target RTO is 24 hours (within 1 business day), and the target RPO is 4 hours. In all failover DR tests and simulated critical failure modes, Tiller achieved a significantly quicker RTO time.
For non-critical issues, not requiring failover to an alternate data centre there would little if any disruption to services.
What system capacity and life planning processes do Tiller follow?
Tiller regularly reviews system capacity and performs life planning to ensure consistent and reliable service availability. This involves active monitoring to manage of our systems performance, employing threshold alerts to identify unplanned spikes in usage of response times, and implement automatic scaling to manage those events.
The planning also includes addressing security and maintenance patching, as well as end-of-life dates for operating systems and components that the system relies on. Managing the testing and deployment of the Maintenace patches and for end-of-life events managing the seamless transition over to alternative software or services.
How does Tiller ensure that its operating procedures and practices are documented, reviewed, and endorsed to maintain operational integrity?
Tiller has documented procedures and policies which cover all aspects of its operations and systems activity and environments. We have implemented the ISMS framework for operational and data governance, which is a its tailor-made framework for regulated and supervised businesses.
Tiller undertakes procedure for management reviews for all new documentation or where significant changes have been made. We employ a governance structure with clearly defines roles, responsibilities, and authorities for the management and review of changes. The IT and Operations Committee itself reports to and is answerable to our Executive Committee (Exco). The Exco is ultimately responsible for reviewing and approving all key policies and procedures, ensuring that approved changes are consistently reflected across the organisation and in line with company strategy.
All documentation pertaining to operational requirements is reviewed as part of the annual review process. This systematic approach ensures that operational processes are formalized, consistent, and regularly updated to reflect best practices and changes.
Available Supporting Infrastructure Documents
The following infrastructure related supporting documentation is available via the request form below
TTL - ISMS-DOC-A05-3 Cloud Computing Policy
TTL - ISMS-DOC-A05-4 Cloud Service Specifications
TTL - ISMS-DOC-A08-2 Information Classification Procedure
TTL - ISMS-DOC-A12-2 Change Management Process
TTL - ISMS-DOC-A12-4 Anti-Malware Policy
TTL - ISMS-DOC-A12-5 Backup Policy
TTL - ISMS-DOC-A12-8 Technical Vulnerability Management Policy
TTL - ISMS-DOC-A12-9 Technical Vulnerability Assessment Procedure
TTL - ISMS-DOC-A17-2 BCP (Client Product Services DR Plan)
TTL - ISMS-DOC-A17-6 Availability Management Policy
Infrastructure Documentation Request Form
Last updated