
Platform Quickstart
Achieve end-to-end security and compliance for AI at scale.
From AI discovery to compliance attestation, on platform for complete visibility across you AI ecosystem.
01 CONNECT
02 DISCOVER
03 BILL OF MATERIALS
04 GOVERNANCE
05 VULNERABILITIES
06 DOCUMENT LIBRARY
07 COMPLIANCE
08 ARENA & SHIELD
-- THIRD-PARTY PUBLISHING
-- PUBLIC API
-- REFERENCE
-- SUPPORT

WELCOME
Visibility across your entire AI ecosystem
This Quickstart walks you through the Cranium platform from first integration to compliance attestation. Whether you are securing AI systems, mapping regulatory requirements, or building an inventory of AI assets across your organization, this guide gets you there.
What you will have at the end


THE JOURNEY
Eight stages, one track

BEFORE YOU BEGIN
Have these ready
- Cranium tenant provisioned - Contact your account manager if you need one.
- Repository admin access - Administrator rights to your organization's code repositories.
- Access credentials prepared - A Personal Access Token or OAuth authorization for your VCS (see below).
Access Credentials by Platform
GitHub Personal Access Token with repo scope, or OAuth authentication

GitLab Personal Access Token with read_repository scope

Bitbucket Personal Access Token with repository:read scope

Azure DevOps Personal Access Token with Code (read) scope

STAGE 01 | CONNECT
Connect Your Repositories
Establish Version Control System Integration
GOAL Connect Cranium to your code repositories so it can scan for AI/ML assets.
INSTRUCTIONS
- Open Integrations from the left navigation and select the VCS Integrations tab.
- Click Add New VCS Integration above the integrations list.
- Complete the Create VCS Integration dialog: Name (descriptive), Description (optional), Service (your VCS platform), Base URL (root domain, including an organization name where required), and Authentication Method (Personal Access Token, or OAuth for GitHub).
- Click Save to establish the connection.
Detailed Docs


STAGE 02 | DISCOVER
Discover Your AI Assets
Discover Repositories, Then Run Detect AI
GOAL Discover the projects and repositories in your connected VCS, then run Detection to find where AI lives.
INSTRUCTIONS
- Open Integrations from the left navigation and select the VCS Integrations tab.
- On your VCS integration row, click Discover Repos to run Discovery. Cranium finds the projects and repositories in that integration and populates the Detect AI tables (re-run later with Re-run Discovery in the row flyout).
- When Discovery completes, the row action becomes Detect AI. Click it (or open Detect AI from the left navigation) to review the discovered projects, groups, and repositories.
- Run Detection: use Run Detect AI on a single repository or group, select items and click Detect AI in Selected, or choose Detect AI Everywhere to scan all repositories.
- Review results on the Repositories tab (per-repo AI Detected) and the VCS Projects / Orgs / Groups tab, which rolls up scan results and AI-detected counts per project or group.
Detailed Docs


STAGE 03 | BILL OF MATERIALS
Create Your First AI BOM
Generate a Comprehensive Component Inventory
GOAL Produce a Bill of Materials cataloging the models, datasets, and technologies in a target system.
INSTRUCTIONS
- Navigate to Artifacts > Bill of Materials.
- Click Add Bill of Materials.
- Selected a scanning method: Public Repository (direct GitHub URL), Private Repository (from a connected VCS), or Inventory (from Detect AI discoveries).
- Capture BOM details: Name (a descriptive identifier), Description (system purpose and context), and Owner (the responsible party).
- Start the scan with Save & Scan Repository.
Detailed Docs
CODESENSOR ANALYSIS
CodeSensor catalogs models, datasets, and technologies from Python, Go, Java, JavaScript, TypeScript, Rust and configuration files using a three-tier approach: package extraction, AST-based analysis, and LLM-powered code understanding. AgentSensor, embedded in the scan, additionally identifies AI agent frameworks and agentic patterns such as tool-calling architectures, multi-agent orchestration, and memory structures.


