Articles
Prepare for the ICO code against current duties The ICO is required to prepare a statutory AI and automated decision-making code. Existing data-protection duties continue while it is developed. Assess live systems now and distinguish current obligations from anticipated guidance. Reporting a serious AI incident starts long before the incident Serious-incident reporting needs facts about the system, affected people and resulting action. Establish records, detection routes and accountable owners before an event, then assess the applicable duty and reporting deadline. Sovereign inference is a control question, not a map question An EU processing region answers only part of a sovereignty requirement. Specify operator jurisdiction, support access, retained records, change authority and continuity, then assess the arrangement against the workload’s actual needs. Five decisions, not two: how an assessment should end A risk assessment should support a recorded decision, with conditions, owners and remaining uncertainty. Five possible outcomes help distinguish acceptable use from work that needs controls, redesign or specialist review. Use NIST’s draft overlays to sharpen the AI security review NIST’s developing AI security overlays offer a use-case vocabulary for reviewing controls. Map the relevant assistant, predictive-model and agent exposures now, while keeping draft guidance separate from contractual or legal requirements. The questions to ask an AI supplier before you sign AI due diligence needs evidence, change and exit questions alongside security review. Agree responsibilities, usable records and transition conditions before accepting the service dependency. Your data records a process, not the world Operational history reflects selection, recording and past policy as well as outcomes. Explain how the dataset was produced, then test whether its labels and population support the decision the proposed model must make. Agents need identities, not API keys An agent needs an identifiable actor, explicit authority and bounded credentials. Preserve the delegating person or organisational owner in the action record, and test scope, expiry and revocation before granting access. Carry access control through the retrieval system A well-sourced answer can still disclose information to someone without permission to see it. Carry entitlement through ingestion, retrieval, caching and revocation, and test access separately from answer quality. Review tool definitions as a supply-chain dependency Tool definitions are supplier-controlled inputs to an agent’s context. Review their provenance, permissions and changes as part of the software supply chain, and test whether untrusted text can influence an authorised action. Plan the embedding change as a migration Changing an embedding model can require a new index, a retrieval evaluation and a controlled cutover. Record the source versions, transformations and permissions needed to rebuild the service before committing to the switch. Include power availability in the architecture review Power availability can affect where AI capacity is offered, when it becomes available and what a workload costs. Include it in placement and capacity reviews, while keeping energy estimates separate from measured usage.
Bring us the question
Something here already on your desk?
Bring the question, the systems involved and the decision you need to make. We will confirm whether a scoped engagement is appropriate.