Singapore - Personal Data Protection Ac (PDPA) (2012) — reference-depth plugin backed by the SCF crosswalk (30 SCF → 14 framework controls).

version
0.1.0
GitHub stars
436

Install

/plugin install singapore-pdpa@grc-engineering-suite

Run it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.

Contents

Discovered from source

Skills 1

Singapore - Personal Data Protection Ac (PDPA) (2012) Expert

Reference-depth expertise for Singapore - Personal Data Protection Ac (PDPA) (2012). This plugin bundles the SCF crosswalk (30 SCF controls → 14 framework controls) with framework-specific context.

Framework identity

  • SCF framework ID: apac-sgp-pdpa-2012
  • Region: APAC
  • Country: SG

TODO: add the following when filling in expertise. Reference depth expects all of these to have at least two-sentence answers.

Framework in plain language

TODO: one-paragraph summary of what Singapore - Personal Data Protection Ac (PDPA) (2012) exists to do and who it affects. Avoid verbatim regulation text — paraphrase and cite articles/sections by number.

Territorial scope and applicability

TODO: who must comply, where operations must be happening, what the carve-outs are.

Mandatory artifacts

TODO: the named documents or registers the framework requires (e.g. GDPR's ROPA/DPIA, PCI DSS's ROC/SAQ, ISO 27001's Statement of Applicability). Stub if uncertain; a Full-depth PR can add commands to generate each.

Cadence and timelines

TODO: notification windows (e.g. GDPR 72 hours), assessment frequency, recertification cycles.

Regulator and enforcement

TODO: who enforces, how penalties are calculated, recent enforcement patterns worth knowing.

Interaction with other frameworks

TODO: overlaps with GDPR / ISO / NIST / sectoral rules. Reference the cross-framework analyzer outputs when useful.

Common misinterpretations

TODO: at least 2–3 community-level misunderstandings this plugin should correct. Example: "ITAR only affects munitions" (it covers technical data too).

Command routing

  • /singapore-pdpa:scope — determine applicability
  • /singapore-pdpa:assess — run a gap assessment
  • /singapore-pdpa:evidence-checklist — enumerate evidence requirements

All three delegate to /grc-engineer:gap-assessment with SCF framework ID apac-sgp-pdpa-2012 for the control-by-control mechanics, and wrap the results in Singapore - Personal Data Protection Ac (PDPA) (2012)-specific terminology.

Levelling up to Full

Full-depth plugins add framework-specific workflow commands tied to the audit ritual. Candidates for this framework:

TODO: propose 2–4 framework-specific commands. Examples from existing Full-depth plugins:

  • soc2: /soc2:service-auditor-prep, /soc2:trust-service-matrix
  • fedramp-rev5: /fedramp-rev5:poam-review, /fedramp-rev5:ssp-outline
  • pci-dss: /pci-dss:roc-walkthrough, /pci-dss:saq-route
  • cmmc: /cmmc:c3pao-readiness

References

Commands 3

Singapore - Personal Data Protection Ac (PDPA) (2012) Assessment

Runs a compliance gap assessment against Singapore - Personal Data Protection Ac (PDPA) (2012) by delegating to /grc-engineer:gap-assessment with the framework's SCF identifier, then overlays framework-specific context and evidence requirements.

Usage

/singapore-pdpa:assess [--scope=<scope>] [--sources=<connector-list>]

Arguments

  • --scope=<scope> (optional) — narrow the assessment to a specific part of the framework. Valid scopes depend on the framework; TODO: enumerate the standard sections/articles of Singapore - Personal Data Protection Ac (PDPA) (2012) here.
  • --sources=<connector-list> (optional) — comma-separated connector plugins.

What the assessment produces

  1. Compliance score — overall Singapore - Personal Data Protection Ac (PDPA) (2012) readiness percentage, weighted by mapped SCF controls.
  2. Applicable-requirements summary — which parts of the framework apply to the organization (see /singapore-pdpa:scope to narrow this down first).
  3. Control-by-control gap — every 14 mapped control, with pass/fail/inconclusive status from connector findings.
  4. Evidence gaps — controls where no evidence source is configured.
  5. Remediation roadmap — prioritized by severity and effort.

Delegation

Under the hood:

/grc-engineer:gap-assessment "apac-sgp-pdpa-2012" [--sources=<connector-list>]

The SCF crosswalk expands 30 SCF controls into the 14 Singapore - Personal Data Protection Ac (PDPA) (2012) controls.

Framework-specific notes

TODO: replace this section with framework-specific assessment guidance. At Reference depth, include at minimum:

  • Which assessment scope is most commonly requested
  • Known interactions with sibling frameworks (e.g. GDPR + UK DPA, or CMMC + NIST 800-171)
  • Any mandatory cadence (annual self-attestation, biennial external audit, etc.)
  • Common misinterpretations in community guidance that this plugin corrects

Singapore - Personal Data Protection Ac (PDPA) (2012) Evidence Checklist

Baseline evidence checklist for a Singapore - Personal Data Protection Ac (PDPA) (2012) assessment. The SCF crosswalk maps 30 SCF controls to the 14 Singapore - Personal Data Protection Ac (PDPA) (2012) controls; this command enumerates what evidence tends to be expected for each SCF family that's in scope.

Usage

/singapore-pdpa:evidence-checklist [--family=<SCF_family_code>]

Arguments

  • --family=<SCF_family_code> (optional) — restrict to a single SCF family (e.g. IAC, CRY, AST, BCD). Defaults to all families mapped for this framework.

Output

Markdown checklist grouped by SCF family with:

  • SCF control ID → framework-native control ID(s) (from crosswalk)
  • Evidence types typically expected (logs, configs, policy documents, tickets, training records)
  • Which connector plugins can collect each type automatically
  • Which items require manual upload / narrative

Framework-specific evidence

TODO: at Reference depth, replace this section with framework-specific evidence patterns. Items worth capturing:

  • Mandatory artifacts unique to Singapore - Personal Data Protection Ac (PDPA) (2012) (e.g. DPIA for GDPR, ROC for PCI DSS, SSP for FedRAMP)
  • Assessor expectations per control family
  • Retention periods required by the regulator
  • Artifacts auditors request repeatedly across engagements

Singapore - Personal Data Protection Ac (PDPA) (2012) Scope

Determines whether and how Singapore - Personal Data Protection Ac (PDPA) (2012) applies to the organization. Reference-depth scope is a decision-tree prompt; Full-depth plugins extend this with jurisdiction-aware logic.

Usage

/singapore-pdpa:scope

What this produces

  • Applicability verdict: In-scope / out-of-scope / partially in-scope, with the triggers that led there
  • In-scope entity types: (controller, processor, covered entity, critical-entity operator, etc. — framework-dependent)
  • In-scope data/systems: what the framework's definitions pull in
  • Jurisdiction reach: where operations must comply (single country, EU member states, EEA, etc.)
  • Carve-outs: exemptions the organization can claim
  • Next steps: whether to proceed with /singapore-pdpa:assess or /singapore-pdpa:evidence-checklist

Framework-specific scope triggers

TODO: replace with framework-specific triggers. Singapore - Personal Data Protection Ac (PDPA) (2012) scope depends on (at minimum):

  • Territorial reach — where operations happen and where customers/subjects are
  • Entity classification — how the framework defines in-scope actors
  • Sector/industry fit — financial, healthcare, critical infrastructure, government
  • Thresholds — revenue, headcount, user base, transaction volume

This scope command should ask only the questions that actually matter for this framework, then output the applicability verdict without asking the user to search through the whole regulation.

Sponsors

Details

Marketplace
GRCEngClub/claude-grc-engineering
Source
plugins/frameworks/singapore-pdpa
Category
Community

More from GRCEngClub/claude-grc-engineering

All 70