VulnGPTDOCUMENTATION

NOVASECLABS / KNOWLEDGE BASE

Understand the system.
Interrogate the evidence.

Product context, technical principles, application-security practice, and enterprise evaluation resources for VulnGPT.

01 Product & technical context 02 Practitioner resources 03 Enterprise evaluation

DOCUMENT LIBRARY

Find what you need.

Search by topic or narrow the library by audience.

VulnGPT is in private beta. Documentation describes product direction and evaluation guidance; it does not guarantee current feature availability.

Showing all documents

START HERE 0101

Product overview

What VulnGPT is being built to investigate, who it serves, and where its boundaries are.

Read document ↗
TECHNICAL FOUNDATION 0202

Technical approach

A conceptual model for investigating behavior across identity, authorization, and application state.

Read document ↗
SYSTEM MODEL 0303

System overview

Public conceptual architecture, trust boundaries, and the separation between test context and evidence review.

Read document ↗
EVIDENCE STANDARD 0404

Evidence and validation

How to distinguish a suspicious signal from a supported, reviewable security conclusion.

Read document ↗
PRACTITIONER GUIDE 0505

Security testing playbook

Controlled patterns for object ownership, roles, multi-step workflows, sessions, and ambiguous results.

Read document ↗
EVALUATION TOOL 0606

Capability evaluation matrix

Scenario dimensions, required context, evidence expectations, and common false conclusions.

Read document ↗
REPRODUCIBLE METHOD 0707

Evaluation protocol

Define ground truth and outcomes before a run; separate execution, observability, correctness, and evidence quality.

Read document ↗
REFERENCE 0808

Application security use cases

Representative application behaviors that motivate contextual security testing.

Read document ↗
REFERENCE 0909

Security glossary

Shared definitions for application-security, evidence, authorization, and workflow terminology.

Read document ↗
BUYER GUIDE 1010

Enterprise evaluation

A structured diligence guide for security, architecture, procurement, privacy, and product stakeholders.

Read document ↗
TRUST CENTER 1111

Security and privacy

Public trust boundaries and the specific questions that require current vendor confirmation.

Read document ↗
TRUST MODEL 1212

Security model

Conceptual actors, data assets, trust boundaries, and threat scenarios for evaluation.

Read document ↗
WORKSHEET 1313

Assessment plan

Define scope, identities, operational constraints, data handling, approvals, and success criteria.

Read document ↗
REPORTING STANDARD 1414

Finding report standard

Structure a finding around the expected boundary, evidence, impact, uncertainty, and retest.

Read document ↗
PUBLICATION POLICY 1515

Benchmark governance

Reproducibility, denominator integrity, independent review, and benchmark publication gates.

Read document ↗
CLAIM CONTROL 1616

Claims and messaging

Approved product language and guardrails for performance, security, and assurance statements.

Read document ↗
MAINTAINERS 1717

Release process

Review, verification, publication, and correction procedures for the public showcase.

Read document ↗
SAFE USE 1818

Responsible testing

Authorization, scope, data minimization, safe execution, and coordinated disclosure guidance.

Read document ↗
MAINTAINERS 1919

Repository maintenance

Local validation, asset hygiene, public-content review, and repository ownership.

Read document ↗
QUICK ANSWERS 2020

Frequently asked questions

Product status, access, intended use, supported claims, and common evaluation questions.

Read document ↗
MACHINE-READABLE RESOURCES 2121

Public evaluation schemas

Optional JSON formats for externally documenting findings and benchmark reports—not VulnGPT API contracts.

Read schemas ↗

IMPORTANT CONTEXT

Public documentation.
Bounded claims.

VulnGPT is in private beta. These documents describe product direction, conceptual methods, and evaluation resources. They do not guarantee feature availability, security certification, benchmark performance, or contractual controls. Confirm the proposed use case and current terms with NovaSecLabs.