{
  "@context": "https://tradecompliancerecords.com/schemas/v2/regulation.json",
  "schema_version": "2.2.0",
  "open_data": true,
  "ai_optimized": true,
  "slug": "imo-isps-code",
  "name": "IMO International Ship and Port Facility Security Code",
  "authority": "International Maritime Organization",
  "region": "Global",
  "cluster": "Port Security",
  "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": "Code",
  "key_obligations": "Ship security plans; port facility security plans; ISSC certificates; security levels",
  "enforcement_bodies": "IMO; flag state; port state control",
  "penalty_ranges": null,
  "affected_hs_codes": null,
  "mandatory_deadline": null,
  "applicability_scope": null,
  "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/imo-isps-code.html",
    "pdf_url": "https://tcr-vault.tradecompliancerecords.com/regulations/imo-isps-code/imo-isps-code.html",
    "file_size_bytes": 61396,
    "version_date": "2026-05-25",
    "last_verified_at": "2026-05-25T05:00:52.634Z"
  },
  "operational_consequences": null,
  "logistical_liability_exposure": false,
  "verification_consensus_score": "100%",
  "verification_notes": null,
  "tcr_authority_page": "https://tradecompliancerecords.com/wiki/imo-isps-code",
  "created_at": "2026-05-20 19:17:35",
  "infographic_r2_key": null,
  "infographic_sha256_hash": null,
  "infographic_generated_at": null,
  "infographic_approved": 0,
  "origin_problem": "2001 September 11 attacks (2,977 deaths, USA) highlighted vulnerabilities in global maritime security.",
  "problem_statement": "Global maritime security was inconsistent and vulnerable to terrorist threats.",
  "pre_regulation_status_quo": "No mandatory global security standards for ships and ports. Security measures varied widely by country.",
  "operational_pain_points": [
    "ISSC certification: mandatory for all ships over 500 gross tonnage (Article 5)",
    "Security level compliance: must adjust to port state requirements (Article 8)",
    "Ship security assessment: required every 5 years (Article 9)",
    "Port facility security plan: must be updated every 5 years (Article 10)",
    "Security drills: minimum once every 3 months (Article 13)"
  ],
  "search_intent_tree": null,
  "paa_questions": [
    {
      "q": "What are the penalties for non-compliance with IMO International Ship and Port Facility Security Code?",
      "a": "• Max penalty: Not publicly specified\n• Trigger: Non-compliance with security plans (Article 9)\n• Enforcement body: Flag state, port state control\n• First offence vs repeat: Not publicly specified"
    },
    {
      "q": "Who must comply with IMO International Ship and Port Facility Security Code?",
      "a": "• Threshold: Ships over 500 gross tonnage\n• Entity types: Shipping companies, port facilities\n• Exemptions: Not publicly specified\n• Geographic scope: Global"
    },
    {
      "q": "What is the compliance deadline for IMO International Ship and Port Facility Security Code?",
      "a": "• Phase 1 deadline: Not publicly specified\n• Phase 2 deadline: Not publicly specified\n• Transitional period: Not publicly specified\n• Enforcement start: 1 July 2004"
    },
    {
      "q": "What documents are required for IMO International Ship and Port Facility Security Code compliance?",
      "a": "• Ship Security Plan: Outlines security measures (Article 9)\n• Port Facility Security Plan: Details port security measures (Article 10)\n• Retention period: Not publicly specified\n• Submission format: Not publicly specified"
    },
    {
      "q": "How does IMO International Ship and Port Facility Security Code affect importers?",
      "a": "• Security compliance verification: Required for port entry (Article 8)\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 International Ship and Port Facility Security Code?",
      "a": "• Primary enforcer: Flag state, port state control\n• Investigation trigger: Audit, random checks\n• Appeal process: Not publicly specified\n• Cross-border coordination: IMO guidelines"
    },
    {
      "q": "Are there exemptions under IMO International Ship and Port Facility Security Code?",
      "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 International Ship and Port Facility Security Code interact with other regulations?",
      "a": "• Overlaps with: SOLAS Convention\n• Conflicts with: Not publicly specified\n• Supersedes: Not publicly specified\n• Mutual recognition: Not publicly specified"
    },
    {
      "q": "What supply chain traceability does IMO International Ship and Port Facility Security Code require?",
      "a": "• Tier depth: Not publicly specified\n• Data fields required: Not publicly specified\n• Technology standard: Not publicly specified\n• Audit frequency: Not publicly specified"
    },
    {
      "q": "What is the cost of IMO International Ship and Port Facility Security Code 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"
}