스킬 basin
📦
basin
콘텐츠 리비전 r1 높은 위험 🌐 네트워크 접근📁 파일 시스템 접근⚙️ 외부 명령어
Build Cloudflare Basin Analytics Workflows
Streaming analytics requires coordinated ingestion, table management, and query configuration. This skill provides Cloudflare Basin references and implementation patterns across Pipelines, Catalog, and SQL.
지원: Claude Codex Code(CC)
설치 전에 중지하고 확인을 요청하세요.
계획을 검토하고 파일을 변경하기 전에 사용자의 명시적 동의를 받으세요.
내 에이전트로 설치
이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.
에이전트 요청
Review the Skillstore skill "basin" from https://skillstore.io/skills/cloudflare-basin.md and its manifest at https://skillstore.io/api/skills/cloudflare-basin/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.
에이전트가 읽기 쉬운 리소스
AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.
테스트해 보기
"basin" 사용 중입니다. Which services should receive Worker events and support SQL reports?
예상 결과:
- Use a Basin Pipelines stream to receive validated Worker events.
- Connect the stream through row-level transformations to a Basin Catalog Iceberg sink in R2.
- Use Basin SQL for aggregate reports, with scoped credentials and protected dashboard access.
- Verify current command syntax and confirm data delivery after the first flush.
"basin" 사용 중입니다. The stream accepts events, but the table remains empty. What should I check?
예상 결과:
- Check pipeline state and failure reason without changing resources.
- Compare events with the stream schema and inspect validation error metrics.
- Check sink credentials, bucket availability, and catalog enablement.
- Allow for the documented first-flush delay and verify both written files and query results.
"basin" 사용 중입니다. Review the dashboard and Logpush examples before production deployment.
예상 결과:
- Require caller authentication and authorization before executing dashboard queries.
- Enable ingestion authentication and control request volume.
- Remove raw ClientIP from stored projections; hashing an additional column does not redact the original.
- Check credential presence without printing tokens and store Worker tokens as secrets.
보안 감사
높은 위험v1 • 2026. 10. 9. 버전별 보고서 열기
All 70 static matches are false positives involving documentation links, placeholder URLs, legitimate service requests, SQL identifiers, and TypeScript strings. Four semantic risks concern unauthenticated ingestion, an unprotected analytics endpoint, ineffective IP redaction, and a command that prints an API token. No evidence found of prompt injection, malicious exfiltration, or covert code execution in the reviewed files.
16
스캔된 파일
1,104
분석된 줄 수
0
검토 항목
0
오탐 무시됨
확인된 보안 우려 사항 (4)
높음
Dashboard Worker Exposes Analytics Without Caller Authorization
The Worker matches "/api/analytics", queries with its server-side token, and returns result.rows without checking caller identity or permissions. A public deployment without external protection could disclose analytics and permit repeated billable queries.
The complete handler performs only a pathname check before returning authenticated query results. No caller authentication is shown; external deployment controls could reduce exposure.
중간
HTTP Ingestion Templates Disable Authentication
The REST example sets "authentication": false, and Terraform also sets authentication = false for HTTP ingestion. If deployed, unauthenticated senders could inject events, corrupt analytics, and increase storage or processing costs.
Both executable configuration examples explicitly disable authentication without requiring an upstream access boundary. Exploitation depends on deploying these examples and accessing the ingest endpoint.
중간
Claimed IP Redaction Retains Raw Client Addresses
The Logpush transform selects ClientIP alongside sha256(ClientIP) AS hashed_ip while claiming "redact PII at ingest". The stored output retains the original address, so following this example does not achieve the stated redaction.
The same SELECT explicitly includes both the raw ClientIP column and its hash. The misleading redaction comment directly contradicts the output projection.
중간
Troubleshooting Command Prints Authentication Secret
The checklist recommends "echo $WRANGLER_BASIN_SQL_AUTH_TOKEN" to test token presence. This reveals the complete credential in terminal output and can expose it through captured logs or assistant transcripts.
The command explicitly expands and prints the authentication token rather than checking whether it exists. Further disclosure depends on how terminal output is recorded.
위험 요인
🌐 네트워크 접근 (26)
references/catalog/api.md:22 references/pipelines/api.md:14 references/pipelines/api.md:29 references/pipelines/api.md:36 references/pipelines/api.md:41 references/pipelines/api.md:109 references/pipelines/api.md:114 references/pipelines/patterns.md:9 references/pipelines/patterns.md:48 references/pipelines/patterns.md:48 references/pipelines/patterns.md:93 references/pipelines/README.md:51 references/sql/api.md:8 references/sql/configuration.md:36 references/sql/patterns.md:52 references/sql/patterns.md:62 references/sql/patterns.md:26 references/sql/patterns.md:22 references/sql/patterns.md:38 references/sql/patterns.md:51 SKILL.md:8 SKILL.md:12 SKILL.md:18 SKILL.md:19 SKILL.md:20 SKILL.md:22
📁 파일 시스템 접근 (19)
references/catalog/api.md:30 references/catalog/patterns.md:10 references/catalog/patterns.md:11 references/catalog/README.md:16 references/pipelines/api.md:124 references/pipelines/gotchas.md:45 references/pipelines/patterns.md:122 references/pipelines/patterns.md:125 references/pipelines/patterns.md:130 references/pipelines/README.md:88 references/pipelines/README.md:89 references/sql/api.md:3 references/sql/api.md:96 references/sql/configuration.md:7 references/sql/patterns.md:109 references/sql/patterns.md:114 references/sql/patterns.md:118 references/sql/README.md:63 references/sql/README.md:64
감사자: codex
이 보고서 공유 및 인용
버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.
보고서 링크 복사
https://skillstore.io/skills/cloudflare-basin/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 배지
[](https://skillstore.io/skills/cloudflare-basin?utm_source=security_passport_badge)HTML 배지
<a href="https://skillstore.io/skills/cloudflare-basin?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cloudflare-basin/security.svg" alt="Skillstore security assessment" loading="lazy"></a>임베드 카드
<iframe src="https://skillstore.io/embed/skills/cloudflare-basin.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>학술 인용 (APA · BibTeX · CFF)
APA 인용
cloudflare. (2026). basin security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cloudflare-basin/audits/1BibTeX 인용
@techreport{cloudflare-cloudflare-basin-2026,
author = {cloudflare},
title = {basin security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/cloudflare-basin/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "basin security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "cloudflare"
date-released: "2026-10-09"
url: "https://skillstore.io/skills/cloudflare-basin/audits/1"
identifiers:
- type: other
value: "skillstore:cloudflare-basin:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore 점수
이 점수의 이유 증거 신뢰도: 중간 36
아키텍처
85
유지보수성
87
콘텐츠
65
커뮤니티
83
사양 준수
만들 수 있는 것
Design a Streaming Analytics Pipeline
Plan event schemas, Worker ingestion, SQL transformations, and Iceberg sinks for an R2 analytics workflow.
Develop a Protected Analytics Dashboard
Adapt the Basin SQL Worker pattern with application access controls, bounded queries, and server-side credential storage.
Diagnose Missing Analytics Events
Investigate pipeline status, delayed flushes, validation errors, sink credentials, and delivery metrics before changing infrastructure.
이 프롬프트를 사용해 보세요
Choose the Basin Components
Explain which Basin components fit my event analytics workload: [workload]. Identify required resources and questions before proposing commands.
Plan Authenticated Event Ingestion
Plan a Basin pipeline for [event schema] in [bucket]. Include authenticated ingestion, client validation, scoped credentials, and current Wrangler command checks.
Investigate Missing Events
Events are accepted but missing from [table]. Use these sanitized metrics: [metrics]. Propose read-only checks without printing secrets or deleting resources.
Review an Analytics Architecture
Review [architecture] for Basin analytics. Assess caller authorization, IP minimization, partition filtering, compaction, schema migration, and rollback using current provider references.
모범 사례
- Check current provider documentation and installed tool versions before applying migration commands or permission changes.
- Require ingestion authentication and dashboard authorization; scope credentials and never print secret values during diagnostics.
- Validate events before sending, verify stored output, and use partition filters, query limits, and appropriate table maintenance.
피하기
- Deploying unauthenticated ingest or dashboard examples directly into production.
- Assuming accepted events are persisted without checking validation errors, sink files, and query results.
- Claiming IP redaction while storing raw addresses, or exposing authentication tokens in troubleshooting output.
자주 묻는 질문
What does this skill provide?
It provides reference guidance and implementation patterns for Basin Pipelines, Basin Catalog, and Basin SQL over R2.
Does installation create Cloudflare resources?
The reviewed package contains Markdown references, not provisioning scripts. Resource creation requires separately running authorized tools or API requests.
Does it cover the former Cloudflare product names?
Yes. It maps Pipelines, R2 Data Catalog, and R2 SQL to Basin names and warns that command migration requires verification.
Can Basin SQL modify data or replace a transactional database?
No. The references describe Basin SQL as read-only analytics; writes require other engines, and transactional workloads need a suitable database.
Why can accepted events be missing from queries?
Deferred schema validation, first-flush delay, roll intervals, and sink failures can prevent immediate visibility. Check service metrics and stored files.
Are the examples ready for production?
No. Review access controls, ingestion authentication, IP handling, secret diagnostics, current API behavior, and credential scope before deployment.
개발자 세부 정보
작성자
cloudflare라이선스
MIT
Skillstore 리비전
r1
버전 안내
작성자가 버전을 선언하지 않았습니다.
리포지토리
https://github.com/cloudflare/skills/tree/a18ffe2a99448ebff262fc87915b0fd14bab9b70/skills/basin참조
e406bf64b5db6e514879399e87b346fa7ff7c2fb
유지보수 최신성
2026. 10. 11.
사용량
0 다운로드 · 0 조회