STAGE 04 | GOVERNANCE
Establish AI Governance
Create Your First AI System, and Generate the AI Card
GOAL Create a centralized AI System record with full traceability. This is the artifact that anchors your governance program, and the AI Card is its customer-facing output, ready to share with risk, audit, and procurement stakeholders.
INSTRUCTIONS
- Navigate to AI System Manager > My AI Systems.
- Click Add AI System.
- Define the system identity: Name, Description (purpose and capabilities), and Owner (accountability).
- Click Continue to proceed.
- Complete the governance details.
- Attach relevant artifacts: the Bill of Materials from Step 3, compliance frameworks, and supporting documentation.
- Click Save. The AI Card is generated automatically from this record.
Detailed Docs


STAGE 05 | VULNERABILITIES
Assess Security Posture
Review Findings on the Vulnerabilities Page
GOAL Triage vulnerabilities across your entire AI ecosystem from one place: adversarial model risks alongside CVE-based technology findings.
INSTRUCTIONS
- Open Vulnerabilities from the left navigation.
- Switch between the Models and Technologies tabs. Models list adversarial attack-category findings with a Vulnerability Likelihood score; Technologies lists CVE findings from detected packages with CVSS scores and severity.
- Toggle Show Severity Statistics to see Critical, High, Medium, and Low count for the active tab.
- Filter by AI System, BOM, model, or severity to focus on what matters most.
- Resolve, ignore, or restore findings as you work through them, and use Export Vulnerabilities to push all or filtered results into your vulnerability-management workflow.
Details Docs


STAGE 06 | DOCUMENT LIBRARY
Build Your Document Library
Upload Policy and Governance Documents
GOAL Populate your Document Library so the Compliance Agent (Step 7) can search your policies when answering framework questions.
INSTRUCTIONS
- Navigate to Document Library in the left navigation.
- Click Add Document.
- Upload your governance documents: AI governance policies, Standard Operating Procedures, risk-management frameworks, and data-handling and privacy policies.
- Wait for document processing to complete.
- Confirm documents appear with Processed status before continuing.
Detailed Docs


STAGE 07 | COMPLIANCE
Establish Compliance
Attach and Complete a Framework
GOAL Map your AI System to a regulatory or governance framework and generate citation-backed answers with Compliance Agent.
INSTRUCTIONS
- Within you AI System, click Add Artifact.
- Select Compliance Framework.
- Choose a framework: NIST AI RMF Starter Pack v2 (Compliance Agent supported), EU AI Act, or ISO/IEC 42001.
- Complete the framework questions.
- Click Evaluate Answers for scoring.
Detailed Docs


