PARTNERS

Add selected Workbench capabilities through bounded OEM and partner integrations

Commercial portal · Private offers

Private offers for bounded technical and partner decisions.

A private offer defines one commercial relationship: the selected outcome, scope, inputs, outputs, deployment or delivery model, evidence boundary, responsibilities, support, timing, and commercial terms. Choose the relevant path first; the packet, intake, contracts, and proposal then adapt to that path.

Private offers may support direct SOW, invoice, enterprise procurement, or other approved buying paths. AWS-compatible deployment or procurement support may be discussed where relevant; this does not imply an AWS Marketplace listing unless one exists.

How the buying motion works

Get to yes without waiting on every process sequentially

We help product, security, legal, and finance get to yes quickly with a scoped plan, approval packet, and evidence-ready deliverables. Pre-Engagement Scoping confirms the decision, scope, information boundary, authorization requirements, procurement path, and appropriate commercial instrument before paid work begins — it is not free consulting.

  1. 01

    Choose the relationship

    Select the engagement, product, pilot, Academy, workforce, or partner motion.

  2. 02

    Define the bounded scope

    Confirm the system, workflow, capability, learners, partner object, or business decision in scope.

  3. 03

    Confirm the information boundary

    Identify what can safely be supplied during qualification and what requires NDA, DPA, ROE, or secure exchange.

  4. 04

    Assemble the applicable packet

    Generate only the technical, legal, procurement, evidence, and commercial material required for that relationship.

  5. 05

    Review the offer

    Confirm scope, deliverables, responsibilities, timing, support, price, and applicable agreements.

  6. 06

    Approve and activate

    Begin only after the required commercial and authorization conditions are satisfied.

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 / Program Definition

Output: Draft Engagement Plan

  • system or capability in scope
  • workflow and integration points
  • access or environment needs
  • authorization and boundaries

Legal

Output: NDA + Scoping Authorization

  • mutual NDA
  • data handling
  • authorized use 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

Readiness packet

Bundle a scoped pentest or red team engagement

A private offer can include scoped penetration testing, cloud review, or adversarial red teaming. Build the readiness packet first — targets, authorization, ROE, access, evidence handling, and deliverables — so the offer and SOW come together cleanly.

Readiness Packet

Prepare the test before selecting the tester.

Cobalt-style onboarding for scoped security testing, adversarial review, cloud assessment, and AI/agentic red teaming.

  • Scope Brief & Target Inventory
  • Rules of Engagement & Authorization
  • Access Plan & Evidence Handling
  • Required contracts + Draft SOW inputs

Testing only proceeds against targets your organization owns, controls, or is explicitly authorized to assess.

Enterprise training

Request an Academy enterprise training packet

Team Pack, Enterprise LMS Package, Private Cohort, Workforce Platform Partner Add-On, and Academy Content Licensing options are available. Covers seat access, supported LMS delivery, facilitator guides, Q&A checkpoint keys, manager reports, and enterprise training terms. SCORM 1.2 preview available; full package by implementation scope.

From packet to offer

Private offers are generated from readiness packets

A private offer should be generated from a clear packet, not a vague intake thread. Complete the readiness packet for your engagement, then we turn it into a fixed-fee offer.

  1. 1Choose your buyer pressure
  2. 2Complete the readiness packet
  3. 3Confirm NDA / legal path
  4. 4Generate draft SOW inputs
  5. 5Request a fixed-fee private offer
  6. 6Kickoff after approval

Readiness packets

Pick the packet to turn into an offer

Each packet captures scope, authorization, access, evidence, and contracts — everything finance and legal need to approve a fixed-fee engagement.

PacketPre-launch review

Launch Review Packet

We are launching an AI feature, copilot, RAG system, agent, or workflow soon and need launch-risk clarity fast.

Typical duration: 5–10 business days; first findings targeted within 5 business days.
System Boundary Record

Required to assemble

Target AI feature or workflow · Lifecycle stage · Release pressure · Architecture overview · Evidence available · NDA/SOW path

Likely blockers

Missing staging/demo access · Unclear system prompt / RAG / tool boundaries · No launch owner · No buyer/security evidence owner

PacketDeep assessment

Product Security Packet

We need a full architecture, data-flow, trust-boundary, model/provider, RAG, and tenant-isolation review beyond an urgent launch gate.

Typical duration: 2–4 weeks, depending on scope.
System Boundary Record
PacketBuyer enablement

Buyer Evidence Packet

Enterprise buyers are asking AI security questions we cannot answer cleanly, and the deal/security review is slowing down.

Typical duration: 1–4 weeks, depending on scope.
AI Security Questionnaire Answer Bank

Required to assemble

The buyer questions / questionnaire · Claims needing support · Existing evidence · Trust-center / audience

Likely blockers

No evidence owner · Claims lack scope / date · Unclear what is public-safe

PacketAgent security

Agent Authority Packet

Agents, tools, credentials, workflows, approvals, and actions have unclear blast radius.

Typical duration: 2–5 weeks, depending on scope.
Agent Authority Map

Required to assemble

Agent / tool inventory · Permissions & credentials model · Approval & rollback paths · Logs / audit coverage

Likely blockers

Unclear tool / action blast radius · No rollback path · Missing audit logs

PacketReadiness packet

Pentest Readiness Packet

We need a pentest or adversarial test, but scope, authorization, ROE, access, window, evidence, and procurement are not ready.

Packet readiness can begin immediately after intake; engagement timing depends on scope and access.
Scope Brief

Required to assemble

Target inventory · Ownership / authorization · ROE · Testing window · Emergency contact · Access plan · Evidence rules

Likely blockers

Third-party target authorization · No testing window · Missing stop contact · Production constraints unresolved

PacketAdversarial testing

AI Red Team Packet

We need adversarial validation of prompt injection, RAG exposure, tool abuse, tenant leakage, and unsafe autonomy.

Typical duration: 2–5 weeks, depending on scope.
AI Red-Team Scope Document

Required to assemble

Model / provider / app surface · Prompt / RAG / tool boundaries · Allowed adversarial methods · Prohibited methods · Evidence handling · Human approval points

Likely blockers

Unclear tenant / data boundaries · No safe test data · Tool / action blast radius unclear

Routes to:

PacketRAG security

RAG Boundary Packet

RAG retrieval, embeddings, ingestion, and tenant boundaries may leak customer or cross-tenant data.

Typical duration: 2–5 weeks, depending on scope.
AI Red-Team Scope Document

Required to assemble

Source systems · Corpus sensitivity · Tenant boundaries · Retrieval access rules · Eval / logging coverage

Likely blockers

Unclear source ownership · Production customer data present · No retrieval logs / evals

PacketIntegration security

Connector Security Packet

OAuth apps, SaaS connectors, scopes, webhooks, token storage, and connected actions need a least-privilege review.

1–3 weeks depending on connector count.
Connector Inventory

Required to assemble

Connected apps · OAuth scopes · Read/write actions · Webhook / callback handling · Token storage assumptions · Revocation path

Likely blockers

Excessive OAuth scopes · Unclear admin ownership · Missing revocation process

PacketIdentity & onboarding

Enterprise Onboarding Packet

Enterprise SSO/SCIM, RBAC, provisioning, deprovisioning, and auditability are becoming a deal blocker.

1–3 weeks depending on IdP and provisioning complexity.
IdP Compatibility Matrix

Required to assemble

IdP · SSO protocol · SCIM / provisioning · Role / group mapping · Deprovisioning · Audit / logging needs

Likely blockers

No IdP owner · Unclear role model · No test users / groups

PacketGovernance program

Program Build Packet

AI security is scattered policy with no operating model, ownership, controls, evidence, or cadence.

Typical duration: 4–10 weeks or retainer, depending on scope.
AI Security Operating Model
PacketDiagnostic

Maturity Scorecard

We do not yet know our AI security gaps or where to invest first.

Typical duration: 1–3 weeks, depending on scope.
Analyst-reviewed program baseline
PacketEngineering controls

Secure AI SDLC Packet

AI security is not operationalized in engineering: CI/CD, design review, code review, evals, logging, and release gates.

3–6 weeks or phased.
AI SDLC Current-State Map

Required to assemble

Current SDLC / CI-CD · Release process · Eval / test coverage · Design / code review practice

Likely blockers

No release-gate owner · Eval coverage gaps · No logging baseline

PacketGuardrails & evals

Guardrails & Evals Packet

Our guardrails, evals, refusal behavior, and release criteria have unknown coverage and failure modes.

Typical duration: 2–5 weeks, depending on scope.
Guardrails and Evals Review Memo
PacketVendor risk

Provider Risk Packet

We need clarity on model/provider data flows, retention, training terms, residency, logging, and fallback risk.

1–2 weeks.
Provider Inventory

Required to assemble

Providers in use · Data sent to each · Logging approach · Residency requirements

Likely blockers

No DPA from provider · Unclear retention / training terms · No fallback design

PacketClaims & evidence

Claim-Readiness Packet

We need to control what we can safely say publicly or to buyers after assessment work.

Days to 1–2 weeks depending on scope of claims.
Allowed Claims

Required to assemble

Intended claim · Audience · Evidence source · Scope / date / limitations · Approval owner · Public-safe summary needs

Likely blockers

Draft evidence treated as final · Claim lacks scope / date · No approval owner

PacketSpecialized

Custom Support Packet

We have a specialized AI security need that does not fit a standard service.

Scoped after a short discovery.
Scoped Plan

Engagement readiness

Ready to scope is not the same as authorized to test.

Testing starts only after the required SOW, ROE, target list, access path, and testing window are approved.

Technical Scope

Needs input

Technical owner or security owner

Inputs: Target systems, lifecycle stage, architecture overview, boundaries

Next: Define the in-scope systems and surfaces

Build a packet

Legal / NDA / DPA / SOW

Needs input

Legal owner

Inputs: Mutual NDA, DPA if personal/customer data, SOW or no-cost scoping

