CROSSWALKS

GAISSF to CRO 019 ISO IEC 42001 Crosswalk

Public crosswalk publication mapping GAISSF v1.0 to CRO 019 ISO IEC 42001, with scope, method, limitations and traceability.

GAISSF™ v1.0

ISO/IEC 42001:2023 Mapping

Verified control, evidence-reuse and residual-testing crosswalk

Document ID: GAISSF-CRO-019

Version: 1.0

Status: Verified Publication Candidate

Classification: Informative Crosswalk

Publisher: ODA3 Institute

Legal entity: ODA3 Pvt Ltd

Source baseline: ISO/IEC 42001:2023(E); GAISSF v1.0; VTS v1.0.1

Document Control and Reliance Notice

PurposeSupport comparative analysis, ISO evidence reuse, GAISSF gap identification and residual VTS planning.
Mapping directionGAISSF control → ISO/IEC 42001 clauses, Annex A controls and Annex B guidance.
Normative statusInformative. GAISSF-NOR-001/NOR-004 and ISO/IEC 42001 remain authoritative for their own requirements.
Copyright handlingISO/IEC text was used as a controlled internal source. This document uses identifiers and original paraphrase and does not reproduce the standard.
Conformity claimA mapping does not establish equivalence, implementation, certification or compliance.
VTS statusDemo fixtures are non-certifying. Certification use requires approved fixtures, evidence schema, persistent signing key and signed manifest.
MaintenanceReview on GAISSF release, VTS/schema change, ISO amendment/corrigendum, or identified mapping defect.

1. Executive Assessment

The complete ISO/IEC 42001:2023 source supplied by the user was used to revalidate all 59 GAISSF controls. ISO/IEC 42001 provides substantial management-system, risk, impact, lifecycle, data, resource, supplier, documentation and assurance coverage. It generally does not prescribe the control-specific adversarial, agentic, runtime, content-security or cyber-physical mechanisms and quantitative pass criteria defined by GAISSF and its VTS.

The principal reuse opportunity is documentary and governance evidence. The principal residual is technical validation: an organization may reuse ISO-aligned records, but must still demonstrate the GAISSF outcome and linked VTS criteria where applicable.

2. Mapping Method

  • Map by objective, scope, trigger, lifecycle stage, evidence and assurance—not keywords alone.
  • Use the most specific ISO location supported by the source, including Annex B where it materially informs interpretation.
  • Classify the relationship as Direct enablement, Strong partial, Partial, Supporting or Contextual.
  • Record residual requirements and notably absent technical mechanisms in every row.
  • Treat evidence reuse as conditional on scope match, authenticity, currency, completeness and operating effectiveness.

3. Relationship Taxonomy

RatingMeaningPermitted interpretation
Direct enablementThe GAISSF control explicitly performs or governs the ISO mapping activity.Supports execution of the mapping process; does not itself establish ISO conformity.
Strong partialSubstantial objective, scope and evidence overlap.Evidence may be reused after qualification; GAISSF residual remains.
PartialRelated objective or lifecycle coverage with material differences.Use as supporting evidence only.
SupportingGeneral governance or assurance support.Do not treat as control satisfaction.
ContextualRelevant external-regime or comparison context.No equivalence or compliance inference.

4. Evidence-Reuse Decision Rules

  1. Confirm the ISO AIMS scope matches the GAISSF assessment boundary and AI-system inventory.
  2. Verify the record addresses the same control objective, system, period, supplier and lifecycle stage.
  3. Reject policy-only evidence where the GAISSF control requires operating-effectiveness or technical test evidence.
  4. Preserve provenance, version, approvals, retention, integrity and chain of custody.
  5. Execute the linked VTS where the ISO record does not demonstrate the GAISSF pass criteria.
  6. Record accepted, partially accepted and rejected evidence with rationale.

5. Notably Absent at the ISO Baseline

ISO/IEC 42001 deliberately permits additional controls beyond Annex A. The following are not prescribed as discrete, testable mechanisms by ISO/IEC 42001 and therefore remain GAISSF residuals where applicable: prompt-injection and jailbreak defenses; least-agency and multi-agent trust controls; model extraction and backdoor testing; LoRA, merge and quantization integrity; AI BOM and model scanning; MCP monitoring and shadow-AI discovery; content filters, leakage tests and watermark robustness; deepfake and AI social-engineering defenses; and functional-safety mechanisms such as safe state, emergency stop, actuator verification and physical-environment integrity monitoring.

6. Detailed 59-Control Crosswalk

Each row must be read together with its residual and VTS columns. ISO locations are reference identifiers; no protected ISO text is reproduced.

