What your CISO will ask, answered

The main security surface of a consultancy is its people. The screening, substitution and confidentiality commitments below are written into the engagement agreement. Design teams have two senior practitioners and build teams three, with James Rooney accountable on every engagement. Associates come through work he knows at first hand or referrals from people he has delivered with; nobody is recruited after a client commits. Every person on your engagement is senior, with no pyramid of juniors behind them. BS7858-standard screening (identity, right to work, employment history and criminal record checks) completed before any client access, for employees and associates alike. Every associate is contracted to written confidentiality and to your data-handling requirements before any client access. Confidentiality obligations survive the end of the engagement indefinitely.

Our default is to work on your infrastructure under your controls, rather than pulling your data out to ours. We use your identity provider, your access controls and your devices where you provide them. Working software is built and deployed on your infrastructure and designed around your organisation's policies, so there is nothing to migrate off our estate when the engagement ends. Access is requested against the principle of least privilege and time-boxed to the engagement, with a documented offboarding step on exit. Where we use our own devices, they are full-disk encrypted, MDM-managed, screen-locked and remotely wipeable. Client data is not copied to Tenhaw-controlled storage unless the engagement agreement expressly permits it. We do not retain client production data after an engagement ends; retention and deletion terms are set in the Data Processing Agreement.

Where engagement data is processed, and under what terms. Engagement data is processed in the United Kingdom by default, with EU residency available where your policy requires it. Our default is to work inside your estate under your controls, so in most engagements your data never leaves your own infrastructure. Where data does reach our systems, it is processed in the UK on encrypted, MDM-managed devices and deleted at engagement end under the terms of the Data Processing Agreement. Every engagement sub-processor is published on this page and annexed to the Data Processing Agreement, the service processors with entity, location, purpose and transfer mechanism. The model providers are named with their purpose; the contracting entity and transfer mechanism for the one you approve are set in your engagement's annex.

The full sub-processor list for consulting engagements, as annexed to the Data Processing Agreement. It is short, because delivery happens inside your estate. Google Workspace (Google Ireland Limited): business email, calendar and documents carrying engagement correspondence and client contact details, processed in the UK and EU, with any US support access governed by the UK Addendum to the EU Standard Contractual Clauses. Close (Elastic Inc., United States): customer relationship management holding client contact records, under the UK International Data Transfer Addendum and Standard Contractual Clauses. Cal.com Inc. (United States): scheduling, processing the name, email address and meeting details provided when booking a call, under Standard Contractual Clauses. Model providers (Anthropic, OpenAI and Google): only content named and approved by you in writing for your engagement, under zero-retention or enterprise agreements. The processors behind this website are listed separately in the Privacy Policy and do not touch engagement data.

What happens if something goes wrong, and how quickly you hear about it. A personal data breach affecting your data is notified to you without undue delay, and in any event within 24 hours of us becoming aware of it, as a term of the Data Processing Agreement, so your own 72-hour regulatory clock starts with time to spare. A security incident touching your engagement is raised with your named contact by the route agreed at kickoff, with an initial notification first and updates as the investigation progresses. A written incident report follows, covering root cause, impact and remediation, and we stay engaged until your own team closes the incident. Vulnerability reports to security@tenhaw.com are acknowledged within two working days, and we do not take legal action against good-faith research.

AI-accelerated delivery runs under the same engineering controls as any other build. They run in the pipeline from the first commit, and because we build on your infrastructure they run under your standards and land in your audit trail. Static analysis with quality gates, SonarQube or Semgrep or your own equivalent, runs on every commit. Dependency and vulnerability scanning, Snyk or Dependabot, on every build, with continuous alerts on newly disclosed CVEs. Secrets scanning with push protection in CI and before commit, GitHub secret scanning or gitleaks. A software bill of materials and licence provenance checks for anything we ship, so AI-generated code arrives with its supply chain documented. Protected main branches and human code review before merge, with a model-led security review of the whole system roughly every fifth prompt during a build. Independent penetration testing in the productionisation phase, scoped to the code that shipped.

