A Network Allow-List Won't Stop Exfiltration
The article discusses the limitations of network allow-lists in preventing data exfiltration from untrusted code. It highlights that while allow-lists can block unauthorized connections, they cannot detect data being sent through authorized channels. The piece emphasizes the need for more robust solutions, such as L7 egress proxies with data-loss prevention features, to address these vulnerabilities.
- ▪Network allow-lists can prevent unauthorized connections but fail to stop data exfiltration through authorized channels.
- ▪Recent incidents in the software supply chain have shown that package registries can be exploited to harvest credentials.
- ▪Implementing an L7 egress proxy with data-loss prevention can help mitigate the risks associated with data leaving through allowed connections.
Lobsters files mainly under programming. We currently carry 187 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 | Dergraf |
| Canonical URL | https://www.dergraf.org/notes/canister-egress-proxy-dlp/ |
| Publication time | Sun, 24 May 2026 03:31:24 -0500 |
| Retrieval time | 2026-05-24T08:37:31.504Z |
| Last seen | 2026-05-24T08:37:31.504Z |
| 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 | K8R80Qm4EooD |
| 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
A Network Allow-List Won't Stop ExfiltrationMay 18, 2026· 9 min readSay you run a piece of untrusted code – an AI-generated script, a dependency’s postinstall hook, a build step from a repo you just cloned – inside a sandbox. You lock it down: no filesystem access outside the working directory, no network except the one domain it legitimately needs, no dangerous syscalls. That stops a lot of bad behavior.It also has a blind spot, and it’s a big one.I ran into this building Canister, a lightweight, unprivileged Linux sandbox – it stacks user namespaces, seccomp, and network isolation to run untrusted commands with minimal privileges, no root and no container runtime. But the blind spot below isn’t specific to Canister.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Dergraf.
Discussion
0 commentsMore from Dergraf