Controlled Publication. The table below shows a representative sample (6 of 59 total records). The complete control-by-control mapping register — full requirement-level traceability, evidence guidance and machine-readable export — is a Controlled Publication. Contact ODA3 Institute for access.
GAISSF controlVTSISO/IEC 42001 locationsRelationship / confidenceEvidence potentially reusableAdditional GAISSF validationResidual / notably absent
D1-CTL-01 Dataset Provenance & Poisoning PreventionD1-CTL-01-VTS-001 Automated tests/d1_model_integrity/test_dataset_provenance.py6.1.2; 6.1.3; 8.1; 8.2; 8.3; A.4.3; A.6.2.4; A.7.2; A.7.3; A.7.4; A.7.5; B.4.3; B.6.2.4; B.7.2-B.7.5Strong partial HighRisk/impact assessments; treatment and SoA records; controlled lifecycle documentation; monitoring, audit, supplier, competence, or communication records applicable to the cited locations.hash_verified = True; source_in_allowlist = True; poisoning_score = 0; test_coverage >= 1000 samples Action: Execute or independently verify the linked GAISSF VTS using scope-appropriate, non-demo fixtures and preserve schema-valid signed evidence.ISO/IEC 42001 supports data, resource, lifecycle, validation, and monitoring governance but does not prescribe this model-integrity technique or GAISSF VTS threshold.
D1-CTL-02 Model Extraction ResistanceD1-CTL-02-VTS-001 Automated tests/d1_model_integrity/test_model_extraction.py6.1.2; 6.1.3; 8.1; 8.3; 9.1; A.6.2.4; A.6.2.6; B.6.2.4; B.6.2.6Partial MediumRisk/impact assessments; treatment and SoA records; controlled lifecycle documentation; monitoring, audit, supplier, competence, or communication records applicable to the cited locations.extraction_success_count < 10 (0.1% of queries); detection_alerts_triggered = True; rate_limiting_enforced = True Action: Execute or independently verify the linked GAISSF VTS using scope-appropriate, non-demo fixtures and preserve schema-valid signed evidence.ISO/IEC 42001 supports data, resource, lifecycle, validation, and monitoring governance but does not prescribe this model-integrity technique or GAISSF VTS threshold.
D1-CTL-03 Behavioral Drift DetectionD1-CTL-03-VTS-001 Automated tests/d1_model_integrity/test_behavioral_drift.py6.1.2; 6.1.3; 8.1-8.3; 9.1; 10.1-10.2; A.6.2.4; A.6.2.6; A.6.2.8; B.6.2.4; B.6.2.6; B.6.2.8Strong partial HighRisk/impact assessments; treatment and SoA records; controlled lifecycle documentation; monitoring, audit, supplier, competence, or communication records applicable to the cited locations.max_kl_divergence < 0.05; accuracy_drop < 5% over 30 days; alert_generated_for_any_drift_event = True Action: Execute or independently verify the linked GAISSF VTS using scope-appropriate, non-demo fixtures and preserve schema-valid signed evidence.ISO/IEC 42001 supports data, resource, lifecycle, validation, and monitoring governance but does not prescribe this model-integrity technique or GAISSF VTS threshold.
D1-CTL-04 Federated Learning Poisoning PreventionD1-CTL-04-VTS-001 Hybrid (Automated + Manual Review) tests/d1_model_integrity/test_federated_poisoning.py6.1.2; 6.1.3; 8.1; A.4.2-A.4.5; A.6.1.3; A.6.2.4; A.7.2-A.7.5; B.4; B.6.1.3; B.6.2.4; B.7Partial MediumRisk/impact assessments; treatment and SoA records; controlled lifecycle documentation; monitoring, audit, supplier, competence, or communication records applicable to the cited locations.malicious_gradient_detection_rate >= 95%; poisoned_gradients_excluded_from_aggregation = True Action: Execute or independently verify the linked GAISSF VTS using scope-appropriate, non-demo fixtures and preserve schema-valid signed evidence.ISO/IEC 42001 supports data, resource, lifecycle, validation, and monitoring governance but does not prescribe this model-integrity technique or GAISSF VTS threshold.
D1-CTL-05 Embedding Space RobustnessD1-CTL-05-VTS-001 Automated tests/d1_model_integrity/test_embedding_robustness.py6.1.2; 6.1.3; 8.1; 9.1; A.6.2.4; A.6.2.6; B.6.2.4; B.6.2.6Partial MediumRisk/impact assessments; treatment and SoA records; controlled lifecycle documentation; monitoring, audit, supplier, competence, or communication records applicable to the cited locations.classification_change_rate < 5% under bounded perturbation (epsilon=0.1); certified_radius_measured = True Action: Execute or independently verify the linked GAISSF VTS using scope-appropriate, non-demo fixtures and preserve schema-valid signed evidence.ISO/IEC 42001 supports data, resource, lifecycle, validation, and monitoring governance but does not prescribe this model-integrity technique or GAISSF VTS threshold.
D1-CTL-06 Post-Quantum Model Signing & Crypto HardeningD1-CTL-06-VTS-001 Automated tests/d1_model_integrity/test_pqc_signing.py6.1.3; 7.5.3; 8.1; A.4.4; A.4.5; A.6.2.3-A.6.2.5; B.4.4-B.4.5; B.6.2.3-B.6.2.5Supporting MediumRisk/impact assessments; treatment and SoA records; controlled lifecycle documentation; monitoring, audit, supplier, competence, or communication records applicable to the cited locations.legacy_rsa_signature_rejected = True; tls_downgrade_blocked = True; pqc_key_exchange_enabled = True Action: Execute or independently verify the linked GAISSF VTS using scope-appropriate, non-demo fixtures and preserve schema-valid signed evidence.ISO/IEC 42001 supports data, resource, lifecycle, validation, and monitoring governance but does not prescribe this model-integrity technique or GAISSF VTS threshold.

7. Reverse Traceability Summary

ISO locationPrimary subjectGAISSF reuse / limitation
Clauses 4-5Context, scope, leadership, policy, rolesPrimarily D6 and D8; supports D3/D4 accountability and boundary decisions.
Clause 6Risk, impact, treatment, objectives and change planningCross-domain support; strongest general bridge to GAISSF control selection and residual controls.
Clause 7Resources, competence, awareness, communication and documented informationD6/D7 governance evidence and evidence-control support across all domains.
Clause 8Operational planning, risk treatment and impact assessmentOperational bridge to all domains, but does not define most GAISSF technical mechanisms.
Clauses 9-10Monitoring, audit, management review, corrective action and improvementAssurance reuse across all domains; technical retesting remains required.
Annex A.2-A.3Policy and internal organizationD6 governance; D3/D4 accountability.
Annex A.4AI resourcesD1, D3, D4 and D9 resource/component inventories.
Annex A.5AI-system impactsD5, D7, D8 and D9 impact/harm assessment.
Annex A.6AI lifecycleBroadest technical-governance overlap across D1-D6 and D9.
Annex A.7Data for AI systemsD1 and D5 data governance, provenance, quality and preparation.
Annex A.8Information for interested partiesD5/D6/D8 documentation, concerns, incident communication and reporting.
Annex A.9Responsible useD2/D3/D5/D6/D7 use controls and human oversight.
Annex A.10Third-party and customer relationshipsD4 and D6 supplier/shared-responsibility governance.

8. VTS and Certification Handling

  • The VTS release manifest links all 59 controls to executable test files.
  • Demo mode and placeholder fixtures are non-certifying.
  • Certification use requires the evidence schema, persistent Ed25519 signing key, real or certified-simulation fixtures and a signed manifest.
  • ISO evidence may reduce duplicate documentary work but does not waive GAISSF technical validation or independent verification.
  • Any test substitution, inherited evidence or compensating control decision must be documented by the applicable assessment scheme.

9. Source Register

SourceUse
ISO/IEC 42001:2023(E)Complete 62-page source supplied by user; internal controlled use; not distributed with CRO-019.
GAISSF-NOR-001 v1.0Authoritative framework, conformance and evidence baseline.
GAISSF-NOR-004 v1.0Authoritative 59-control catalogue and VTS/evidence records.
GAISSF-NOR-005 v1.0Controlled terminology.
GAISSF-NOR-006 v1.0Controlled source and crosswalk citation rules.
GAISSF VTS v1.0.1Executable 59-control validation package and release manifest.
GAISSF evidence schema v1.0Machine-readable evidence structure.
GAISSF implementation/crosswalk schemas v1.0Machine-readable control and mapping structures.

10. Publication and Claims Rules

  • Publish CRO-019 as informative, version-controlled and source-bounded.
  • Do not reproduce the supplied ISO/IEC PDF or substantial ISO text.
  • Do not state that GAISSF is equivalent to ISO/IEC 42001 or that one certification satisfies the other.
  • Identify the exact GAISSF and ISO editions in every mapping claim.
  • Publish the DOCX/PDF explanation together with the XLSX register and JSON register.
  • Record changes to mappings, relationship ratings, VTS IDs or source editions in controlled release notes.

Annex A — Mapping Register Field Definition

FieldDefinition
control_idStable GAISSF control identifier.
vts_id / vts_test_fileExecutable validation traceability.
iso_42001_referencesClause, Annex A control and Annex B guidance identifiers.
relationshipNature of overlap without equivalence.
mapping_confidenceStrength of source-based mapping conclusion.
iso_evidence_reuseEvidence candidates subject to qualification.
additional_gaissf_validationResidual VTS or independent verification action.
gaissf_residual_notably_absentSpecific mechanism or outcome not prescribed by the ISO baseline.