Binh
5fd8f98014
The Compliance Engine maps newly uploaded scans and GPO evaluations to ISO controls while the new Data Hub switch "Map new scans automatically" is on (default off). An engine-side watcher reads only through ComplianceReadPort: active scan runs and, for GPOs, the deviation rows of each timeslot as filtered Result DB pages. It starts the existing ISO batch per new scan run or per timeslot with new GPO rows; already mapped rules are reused, so only new rules reach the model. Existing data forms the baseline and is not mapped retroactively. The switch lives in the engine's own settings file, not a Core table. Switching the Compliance Engine off in the Engines popup also switches automatic mapping off server-wide. Core changes (released Platform, Core Tests, Presentation, Governance): PUT /reference-data/iso-corpus/auto-mapping route, setIsoAutoMapping API client method, subscribeEnginePreferences export, AGENTS.md decision and product version 2.19.1 -> 2.20.0. |
||
|---|---|---|
| .. | ||
| ai | ||
| artifacts | ||
| compliance | ||
| gpo | ||
| postgres | ||
| reference-data | ||
| remediation | ||
| reporting | ||
| assessor-http-server.ts | ||
| import-executor.ts | ||
| import-worker-client.ts | ||
| import-worker.ts | ||
| index.ts | ||
| node-import-runtime-adapters.ts | ||
| repository-factory.ts | ||