Every scanner checks what exists. Nobody checks what's missing
Cloud security scanners typically check existing resources for misconfigurations but fail to detect orphaned references left behind after resource deletion. These dangling references in IAM policies, event rules, and configurations can lead to security gaps, especially when deleted resource names are reclaimed by attackers. The risk spans data exposure, privilege inheritance, and undetected system failures.
- ▪When cloud resources are deleted, references to them often remain in policies, triggers, and configurations.
- ▪Orphaned references to deleted S3 bucket names can allow attackers to claim the name and receive data intended for the original owner.
- ▪IAM trust policies protect against deleted role ARNs, but resource-based policies on S3, KMS, and SNS do not.
- ▪CloudWatch alarms may fire successfully but fail to notify if the target SNS topic has been deleted.
- ▪Reclaimed resource names in permission policies can lead to unintended data disclosure and compliance violations.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
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 | DEV Community |
| Canonical URL | https://dev.to/bala_paranj_059d338e44e7e/every-scanner-checks-what-exists-nobody-checks-whats-missing-258e |
| Publication time | Tue, 28 Apr 2026 12:10:08 +0000 |
| Retrieval time | 2026-04-28T12:24:31.929Z |
| Last seen | 2026-04-28T12:24:31.929Z |
| 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 | bBL9wyXNNolO |
| 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
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3862804) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Bala Paranj Posted on Apr 28 Every scanner checks what exists. Nobody checks what's missing #aws #security #cloud #devops When cloud resources are deleted, the references to them persist — in IAM policies, event triggers, compute configs, and trust relationships. These orphaned references create exploitable gaps that no per-resource scanner can detect. The finding doesn't live on any single resource. It lives in the space between what's referenced and what exists.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV Community.
Discussion
0 commentsMore from DEV Community
