Corstorphine Building Society: documents logo

Security review session: scheduling

Email thread

Corstorphine Building Society: documents logo Corstorphine Building Society: documents · sales

Hannah Lowe and Euan Rattray agreed a Tuesday 10:00 Enterprise security review session. Euan asked for access control evidence, incident history and connector processing locations beforehand, as documents rather than assurances.

What was said

What this says

Current to 11 Oct 26

Hannah Lowe and Euan Rattray agreed a Tuesday 10:00 Enterprise security review session. Euan asked for access control evidence, incident history and connector processing locations beforehand, as documents rather than assurances.

Ask: Euan wants three documents before the session: how access to the brain is controlled, the incident history, and where each connector's data is processed.

Customer view: he will not close findings on a reference to another customer's review. His risk analyst will draft a paper for the board's risk committee.

Next: Hannah has held the time and promised an access model diagram and a processing table. She is checking with Ewan what incident history can be shared.

AI · claude-sonnet-5-5 · 11 Oct 2026

The thread

Updated 9 Oct 26
Typesales
Messages3
First message2026-08-17
Last message2026-08-20

Messages

  1. Hannah Lowe
    Hannah Lowe 17 Aug 2026 15:04
    to Euan Rattray
    Hello Euan, Thank you for your time on the call. To be precise about where we left it: you have a set of open findings from the architecture walkthrough, and I owe you written answers on a few of them before we sit down properly. I would like to book the Enterprise security review session for sometime next week. The short answer on the architecture is that BB-Demo runs inside your own Snowflake account, so the question of where the data is stored and who can see it is largely governed by your existing controls. The longer answer is that I would rather walk you through the access model with a diagram than have you take that on trust, and I will put the detail in writing afterwards. Could you tell me which days suit you, and who from your side should be in the room? I would suggest someone who can speak to the Snowflake roles and network configuration, as that is where most of the useful questions tend to land. Thanks, Hannah
  2. Euan Rattray
    Euan Rattray 18 Aug 2026 15:09
    to Hannah Lowe
    Hannah, Thank you. Tuesday morning would suit me, ideally from 10:00. Our platform owner should attend, as he owns the Snowflake side and can answer for the roles and network rules. I would also like our risk analyst to listen in, as she will be drafting the paper for the board's risk committee. So that the session is not wasted, I would ask that you send the following beforehand: First, please evidence how access to the brain is controlled: who has standing access, and how that access is reviewed. Second, what is the incident history for the service? A statement that there have been none is not sufficient on its own; please say what records you hold. Third, please set out where each connector's data is processed and whether anything leaves the Snowflake account at any point. I will not be able to close any of my open findings on the basis of a reference to another customer's review, so please send documents rather than assurances. Euan Rattray
  3. Hannah Lowe
    Hannah Lowe 20 Aug 2026 08:19
    to Euan Rattray
    Euan, Tuesday at 10:00 is fine and I have held the time. I will send a calendar invitation shortly, addressed to you; please forward it to your platform owner and your risk analyst, or give me their addresses and I will add them. On your three questions: First, I will send the access model with a diagram, showing the roles BB-Demo needs inside your Snowflake account and who can use them. I will put that in writing so that you have something to test. Second, the incident history. I want to check exactly what we can share before I send it, and I will confirm with Ewan on our side first. I would rather give you a correct answer a day later than a quick one I cannot stand behind. Third, the processing locations per connector. I will give you a table so you can see each source and where it is handled. If anything else is on your list of open findings that you would like covered on Tuesday, send it over and I will add it to the agenda. Thanks, Hannah On 18 Aug 2026, at 15:09, Euan Rattray wrote: > Tuesday morning would suit me, ideally from 10:00.

BB-Demo is a fictional company; every organisation and person here is invented. B-Brain is the tool. Built by site/build_site.py from the site tree, data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Brain is one place to read everything the company knows about its customers: the CRM, calls, emails, support tickets, product usage, invoices, documents, news and HR. Every page is built from those systems and the data is current to Fri 9 Oct 2026.

How to use the site

How to ask

Press Ask Brain in the header. Type a question, or pick one of the examples.

The site itself does not call an AI model; answers in Claude come from the same figures you see here.

What the data covers

DataRecords
Organisations150
People at customers573
BB-Demo staff48
Calls1,382
Email threads2,122
Support tickets789
Documents850
Deals217
Invoices187
Events49
News items84

Data as of Fri 9 Oct 2026. Text marked AI was written by the brain from the records listed in its made-from link; an AI output that cannot cite its evidence is refused and the previous text kept. Where two systems disagree (for example a contract and the CRM), the key facts show both values and mark the difference.

BB-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Brain is the tool that reads its data.

Who to contact

Email support@b-brain.example or talk to your B-Brain account team. Tell us the page address and what looked wrong; a screenshot helps.

HelpAsk B

Ask B

B-Brain · read-only