AI Security Assessment

Two weeks at the published floor for the AI security practice. The floor covers up to 3 distinct systems, models or accounts; beyond that, each further block of up to 3 systems adds 10 percent, capped at 30 percent, and more than 12 systems needs a scoping call.

Two weeks buys the practice's shorter adversarial shapes, chosen at the scoping call: an LLM red team (the site scopes it at 2–4 weeks, adversarial) against a deployed model or assistant, or a RAG and retrieval review (2–3 weeks, targeted) against the retrieval path. We assess the deployment as one system — the prompt, the index, the tools and the cloud account underneath — because that is the surface an attacker actually gets.

Testing is chained and stateful rather than single-shot: prompt injection through every channel the system will accept text from, including filenames, retrieved documents and tool output; jailbreak chains, instruction-hierarchy collapse and refusal-boundary mapping under sustained pressure. In the retrieval shape that means tenant isolation in embedding stores, indirect injection via ingested documents, extraction of source material through reconstruction attacks, and access-control drift between the source system and the index that mirrors it. We report the path, not just the payload.

Fixed fee and fixed window, scoped with a written deliverable and an end date agreed before it starts. No retainers you cannot exit and no findings held back for a follow-on sale: everything we find goes in the report at the time we find it. We take no percentage of savings and hold no reseller margin on any platform we might recommend. What we deliver is yours — the harness, the code and the reasoning — so if you never call us again, everything still works.

The price is the published floor for the practice and its status is confirmed: PinkCloud quotes from this figure. It is a floor rather than a flat fee — the scope described above buys it, and while we are scoping, more systems, an expedited start or compliance evidence quote above it, so a binding quote can come out above an indicative one. The floors are published so you can rule us in or out without a call, and engagements are quoted against scope, never against what we think you can pay. The floor is priced for senior-only staffing: the people who scope the engagement are the people who deliver it, and the practice floors sit deliberately above the entry product rather than being discounted to meet it. An indicative quote is valid 14 days and is never binding; a binding quote follows a scoping call and is approved by a named person at PinkCloud.

Assumptions: senior-only staffing; remote delivery unless on-site is agreed; the client provides access within 3 business days of the start; taxes excluded, as the Service offer published on the practice page also states; the fixed fee is an agreed budget of 140 hours of senior time at our published hourly rate.

What the fee buys, and what happens if the work does not fit. Two rules apply at two different times and both hold. Before you sign, while the scope is being sized, the figure is a floor: more systems, an expedited start or compliance evidence quote above it. Once you have signed, the quoted fee and the two-week window hold: if the agreed work proves larger than we estimated, the scope flexes rather than the fee, what comes out is agreed in writing with you, and an overrun is never billed by the hour. The hourly rate is reached only by adding scope — a change request or a separate engagement, agreed in writing before it starts — never by the agreed work turning out to be bigger.

Testing conditions: scope, rate limits and data handling are agreed in writing before anything runs, and we default to a staging environment mirroring production configuration. Where production is genuinely the only meaningful target, we agree explicit blast-radius limits and a rollback path first. Any data encountered is handled under the engagement's NDA and destroyed on completion. Access to model weights is never a precondition: most engagements are black- or grey-box against a deployed endpoint.

Confidentiality and staffing: the roster staffing the work is disclosed under NDA before you sign anything. We never publish client work without written permission and never with identifying detail; novel techniques that are not client-specific may be written up generically, always after remediation and always with the client's sign-off on the wording. What you send is shown only to the people at PinkCloud who will answer, and is never published, used in marketing or shared with other prospects. We do not backfill an engagement with people who were not in the scoping call.

If a prior Exposure Review turns into a larger engagement, the site states that its fee comes off the first invoice, while the pricing rules list crediting the entry fee against a follow-on as a human decision and a decision record each.

Payment, cancellation and liability terms are agreed in the engagement contract before work starts.