Quillmark Health: documents logo

Incident history request for vendor security review

Email thread

Quillmark Health: documents logo Quillmark Health: documents · exec

Megan Alvarez, CISO, asks Jordan Pike for a written statement of incidents in the last ninety days, covering availability, freshness, integrity and unauthorised access. She wants a reply by end of day tomorrow.

What was said

What this says

Current to 10 Oct 26

Megan Alvarez, CISO, asks Jordan Pike for a written statement of incidents in the last ninety days, covering availability, freshness, integrity and unauthorised access. She wants a reply by end of day tomorrow.

Ask: four numbered points covering events, access, root cause and fixes, and customer notification. Every item must be answered explicitly, even if there is nothing to report.

Customer view: Megan will not accept a general assurance and needs a statement to file with the review. The thread, dated 23 Jul 2026, shows the vendor review still being worked.

Next: Jordan must coordinate a written, itemised answer quickly.

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

The thread

Updated 9 Oct 26
Typeexec
Messages1
First message2026-07-23
Last message2026-07-23

Messages

  1. Megan Alvarez
    Megan Alvarez 23 Jul 2026 13:00
    to Jordan Pike
    Jordan, For the record, I am working through the open findings on BB-Demo's vendor review and need to close out the incident section before it goes further within Quillmark Health. Please describe any incidents in the last ninety days, in writing, covering the following: 1. Any event affecting availability, data freshness or data integrity for any customer environment, whether or not it was classified as a security incident. 2. Any event that involved unauthorised access, or suspected unauthorised access, to customer data or to the Snowflake accounts the brain runs in. 3. For each item above, the date it began, the date it was resolved, the root cause, and what was changed to prevent a repeat. 4. Whether any customer was notified, and how. If there is nothing to report under a given number, please say so explicitly rather than leaving it blank. I cannot accept "best effort" or a general assurance as a response. Our risk posture requires a statement I can file with the review. I would appreciate a reply by end of day tomorrow if that is feasible. If you need Hannah or anyone else on your side to contribute, please include them. Megan Alvarez, CISO

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
Organisations75
People at customers290
BB-Demo staff40
Calls784
Email threads1,169
Support tickets449
Documents477
Deals117
Invoices101
Events49
News items56

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.

Ask B

Ask B

B-Brain · read-only