Japan APPI reference plugin with scope, evidence checklist, and SCF-backed gap assessment.

version
0.1.0
GitHub stars
436

Install

/plugin install jp-appi@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

Japan APPI Expert

Reference-depth expertise for Japan's Act on the Protection of Personal Information (APPI), represented in SCF as apac-jpn-ppi-2020. This plugin bundles the SCF crosswalk (58 SCF controls -> 134 framework controls) with APPI-specific assessment context.

Framework Identity

  • SCF framework ID: apac-jpn-ppi-2020
  • Region: APAC
  • Country: JP
  • Regulator: Personal Information Protection Commission (PPC), Japan
  • Common shorthand: APPI / Japan PPI
  • Current assessment baseline: amended APPI fully in effect from April 1, 2022

Framework In Plain Language

APPI is Japan's national privacy law for organizations that handle personal information and retained personal data. It focuses on purpose specification, fair collection and use, security safeguards, third-party disclosure, cross-border transfer, breach response, and individual rights. For GRC work, treat APPI as both a privacy governance framework and an operational evidence framework: the assessor needs to see where Japanese personal data is collected, how it is used, who receives it, how incidents are escalated, and whether transfer and consent records match actual system flows.

Territorial Scope And Applicability

APPI applies to business operators handling personal information in Japan and can reach foreign operators that provide goods or services to individuals in Japan and handle their personal information. Scope analysis should identify whether the organization is a personal information handling business operator, whether it handles retained personal data, and whether it transfers personal data to third parties or recipients outside Japan. Do not assume APPI is only for Japan-incorporated entities; customer location, service targeting, and Japan data flows matter.

Mandatory Artifacts

Evidence usually centers on documented purposes of use, privacy notices, consent and opt-out records, third-party transfer records, cross-border transfer disclosures, processor or entrustee management, security-control policies, breach response procedures, and data subject request handling records. APPI does not mirror GDPR's Article 30 ROPA or DPIA terminology, but mature programs should maintain equivalent data inventories, transfer registers, incident logs, and vendor oversight files so APPI obligations can be demonstrated.

Cadence And Timelines

There is no SOC-style annual certification cycle in APPI. Assess recurring operating evidence on a risk-based cadence: access reviews, vendor reviews, privacy notice updates, transfer records, consent changes, and breach exercises should be refreshed when systems or purposes change and at least during annual privacy governance review. Breach reporting under the amended APPI is mandatory for specified incident categories; teams should preserve both the initial triage timeline and final report package to the PPC, plus affected-individual notification analysis.

Regulator And Enforcement

The Personal Information Protection Commission (PPC) is Japan's data protection regulator. PPC oversight can involve guidance, recommendations, orders, reporting demands, and administrative or criminal consequences for serious non-compliance. In assessment output, separate legal penalty analysis from technical control evidence: this plugin should identify likely gaps and evidence needs, not provide a penalty calculation.

Interaction With Other Frameworks

APPI commonly overlaps with GDPR for EU-Japan transfers, especially because Japan has an EU adequacy decision with supplementary rules. It also overlaps with ISO 27001/27002, SOC 2 privacy/security criteria, NIST privacy and security controls, and sectoral Japanese obligations for finance, healthcare, telecom, and government suppliers. Use the SCF crosswalk for control mechanics, but keep APPI-specific reporting focused on Japanese personal-data purpose, disclosure, transfer, and breach obligations.

Common Misinterpretations

  • "APPI only applies to companies incorporated in Japan." Foreign operators can be in scope when they provide goods or services to people in Japan and handle their personal information.
  • "EU adequacy means no APPI transfer work is needed." Adequacy helps EU-to-Japan transfers, but APPI still requires evidence for onward transfer, third-party provision, purpose limitation, and security safeguards.
  • "Breach notification is voluntary guidance." The amended APPI made PPC reporting and affected-person notification mandatory for specified breach categories; assessors should request incident triage and notification evidence.
  • "Pseudonymized information is unregulated." APPI introduced specific handling rules for pseudonymously processed information; teams still need governance over creation, separation, access, and downstream use.

Command Routing

  • /jp-appi:scope - determine applicability
  • /jp-appi:assess - run a gap assessment
  • /jp-appi:evidence-checklist - enumerate evidence requirements

All three delegate to /grc-engineer:gap-assessment with SCF framework ID apac-jpn-ppi-2020 for the control-by-control mechanics, and wrap the results in APPI-specific terminology.

Levelling Up To Full

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

  • /jp-appi:breach-triage - classify whether an incident likely triggers PPC reporting and affected-person notification.
  • /jp-appi:cross-border-transfer-check - review recipient country, consent/disclosure basis, equivalent-measures monitoring, and onward-transfer records.
  • /jp-appi:purpose-use-register - build or review the purpose-of-use inventory for Japanese personal data.
  • /jp-appi:entrustee-review - assess outsourced processing, sub-entrustee controls, and supervision evidence.

References

Commands 3

Japan APPI Assessment

Runs a compliance gap assessment against Japan's Act on the Protection of Personal Information (APPI) by delegating to /grc-engineer:gap-assessment with the framework's SCF identifier, then overlays APPI-specific context and evidence requirements.

