Assessor_2.0/fixtures/README.md

4.0 KiB

Synthetic source fixtures

These inputs are now registered in tests/importers/import-contracts.json and checksum-protected by the mandatory import compatibility gate. See docs/IMPORT_COMPATIBILITY.md. Keep existing inputs and expected behavior; extend with new synthetic cases instead of replacing a working format. Customer reports are not permitted as compatibility baselines.

All files below are deliberately small, synthetic, and free of customer or company data. They are regression inputs for the generic import pipeline, not complete vendor golden files. Source-specific recognition and semantic extraction remain part of Phase 6.

PingCastle

CIS-CAT

  • Files: cis-cat/assessment.synthetic.html and cis-cat/assessment.future-controls.synthetic.html
  • Basis: the official CIS-CAT guide documents the HTML sections Summary, Profiles, Assessment Results, and Assessment Details; it also documents Pass, Fail, Error, Unknown, and Manual result states and the detail areas Description, Rationale, Remediation, Impact, Assessment, References, and CIS Controls.
  • assessment.future-controls.synthetic.html repeats the same rule structure with control mappings the application cannot know in advance: a newer revision of the same CIS series and an unrelated framework. It is the regression input for section detection that must read its headings from the report instead of a fixed list, so that hidden evidence and control tables keep reaching the results window when a later report adds a framework.
  • Sources:

Maester

maester/application-json-binding.synthetic.html protects the current static declaration in an application/json script. maester/multi-tenant.synthetic.html protects separate native tenant paths. Both contain only invented Dummy values.

Compatibility references use synthetic data only, including when a real report reveals a new structure.