STAGE 08 | ARENA & SHIELD
Test Your Defenses
Arena and Shield — Adversarial Posture and Guardrail Effectiveness
GOAL Stress-test the AI system itself with Arena, then measure how well your guardrails block adversarial attacks with Shield.
Arena performs automated red-teaming of discovered LLMs across eight attack categories: jailbreaks, prompt injection, encoding attacks, hallucinations, harmful response generation, misinformation, data leakage, and cyberattack enablement. Shield then measures how well your safety guardrails block those attacks, returning per-category block rates and exposing gaps in your defense configuration.
INSTRUCTIONS
- Navigate to Arena Shield and click Start a New Test Run.
- Enter a descriptive Test Run Name.
- Select your Base Model, populated from LLMs discovered in your AI BOMs (only Arena-testable models appear).
- Choose a System Prompt: Template (a preconfigured adversarial prompt), Discovered (extracted from the model's BOM), or Custom.
- Click Configure Guardrails to add defense models: Input defense screens prompts before they reach the model; Output defense screens responses before delivery.
- Click Begin Test Run and monitor progress on the results page.
- Review per-category results: block rate per attack category, breakthrough rate, and overall defense effectiveness score.
Detailed Docs


BEYOND THE JOURNEY
Third-party publishing
Deliver transparency without granting tenant access
Once an AI System is governed and its AI Card has been generated in Step 4, you can share that card with organizations outside your own. Publishing delivers a point-in-time AI Card, with only the artifacts you choose to include, to a specific third-party organization, giving customers, auditors, and procurement teams the transparency they need without any access to your Cranium tenant.
GOAL Publish an AI Card to an external organization and manage it from the AI System Manager.
INSTRUCTIONS
- Navigate to AI System Manager > Published AI Cards and click Publish AI Card. You can also start from an AI System's detail page via Publish New AI Card > To Organization.
- Recipient Details. Select or add the recipient organization, entering its name and a contact point: first name, last name, and email.
- Configure Card. Choose the AI System to publish, give it a Published Name, and attach the artifacts to include: Bill of Materials, Vulnerability Reports, Compliance Frameworks, and Document Library files.
- Review & Publish. Confirm the recipient, published name, and attached artifacts, then click Publish.
- Locate the card under Published AI Cards, where you can track its status and manage it.
Detailed Docs


INTEGRATE
Cranium Public API
Cranium exposes a Public API for teams that prefer to integrate platform capabilities into their existing toolchain rather than driving them through the UI. Typical use cases include:
- Export vulnerability findings into your existing vulnerability-management workflow, such as Jira or ServiceNow.
- Put Bill of Materials data into your internal asset inventory or SBOM consolidation tooling.
- Surface Arena model inventory and attack-category data in your security-operations dashboards.
API documentation, authentication, and the endpoint reference live under the Public API category on docs.cranium.ai.
Detailed Docs

REFERENCE
Glossary
- AgentSensor - The component of CodeSensor that scans specifically for AI agent frameworks and agentic patterns, including tool-calling architectures, multi-agent orchestration, and memory structures.
- AI BOM - AI Bill of Materials. A comprehensive inventory of an AI system's components: models, datasets, dependencies, and configuration. Cranium's equivalent of a software BOM, specialized for AI.
- AI Card - Cranium's standardized transparency artifact for an AI system, summarizing identity, ownership, BOM, vulnerability posture, and compliance status in a format suitable for external sharing.
- AI System - Cranium's central governance record for an AI/ML system. Anchors ownership, attached artifacts, and ongoing assessment.
- Arena - Cranium's automated red-teaming environment. Tests LLMs across eight attack categories, from jailbreaks and prompt injection to data leakage and cyberattack enablement.
- Arena Shield - Cranium's guardrail-effectiveness testing. Measures how well defense models block adversarial attacks across the same eight attack categories.
- CodeSensor - Cranium's code-analysis engine. Catalogs models, datasets, and technologies using three-tier analysis: package extraction, AST-based analysis, and LLM-powered code understanding.
- Compliance Agent - Automation that maps policies and SOPs to framework requirements and generates citation-backed answers. Currently supports NIST AI RMF Starter Pack v2.
- CVE - Common Vulnerabilities and Exposures. The industry-standard catalog of publicly disclosed security vulnerabilities, maintained by MITRE.
- Detect AI - Cranium's automated discovery of AI/ML code across connected repositories.
- EU AI Act - The European Union regulatory framework governing AI systems, with tiered obligations based on risk classification.
- ISO/IEC 42001 - The international standard for AI management systems, focused on responsible AI governance.
- MITRE ATLAS - Adversarial Threat Landscape for Artificial-Intelligence Systems. A MITRE knowledge base of adversary tactics targeting AI.
- NIST AI RMF - The U.S. NIST AI Risk Management Framework. A voluntary framework for managing AI risks.
- OSV - Open Source Vulnerabilities. A distributed vulnerability database for open-source software.
- OWASP ML Top 10 - The Open Web Application Security Project's catalog of the top ten machine-learning security risks.
- PAT - Personal Access Token. An authentication credential used in place of a password for programmatic access to a VCS.
- VCS - Version Control System. A source-code management platform such as GitHub, GitLab, Bitbucket, or Azure DevOps.

WE ARE HERE TO HELP
Secure and govern AI, with a team behind you.
Questions are you work through the platform? Reach the people and resources that can help you move faster.
- Support Portal - support.cranium.ai
- Knowledge Base - docs.cranium.ai
- Training - learn.cranium.ai
- Email - [email protected]