Our engineers work inside client estates and client data. The rules below govern every AI tool that touches them. No client data, code or documentation goes into any AI tool that has not been named and approved by you in writing. Where you have an approved enterprise AI tenancy, we work inside it rather than bringing our own. Where you have no approved tenancy, the default toolchain is named for your review: Anthropic's Claude Code, OpenAI's models and Google's Gemini, combined for what each does best, running inside your infrastructure and aligned to your policies, and substituted for your approved stack on request. We use zero-retention or enterprise agreements with model providers so client content is not retained or used for training. Agentic systems we build for you are designed with action logging, human-in-the-loop approval gates for consequential or irreversible decisions, and an auditable trail from decision to outcome. Model and agent risk is documented during operating model design, with your second-line risk function as a co-author rather than a reviewer.

What your procurement, legal and risk teams will ask for. All of it is available during supplier onboarding. Master Services Agreement and Statement of Work templates. Data Processing Agreement including sub-processor annex, UK IDTA or EU SCCs, and Article 28 change-notice terms. Professional indemnity, public liability, employers' liability, cyber and legal expenses certificates, with the cover levels listed on this page. Liability cap agreed per engagement in the SOW, with breach of confidentiality and data protection treated separately. You own all deliverables and any code written in your environment, on payment. 30 days' notice on retainers, with a documented handover on exit.

Our own estate is small, because we deliberately hold very little. This site is a static marketing site with no customer accounts and no client data on it. Statically generated and served over TLS with HSTS, X-Content-Type-Options, X-Frame-Options, Referrer-Policy and Permissions-Policy headers set. No client data, no accounts and no authenticated area; the visitor-analytics estate is disclosed in full in our Privacy Policy. Third-party processors used by this site are listed individually in our Privacy Policy. Multi-factor authentication is enforced on every business system we operate.

Professional indemnity £1,000,000, Employers' liability £10,000,000, Public liability £1,000,000, Cyber £25,000, Legal expenses £100,000. Certificates are available during supplier onboarding. Any line on the schedule can be increased for a specific engagement, with the additional premium priced into it. Name the limit your supplier standard requires, on any call, and the increased cover is in place at that limit within three working days, ahead of contract signature. We hold no client production data and work inside your estate under your controls, which is what limits the exposure these lines answer for. Liability is capped per engagement in the Statement of Work, with breach of confidentiality and data protection treated separately.

Held today: UK GDPR and Data Protection Act 2018 compliant, as a UK-registered company; DPA with sub-processor annex available for every engagement; 24-hour personal data breach notification, committed in the Data Processing Agreement; UK data processing by default, with EU residency available where an engagement requires it; Engagement sub-processor list published on the security page and annexed to the DPA; BS7858-standard personnel screening before client access; Design and build teams have two and three senior practitioners respectively, selected through work James Rooney knows at first hand or trusted referrals; Named-tool-only policy for AI systems touching client data; Professional indemnity £1m, employers' liability £10m, public liability £1m, cyber £25k, legal expenses £100k. In progress: Cyber Essentials Plus: certification in progress; ISO 27001: gap assessment complete, certification targeted for 2027; ISO/IEC 42001 (AI management systems), under assessment, and increasingly the one clients ask for; SOC 2 Type II: will follow ISO 27001 where clients require it. Everything in the held list can be evidenced during supplier onboarding. Nothing in the in-progress list is certified yet.

That depends on whether your policy allows compensating controls. Tenhaw is not ISO 27001 certified today, though the gap assessment is complete and certification is targeted for 2027, Cyber Essentials Plus is certifying now, and SOC 2 Type II will follow ISO 27001 where clients require it. What usually satisfies a risk function in the meantime is the delivery model. Work happens on your infrastructure under your controls, engagement data is processed in the UK by default, and 24-hour breach notification is committed as a term of the Data Processing Agreement. If ISO 27001 is a hard gate, raise it on the first call and we will tell you whether we can meet it in your timeframe.

