An open, vendor-neutral standard for verifying open-source intelligence. OOVS v0.1.0 defines ten testable requirements published simultaneously as normative text and machine-readable data, with one acceptance test per requirement, a portable assessment schema, and continuous validation.
The normative standard is published at https://github.com/OWASP/OWASP-Open-Source-Intelligence-Standard/blob/main/oovs/v0.1/standard.md
Machine-readable artefacts accompany it: the requirement catalogue at oovs/v0.1/requirements.json with its schema, the acceptance tests at oovs/v0.1/tests.json with one test per requirement, the assessment result schema at oovs/v0.1/assessment.schema.json with a worked synthetic example, and informative mappings to public guidance at oovs/v0.1/mappings.md.
Requirement identifiers follow OOVS-v0.1.0-NN and acceptance tests follow OOVS-v0.1.0-TNN. Identifiers are stable within the 0.1 line, so reports and tooling should always cite the version.
Project Leader
Project leader for the OWASP Open Source Intelligence Standard. Designed the OOVS assurance baseline and the specification-as-code pipeline that keeps its normative text, machine-readable requirements, acceptance tests, and hash-pinned release manifests provably consistent in continuous integration. Interests: OSINT verification, provenance and source-origin independence, attribution, and accountable use of AI in analytic workflows.