motherduck-security-governance

Explains MotherDuck security, governance, and access-control patterns for architecture decisions.

Updated Oct 15, 2019
One-click install
npx skills add https://github.com/kkkaoru/dotfiles --skill motherduck-security-governance-kkkaoru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: motherduck-security-governance
Source: https://github.com/kkkaoru/dotfiles/tree/main/.agents/skills-stroage/motherduck-security-governance
Command: npx skills add https://github.com/kkkaoru/dotfiles --skill motherduck-security-governance-kkkaoru

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams evaluating MotherDuck for production workloads need accurate guidance on security posture, tenant isolation, credential handling, residency, and sharing boundaries without overstating compliance claims. ## Core Features & Use Cases - Governance Workflow: Walks through credential ownership, isolation boundaries, access rights, and residency constraints step by step. - Public Security Anchors: Grounds answers in documented facts such as SOC 2 Type II attestation, GDPR verification, service accounts, SSO, and read-only zero-copy shares. - SQL Validation Checks: Provides queries against MD_ALL_DATABASES and MD_INFORMATION_SCHEMA to verify actual database and share boundaries. - Use Case: A technical owner designing a multi-tenant B2B analytics app uses this Skill to decide between structural database isolation and query-time filtering, and to position service accounts correctly. ## Quick Start Ask the assistant to review whether your proposed MotherDuck architecture meets your tenant isolation and credential-handling requirements.

Frequently Asked Questions about motherduck-security-governance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I isolate tenants in MotherDuck for a B2B application?

Prefer structural isolation over query-time tenant filtering for serious B2B workloads. Use separate databases, service accounts per customer boundary, or hypertenancy patterns rather than relying on row-level filters in shared tables.

What security certifications does MotherDuck have?

MotherDuck publicly states it has a SOC 2 Type II attestation and is GDPR verified, with signed DPAs available via [email protected]. Compliance reports and contractual commitments require confirmation through current Trust and Security channels.

Should I use personal tokens or service accounts in MotherDuck production systems?

Use service accounts for production systems, not personal tokens. Service accounts are organization-owned non-human identities designed for applications and automation, and credentials should stay in backend-controlled secrets.

Can MotherDuck shares enforce row-level security?

No. Shares are zero-copy, database-level, and read-only publication boundaries. They are suitable for governed data distribution but are not a substitute for row-level or table-level entitlement enforcement.

Does MotherDuck support data residency requirements?

MotherDuck's public pricing page lists AWS us-east-1 and eu-central-1 regions. Treat residency as a first-class architectural constraint and verify current region availability and contractual guarantees through official Trust and Security materials.

Does MotherDuck support SSO with Okta or Microsoft Entra ID?

MotherDuck publicly documents SSO support with identity providers such as Okta, Microsoft Entra ID, and SAML/OIDC options. Verify current plan requirements, verified domains, and IdP ownership before proposing a rollout.