Testing
AuraScore 81/100

Humanitarian Case Management Data Privacy Verification Matrix

Design a test matrix verifying PII masking, data boundaries, and privacy safeguards for nonprofit case management systems.

Use this template when validating data anonymization, role-based access control, and privacy protections in vulnerable community support software. It delivers a comprehensive test matrix for QA and security developers.

Template

Role: Senior Nonprofit Data Privacy & Security Test Lead with expertise in vulnerable beneficiary protections.

Context

  • Mission Context: {{ngo_mission_context}}
  • Beneficiary Data Fields: {{case_data_types}}
  • Threat Model & Adversaries: {{vulnerability_threat_model}}
  • Governing Privacy Standards: {{regulatory_frameworks}}
  • Test Environment Constraints: {{test_environment_constraints}}
  • Integration Endpoints: {{integration_endpoints}}

Task

Produce a Data Protection & Privacy Verification Matrix that verifies data masking, tenant isolation, and cryptographic safeguards for beneficiary records across {{integration_endpoints}} without leaking sensitive PII.

Method

  1. Classify all attributes in {{case_data_types}} according to harm potential defined in {{vulnerability_threat_model}}.
  2. Map anonymization and tokenization requirements against mandates in {{regulatory_frameworks}}.
  3. Construct negative test cases simulating field-level leakage during cross-border syncing or export workflows.
  4. Define role-based access control (RBAC) boundaries separating intake workers, external auditors, and platform administrators.
  5. Align synthetic test data generation recipes with {{test_environment_constraints}} to avoid using live beneficiary information.
  6. Detail cryptographic verification tests for data in transit and at rest across each system interface.
  7. Populate a verification matrix with explicit inputs, boundary exploits, and expected masking outcomes.

Constraints

  • You MUST NOT permit any raw or unmasked PII across {{integration_endpoints}} in test definitions.
  • You MUST define validation steps for both direct database queries and application UI layers.
  • At least two matrix test cases MUST target offline/field-synchronization failure modes.
  • All test vectors must reflect realistic constraints imposed by {{ngo_mission_context}}.

Output format

Provide the deliverables structured as follows:

  1. Threat Context & Scope Boundary (under 150 words).
  2. Privacy & Masking Test Matrix (Markdown table with columns: Scenario ID, Data Category, Threat Vector, RBAC Persona, Test Procedure, Expected Redaction/Masking Behavior, Risk Level).
  3. Data Leakage Remediation & Logging Rules (4-5 technical requirements for audit trails).

Self-review

  • Validate that all 6 input variables are correctly operationalized.
  • Ensure matrix includes no fewer than 7 distinct security/privacy test cases.
  • Check that zero production or unmasked PII is suggested in test data strategies.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

developers
developers-testing
public-sector-nonprofit
data-privacy
nonprofit
security-testing