NEW

Start with the pressure: sales, launch, abuse, agents, data, or guardrails

Deep assessment

AI Product Security Assessment Packet

A product-security risk map and remediation roadmap with buyer-ready evidence.

The first deliverable is a decision package: what is in scope, what is required, what is blocked, and what can proceed.

No production testing, adversarial activity, access to secrets, or customer-data processing happens without explicit authorization and the right agreement path. Do not enter secrets or credentials here.

What to gather for this packet

Needed: AI system inventory · Architecture & data-flow docs · Read access to staging/demo · Authz and tenancy model

Helpful: Prior pentest reports · Threat models · Compliance context

Bring names and high-level descriptions only — exact targets, accounts, and credentials are shared later through a secure channel.

Engagement

Readiness inputs

Deliverables you want

Packet modules

  • Scope BriefWhat is in scope, what decision is being made, and what success looks like.
  • Authorization StatementConfirmation the org owns, controls, or is authorized to assess the targets.
  • Evidence Handling PlanWhere evidence is stored, redaction, retention, and deletion.
  • Contract RequirementsThe required and conditional agreements for this engagement.
  • Draft SOW InputsScope, window, deliverables, and acceptance inputs for the SOW.
  • Open QuestionsWhat is still required before a scoping call or private offer.
  • Follow-On RecommendationsNatural next services once this engagement completes.
  • Target InventoryThe named systems, endpoints, repos, accounts, or surfaces in scope.
  • Access PlanHow access and test accounts are provisioned through a secure channel.
  • Technical Access ChecklistArchitecture, prompts, RAG, agents, authz, and logs needed to start.
  • Data Handling PlanData sensitivity, masking, sample-only, retention, and deletion rules.
  • AI / Agent BoundaryModels, tools, actions, approvals, and rollback paths in scope.
  • Deliverables PlanThe artifacts the buyer will receive and in what format.

AI Product Security Assessment Packet — preview

Deep assessment

Scope Brief

  • Organization: To be specified during scoping
  • Decision: A product-security risk map and remediation roadmap with buyer-ready evidence.
  • Driver: We need a full architecture, data-flow, trust-boundary, model/provider, RAG, and tenant-isolation review beyond an urgent launch gate.

Authorization Statement

  • Not yet confirmed — required before any access or testing.

Evidence Handling Plan

  • Evidence stored in an access-controlled encrypted store; redaction; agreed retention + deletion.

Contract Requirements

  • Mutual NDA — Required for this engagement.
  • Evidence Handling Policy — Required for this engagement.
  • Statement of Work Template — Required for this engagement.
  • Assessment Terms Addendum — Required for this engagement.

Draft SOW Inputs

  • Engagement: AI Product Security Assessment Packet
  • Deliverables: 7 selected
  • Budget category: Product security / AppSec / security assurance

Open Questions

  • Authorization (own / control / explicitly authorized to assess the targets)
  • Target inventory (named systems/endpoints in scope)
  • Agent boundary (tools, actions, approvals, rollback)
  • Access plan (how access and test accounts are provisioned securely)

Follow-On Recommendations

  • ai red team adversarial testing
  • agentic workflow security
  • ai governance program build
  • claim readiness evidence

Target Inventory

  • No named targets yet — required before testing.

Access Plan

  • Access plan needed — secure-channel provisioning, no public credentials.

Technical Access Checklist

  • Architecture, prompts, RAG, agents, authz, and logs needed to start.

Data Handling Plan

  • Sensitive data in scope: No
  • Standard handling; secrets masked; minimum-necessary access.

AI / Agent Boundary

  • Agent boundary needed.

Deliverables Plan

  • Product Security Risk Map
  • AI System Inventory
  • Trust Boundary Map
  • Data Flow Review
  • Architecture Findings
  • Remediation Roadmap
  • Evidence Summary

Onboarding

Move four tracks in parallel

We put legal, finance, procurement, and technical scoping on parallel rails so the work can start without waiting on every internal process sequentially.

Technical Scoping

Output: Draft Launch Review Plan

  • architecture
  • demo/staging
  • prompts
  • RAG
  • agents/tools
  • authz
  • logs/evals
  • test boundaries

Legal

Output: NDA + Scoping Authorization

  • mutual NDA
  • data handling
  • authorized testing boundaries
  • confidentiality
  • work-product terms

Finance / Procurement

Output: Procurement Packet

  • vendor profile
  • tax/payment details
  • budget category
  • fixed-fee quote path
  • invoice terms
  • onboarding answers

Internal Approval

Output: Approval Memo

  • why now
  • business pressure
  • risk if delayed
  • expected deliverables
  • timeline
  • decision needed

Output

Your output: a clear, measurable prescription.

SCOPE delivers a one-page engagement plan you can share and act on immediately.

  • Situation & core problem
  • Desired outcome & success criteria
  • Key risks & assumptions
  • Recommended path(s)
  • Effort, timing & impact
  • Open questions & next step

SCOPE Prescription

Situation

Criteria

Recommended path

Next step

Export as markdown ↗