Repository navigation
Conversation
…andard v2.0 design spec
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements the vendor-neutral Open Security Usecase & Blue Team Evaluation Metadata Standard (
schema_version: "2.0") for standardized telemetry replay, cross-platform SIEM/Lakehouse bindings (Google SecOps, Databrickssecops_ocsf.*, Sigma, Splunk), and held-out Blue Team agent evaluations:src/logstory/schema/models.py):SecurityUsecaseManifest,SecurityUsecaseEval,ParsedUsecasePackage,parse_usecase_package,export_json_schemas) with strict unknown-key rejection and lossless round-trip serialization.schemas/usecase.schema.jsonandschemas/eval.schema.json.src/logstory/schema/validator.py):G1_SCHEMA: Structural and enum validation against v2 manifest and evaluation schemas.G2_INTEGRITY: Verifies on-disk telemetry/detection file paths and cross-referenceskill_chain[].evidence_streamsagainst declaredtelemetrystream_ids.G3_ANTI_SPOILER: Rejects ground-truth keys inside<USECASE>.mdfrontmatter and checks that held-out malicious IOCs, compromised accounts, and patient-zero hosts fromeval.yamldo not leak above<!-- BEGIN_SOLUTION -->.G4_COUNTERFACTUAL: Verifies bidirectional twin consistency acrosscounterfactual_pairscenarios.G5_LEGACY_V1: Emits upgrade warnings for v1 manifests by default and errors under--strict-v2.usecases/generate_usecase_docs.py,usecases/usecase_template.j2):normalize_frontmatter_for_template()and a stdlib fallback renderer while migrating built-inusecases/NETWORK_ANALYSISandusecases/RULES_SEARCH_WORKSHOPtoschema_version: "2.0"+eval.yaml.src/logstory/logstory.py):logstory usecases validate [TARGET] [--strict-v2] [--format text|json]logstory usecases inspect <USECASE> [--blind|--include-eval] [--format text|json]logstory usecases export-schemas [--output-dir DIR]logstory replay usecase <USECASE> --with-paired-baselinesVerification
pytest tests/ -v:237 passed(including 62 new unit, CLI, and 47-scenario corpus tests).ruff check .andpyink --check .: 0 issues.