{
  "@context": "https://tradecompliancerecords.com/schemas/v2/regulation.json",
  "schema_version": "2.2.0",
  "open_data": true,
  "ai_optimized": true,
  "slug": "imo-isps-code-2002",
  "name": "IMO ISPS Code — International Ship and Port Facility Security",
  "authority": "International Maritime Organization",
  "region": "Global",
  "cluster": "transport",
  "wikidata_qid": null,
  "wikidata_entity": null,
  "wikipedia_article": null,
  "official_source_url": "https://www.imo.org/en/OurWork/Security/Pages/SOLAS-XI-2%20ISPS%20Code.aspx",
  "gov_entry_url": null,
  "document_types": null,
  "key_obligations": null,
  "enforcement_bodies": null,
  "penalty_ranges": null,
  "affected_hs_codes": null,
  "mandatory_deadline": "2004-07-01",
  "applicability_scope": "Ships and port facilities must maintain security plans with verifiable documentation — hash-verifiable for port state control.",
  "cryptographic_integrity": {
    "sha256_hash": "358afab11c33f8199f55a1d29ab216b705814cd5b1413c337d28e864734b8ebb",
    "hash_algorithm": "SHA-256",
    "status": "cryptographically_hardened",
    "source_document_verified": true,
    "provenance": "source_document",
    "provenance_note": "SHA-256 derived from an ingested source document.",
    "r2_key": "regulations/imo-isps-code-2002/imo-isps-code-2002.html",
    "pdf_url": "https://tcr-vault.tradecompliancerecords.com/regulations/imo-isps-code-2002/imo-isps-code-2002.html",
    "file_size_bytes": 61396,
    "version_date": "2026-05-21",
    "last_verified_at": "2026-05-21T07:00:46.448Z"
  },
  "operational_consequences": null,
  "logistical_liability_exposure": false,
  "verification_consensus_score": "0",
  "verification_notes": null,
  "tcr_authority_page": "https://tradecompliancerecords.com/wiki/imo-isps-code-2002",
  "created_at": "2024-01-01",
  "infographic_r2_key": null,
  "infographic_sha256_hash": null,
  "infographic_generated_at": 1785141034725,
  "infographic_approved": 0,
  "origin_problem": "2001 September 11 attacks (2,977 deaths, USA) highlighted vulnerabilities in maritime security globally.",
  "problem_statement": "Global maritime security gaps exposed by terrorist threats.",
  "pre_regulation_status_quo": "No mandatory security plans for ships and ports. Lack of standardized security measures globally.",
  "operational_pain_points": [
    "Security plan documentation: must be hash-verifiable for port state control",
    "Verification frequency: annual audits required for compliance",
    "Training requirement: minimum 5 hours per crew member annually",
    "Security equipment: mandatory installation on all vessels over 500 gross tonnage",
    "Compliance reporting: quarterly submission to national maritime authority",
    "Incident reporting: within 24 hours of security breach"
  ],
  "search_intent_tree": null,
  "paa_questions": [
    {
      "q": "What are the penalties for non-compliance with IMO ISPS Code — International Ship and Port Facility Security?",
      "a": "• Max penalty: Not publicly specified\n• Trigger: Failure to maintain security plan\n• Enforcement body: Not specified\n• First offence vs repeat: Not publicly specified"
    },
    {
      "q": "Who must comply with IMO ISPS Code — International Ship and Port Facility Security?",
      "a": "• Threshold: Not publicly specified\n• Entity types: Ships, port facilities\n• Exemptions: Not publicly specified\n• Geographic scope: Global"
    },
    {
      "q": "What is the compliance deadline for IMO ISPS Code — International Ship and Port Facility Security?",
      "a": "• Phase 1 deadline: Not publicly specified\n• Phase 2 deadline: Not publicly specified\n• Transitional period: Not publicly specified\n• Enforcement start: Not publicly specified"
    },
    {
      "q": "What documents are required for IMO ISPS Code — International Ship and Port Facility Security compliance?",
      "a": "• Security Plan: Verifiable documentation\n• Incident Report: Breach details\n• Retention period: Not publicly specified\n• Submission format: Electronic"
    },
    {
      "q": "How does IMO ISPS Code — International Ship and Port Facility Security affect importers?",
      "a": "• Security compliance verification\n• Customs declaration requirement: Not publicly specified\n• Due diligence or traceability requirement: Not publicly specified\n• Cost estimate: Not publicly specified"
    },
    {
      "q": "What is the enforcement mechanism for IMO ISPS Code — International Ship and Port Facility Security?",
      "a": "• Primary enforcer: Not specified\n• Investigation trigger: Not publicly specified\n• Appeal process: Not publicly specified\n• Cross-border coordination: Not publicly specified"
    },
    {
      "q": "Are there exemptions under IMO ISPS Code — International Ship and Port Facility Security?",
      "a": "• SME exemption: Not publicly specified\n• Sector exclusions: Not publicly specified\n• Transitional exemptions: Not publicly specified\n• Article reference: Not publicly specified"
    },
    {
      "q": "How does IMO ISPS Code — International Ship and Port Facility Security interact with other regulations?",
      "a": "• Overlaps with: Not publicly specified\n• Conflicts with: Not publicly specified\n• Supersedes: Not publicly specified\n• Mutual recognition: Not publicly specified"
    },
    {
      "q": "What supply chain traceability does IMO ISPS Code — International Ship and Port Facility Security require?",
      "a": "• Tier depth: Not publicly specified\n• Data fields required: Not publicly specified\n• Technology standard: Not publicly specified\n• Audit frequency: Annual"
    },
    {
      "q": "What is the cost of IMO ISPS Code — International Ship and Port Facility Security compliance for a mid-size company?",
      "a": "• Implementation cost: Not publicly specified\n• Annual compliance cost: Not publicly specified\n• Penalty risk: Not publicly specified\n• Source: Not publicly specified"
    }
  ],
  "enrichment_status": "enriched"
}