It is deleted, and in most engagements there is nothing to delete because the data never left your estate. Tenhaw's default is to work and build on your infrastructure under your controls, so code, documentation and credentials live in your systems from day one. Where engagement data has reached our systems, it is processed in the UK on encrypted, MDM-managed devices and deleted at engagement end, with the retention and deletion terms set in the Data Processing Agreement. We do not retain client production data once an engagement closes. The deliverables, including any code written in your environment, are yours on payment, and retainers end on 30 days' notice with a documented handover.

No. Tenhaw works under zero-retention or enterprise agreements with model providers, so client content is not retained by them or used for training. In front of that commitment sits a named-tool-only policy, under which no client data, code or documentation goes into any AI tool that has not been named and approved by you in writing. The model providers on an engagement, Anthropic, OpenAI and Google, process only content you have approved in writing for that engagement, and the contracting entity and transfer mechanism for the provider you approve are set in your engagement's annex to the Data Processing Agreement.

Yes, and that is the default position wherever you have an approved enterprise AI tenancy. Tenhaw works inside it rather than bringing its own tooling. Where you have no approved tenancy, the toolchain is named for your review before anything touches your estate: Anthropic's Claude Code, OpenAI's models and Google's Gemini, combined for what each does best, running inside your infrastructure and aligned to your policies, and substituted for your approved stack on request. Model and agent risk is documented during operating model design, with your second-line risk function brought in as a co-author of the framework rather than a reviewer of it.

Yours, wherever you provide them. The default is your identity provider, your access controls and your devices, with access requested against the principle of least privilege, time-boxed to the engagement and closed with a documented offboarding step on exit. Where Tenhaw's own devices are used, they are full-disk encrypted, MDM-managed, screen-locked and remotely wipeable, and client data is not copied to Tenhaw-controlled storage unless the engagement agreement expressly permits it. Multi-factor authentication is enforced on every business system Tenhaw operates. If your access model works differently from this, the call is where we work out whether it fits.

The Master Services Agreement, the Statement of Work template, the Data Processing Agreement with its sub-processor annex, insurance certificates and completed security questionnaires. Ask legal@tenhaw.com and it is sent the same week, usually the same day, and every commitment on the security page can be evidenced from it. If your review needs something the pack does not carry, ask and we will tell you whether we can produce it. For a questionnaire of your own, the fastest route is to bring the document to a 30-minute call with James Rooney, where we will tell you which items we can evidence today and which are still in progress.

Yes. Independent penetration testing runs in the productionisation phase, scoped to the code that shipped, so the system is tested by someone other than the people who built it before it carries real work. It is the last gate rather than the only one. Static analysis with quality gates on every commit, dependency and vulnerability scanning on every build with continuous alerts on newly disclosed CVEs, secrets scanning with push protection, and protected main branches with human code review before merge all sit in front of it. Because the build happens on your infrastructure, every one of those runs under your standards and lands in your audit trail.

No. Confidentiality obligations survive the end of the engagement indefinitely, and they are written into the engagement agreement itself. Every associate is contracted to written confidentiality and to your data-handling requirements before any client access, and BS7858-standard screening is completed before anyone reaches your estate, for employees and associates alike. In the Statement of Work, breach of confidentiality and data protection are treated separately from the general liability cap, which is the position a procurement review usually wants to see stated rather than negotiated.

Yes. The Data Processing Agreement carries Article 28 change-notice terms, so telling you about a new sub-processor is a contractual obligation rather than a courtesy. The current list is published on our security page and annexed to your DPA, with entity, location, purpose and transfer mechanism given for each service processor, so your reviewer can check it without asking us. It stays short because delivery happens inside your estate: business email and documents, CRM, scheduling, and the model providers you have approved. Model providers are the line worth watching with any AI supplier, and ours receive only content you have named and approved in writing for your engagement.

Residency and transfer mechanism are different questions, and this page answers both. Close is Elastic Inc. in the United States, and what it holds is client contact records, under the UK International Data Transfer Addendum and Standard Contractual Clauses. Your engagement data is a separate matter, processed in the United Kingdom by default, with EU residency available where your policy requires it, and in most engagements it never leaves your own infrastructure at all, because we build inside your estate under your controls. Engagement correspondence sits in Google Workspace, contracted through Google Ireland Limited and processed in the UK and EU.

