Security & Compliance for AI

Prompt-injection defense, data handling and audit trails that hold up to review.

What it is

An AI application has an attack surface older software did not: the prompt itself, every tool the model can call, every document it retrieves, and the customer data that flows through all of them. GTDataWorks audits your application end to end (prompts, tools, data flows, secrets) and then hardens it: prompt-injection detection, PII handling, least-privilege tool access, a default-deny network policy for agents, and audit logging.

Findings arrive as a retained-proof report rather than a slide deck: a finding ledger, an evidence manifest with SHA-256 hashes, and a negative control that proves the checks can fail. Your users see the same product as before. What changes is that a crafted email or web page can no longer talk the assistant into leaking a record, and when a client's security reviewer asks how you know, you hand them the report.

The controls are GDPR- and HIPAA-aware engineering controls: data minimization, access control, audit logging, PII handling. GTDataWorks does not issue certifications or legal advice. The report is written so your counsel or auditor can use the evidence.

What you get

The report is built to be re-checked by a stranger: every finding points at a hashed piece of evidence, and the negative control shows the checks are not a rubber stamp.

  • Retained-proof audit report
  • Hardening changes
  • Policy files
  • Re-test receipt

How the work runs

  1. Scope and threat model

    Agree what is in scope (the application, its prompts, tools, data stores and secrets), who the adversaries are, and what a bad day looks like: a leaked record, an unauthorized action, a poisoned answer. The scope statement is the first page of the report.

  2. Prompt, tool and data-flow review

    Read every system prompt and tool definition, trace where customer data enters and leaves, and list each tool's permissions against what it needs to do its job.

  3. Injection and exfiltration tests

    Prompt-injection payloads run through dif-defense against the live application, in direct input and in retrieved documents, emails and web pages. Exfiltration attempts go through tools, links and markdown, with the agent held under a default-deny network policy so every host it tries to reach is recorded.

  4. Hardening

    Fix what the tests found: least-privilege tool access, PII handling, secrets management, OAuth 2.0 and JWT where sessions need them, role-based access, audit logging. The policy files that enforce it are yours to keep.

  5. Retained-proof report

    A finding ledger with an ID, severity, evidence and disposition for every finding; an evidence manifest listing each artefact with its path, size and SHA-256 hash; and a negative control, a case designed to fail, that shows the checks can fail.

  6. Re-test receipt

    After your fixes land, the tests run again and you receive a re-test receipt that states which findings are closed, which are open, and the hash of the evidence behind each.

Pricing

Hourly

$80–$150/hr

Hardening and remediation work.

Prices are in USD and are starting points. The final quote follows a scoping call.

Where it fits

A good fit when

  • An AI application touches customer data, in healthcare, finance, legal or anywhere a leak would matter.
  • An agent has tools (email, databases, browsers, payments) whose permissions nobody has reviewed since launch.
  • A client or procurement questionnaire asks how you tested for prompt injection, and you want to answer with evidence rather than a paragraph.

Not a fit when

  • You need a certification (SOC 2, ISO 27001, a HIPAA attestation) or a legal opinion. This work produces engineering controls and evidence; an auditor or counsel issues those.
  • The application is not built yet. Build it with containment from the start instead: Agent Orchestration & Workflow Automation gates every external action behind a policy check.
  • You want a penetration test of your network or web application rather than the AI layer. This audit is scoped to prompts, tools, data flows and agent containment.

Questions

What does the audit report look like, and who is it for?

A retained-proof report: a scope statement, a finding ledger (ID, severity, evidence and disposition for each finding), an evidence manifest listing every artefact with its path, byte size and SHA-256 hash, and a negative control. It is written for two readers: your engineers, who need to reproduce and fix each finding, and procurement or a client's security reviewer, who need to see what was tested, what was not, and that the evidence has not changed since.

Is this a GDPR or HIPAA certification?

No, and nothing on this page is legal advice. The work implements GDPR- and HIPAA-aware engineering controls (data minimization, access control, audit logging, PII handling) and documents them so your counsel or auditor can use the evidence. Certifications and legal opinions come from them.

Where does your data go during the audit?

Nowhere new. Tests run against your environment, under accounts and keys you issue, and findings and evidence are stored in a repository you own. Model-provider keys stay yours. Any access granted to the studio is revoked at the end of the engagement, and the report records when.

What happens after the re-test?

You keep the report, the policy files and the hardening changes, and the test harness stays in your repository so the checks can run again after a release. If you want the studio to run them, or a new feature widens the scope, that is hourly work or a new audit.

Audit the AI layer, with receipts

Name the application and the data it touches. The brief builder asks the rest, and a scoping call sets the quote.