Corstorphine Building Society - Security Questionnaire
Documentfinal Corstorphine Building Society · security_questionnaire · final · 2026-04-09
BB-Demo's completed security questionnaire for the Society's Enterprise evaluation, written by Theo Gallagher on 9 Apr 2026. It states no figures: availability, P1 response and price are left to the executed order form. Four open points remain.
What it says
What this says
Current to 13 Oct 26BB-Demo's completed security questionnaire for the Society's Enterprise evaluation, written by Theo Gallagher on 9 Apr 2026. It states no figures: availability, P1 response and price are left to the executed order form. Four open points remain.
What it is: a final, version one questionnaire answering the Society's security review for the Enterprise tier. It covers architecture, access control, data protection, availability, resilience and an exit plan.
Commits: nothing contractually. The text says "Nothing here is a contractual commitment until it appears in an executed order form."
Unusual: service levels are described but not quantified. Availability figures are "set in the executed order form", and the document asserts no certification.
Not settled: BB-Demo staff role design in the Society's Snowflake account is "To be confirmed". Whether member-level personal data is in scope, which certifications are required, and whether the EU residency add-on, Premium support or Sandbox are wanted are all awaiting the Society.
As found in this document
The document
Body
Corstorphine Building Society - Security Questionnaire
Status: Final, version one Completed by: Theo Gallagher, Solutions Engineer, BB-Demo Account owner: Tom Ashdown, BB-Demo Date: Thursday 9 April 2026 (also written 9 Apr 2026) Folder: Customers/Corstorphine Building Society/Security
Purpose and scope
This questionnaire records BB-Demo's answers to the security review for Corstorphine Building Society, a Scottish mutual regulated by the PRA and the FCA. The Society is evaluating the Enterprise tier so that intermediary distribution and member services share one view of each mortgage broker firm.
The answers describe the Enterprise tier as it would be delivered to the Society. Where a control depends on the Society's own Snowflake account or on a decision the platform team must confirm, the answer says so and does not guess. Nothing here is a contractual commitment until it appears in an executed order form.
How to read the answers
Read the whole document (7,953 characters)
- Answer states what BB-Demo does today, in plain terms.
- Evidence says what BB-Demo can show on request. Where evidence has not yet been attached, the entry says so.
- Owner is the BB-Demo role that holds the control.
- Anything marked "to be confirmed" is an open point, not a claim.
Section A: Architecture and data location
| Topic | Question | Answer | Evidence | Owner |
|---|---|---|---|---|
| Where the brain runs | Where is customer data processed and stored? | The company brain is built and run inside the customer's own Snowflake account. BB-Demo does not copy the Society's data into a separate BB-Demo data store as the system of record. | Architecture description can be walked through on a call. | Solutions Engineering |
| Data residency | Can data be kept in a named region? | Dedicated EU or US data residency is available as an add-on. Because the brain sits in the Society's Snowflake account, the region follows the account the Society chooses. | Order form wording if the add-on is taken. | Solutions Engineering |
| Source systems | Which systems does the brain read? | Only the systems the Society chooses to connect, such as the CRM, the helpdesk, the call recorder, Microsoft 365 and the accounting system. Each connector is configured and approved by the Society. | Connector list agreed at implementation. | Customer Success |
Section B: Access control
| Topic | Question | Answer | Evidence | Owner |
|---|---|---|---|---|
| Single sign-on | Is SSO supported? | Yes. SSO and SCIM are part of the Enterprise tier. | Tier description in the proposal and order form. | Solutions Engineering |
| Provisioning | Are joiners and leavers handled automatically? | With SCIM, user accounts follow the Society's identity provider, so a leaver removed there loses access to the brain. The Society owns the joiner and leaver process. | Configuration walk-through at implementation. | Customer Success |
| BB-Demo staff access | Who at BB-Demo can see customer data? | Access is limited to staff who need it to deliver the service and is granted through the Society's Snowflake account roles. The exact role design is to be confirmed with the platform team before implementation starts. | To be attached once confirmed. | Platform team |
| Least privilege | Can the Society restrict what the brain can read? | Yes. Each connector reads only what its credentials allow, and the Society sets those permissions at source. | Connector permission summary at implementation. | Customer Success |
Section C: Data protection
| Topic | Question | Answer | Evidence | Owner |
|---|---|---|---|---|
| Encryption | Is data encrypted in transit and at rest? | Encryption at rest is provided by the Snowflake account the brain runs in. Connections between systems use encrypted transport. Key management choices sit with the Society as the account holder. | Snowflake account settings, held by the Society. | Solutions Engineering |
| Retention and deletion | What happens to data at the end of the contract? | Because the data lives in the Society's own account, it stays under the Society's control. BB-Demo's components are removed on exit. The detailed exit steps are part of the exit plan below. | Exit plan, section F. | Solutions Engineering |
| Personal data | Is member personal data used? | Only where the Society connects a source that contains it. The Society should decide in scoping whether member-level data is in scope for the first phase. This is an open point for the Society. | Scoping notes. | Account owner |
Section D: Availability and support
| Topic | Question | Answer | Evidence | Owner |
|---|---|---|---|---|
| Availability | What availability is committed? | Enterprise carries the highest availability level in the BB-Demo tiers, with service credits for availability and for data freshness. The exact figures are set in the executed order form. | Service level schedule in the order form. | Account owner |
| Data freshness | When is data refreshed? | The nightly refresh completes by early morning customer local time on business days, on every tier. Availability and freshness are measured separately. | Refresh reporting, available on request. | Customer Success |
| Incident response | How fast is a priority incident acknowledged? | Enterprise has the fastest first-response target of the three tiers, measured in minutes rather than business hours. Premium support, with a named engineer, is an optional add-on. | Support terms in the order form. | Support |
| Testing changes | Can changes be tested before they go live? | A Sandbox is available as an add-on for Enterprise, so the Society can test connector and permission changes away from production. | Add-on description. | Solutions Engineering |
Section E: Regulatory and resilience
| Topic | Question | Answer | Evidence | Owner |
|---|---|---|---|---|
| Regulated buyer | Does BB-Demo support the Society's supplier due diligence? | Enterprise implementation includes security review support. BB-Demo will answer follow-up questions and supply documents the Society's risk team asks for. | This document and follow-ups. | Solutions Engineering |
| Third-party assurance | Which independent certifications does BB-Demo hold? | This questionnaire does not assert any certification. If the Society requires one, we will state what we hold, with evidence, in a separate reply rather than imply it here. | Open point. | Solutions Engineering |
| Operational resilience | How does BB-Demo support the Society's resilience obligations? | The Society's own Snowflake account carries the data, so the Society keeps control of continuity for its data. BB-Demo's contribution is the brain components and support, covered by the exit plan. | Exit plan, section F. | Solutions Engineering |
Section F: Exit plan
- The Society keeps its data in its own Snowflake account throughout the term.
- On exit, BB-Demo components are switched off and removed, and connector credentials are revoked by the Society.
- The Society can export pages and configuration it has built before exit.
- The Society's risk team should confirm what evidence of removal it needs. We can evidence that removal steps were carried out once they are agreed.
Open points
| Point | Owner | Status |
|---|---|---|
| Role design for BB-Demo staff access in the Society's Snowflake account | Platform team | To be confirmed |
| Independent certifications the Society requires | Solutions Engineering | Awaiting the Society's requirement |
| Whether member-level personal data is in scope for the first phase | Account owner with the Society | Awaiting the Society |
| Whether the EU data residency add-on, Premium support or Sandbox are wanted | Account owner with the Society | Awaiting the Society |
Sign-off
Completed by Theo Gallagher, Solutions Engineer, BB-Demo, on Thursday 9 April 2026. Commercial contact: Tom Ashdown, account owner, BB-Demo.
Thanks, Theo
Unusual terms
Current to 9 Oct 26- No certification asserted
- Service level figures deferred to the order form
- Staff access role design to be confirmed