You do, in the normal case, because you are the controller and we are your processor. A personal data breach affecting your data is notified to you without undue delay, and in any event within 24 hours of us becoming aware of it, as a term of the Data Processing Agreement, so your own 72-hour regulatory clock starts with time to spare. The first notification goes to your named contact by the route agreed at kickoff, updates follow as the investigation runs, and a written report covering root cause, impact and remediation comes after it. We stay engaged until your own team closes the incident.

Four things, none of which takes long. Accounts in your identity provider with least-privilege access, time-boxed to the engagement. A signed Data Processing Agreement with its sub-processor annex. Written approval of the AI tools that will be used, because nothing of yours goes into a tool you have not named in writing. And a named contact for security incidents, with the route we should use to reach them. On our side, BS7858-standard screening covering identity, right to work, employment history and criminal record is completed before anyone reaches your estate, for employees and associates alike, and offboarding is a documented step on exit.

Partly, and the mismatch is worth knowing before you send it. We are a consultancy, so the posture is mostly about people and access rather than a product. With no customer portal and no authenticated area, the sections on tenancy, session handling and user provisioning come back as not applicable. The ones that bite are personnel screening, access into your systems, sub-processors, breach notification terms and which AI tools touch your data, and all of those are answered on this page. Completed questionnaires come in the onboarding pack from legal@tenhaw.com, or bring yours to a 30-minute call and we will work through it live.

Email security@tenhaw.com and you will have an acknowledgement within two working days. We do not pursue legal action for good-faith research, so nobody needs to negotiate terms before telling us about a problem. That address covers this website and anything else we run. The site itself is statically generated with no accounts, no authenticated area and no client data on it, so the surface there is deliberately small. Anything found inside a live engagement is better raised with the contact and route agreed at kickoff, where it is handled as a security incident and closed out with a written report covering root cause, impact and remediation.

Yes, for anything we ship. A software bill of materials and licence provenance checks run over the code that goes out, so AI-generated work arrives with its supply chain documented rather than assumed. That matters more when a model is proposing dependencies than when a person is, because the reach for a convenient library is instant and nobody on your team chose it. Dependency and vulnerability scanning runs on every build, with continuous alerts on newly disclosed CVEs, so the picture stays current after handover. All of it runs in your pipeline on your infrastructure, so the evidence sits in your estate and stays there when we leave.

Yes, and in your own logs rather than in a report we write. We work through your identity provider, your access controls and your devices where you provide them, and working software is built and deployed on your infrastructure, so commits, pipeline runs, access grants and deployments land in your audit trail as they happen. Access is requested against the principle of least privilege and time-boxed to the engagement, so what each person can reach is visible to you when it is granted rather than reconstructed later, and offboarding is a documented step on exit. There is nothing to migrate off our estate when the engagement ends.

Yes. The provider list on an engagement is the one you approve in writing, and a provider your policy rules out is simply not used. Where you have no preference, the default is Anthropic's Claude Code with OpenAI's models and Google's Gemini, each picked for what it does best and run inside your infrastructure under your policies. Tenhaw does not resell or mark up models, platforms or licences, so nothing you mandate or exclude becomes revenue for us. The honest limit is delivered experience. Everything we have shipped runs on Microsoft Azure including Azure OpenAI, so on a stack we have not shipped on we work alongside your own platform engineers rather than leading the platform work.

Yes, on evidence a reviewer can check today, starting with the large organisations that have already bought the work. Anglo American, YNAP, Yondr and Greggs were delivered under the Tenhaw banner, and the live London specialty insurance engagement, confidential at the client's request, is a proof of concept being productionised now. Tenhaw LTD is registered in England and Wales, with the company number on the contact page, and screening is BS7858-standard before any client access. Insurance is published as figures, professional indemnity £1m and employers' liability £10m. Name the limit your supplier standard requires, on any call, and the increased cover is in place within three working days, priced in. Cyber Essentials Plus is certifying now, ISO 27001 targeted for 2027.