Aviation Transport Security Program or Maritime / Ship / Offshore Security Plan

Content of an aviation industry participant's Transport Security Program (TSP, Aviation Transport Security Act 2004 s 16; disclosing TSP content without the participant's consent is an offence under Aviation Transport Security Regulations 2005 reg 2.06) and of maritime security plans, ship security plans and offshore security plans (Maritime Transport and Offshore Facilities Security Regulations 2003 regs 3.12, 4.115 and 5A.105 require them to be protected against unauthorised access, amendment and disclosure). Enforcement needs populated plan structure: named port / company / ship / offshore security officers (PSO, CSO, SSO), 24-hour security contact numbers, restricted and cleared zone or screening point tables, and executed Declarations of Security. Australian law has no "Security Sensitive Information" marking; US TSA Sensitive Security Information (49 CFR 1520) material is an explicit exclusion.

Type: regex
Engine: boost_regex
Confidence: medium
Confidence justification: Medium: the plan names are statutory, but no marking is mandated and there is no public plan identifier, so enforcement relies on populated plan content (officer names, contact numbers, zone and screening-point tables, Declarations of Security). "Ship Security Plan" is also an international ISPS term, so non-Australian ship plans with the same structure will enforce. 85/75 are heuristic evidence tiers, not measured accuracy; test values are synthetic.
Jurisdictions: au
Regulations: Aviation Transport Security Act 2004 (Cth), Aviation Transport Security Regulations 2005 (Cth), Maritime Transport and Offshore Facilities Security Act 2003 (Cth), Maritime Transport and Offshore Facilities Security Regulations 2003 (Cth)
Frameworks: PSPF, QGISCF
Data categories: security, infrastructure, transport
Scope: narrow
Risk rating: 9
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?i)\b(?:Transport\s+Security\s+Program(?:me)?|Maritime\s+Security\s+Plan|Ship\s+Security\s+Plan|Offshore\s+(?:Facility\s+)?Security\s+Plan|International\s+Ship\s+Security\s+Certificate)s?\b

Corroborative evidence keywords

unlawful interference, approved by the Secretary, maritime security level, Aviation Transport Security Act 2004, Maritime Transport and Offshore Facilities Security Act 2003, TSP, ISSC

Proximity: 300 characters

Should match

Port of Carrow Bay - Maritime Security Plan v4.2 (approved by the Secretary 2 May 2026) Port Security Officer: Harriet Vale, 24-hour contact: 0412 555 318 Land-side restricted zone: LSRZ-02 Berth 3 container apron Maritime security level 2: close gate 5 and escort all visitors. Suspected unlawful interference is reported to the PSO immediately. — 85 tier - maritime security plan with named PSO, 24-hour number and zone row plus approval and security level evidence
MV Kestrel Dawn - Ship Security Plan, section 2 Ship operator, CSO and SSO Ship Security Officer: Tomasz Reyne (Chief Officer) — 75 tier - ship security plan with one named security officer
Carrow Regional Airport Transport Security Program (Aviation Transport Security Act 2004) Screening point: SP-1 Terminal departure gate Cleared zone: CZ-A domestic sterile area Aviation Security Manager: Lena Marsh — 85 tier - airport TSP with screening point, cleared zone and security manager plus the Act
Offshore Security Plan - Gannet Deep FPSO Offshore Security Officer: Priya Castell Muster and access procedures follow in section 5. — 75 tier - offshore security plan with a named security officer
Ship Security Plan annex C Declaration of Security ref: DOS-2026-117 agreed with the Port of Carrow Bay PSO. Company Security Officer: Marta Olsen Maritime security level 1 applies at berth. — 85 tier - executed Declaration of Security plus named CSO and security level evidence

Should not match

SENSITIVE SECURITY INFORMATION WARNING: This record contains Sensitive Security Information that is controlled under 49 CFR parts 15 and 1520. Ship Security Plan (33 CFR 104) Company Security Officer: Dana Whitfield — US TSA SSI-marked vessel plan (exclusion - not an Australian marking)
Security regulated ports must have a maritime security plan approved by the Secretary. The plan sets out measures for maritime security levels 1, 2 and 3, identifies land-side restricted zones and names the port security officer. See homeaffairs.gov.au for guidance. — Home Affairs guidance
Maritime Security Plan template Port Security Officer: ________ 24-hour contact: ________ Land-side restricted zone: [insert zone] — Blank template
Airport screening officers wanted: help deliver the airport's Transport Security Program at our regional terminal. Must hold or be eligible for an ASIC. — Job advertisement / news
Ship Security Plan short course: in this course the Ship Security Officer: Role And Duties module explains how an SSO drills the crew. — Training course

Known false positives

US TSA Sensitive Security Information (49 CFR 1520) and US Coast Guard vessel / facility security plans (33 CFR) carry the same officer and zone structure. Mitigation: 49 CFR, 33 CFR, Transportation Security Administration and "Sensitive Security Information" hard-exclude the enforce tiers.
Home Affairs guidance, airport and port web pages, and training courses explain TSP and plan contents. Mitigation: Guidance stays at 65 discovery; enforce tiers need populated officer names, numbers, zone rows or Declarations of Security, and exclude homeaffairs.gov.au / legislation.gov.au and course wording.
Blank plan templates. Mitigation: Blank lines, bracket placeholders and n/a/tbc values are rejected; template wording is excluded by the shared template-exclusion dictionary.
International ISPS ship security plans for non-Australian ships. Mitigation: Accepted - they carry the same security risk; jurisdiction tagging is au because the plan regime and offences referenced are Australian.