Aegis / Redwood Clinical - ISO 27001 Preparation
Aegis to activate Comply v2; Redwood to run ISO 27001 baseline before working session
Redwood Clinical is preparing for ISO 27001 certification, with its CISO targeting Q1 2027. Aegis introduced Kevin O'Brien as the technical lead and walked Thomas Hargrove through Comply v2's on-demand reporting engine, which maps live environment data to Annex A controls. Thomas was impressed by the granularity and multi-framework support for HIPAA, SOC 2, and PCI DSS. The team agreed to activate Comply v2, run a baseline report, and hold a technical working session in two weeks with Redwood's security analyst Priya. Aegis will send a calendar invite and a prep document before that session.
How the call went
Customer moved from a neutral-to-frustrated discussion of audit pain to clear satisfaction after seeing live-reporting capabilities and a lighter-than-expected activation path.
Opening
0Close
+18 scored turns of 39. Hover a point for the model's reason, or read the transcript.
How the conversation ran?Talk share is measured from speech time in the captured portion of the transcript.
- Questions we asked
- 4
- Questions they asked
- 4
- Turns
- 39
- Longest silence
- 2s
Who was on the call
AegisCloud
Customer
- Thomas Hargrove?Matched on an initial rather than a full name, so attribution is weaker.
What happened7
The moments the model picked out, grouped by kind. Each opens onto the turns behind it.
Issue raised1?A problem was brought up on the call.
Thomas shares that Redwood is early in its ISO journey and that a February gap assessment found significant work on evidence collection and continuous monitoring; he recalls a HIPAA audit that took three weeks.
Commitment1?Someone committed to doing something.
Kevin proposes a baseline report in the first two weeks and a technical working session; Thomas agrees and names Priya as the compliance lead.
Decision1?A decision was reached.
Thomas confirms the CISO targets Q1 2027 for the formal audit, leaving roughly eight or nine months.
Praise3?The customer said something positive.
Thomas says the live Annex A mapping is genuinely impressive and more granular than expected.
Thomas notes the multi-framework support was requested at renewal and is glad it shipped.
Thomas says the call was reassuring and that Redwood now has a path forward.
Confusion1?Someone was unclear or misunderstood something.
Thomas asks whether the Comply v2 report is a template or pulls live data from Redwood's environment.
What was promised5
| Commitment | Owner | Due | Action type | ||
|---|---|---|---|---|---|
| Send calendar invite for the technical working session with Thomas and Priya. | Kevin O'BrienAegisCloud | 10 May 2026said “two weeks out” | schedule session?Arrange, coordinate, or block time for a meeting, call, demo, working session, or walkthrough, including inviting participants and confirming attendance. | ||
| Activate Comply v2 on Redwood's tenant and complete configuration review. | No owner | 10 May 2026said “before that working session” | engineering or configuration change?Implement, deploy, fix, configure, activate, enable, migrate, backfill, or decommission a product, system, or infrastructure, including code changes and environment configuration. | ||
| Run the first Comply v2 baseline report before the technical working session. | Thomas HargroveCustomer | 10 May 2026said “before that working session” | document or write up?Write, draft, compile, update, or finalize a document, report, runbook, case note, plan, or summary, including creating shared docs and drafting communications. | ||
| Send a prep document explaining what to expect from the baseline report. | Kevin O'BrienAegisCloud | No date given | send artefact?Deliver or transmit a prepared document, report, email, or update to a recipient by sharing, emailing, circulating, or handing it over. | ||
| Include Priya on the technical working session. ComplyImplied only | Thomas HargroveCustomer | 10 May 2026said “on the next call” | schedule session?Arrange, coordinate, or block time for a meeting, call, demo, working session, or walkthrough, including inviting participants and confirming attendance. |
Themes and issues4
What the call was about, and the specific issue recorded under each theme.
| Theme | As the model phrased it?The wording the model used before mapping it to the shared taxonomy. | Issue | |
|---|---|---|---|
| Compliance?Calls about regulatory, audit, and security compliance obligations, reporting, and readiness. | compliance | iso 27001 certification preparation | |
| Compliance?Calls about regulatory, audit, and security compliance obligations, reporting, and readiness. | audit readiness | continuous evidence collection | |
| Onboarding?Calls about customer onboarding, adoption, configuration, demos, and initial product usage. | product onboarding | compliance module activation | |
| Compliance?Calls about regulatory, audit, and security compliance obligations, reporting, and readiness. | security compliance | multi-framework reporting |
Numbers stated on this call4
Values are shown exactly as they were spoken.
| Claim | As spoken | Metric | Stated by | |
|---|---|---|---|---|
| Time spent pulling logs and documentation for prior HIPAA audit | “three weeks” | effort | Thomas Hargrove | |
| Time from call date to targeted ISO 27001 audit | “roughly eight or nine months” | duration | Thomas Hargrove | |
| Redwood IT time required to enable Comply v2 | “maybe an hour” | effort | Kevin O'Brien | |
| Timeframe for running the first baseline report | “in the first two weeks” | duration | Kevin O'Brien |
Coaching5
How the AegisCloud side handled the call.
Strengths (3)
Kevin asked about Redwood's ISO journey and audit timeline before recommending a next step, aligning the proposal with the CISO's Q1 2027 target.
Daniel and Kevin offered line-by-line interpretation of the baseline report and a dedicated point of contact, which addressed the customer's anxiety about interpreting compliance output.
The team converted the discussion into concrete next steps that Thomas was able to recap back accurately.
Improvement notes (2)
The working session was proposed as 'maybe two weeks out' without confirming Priya's or the IT team's availability; the date is not firm.
Next step secured?Whether the rep locked in a concrete next step.FYIIn the recap, Thomas attributed Comply v2 activation to Daniel but then said 'Kevin's team handles the module enablement', leaving the activation owner ambiguous.
Accountability?Whether the rep took ownership.FYI
How far to trust this call
Every fact above was extracted from the captured portion of the transcript only.
9 min captured of 29 min stated. Anything said in the remaining 20 min is absent from this page.
0 turns flagged low-confidence.
- Clocks unaligned(warning)
1 participant(s) speak before joining — transcript and events are on different clocks. Do NOT derive absolute timestamps by joining these two sources.
- Partial transcript(warning)
transcript covers 29.0% of a 28.8min meeting; 19.8min after the final turn is unaccounted for
The model's own note: Transcript is partial; call span is 8.9 minutes. Substantive content present.
Extracted 2 Aug 2026 by deepseek-v4-flash · extractor v1.0.0 · schema v1.1.0 · extended thinking on · 26,211 tokens