AGENT SKILL

data-security-checklist

Screen a data design or release for classification, least privilege, encryption, secrets, masking, retention, deletion, audit, and non-production use. Use during intake, design review, contract review, and production readiness; escalate detailed threat modeling, privacy law, and certification work.

License 许可
Apache-2.0
所属仓库
cwik-tech/octopus
最近更新
2026-10-27
Stars
★ 0
Forks
0

01 前言 Front Matter

name
data-security-checklist
description
Screen a data design or release for classification, least privilege, encryption, secrets, masking, retention, deletion, audit, and non-production use. Use during intake, design review, contract review, and production readiness; escalate detailed threat modeling, privacy law, and certification work.

03 SKILL.md 正文

Data Security Checklist

Scope

This is a cross-cutting screening control, not a substitute for a security, privacy, legal, or compliance specialist.

Method

  1. Inventory sensitive fields and assign a classification with an owner and authority.
  2. Map each principal, service, environment, and consumer to the minimum required access. Separate authentication from authorization.
  3. Verify encryption requirements in transit and at rest, including backups, replicas, logs, exports, and temporary storage.
  4. Verify secrets are externally managed, scoped, rotated, and excluded from code, logs, fixtures, and artifacts.
  5. Define masking, tokenization, or aggregation for sensitive fields and prove downstream copies inherit the policy.
  6. Define retention, legal hold, deletion, and propagation to derived datasets, caches, backups, and non-production environments.
  7. Define audit events for access, privilege changes, exports, destructive operations, and policy overrides without logging protected values.
  8. Review non-production data use, synthetic alternatives, incident response, and break-glass access.

Escalate when

  • The legal basis, consent, residency, or regulatory interpretation is unclear.
  • Threat modeling, penetration testing, certification, or infrastructure security is required.
  • Cross-border transfer, re-identification, cryptographic design, or privileged access creates material risk.

Shared resources

Load only the resources needed for the current task. The links resolve inside the current agent package.

  • ../../references/security-control-baseline.md
  • ../../templates/production-readiness-checklist.md
  • ../../templates/data-contract.yaml

Output

Return each control as satisfied, unsatisfied, not applicable with rationale, or decision-blocking. Name the owner and evidence for every satisfied control.

04 同仓库更多 Skills

cwik-tech
cwik-tech/octopus

twenty-year-land-plan

Apply the Bren discipline of evaluating every land and development decision on a twenty-year horizon, with a comprehensive plan for how the land, the community, and the surrounding public infrastructure evolve together. Deals optimized for a five-year exit are structurally different from deals that compound across generations; insist on knowing which kind you are making. Use when evaluating land, entitlements, master-planned development, or phasing decisions, and when separating five-year exit deals from generational holds.

★ 0
cwik-tech
cwik-tech/octopus

thematic-gut-check

Apply the Gray discipline of identifying the structural theme behind every real estate deal, testing where that theme sits in its capital-flow lifecycle, and insisting that deals without a named theme — or deals late in a crowded theme — clear a higher bar. A mediocre deal in a strong theme usually beats a clever deal in a weak one. Use when naming the structural thesis behind a deal, judging whether that theme is early or crowded, and setting the bar the deal must clear.

★ 0
cwik-tech
cwik-tech/octopus

supply-pipeline-gut-check

Apply the Zell discipline of grounding every real estate thesis in the local supply pipeline. Demand counts over adjectives — units under construction, units permitted, units proposed — and convert them into a forward absorption schedule. A deal that ignores the pipeline is a bet on a market you have not actually studied. Use when validating a market thesis, forecasting absorption and rent growth, or counting units under construction, permitted, and proposed.

★ 0
cwik-tech
cwik-tech/octopus

ruin-scenario-mapping

Apply the Taleb discipline of identifying, for every real estate deal, the specific chain of events that produces ruin — permanent, unrecoverable capital loss — and verifying that no single such chain has non-trivial probability. Deals with any plausible ruin path must be restructured or abandoned. Use when sizing leverage, testing refinancing, covenant, and liquidity risk, or checking whether any single failure chain can permanently wipe out the position.

★ 0
cwik-tech
cwik-tech/octopus

revenue-cost-architecture

Design a venture's revenue streams, pricing logic, cost structure, and unit economics so the business model has a coherent theory of value capture, not just value creation. Use after the value proposition and customer segment are set and before financial projections, when choosing a pricing model, calculating contribution margin or CAC payback, or checking whether the unit economics hold at scale.

★ 0
cwik-tech
cwik-tech/octopus

replacement-cost-stress-test

Apply the Buffett discipline of pricing every real estate asset against the cost to rebuild it from scratch. The ratio of purchase price to replacement cost sets a ceiling on long-run downside: below replacement cost, new supply cannot profitably undercut you; at or above it, you are buying a liability disguised as an asset. Use when setting a purchase price, judging downside protection, or testing how exposed an asset is to newly built competing supply.

★ 0