Usage

/jp-appi:assess [--scope=<scope>] [--sources=<connector-list>]

Arguments

  • --scope=<scope> (optional) - narrow the assessment to an APPI workstream such as purpose-use, security-controls, third-party-transfer, cross-border-transfer, breach-response, data-subject-rights, or entrustee-management.
  • --sources=<connector-list> (optional) - comma-separated connector plugins.

What the assessment produces

  1. Compliance score - overall APPI readiness percentage, weighted by mapped SCF controls.
  2. Applicable-requirements summary - which parts of the framework apply to the organization (see /jp-appi:scope to narrow this down first).
  3. Control-by-control gap - all 134 mapped controls, 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-jpn-ppi-2020" [--sources=<connector-list>]

The SCF crosswalk expands 58 SCF controls into the 134 APPI/PPI mapped controls.

Framework-specific notes

  • Start with /jp-appi:scope when the organization is outside Japan, because APPI can still apply through Japan-facing goods or services.
  • Common assessment scopes are cross-border transfer, breach readiness, vendor/entrustee supervision, privacy notice and purpose-of-use governance, and retained personal data rights handling.
  • For GDPR-adjacent programs, verify that EU adequacy analysis does not obscure APPI-specific onward transfer, third-party provision, and affected-person notification requirements.
  • There is no APPI certification cycle equivalent to SOC 2 Type II or PCI ROC. Use recurring privacy governance, incident exercises, vendor reviews, and data-flow changes as cadence drivers.
  • Treat the SCF ID apac-jpn-ppi-2020 as canonical for tooling even when stakeholders refer to the law as APPI or Japan PPI.

Japan APPI Evidence Checklist

Baseline evidence checklist for a Japan APPI assessment. The SCF crosswalk maps 58 SCF controls to the 134 APPI/PPI controls; this command enumerates what evidence tends to be expected for each SCF family that's in scope.

Usage

/jp-appi: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

Collect APPI evidence around the actual Japanese personal-data lifecycle:

  • Purpose of use and notices: published privacy notices, internal purpose-of-use register, collection forms, consent language, and change approvals.
  • Data inventory and retained personal data: systems holding Japanese personal data, data categories, retention/deletion rules, and request-handling logs for disclosure, correction, suspension of use, or deletion.
  • Third-party provision: recipient lists, legal basis/consent or opt-out records, joint-use notices, transfer logs, and approval records.
  • Cross-border transfer: destination countries, recipient safeguards, consent/disclosure records, equivalent-measures monitoring, and onward-transfer review.
  • Security controls: access reviews, encryption/key management, logging, vulnerability management, endpoint controls, and incident response evidence for personal-data systems.
  • Entrustee supervision: processor/entrustee contracts, due diligence, security questionnaires, sub-entrustee approvals, and periodic oversight results.
  • Breach response: incident intake, triage criteria, PPC reporting analysis, notification records, final incident report, and lessons learned.
  • Pseudonymously or anonymously processed information: generation rules, separation of re-identification keys, access controls, use restrictions, and disclosure controls.

Prefer structured exports from identity, ticketing, DLP, logging, vendor-management, and data-inventory systems over screenshots. Where evidence is narrative, capture the owner, approval date, scope, and affected processing activity.

Japan APPI Scope

Determines whether and how Japan's Act on the Protection of Personal Information (APPI) applies to the organization. Reference-depth scope is a decision-tree prompt; Full-depth plugins extend this with jurisdiction-aware logic.

Usage

/jp-appi:scope

What this produces

  • Applicability verdict: In-scope / out-of-scope / partially in-scope, with the triggers that led there
  • In-scope APPI roles: personal information handling business operator, entrustee, joint-use participant, or third-party recipient
  • In-scope data/systems: personal information, personal data, retained personal data, personal-related information, and pseudonymously or anonymously processed information
  • Jurisdiction reach: Japan operations and qualifying offshore goods or services offered to individuals in Japan
  • Carve-outs: statutory exclusions or low-risk populations the organization can document
  • Next steps: whether to proceed with /jp-appi:assess or /jp-appi:evidence-checklist

Framework-specific scope triggers

Ask the minimum questions needed to classify APPI applicability:

  • Does the organization handle personal information about individuals in Japan?
  • Does it provide goods or services to individuals in Japan, even from outside Japan?
  • Is the organization acting as a personal information handling business operator, an entrusted processor, or both?
  • Does it handle retained personal data used for access, correction, suspension of use, or deletion requests?
  • Are there third-party provisions, joint-use arrangements, outsourced processing, or cross-border transfers?
  • Are there pseudonymously processed information, anonymously processed information, or personal-related information flows?
  • Are sector rules also relevant, such as finance, healthcare, telecom, public-sector, or critical infrastructure obligations?

Return an applicability verdict, the data populations in scope, the APPI roles involved, and which follow-up command should run next. Do not ask users to search the Act; translate answers into practical APPI scoping outcomes.

Sponsors

Details

Marketplace
GRCEngClub/claude-grc-engineering
Source
plugins/frameworks/jp-appi
Category
Community

More from GRCEngClub/claude-grc-engineering

All 70