yonglun/dama-skill / skills/securing-data
securing-data
VerifiedUse when data needs security requirements, classification, risk assessment, identity and access control, masking/encryption, auditability, cloud or vendor safeguards, security exceptions, incident interfaces, or evidence that controls work.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.4 KB |
| agents/openai.yaml | config | 262 B |
| references/playbook.md | markdown | 11.2 KB |
| templates/delivery-pack.en.md | markdown | 3.0 KB |
| templates/delivery-pack.zh.md | markdown | 2.8 KB |
| templates/register.en.xlsx | binary | 8.6 KB |
| templates/register.zh.xlsx | binary | 9.1 KB |
| templates/report.en.docx | binary | 37.5 KB |
| templates/report.zh.docx | binary | 38.0 KB |
templates/delivery-pack.en.md
View on GitHub# Data Security Delivery Pack
Skill: `securing-data`
[Word report](report.en.docx) · [Excel register](register.en.xlsx)
## Record details
| ID | Field | Project value |
| --- | --- | --- |
| `artifact_id` | Artifact ID | |
| `project` | Project | |
| `skill` | Skill | |
| `version` | Version | |
| `date` | Date | |
| `status` | Status | |
| `author` | Author | |
| `owner` | Owner | |
| `approver` | Approver | |
| `purpose` | Purpose | |
| `business_outcome` | Business outcome | |
| `scope` | Scope and exclusions | |
| `source_inputs` | Inputs and sources | |
| `assumptions` | Assumptions and constraints | |
| `decisions` | Decisions | |
| `rationale` | Rationale | |
| `risks` | Risks | |
| `exceptions` | Exceptions | |
| `open_items` | Open items | |
| `due_date` | Due date | |
| `acceptance_criteria` | Acceptance criteria | |
| `evidence_location` | Evidence location | |
| `reviewer_decision` | Reviewer decision | |
| `next_gate` | Next stage gate | |
## Domain analysis and decisions
### Security scope and responsibility (`scope`)
Define assets, processing chain, vendors, and shared-responsibility boundaries.
> Enter project evidence, conclusion, and owner.
### Data and risk classification (`classification`)
Classify data and handling requirements by use, sensitivity, and potential harm.
> Enter project evidence, conclusion, and owner.
### Threats and exposure (`threats`)
Record threat paths, exposure, existing controls, and residual risk.
> Enter project evidence, conclusion, and owner.
### Identity and access design (`access_design`)
Define least privilege, revocation, and denied paths by subject, data, and action.
> Enter project evidence, conclusion, and owner.
### Controls and negative tests (`control_tests`)
Cover encryption, masking, non-production data, export, audit, and unauthorized-access tests.
> Enter project evidence, conclusion, and owner.
### Monitoring incidents and response (`incident`)
Set logging, alerts, incident severity, escalation, and review evidence.
> Enter project evidence, conclusion, and owner.
### Exceptions and residual risk (`residual_risk`)
State exception approval, compensating controls, expiry, and review.
> Enter project evidence, conclusion, and owner.
### Gates and acceptance (`acceptance_evidence`)
List control-test, role-approval, and operations-handoff evidence.
> Enter project evidence, conclusion, and owner.
## Working registers
### Access Matrix (`access`)
Record subject-data-action permissions and denials.
| Subject (`subject`) | Data scope (`data`) | Action (`action`) | Decision (`decision`) | Owner (`owner`) | Approver (`approver`) | Evidence (`evidence`) |
| --- | --- | --- | --- | --- | --- | --- |
| | | | | | | |
### Control Tests (`control_tests`)
Track control effectiveness and remaining exceptions.
| Control (`control`) | Test (`test`) | Test result (`test_result`) | Exception (`exception`) | Owner (`owner`) | Evidence (`evidence`) | Review date (`review_date`) |
| --- | --- | --- | --- | --- | --- | --- |
| | | | | | | |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |