CROSSWALKS
GAISSF to CRO 020 ISO IEC 27001 Crosswalk
Public crosswalk publication mapping GAISSF v1.0 to CRO 020 ISO IEC 27001, with scope, method, limitations and traceability.
GAISSF™ v1.0
ISO/IEC 27001 MAPPING
Crosswalk for Compliance Reuse, Gap Analysis, VTS Traceability and Evidence Qualification
| Document ID | GAISSF-CRO-020 |
|---|---|
| Version | 1.0 |
| Status | Verified Final Publication v1.0 |
| Classification | Informative crosswalk |
| GAISSF baseline | 59 controls across nine domains |
| External baseline | ISO/IEC 27001:2022(E), Third edition |
| Amendment status | Amd 1:2024 tracked as maintenance note; not full-text verified |
| Distribution | Website and GitHub |
Controlled-use notice. This publication maps GAISSF control outcomes to ISO/IEC 27001:2022 clauses and Annex A controls. It does not reproduce the standard, replace an authorized copy, establish equivalence, or independently prove conformity with either framework.
1. Purpose and Scope
CRO-020 supports comparative analysis, control reuse, evidence qualification, implementation planning and gap identification between GAISSF v1.0 and ISO/IEC 27001:2022. It covers all 59 GAISSF controls and the complete ISO/IEC 27001 management-system and Annex A control structure.
2. Source and Copyright Boundary
The complete ISO/IEC 27001:2022(E) source supplied by the user was used as an internal controlled reference. ISO and IEC designations and text remain protected. This publication uses clause/control identifiers and original analytical descriptions only. The licensed source is not included in the release package.
3. Mapping Method
Each relationship was assessed against objective, scope, trigger, asset or system boundary, lifecycle stage, evidence, operating-effectiveness expectation and residual GAISSF VTS requirement. Similar terminology alone was not treated as equivalence.
4. Relationship and Confidence Taxonomy
| Rating | Meaning | Permitted interpretation |
|---|---|---|
| Direct enablement | The GAISSF control explicitly performs or governs an ISO mapping activity. | Supports execution; does not establish ISO conformity. |
| Strong partial | Substantial objective, scope and evidence overlap. | Evidence may be reused after qualification; residual remains. |
| Partial | Related coverage with material differences. | Supporting evidence only. |
| Supporting | General governance or assurance support. | Do not treat as control satisfaction. |
| Contextual | External-regime or comparison context. | No equivalence or compliance inference. |
5. Evidence-Reuse Decision Rules
- Confirm that the ISO/IEC 27001 ISMS scope, assets, suppliers and evidence period match the GAISSF assessment boundary.
- Use the ISO Statement of Applicability as an evidence index, not as automatic proof that a GAISSF control is satisfied.
- Reject policy-only evidence where GAISSF requires technical execution, benchmark results or operating-effectiveness evidence.
- Preserve provenance, approvals, integrity, retention, sampling and chain of custody.
- Execute the linked GAISSF VTS when the ISO evidence does not demonstrate the GAISSF pass criteria.
- Document accepted, partially accepted and rejected reuse decisions with rationale.
6. Notably Absent from the ISO/IEC 27001 Baseline
ISO/IEC 27001 provides a mature information-security management system and broad organizational, people, physical and technological controls. It does not prescribe most AI-specific mechanisms as discrete test outcomes, including prompt-injection resistance, jailbreak testing, agent permission boundaries, model extraction resistance, model backdoor and adapter/merge/quantization integrity testing, AI BOM semantics, model-hub vetting, MCP behavioral monitoring, harmful-content thresholds, watermark robustness, deepfake defenses, AI-specific regulatory mappings, or functional-safety mechanisms for physical AI.
7. Detailed 59-Control Crosswalk
ISO references are identifiers only. Each row must be read with its relationship, evidence-reuse, VTS and residual columns.
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 control | VTS | ISO/IEC 27001 locations | Relationship / confidence | Evidence potentially reusable | Additional GAISSF validation | Residual / notably absent |
|---|---|---|---|---|---|---|
| D1-CTL-01 Dataset Provenance & Poisoning Prevention | D1-CTL-01-VTS-001 Automated tests/d1_model_integrity/test_dataset_provenance.py | 6.1.2; 6.1.3; 8.1; 8.2; 8.3; 9.1; 5.12; 5.13; 5.14; 5.15; 5.33; 5.34; 8.10; 8.11; 8.12; 8.15; 5.7; 8.7; 8.8; 8.16; 8.20; 8.23; 8.29 | Strong partial High | ISMS scope and context; information-security risk assessment and treatment; Statement of Applicability; Annex A implementation records; supplier, access, logging, incident, continuity, privacy, secure-development, audit, management-review and corrective-action evidence applicable to the cited locations. | hash_verified = True; source_in_allowlist = True; poisoning_score = 0; test_coverage >= 1000 samples Action: Qualify the ISO evidence for matching scope, system, period and operating effectiveness; execute or independently verify the linked GAISSF VTS where the ISO evidence does not demonstrate the GAISSF pass criteria. | ISO/IEC 27001 addresses information security governance, secure development, vulnerability management and integrity controls, but does not prescribe this AI-model integrity technique, benchmark, or GAISSF VTS threshold. |
| D1-CTL-02 Model Extraction Resistance | D1-CTL-02-VTS-001 Automated tests/d1_model_integrity/test_model_extraction.py | 6.1.2; 6.1.3; 8.1; 8.2; 8.3; 9.1; 5.15; 5.16; 5.17; 5.18; 8.5; 8.18 | Partial Medium | ISMS scope and context; information-security risk assessment and treatment; Statement of Applicability; Annex A implementation records; supplier, access, logging, incident, continuity, privacy, secure-development, audit, management-review and corrective-action evidence applicable to the cited locations. | extraction_success_count < 10 (0.1% of queries); detection_alerts_triggered = True; rate_limiting_enforced = True Action: Qualify the ISO evidence for matching scope, system, period and operating effectiveness; execute or independently verify the linked GAISSF VTS where the ISO evidence does not demonstrate the GAISSF pass criteria. | ISO/IEC 27001 addresses information security governance, secure development, vulnerability management and integrity controls, but does not prescribe this AI-model integrity technique, benchmark, or GAISSF VTS threshold. |
| D1-CTL-03 Behavioral Drift Detection | D1-CTL-03-VTS-001 Automated tests/d1_model_integrity/test_behavioral_drift.py | 6.1.2; 6.1.3; 8.1; 8.2; 8.3; 9.1; 5.22; 8.15; 8.16; 8.17 | Partial Medium | ISMS scope and context; information-security risk assessment and treatment; Statement of Applicability; Annex A implementation records; supplier, access, logging, incident, continuity, privacy, secure-development, audit, management-review and corrective-action evidence applicable to the cited locations. | max_kl_divergence < 0.05; accuracy_drop < 5% over 30 days; alert_generated_for_any_drift_event = True Action: Qualify the ISO evidence for matching scope, system, period and operating effectiveness; execute or independently verify the linked GAISSF VTS where the ISO evidence does not demonstrate the GAISSF pass criteria. | ISO/IEC 27001 addresses information security governance, secure development, vulnerability management and integrity controls, but does not prescribe this AI-model integrity technique, benchmark, or GAISSF VTS threshold. |
| D1-CTL-04 Federated Learning Poisoning Prevention | D1-CTL-04-VTS-001 Hybrid (Automated + Manual Review) tests/d1_model_integrity/test_federated_poisoning.py | 6.1.2; 6.1.3; 8.1; 8.2; 8.3; 9.1; 5.7; 8.7; 8.8; 8.16; 8.20; 8.23; 8.29 | Partial Medium | ISMS scope and context; information-security risk assessment and treatment; Statement of Applicability; Annex A implementation records; supplier, access, logging, incident, continuity, privacy, secure-development, audit, management-review and corrective-action evidence applicable to the cited locations. | malicious_gradient_detection_rate >= 95%; poisoned_gradients_excluded_from_aggregation = True Action: Qualify the ISO evidence for matching scope, system, period and operating effectiveness; execute or independently verify the linked GAISSF VTS where the ISO evidence does not demonstrate the GAISSF pass criteria. | ISO/IEC 27001 addresses information security governance, secure development, vulnerability management and integrity controls, but does not prescribe this AI-model integrity technique, benchmark, or GAISSF VTS threshold. |
| D1-CTL-05 Embedding Space Robustness | D1-CTL-05-VTS-001 Automated tests/d1_model_integrity/test_embedding_robustness.py | 6.1.2; 6.1.3; 8.1; 8.2; 8.3; 9.1 | Partial Medium | ISMS scope and context; information-security risk assessment and treatment; Statement of Applicability; Annex A implementation records; supplier, access, logging, incident, continuity, privacy, secure-development, audit, management-review and corrective-action evidence applicable to the cited locations. | classification_change_rate < 5% under bounded perturbation (epsilon=0.1); certified_radius_measured = True Action: Qualify the ISO evidence for matching scope, system, period and operating effectiveness; execute or independently verify the linked GAISSF VTS where the ISO evidence does not demonstrate the GAISSF pass criteria. | ISO/IEC 27001 addresses information security governance, secure development, vulnerability management and integrity controls, but does not prescribe this AI-model integrity technique, benchmark, or GAISSF VTS threshold. |
| D1-CTL-06 Post-Quantum Model Signing & Crypto Hardening | D1-CTL-06-VTS-001 Automated tests/d1_model_integrity/test_pqc_signing.py | 6.1.2; 6.1.3; 8.1; 8.2; 8.3; 9.1; 5.33; 8.9; 8.24; 8.25; 8.29; 8.31 | Partial Medium | ISMS scope and context; information-security risk assessment and treatment; Statement of Applicability; Annex A implementation records; supplier, access, logging, incident, continuity, privacy, secure-development, audit, management-review and corrective-action evidence applicable to the cited locations. | legacy_rsa_signature_rejected = True; tls_downgrade_blocked = True; pqc_key_exchange_enabled = True Action: Qualify the ISO evidence for matching scope, system, period and operating effectiveness; execute or independently verify the linked GAISSF VTS where the ISO evidence does not demonstrate the GAISSF pass criteria. | ISO/IEC 27001 addresses information security governance, secure development, vulnerability management and integrity controls, but does not prescribe this AI-model integrity technique, benchmark, or GAISSF VTS threshold. |
8. Reverse Traceability Summary
| ISO location | Primary subject | GAISSF reuse / limitation |
|---|---|---|
| Clauses 4-5 | Context, scope, leadership, policy and roles | Strong reuse for D6/D8 governance and control ownership. |
| Clause 6 | Information-security risk assessment, treatment, SoA and objectives | Cross-domain evidence reuse; additional GAISSF controls are expressly possible under 6.1.3. |
| Clauses 7-8 | Resources, competence, communications, documentation and operation | Supports implementation records; does not replace AI-specific VTS. |
| Clauses 9-10 | Monitoring, audit, management review and corrective action | Strong assurance reuse across all domains. |
| A.5 Organizational | Policy, assets, suppliers, incidents, continuity, compliance, privacy and procedures | Broad support for D4-D8 and governance aspects of all domains. |
| A.6 People | Screening, terms, awareness, confidentiality, remote work and reporting | Supports D6/D7; AI-specific exercises remain residual. |
| A.7 Physical | Physical perimeter, monitoring, environment, equipment and media | Supports D9 infrastructure security but not functional safety. |
| A.8 Technological | Access, authentication, malware, vulnerabilities, configuration, DLP, logging, monitoring, cryptography, networks and secure development | Strong technical-security support for D1-D5, but AI-specific attack models and thresholds remain residual. |
9. Amendment and ISO/IEC 27002 Status
The supplied source verifies ISO/IEC 27001:2022(E), Third edition. ISO/IEC 27001:2022/Amd 1:2024 is tracked as a maintenance note affecting organizational context and interested-party considerations. Because the amendment text was not supplied, CRO-020 does not claim full-text verification of the amendment. ISO/IEC 27002:2022 implementation guidance was also not supplied; CRO-020 therefore maps only to the normative ISO/IEC 27001 clauses and Annex A controls.
10. VTS and Certification Handling
- All 59 GAISSF controls retain traceability to a VTS identifier and executable test file.
- ISO/IEC 27001 evidence may reduce documentary duplication but does not waive GAISSF technical validation.
- Demo fixtures and unsigned evidence are non-certifying.
- Inherited evidence, compensating controls and test substitutions require documented assessment-scheme approval.
11. Source Register and Publication Rules
| Source | Treatment |
|---|---|
| ISO/IEC 27001:2022(E) | Complete licensed source supplied by user; internal controlled use; not redistributed. |
| ISO/IEC 27001:2022/Amd 1:2024 | Maintenance note only; source not supplied and not full-text verified. |
| ISO/IEC 27002:2022 | Not supplied; detailed implementation guidance is outside the verified baseline. |
| GAISSF-NOR-001 v1.0 | Authoritative framework and conformance baseline. |
| GAISSF-NOR-004 v1.0 | 59-control catalogue and VTS/evidence records. |
| GAISSF-NOR-005 / NOR-006 | Terminology, source and mapping rules. |
| GAISSF VTS v1.0.1 and evidence schema v1.0 | Executable validation and machine-readable evidence model. |
- Publish CRO-020 as informative, version-controlled and source-bounded.
- Do not reproduce the supplied ISO/IEC PDF or substantial ISO text.
- Do not claim that ISO/IEC 27001 certification establishes GAISSF conformity or AI safety.
- Publish the explanatory document together with the XLSX and JSON registers.
- Trigger review upon material revision to GAISSF, ISO/IEC 27001, the amendment status, or mapping evidence.