testland/test-data-governance-reference
Pure-reference catalog of test-data lifecycle governance: retention schedules for test datasets, cross-environment data-sharing agreements, deletion of test data containing real PII, refresh cadence, access controls, and the legal basis for each policy under GDPR Art. 5 storage limitation and NIST SP 800-122. Use when defining a data-steward role for test environments, authoring a retention policy for a test database, scoping a data-sharing agreement before promoting a dataset from production to staging, or determining the deletion timeline for any test fixture that contains live personal data.
74
93%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
access-controls.mdreferences/
Access controls
Referenced from SKILL.md. Access to test datasets containing personal data follows the NIST 800-122 principle of minimum necessary access (referenced in §4 control recommendations, grounded in the Fair Information Practices). In practice:
- Role-based access: only testers whose test case requires the data are granted access. Developers not running those tests do not have access to the test database or fixture files.
- Shared credentials are prohibited: each accessor has an individual account so the audit log (NIST 800-122 control family: Audit and Accountability) can attribute access to a named person.
- Elevated-access review: T3 and T4 environments require the data steward's approval for new access grants. Access is time-bounded to the duration of the test engagement.
- Read-only by default: write or delete access to a test dataset containing personal data must be justified separately. A tester running assertions does not need INSERT or UPDATE.
- Offboarding: when a tester leaves the project or the vendor engagement ends, access must be revoked the same day. The offboarding checklist must include test-environment credentials.
CI pipelines that access test databases containing personal data must use dedicated service accounts (not developer credentials) and those accounts must be reviewed when the pipeline is decommissioned.