Next: Start the no-cost scoping / NDA path

Contract packet

Access & Credentials

Needs input

Technical owner or IT/admin owner

Inputs: Access model, test accounts, secure credential-delivery channel

Next: Plan secure access — never via public forms

Evidence Handling

Needs input

Security owner

Inputs: Storage location, redaction, retention, deletion

Next: Confirm evidence storage + retention rules

Evidence Handling Policy

Scheduling & Stop Contacts

Needs input

Technical owner and emergency contact

Inputs: Testing window, blackout dates, stop-testing/emergency contact

Next: Set the window and a reachable stop contact

Procurement / Payment / Private Offer

Needs input

Finance / procurement owner

Inputs: Vendor packet, budget category, PO/payment path, private offer

Next: Request a fixed-fee private offer once scope is clear

Private offers

Do not submit secrets, production credentials, access tokens, regulated data, or unredacted customer records through public forms. Credential exchange happens only after NDA/SOW/DPA/ROE through an approved secure channel.

What you can bundle

One scoped engagement, many components

Products + onboarding

AI Security Workbench tools and platforms with implementation and onboarding included.

Services + retests

Assessments, red teaming, and hardening with scheduled retests.

Academy at scale

Team training, SCORM/LMS packages, and certification seats.

Evidence + reporting

Evidence packs, control mappings, and executive reporting cadence.

Enterprise packages

Common starting points

$3,500/month

AI Security Workbench

AI security program, trust evidence, and remediation workbench

$1,250/month

Code Scanner Team License

Recurring AI code and configuration review for product security, AppSec, and developer teams

$1,500/month

Trust Scanner

AI and security claim scanner for customer-facing trust language

$15,000/year

Adversarial Range

Deployable AI security lab for RAG, agents, telemetry, and evidence validation

$2,400 / year

AIPSA SCORM Training Package

LMS-compatible AI product security training with a supported SCORM 1.2 preview and additional delivery formats by validated implementation scope

$180k–$350k+

Workforce Platform Partner Add-On

The role-readiness layer for cybersecurity training platforms, cyber ranges, and enterprise security teams. Role taxonomy, Q&A bank, job-market signals, hiring calibration, and workforce reporting — under your brand.

$50k–$100k

Scanner Provider OEM Pilot

A bounded OEM pilot that preserves the scanner's finding identity and workflow while adding selected AI-specific findings, connected context, evidence, and optional Attack Path Analysis.

$20k–$35k

AI Launch Security Review

Pre-launch AI security review for product teams shipping LLM features, RAG systems, copilots, agents, or AI workflows.

$18k–$30k

Pen Test & Red Team Readiness Packet

Structured readiness assessment for teams scoping an external pen test or red team engagement — scope, authorization, ROE, evidence handling, and vendor criteria.

$20k–$40k/yr

AI Security Academy

Structured AI security training for security, engineering, product, governance, and trust teams — courses, Q&A checks, LMS delivery, and private cohorts.

By negotiation

Academy Content Licensing

Partner-ready AI security training content — courses, Q&A bank, LMS packages, and workforce readiness modules for training platforms, cyber ranges, and enterprise L&D delivery.

Request a private offer

Tell us what to scope

Do not submit passwords, API keys, OAuth or access tokens, private keys, production credentials, regulated data, unredacted customer records, exploit payloads, or proprietary source code through this public form. Describe the boundary at a high level. Secure exchange methods are established after qualification and, where required, the applicable NDA, DPA, SOW, or rules of engagement.

Pre-filled from your SCOPE session — review and submit.
Red Teamred team

AI Red Team Assessment

Authorized adversarial testing for prompts, retrieval, tools, delegated actions, and abuse cases.

1. Organization and contact

Who should we follow up with?

2. Project / system context

Describe the AI system or product surface you want scoped.

Public forms are for non-sensitive preliminary scoping only. Do not submit passwords, API keys, OAuth or access tokens, private keys, production credentials, regulated, payment, or health data, unredacted customer records, or proprietary source code. Credential exchange happens only through an approved secure channel after NDA/SOW/DPA/ROE.

3. Risk surfaces

Choose the areas that seem relevant. Defaults are pre-selected based on the service.

4. Evidence readiness

Tell us what you likely have and what may be missing. Do not upload secrets here.

What evidence do you already have?

This does not upload files yet. It helps us prepare the right evidence request list.

What might be missing?

5. Outcome and constraints

Help us prepare a useful first response.

Safe scoping reminder

Do not paste credentials, secrets, private keys, regulated records, customer data, or proprietary source code into this form.

Private-offer packet

The default enterprise packet is ready to assemble.

This packet is designed for quote-first and invoice-first motion with legal, procurement, data handling, and evidence language attached to the same opportunity.

Stripe-optimized packet

Payment terms

Net 30, prepaid invoice, or custom procurement terms.

Acceptance terms

Accepted when the agreed deliverables are delivered and the buyer has had a factual review window.

Fulfillment workflow

scope -> packet -> quote / invoice -> acceptance -> launch room

Prefer to browse first? Back to the Marketplace