NEW

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

Publication DSL deliverables

See the artifacts serious AI Product Security work actually produces.

These samples show the maps, matrices, evidence packs, risk registers, and executive summaries that turn advisory work into buyer-ready evidence and engineering action.

Guided sample pack

Northstar Support Cloud

One fictional engagement ties the deliverables together: discovery, inventory, architecture, retrieval authorization, tool permissions, evidence, release gates, and remediation.

How to read it

Start with the intake pack, then follow the artifact chain to launch readiness and remediation.

Buyer-safe posture

This is a sample engagement, not an internal source dump.

Open the guided tour →

Buyer journey

What you actually receive

01

Discovery and intake

02

Inventory and architecture

03

RAG and tool evidence

04

Evidence and questionnaire support

05

Release gate and remediation

06

Red-team summary and roadmap

Artifacts by M.A.D.E. pillar

Every artifact ties to a specific engineering output, not a PDF deliverable.

The data shapes below show what machine-readable looks like in practice. These are not reports — they are the inputs to your CI pipeline, evidence chain, and buyer review.

Map

Inventory, trust boundaries, and architecture artifacts that show exactly what exists and where risk lives. Machine-readable so your team can act, not just read.

{
  "system_id": "rag-pipeline-v2",
  "trust_boundary": "tenant",
  "model_provider": "openai",
  "data_classification": "confidential",
  "tool_surface": ["web_search", "file_read"]
}

Artifacts in this pillar

Attack

Adversarial evidence packages that prove exploitability — not scan output, not a checklist. Structured finding registers your board and auditors will accept.

{
  "finding_id": "F-014",
  "pillar": "attack",
  "severity": "high",
  "vector": "indirect_prompt_injection",
  "exploitability": "confirmed",
  "remediation_id": "R-022"
}

Artifacts in this pillar

Defend

Hardening artifacts your engineers can ship — permission matrices, release gate checklists, and playbooks formatted for CI/CD and incident response workflows.

# ai-release-gate.yaml
checks:
  - id: prompt_injection_regression
    required: true
    coverage_threshold: 1.0
  - id: rag_auth_coverage
    required: true
    threshold: 0.95

Artifacts in this pillar

Evidence

Buyer-ready governance artifacts mapped to NIST AI RMF, ISO 42001, and SOC 2 control language. Designed to unblock enterprise deals, not generate paperwork.

{
  "control_id": "NIST-AI-RMF-GOVERN-1.1",
  "status": "implemented",
  "evidence_artifact": "ai-release-gate-checklist",
  "last_verified": "2026-06-01"
}

Artifacts in this pillar

Full catalog

The full catalog, grouped by buyer stage.

Public flagship artifacts lead the page, followed by technical deep dives and appendix assets. That keeps the gallery useful for buyers instead of just complete for authors.

Public flagship

Buyer-ready evidence and engineering-ready remediation artifacts that should lead the catalog and service pages.

sample
Secondary / technical deep dive

Supporting technical artifacts that deepen the evidence chain.

technical deep dive
Appendix / internal / supporting

Long-pack support material that should stay behind the main catalog surface.

appendix
Why this matters

Buyers do not buy process. They need evidence.

The deliverables make the service concrete before the first call. They show the shape of the work: boundaries, permissions, controls, risks, evidence, decisions, and remediation.