
Existing laws already cover every type of AI security incident
Existing laws already cover every type of AI security incident“If a train jumps the tracks, who is liable? Why should AI be different?”Paul WalshSep 23, 202641Sharetl;drExisting computer misuse laws already cover unauthorised access, interference, and damage, whether done by a person, a script, or an AI agent. AI doesn’t create a legal vacuum or shift blame onto the software.
- ▪Existing laws already cover every type of AI security incident“If a train jumps the tracks, who is liable?
- ▪Why should AI be different?”Paul WalshSep 23, 202641Sharetl;drExisting computer misuse laws already cover unauthorised access, interference, and damage, whether done by a person, a script, or an AI agent.
- ▪AI doesn’t create a legal vacuum or shift blame onto the software.
Hacker News (AI / LLM) files mainly under ai. We currently carry 6,359 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Hacker News (AI / LLM) |
| Canonical URL | https://paulfwalsh.substack.com/p/existing-laws-already-cover-every |
| Publication time | Thu, 24 Sep 2026 18:35:22 +0000 |
| Retrieval time | 2026-09-24T19:05:26.790Z |
| Last seen | 2026-09-24T19:05:26.790Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | MO6eQVLnXcF9 · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Existing laws already cover every type of AI security incident“If a train jumps the tracks, who is liable? Why should AI be different?”Paul WalshSep 23, 202641Sharetl;drExisting computer misuse laws already cover unauthorised access, interference, and damage, whether done by a person, a script, or an AI agent. AI doesn’t create a legal vacuum or shift blame onto the software. Authorisation, control, intent/knowledge/recklessness, and harm still decide liability. Companies and the people who built, configured, deployed, or commissioned the system remain responsible. This post serves as a reference for journalists, researchers, cybersecurity professionals, lawyers, officials, policymakers, regulators, developers, and security teams investigating AI incidents.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Hacker News (AI / LLM).