@blamejs/exceptd-skills 0.12.25 → 0.12.26

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,259 @@
1
+ ---
2
+ name: sector-telecom
3
+ version: "1.0.0"
4
+ description: Telecom and 5G security for mid-2026 — Salt Typhoon, Volt Typhoon, CALEA / IPA-LI gateway compromise, signaling-protocol abuse (SS7 / Diameter / GTP), 5G N6 / N9 isolation, gNB / DU / CU integrity, OEM-equipment supply-chain compromise, AI-RAN / O-RAN security; FCC CPNI + 4-business-day notification, NIS2 Annex I telecom essential entities, UK TSA 2021 + Ofcom, AU SOCI / TSSR, GSMA NESAS, 3GPP TR 33.926 + TS 33.501, ITU-T X.805.
5
+ triggers:
6
+ - telecom security
7
+ - 5g core
8
+ - salt typhoon
9
+ - volt typhoon
10
+ - gnb integrity
11
+ - lawful intercept
12
+ - calea
13
+ - fcc cpni
14
+ - 4-business-day notification
15
+ - gsma nesas
16
+ - ss7
17
+ - diameter
18
+ - gtp
19
+ - 3gpp ts 33.501
20
+ - 3gpp tr 33.926
21
+ - o-ran
22
+ - n6 n9 isolation
23
+ - nis2 annex i
24
+ - uk tsa 2021
25
+ - au soci
26
+ - tssr
27
+ - itu-t x.805
28
+ data_deps:
29
+ - cve-catalog.json
30
+ - atlas-ttps.json
31
+ - framework-control-gaps.json
32
+ - global-frameworks.json
33
+ - cwe-catalog.json
34
+ - d3fend-catalog.json
35
+ atlas_refs:
36
+ - AML.T0040
37
+ attack_refs:
38
+ - T1071
39
+ - T1078
40
+ - T1098
41
+ - T1190
42
+ - T1199
43
+ - T1556
44
+ framework_gaps:
45
+ - FCC-CPNI-4.1
46
+ - FCC-Cyber-Incident-Notification-2024
47
+ - NIS2-Annex-I-Telecom
48
+ - DORA-Art-21-Telecom-ICT
49
+ - UK-CAF-B5
50
+ - AU-ISM-1556
51
+ - GSMA-NESAS-Deployment
52
+ - 3GPP-TR-33.926
53
+ - ITU-T-X.805
54
+ rfc_refs:
55
+ - RFC-9622
56
+ cwe_refs:
57
+ - CWE-287
58
+ - CWE-306
59
+ - CWE-918
60
+ d3fend_refs:
61
+ - D3-NTA
62
+ - D3-NTPM
63
+ - D3-IOPR
64
+ - D3-NI
65
+ forward_watch:
66
+ - "FCC CPNI rule updates (47 CFR 64.2009 / 64.2011 amendments)"
67
+ - "5G AI-RAN security guidance from CISA, ENISA, NCSC, ASD ACSC"
68
+ - "GSMA FS.32 / FS.36 / FS.43 revisions"
69
+ - "Volt Typhoon / Salt Typhoon successor-actor disclosures"
70
+ - "Five Eyes joint advisories on telecom-equipment intrusion"
71
+ - "3GPP TS 33.501 updates (5G security architecture rebaseline)"
72
+ - "O-RAN SFG / WG11 security specifications"
73
+ last_threat_review: 2026-05-15
74
+ ---
75
+
76
+ ## Threat Context (mid-2026)
77
+
78
+ **Salt Typhoon (China nation-state; PRC Ministry of State Security nexus).** The 2024–2026 campaign — disclosed in successive Five Eyes joint advisories from October 2024 onward (CISA / NSA / FBI joint product reissued through 2025–2026) — compromised at least nine US carriers (publicly named: AT&T, Verizon, T-Mobile US, Lumen, Charter, Cox, Windstream, Consolidated, plus undisclosed others) and extended to AU / CA / NZ / UK Tier-1 carriers. Threat actor TTPs map to T1199 (Trusted Relationship) via OEM vendor supply chain, T1098 (Account Manipulation) for persistent admin access on NMS, and T1078 (Valid Accounts) with stolen LI-gateway operator credentials. The campaign's defining feature: targeted access to CALEA-mandated lawful-intercept systems, allowing PRC actors to read US-authorized intercept feeds — including those covering PRC counter-intelligence targets and presidential-campaign communications (2024 election cycle). The intercept-system vector is structurally novel: every carrier serving US-jurisdiction subscribers is legally required to maintain a CALEA-compliant intercept capability, which means every carrier has a high-value, low-monitored attack surface by mandate.
79
+
80
+ **Volt Typhoon (China; OT-adjacent telecom + ISP critical infrastructure).** CISA AA24-038A (Feb 2024) and follow-ons document prepositioning across US critical infrastructure operators, including telecom-adjacent ISPs and edge equipment. Living-off-the-land TTPs (T1190 + T1556) defeat conventional EDR. Distinct from Salt Typhoon in mission (prepositioning vs intelligence collection) but the equipment-supply-chain access pattern overlaps.
81
+
82
+ **Lawful-intercept abuse vectors.** LI gateway compromise can defeat CALEA / IPA-LI / EU EECC Art. 40 mandated intercept capability protections. LIDB poisoning, J-STD-025 / ATIS-1000013 reference-data tampering, and operator-credential theft against the LI-management subsystems are the primary access patterns. The same vectors apply to UK IPA 2016 + TSA 2021, AU TSSR / SOCI Act 2018, Singapore IMDA TCCSCoP, India CERT-In 6-hour rule, Japan Telecommunications Business Act amended 2023.
83
+
84
+ **Signaling-protocol attacks.** SS7 (2G/3G legacy), Diameter (4G LTE/IMS), GTP (3G/4G data plane), and 5G core interfaces N1 / N2 / N4 / N6 / N9 — each carries authentication and authorization fragility legacies. SS7-class abuse remains operationally relevant in mid-2026 against carriers maintaining legacy interconnect. 5G core slice-isolation under TS 33.501 is the modern equivalent control surface.
85
+
86
+ **OEM equipment supply-chain compromise.** Cisco / Juniper / Nokia / Ericsson / Huawei / ZTE equipment vendors are the high-value target. Vendor remote-support inbound tunnels (Cisco TAC, Ericsson ENS, Nokia 1350 OMS) are a recurring intrusion vector. GSMA NESAS (FS.13 / FS.14 / FS.15) is product-time certification — operator-attested deployment posture is the operational gap.
87
+
88
+ **AI-RAN / O-RAN security.** ETSI O-RAN SFG / WG11, 3GPP TR 33.926, NIST IR 8505 (5G Cybersecurity Practice Guide). AI-RAN deployments add model-tampering and slice-mismapping risks that 3GPP TR 33.926 does not yet model.
89
+
90
+ ## Framework Lag Declaration
91
+
92
+ Telecom security mandates lag the current threat reality because the regulatory frame was constructed before the Salt Typhoon-class adversary access pattern surfaced. **NIS2 Annex I** (EU) designates telecom providers as essential entities and requires 24-hour incident notification + supply-chain due diligence (Art. 21(2)(d)), but does not name OEM-equipment firmware integrity attestation, AI-RAN model-tampering controls, or LI-gateway-specific access auditing. **FCC CPNI rules** (47 CFR 64.2009(e) annual certification, 47 CFR 64.2011 4-business-day cyber incident notification effective 2024-03-13) predate the Salt Typhoon LI-system vector and do not require notification on LI-system compromise that does not exfiltrate PII directly. **UK CAF Principle B5** (resilient networks) is outcome-tested but the outcome catalog does not include signaling-anomaly detection, gNB firmware attestation, or slice-isolation tests; lawful-intercept access is covered separately by IPA 2016 + TSA 2021. **AU ISM-1556** (privileged user MFA) covers human privileged users but does not reach telecom NMS service accounts (the actual privilege-holders) or OEM remote-support tunnels. **DORA Art. 21** (EU) binds the financial entity consuming telecom services but does not align cadences with NIS2 telecom-essential-entity reporting and does not bridge to 5G slice-isolation obligations for finance-dedicated slices. **GSMA NESAS** is product-time, vendor-attested certification with no operator-attested-runtime check, no firmware-update-cadence-tied recertification, and no EMS / OSS / NMS coverage. **3GPP TR 33.926** assumes deterministic equipment behavior — adversary-modified firmware that passes the SCAS suite at submission remains undetected after deployment. **ITU-T X.805** (2003) is reference architecture, not a deployment-validation framework, and predates 5G, O-RAN, AI-RAN, and the modern threat model. **CTID Secure AI v2** (2026-05-06) extends MITRE ATLAS coverage of agentic-AI and AI-RAN attacks but is layered guidance, not a mandate.
93
+
94
+ ## TTP Mapping
95
+
96
+ | Tactic | ATT&CK | ATLAS | Description |
97
+ |---|---|---|---|
98
+ | Initial Access | T1199 Trusted Relationship | AML.T0040 (Tool/Plugin Compromise) | OEM vendor remote-support tunnel or AI-RAN plugin compromise opens a path into the operator network |
99
+ | Initial Access | T1190 Exploit Public-Facing Application | — | Internet-facing OSS / EMS / NMS exposed services (Salt Typhoon access pattern) |
100
+ | Persistence | T1098 Account Manipulation | — | Persistent admin role grants on NMS / EMS / OSS after initial compromise |
101
+ | Defense Evasion | T1556 Modify Authentication Process | — | LI-gateway credential pivot — operator account credentials forged or replayed against LI provisioning subsystem |
102
+ | Credential Access | T1078 Valid Accounts | — | Stolen LI-gateway operator credentials used directly, no separate exploitation path |
103
+ | Command and Control | T1071 Application Layer Protocol | — | Living-off-the-land C2 over telecom internal management protocols (SNMP, NETCONF, Telco-IP-fabric) |
104
+ | Collection | T1199 (downstream) | AML.T0040 (downstream) | Pulling subscriber call-detail records, location data, and LI feed contents via compromised access |
105
+
106
+ ATLAS AML.T0040 (Tool / Plugin Compromise) anchors the AI-RAN attack class: plugin-layer compromise of an O-RAN xApp or rApp can route traffic through an adversary-controlled inference path while the NMS believes the legitimate xApp is still in use.
107
+
108
+ ## Exploit Availability Matrix
109
+
110
+ | Vector | PoC status | Weaponization | AI-assist factor | Notes |
111
+ |---|---|---|---|---|
112
+ | LI-gateway operator credential theft | Public (per CISA AA24 advisories) | Confirmed in-the-wild | Low | Salt Typhoon TTP; credentials harvested through OEM-vendor supply chain |
113
+ | OEM vendor remote-support tunnel | Public (TTP class, no single PoC) | Confirmed in-the-wild | Low | Vendor TAC / ENS tunnels documented as Salt Typhoon vector |
114
+ | SS7 / Diameter signaling abuse | Public (signaling-research community) | Commodity | Low | Pre-dates AI-augmented attack landscape |
115
+ | GTP-U tunneling attacks | Public | Demonstrated | Low | Operator-side defense via signaling firewalls |
116
+ | 5G core N4 abuse (PFCP) | Researcher PoCs | Demonstrated | Low | Defense via N4 isolation per TS 33.501 |
117
+ | AI-RAN xApp tampering | No public PoC | Speculative | High (ATLAS AML.T0040 class) | CTID Secure AI v2 forward-watch |
118
+ | gNB firmware tampering | Researcher PoCs (vendor-specific) | Demonstrated against vendor pre-prod | Low | GSMA NESAS scope gap |
119
+ | Slice mismapping (cross-slice leak) | Researcher PoCs against test cores | Demonstrated | Low | TS 33.501 control surface |
120
+
121
+ ## Analysis Procedure
122
+
123
+ ### Phase 1 — govern (jurisdictional clock + obligations)
124
+
125
+ Surface the operator's jurisdictional notification clocks immediately on detection:
126
+
127
+ - **US**: FCC 47 CFR 64.2011 — 4 business days from discovery of PII/CPNI breach; CALEA / Title III LI-system compromise reporting through DOJ / FBI per separate channel
128
+ - **EU**: NIS2 Art. 23 — 24 hours initial notification, 72 hours intermediate, 1 month final (telecom essential entity)
129
+ - **EU finance-touching**: DORA Art. 19 — 4 hours major-ICT-incident initial notification for financial-entity-impacting telecom incidents
130
+ - **UK**: TSA 2021 + Electronic Communications (Security Measures) Regulations 2022 — Ofcom notification immediately on a security compromise of significance; NCSC notification when applicable
131
+ - **AU**: SOCI Act 2018 (as amended 2022) + TSSR 2017 — Critical Infrastructure Centre notification + ACMA where applicable; ASD ACSC reporting per Essential 8 obligations
132
+ - **CA**: Bill C-26 (Critical Cyber Systems Protection Act) notification once in force
133
+ - **JP**: MIC Telecommunications Business Act amended 2023; immediate notification
134
+ - **IN**: Telecommunications (Security) Rules 2024 + CERT-In 6-hour rule
135
+ - **SG**: IMDA TCCSCoP (2022 v2 + 2024 update) — immediate
136
+ - **NZ**: TICSA 2013
137
+
138
+ Wait for operator acknowledgment of the highest-priority clock before proceeding.
139
+
140
+ ### Phase 2 — direct (threat context)
141
+
142
+ Brief the operator on Salt Typhoon-class TTPs + RWEP-threshold bands. For telecom CVEs with active exploitation: live-patch threshold 90, urgent-patch 70, scheduled 30.
143
+
144
+ ### Phase 3 — look (artifacts to capture)
145
+
146
+ Capture the following telecom-specific evidence (use `air_gap_alternative` paths if operator is in disconnected mode):
147
+
148
+ - **LI provisioning audit log** — full activation/deactivation history for the assessment window (typically last 90 days). Air-gap alternative: operator-supplied CSV export.
149
+ - **gNB / DU / CU firmware hashes** — operator-attested hash for every running base station, compared against vendor-published expected hashes. Air-gap alternative: out-of-band hash list verified against PGP-signed vendor bulletin.
150
+ - **NMS / EMS / OSS access logs** — last 90 days of admin actions on the network management plane.
151
+ - **Signaling-flow statistics** — SS7 SCCP / TCAP / MAP message rates per peer; Diameter ABMF / CCR / CCA rates per Diameter peer; GTP-C / GTP-U bytes per APN.
152
+ - **Cross-PLMN signaling exchange patterns** — anomalous PLMN-pair flows that did not previously exchange traffic.
153
+ - **eUICC SIM-swap event log** — recent IMSI swaps, MSISDN reassignments.
154
+ - **5GC slice-isolation verification output** — last AMF / SMF / UPF reachability test per slice.
155
+ - **OEM vendor remote-support tunnel inventory** — open Cisco TAC / Ericsson ENS / Nokia OMS tunnels with last-active timestamp.
156
+ - **NESAS deployment posture report** — most recent operator-attested deployment match against the vendor-certified build.
157
+
158
+ ### Phase 4 — detect (indicators)
159
+
160
+ Walk every indicator's `false_positive_checks_required` list before submitting a hit:
161
+
162
+ - **Anomalous LI activation requests** — provisioning events outside the operator's standard workflow (e.g. activation without paired law-enforcement-agency ticket reference, activation from a service-account that never previously performed LI provisioning).
163
+ - **gNB firmware hash drift** — running firmware does not match the vendor-published or operator-attested expected hash. FP check: rule out staged update window.
164
+ - **NMS access from anomalous source** — admin login from an ASN, region, or device class not previously used for the role. FP check: rule out OEM TAC support session (correlate against open tunnel inventory).
165
+ - **Cross-PLMN signaling spikes** — sudden order-of-magnitude increase in signaling exchange with a previously-quiet PLMN-pair. FP check: rule out legitimate roaming-agreement reactivation, peering reconfiguration.
166
+ - **Unauthorized LI gateway tunnel** — outbound connection from the LI gateway to an IP outside the LE / DOJ / regulator allowlist. FP check: rule out documented maintenance bastion.
167
+ - **OEM firmware downgrade events** — vendor-equipment firmware version regressed below the operator-published minimum. FP check: rule out documented incident-response rollback.
168
+
169
+ ### Phase 5 — analyze (correlation)
170
+
171
+ Match captured artifacts against `data/cve-catalog.json` entries with `attack_class: telecom` or matching `attack_refs`. Cross-reference against `data/framework-control-gaps.json` for FCC-CPNI-4.1, FCC-Cyber-Incident-Notification-2024, NIS2-Annex-I-Telecom, DORA-Art-21-Telecom-ICT, UK-CAF-B5, AU-ISM-1556, GSMA-NESAS-Deployment, 3GPP-TR-33.926, ITU-T-X.805. Score blast-radius based on subscriber count + LI-feed-exposure dimension + AI-RAN slice-mismapping potential.
172
+
173
+ ### Phase 6 — validate (priority-sorted remediation)
174
+
175
+ Priority 1 (immediate): isolate compromised NMS account; revoke and re-issue LI-gateway operator credentials; pull running-gNB firmware hash off every base station and compare against operator-attested expected.
176
+ Priority 2 (24h): rotate all OEM vendor remote-support credentials; close TAC tunnels not actively in use; signaling-firewall block on cross-PLMN spike sources.
177
+ Priority 3 (72h): operator-attested NESAS recertification of every gNB / EMS / OSS; slice-isolation verification across every active 5GC slice; comprehensive review of the last 90 days of NMS admin actions.
178
+
179
+ ### Phase 7 — close (regulator notifications + evidence preservation)
180
+
181
+ Draft jurisdictional notification messages with regulator-specific evidence templates. Preserve LI-system audit trail for downstream law-enforcement / intelligence-community handoff. Schedule a follow-up `reattest` window at the highest applicable regulator deadline minus 48 hours.
182
+
183
+ ## Output Format
184
+
185
+ The investigation evidence bundle returned by phase 5 + 6 has this shape:
186
+
187
+ ```json
188
+ {
189
+ "session_id": "telecom-<iso>",
190
+ "playbook_id": "sector-telecom",
191
+ "classification": "detected | clean | not_detected | inconclusive",
192
+ "evidence_hash": "sha256:...",
193
+ "telecom_specific_findings": {
194
+ "li_gateway_audit": {
195
+ "anomalous_activations": 0,
196
+ "activations_outside_ticket": 0,
197
+ "outbound_tunnel_to_non_allowlist_ip": 0
198
+ },
199
+ "gnb_attestation_state": {
200
+ "expected_hashes_compared": 0,
201
+ "drifted_basestations": [],
202
+ "downgrade_events": 0
203
+ },
204
+ "signaling_anomaly_count": {
205
+ "ss7_per_peer_z_score_outliers": 0,
206
+ "diameter_per_peer_z_score_outliers": 0,
207
+ "gtp_apn_byte_z_score_outliers": 0,
208
+ "cross_plmn_unexpected_pairs": []
209
+ },
210
+ "nms_admin_access": {
211
+ "logins_from_anomalous_asn": 0,
212
+ "service_account_role_grants_outside_workflow": 0,
213
+ "open_oem_tac_tunnels": []
214
+ },
215
+ "oem_firmware_drift": {
216
+ "vendor_published_min_version_violations": [],
217
+ "operator_attested_mismatch": []
218
+ },
219
+ "slice_isolation": {
220
+ "amf_smf_upf_reachability_misses": [],
221
+ "cross_slice_packet_leakage_detected": false
222
+ }
223
+ },
224
+ "jurisdiction_notifications": [
225
+ { "jurisdiction": "US-FCC", "regulation": "47-CFR-64.2011", "deadline_iso": "...", "clock_anchor": "detect_confirmed" },
226
+ { "jurisdiction": "EU", "regulation": "NIS2-Art-23", "deadline_iso": "...", "clock_anchor": "detect_confirmed" }
227
+ ]
228
+ }
229
+ ```
230
+
231
+ ## Compliance Theater Check
232
+
233
+ Theater patterns specific to telecom posture:
234
+
235
+ - **"We have CPNI annual certification."** Annual certification is a process artifact, not a compromise-detection control. The certification covers operational procedures; it does not test LI-gateway compromise detection. Theater test: ask whether the last CPNI certification audit reviewed LI provisioning logs for anomalous activations.
236
+ - **"We are GSMA NESAS certified."** NESAS is product-time, vendor-attested certification of the equipment itself — not the deployed posture. Theater test: ask for the most recent operator-attested-runtime gNB firmware hash report compared against the NESAS-certified build hash. Mismatch or absence is theater.
237
+ - **"OEM firmware is verified at receipt."** Vendor-supplied hash is the input to the receipt verification; the operator does not independently re-derive the hash from upstream OEM-vendor source. Theater test: ask whether the operator separately verifies OEM firmware against an out-of-band PGP-signed vendor bulletin OR an operator-side reproducible build.
238
+ - **"3GPP TR 33.926 tests passed at deployment."** TR 33.926 SCAS is product-class testing; it does not detect adversary-modified firmware that passes the test suite at submission. Theater test: ask for the post-deployment hash-attestation report on the running gNB.
239
+ - **"ITU-T X.805 framework adopted."** X.805 is reference architecture, not validation. Theater test: ask for a deployment validation checklist mapping X.805's 8 dimensions to specific operational telemetry. Most operators cite the framework but do not validate against it.
240
+ - **"We have signaling firewall (SS7 / Diameter / GTP)."** Signaling firewalls are policy-engine dependent on a current threat-actor PLMN catalog. Theater test: ask when the threat-actor PLMN list was last refreshed against GSMA Fraud and Security Group bulletins.
241
+ - **"LI-gateway operator credentials use MFA."** Human-MFA on the LI gateway is necessary but not sufficient — service accounts and OEM remote-support tunnels frequently bypass. Theater test: count the LI-gateway admin actions executed in the last 30 days by service-account principals vs human-MFA principals.
242
+
243
+ ## Defensive Countermeasure Mapping
244
+
245
+ | Threat | D3FEND technique | Operational mapping |
246
+ |---|---|---|
247
+ | Signaling anomaly | D3-NTA (Network Traffic Analysis) | SS7 / Diameter / GTP per-peer baseline + alert on z-score outliers |
248
+ | 5G slice cross-leak | D3-NTPM (Network Traffic Policy Mapping) | Per-slice ACL + AMF/SMF/UPF reachability testing |
249
+ | LI-gateway audit-trail integrity | D3-IOPR (I/O Read) | Immutable / append-only LI provisioning log + cross-system reconciliation |
250
+ | 5GC slice / N6 / N9 isolation | D3-NI (Network Isolation) | Slice ID + DNN + S-NSSAI policy enforcement; N6 transit egress monitoring |
251
+ | OEM firmware tampering | D3-EFA (Executable File Analysis) | Out-of-band hash verification + operator-attested-runtime checks |
252
+
253
+ ## Hand-Off / Related Skills
254
+
255
+ - **incident-response-playbook** — parent IR flow; sector-telecom extends the IR contract with telecom-specific evidence and jurisdictional clocks.
256
+ - **framework-gap-analysis** — invoke for downstream Hard-Rule-5 gap mapping against catalog framework_gaps.
257
+ - **cred-stores** — LI-gateway operator credential storage falls under the cred-stores skill for secret-management depth.
258
+ - **sector-federal-government** — national-security adjacency on LI-system compromise touches federal investigation scope.
259
+ - **mcp-agent-trust** — AI-RAN xApp / rApp compromise (ATLAS AML.T0040 class) crosses into MCP-class agent-tool trust boundaries.