ISO 27018 Assessment
Assess ISO/IEC 27018:2019 PII (Personally Identifiable Information) protection in public cloud for "$ARGUMENTS". Evaluate PII processor obligations and cloud-specific PII protections.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"compliance-iso27018","workflow":"compliance","phase":1,"project":"<project>","event":"skipped","artifact":"01-assess/","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 1 (Assess) of the GRC Lifecycle workflow (compliance); cross-domain workflows run it too. First check .singularskills/log.jsonl for an open run for this project: a run-started line with "project":"<project>" and no later run-finished line for the same workflow and project. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the workflow skill with the workflow the user asked for, or compliance when they named none, followed by <project>; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.
Run this skill's gate before writing: sh <this skill's folder>/scripts/gate.sh <project> <project root>, where <project root> is the folder that contains .singularskills/ (use . when you are already there). If it exits non-zero, stop and tell the user what it printed, unless --skip-checks was given (see Arguments). On a refusal, before you stop, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"compliance-iso27018","workflow":"compliance","phase":1,"project":"<project>","event":"refused","artifact":"01-assess/","note":"<what the gate printed>"}. Once the gate has passed, or under --skip-checks once you have appended the skipped line, append this line before you start work: {"ts":"<ISO timestamp>","skill":"compliance-iso27018","workflow":"compliance","phase":1,"project":"<project>","event":"started","artifact":"01-assess/","note":""}.
Read .singularskills/compliance/<project>/00-scope.md. If this file does not exist, tell the user:
Phase 0 (Scope) has not been completed for "". Run
/compliance-regulatory-landscape <project>first, or use--skip-checksto bypass.
Process
Read context files:
- Read
references/grc-lifecycle-guide.mdfor GRC methodology reference - Read
references/assessment-template.mdfor output structure - Read
.singularskills/compliance/<project>/00-scope.mdfor scope and control framework context
- Read
PII processing context:
- Identify PII categories processed in the public cloud (names, emails, financial data, health data, etc.)
- Determine role: PII controller, PII processor, or both
- Map data flows showing where PII enters, is processed, stored, and exits the cloud environment
- Identify applicable privacy regulations (GDPR, CCPA, etc.) that ISO 27018 supports
PII processor obligations assessment (ISO/IEC 29100 principles):
- Consent and choice — assess mechanisms for obtaining and managing data subject consent
- Purpose legitimacy and specification — assess documentation of processing purposes, limitation to stated purposes
- Data minimization — assess collection limitation, data adequacy, relevance checks
- Use, retention, and disclosure limitation — assess data retention policies, usage restrictions, third-party disclosure controls
- Accountability — assess privacy governance, DPO appointment, privacy impact assessments
- Information security — assess security controls protecting PII (encryption, access control, monitoring)
- Privacy compliance — assess privacy policy publication, compliance monitoring, breach response
- Score each principle: Compliant / Partially Compliant / Non-Compliant
Cloud-specific PII protections assessment:
- Data location disclosure — assess transparency about where PII is stored and processed geographically
- Sub-processor transparency — assess disclosure of sub-processors, notification of sub-processor changes, contractual flow-down requirements
- Breach notification to controllers — assess incident notification procedures to PII controllers, timeline commitments, content requirements
- Data return and disposal — assess data portability upon contract termination, secure deletion procedures, deletion certification
- Government access disclosure — assess policy for handling government data access requests, transparency reporting
- PII transmission security — assess encryption in transit, secure API design, data transfer mechanisms
- Score each protection: Implemented / Partially Implemented / Not Implemented
Contractual requirements review:
- Assess Data Processing Agreements (DPAs) for ISO 27018 alignment
- Check contractual obligations with sub-processors
- Verify controller notification procedures are contractually defined
Write the artifact to
.singularskills/compliance/<project>/01-assess/iso27018.mdfollowing the assessment template structure with:- PII Processing Context — data types, roles, data flows
- PII Processor Obligations — 7 principles scored with findings
- Cloud-Specific PII Protections — cloud protections scored with findings
- Contractual Requirements — DPA and sub-processor agreement review
- Overall Compliance Score — score = (Compliant/Implemented + 0.5 × Partially Compliant/Implemented) ÷ assessed principles and protections, as a percentage; show it with a heatmap
- Remediation Priorities — ranked list of gaps to address
Output
The ISO 27018 assessment written to .singularskills/compliance/<project>/01-assess/iso27018.md. Present a summary to the user highlighting:
- PII categories and processing role identified
- Overall PII protection compliance score (percentage, as defined above)
- Top 3 PII protection gaps
- Sub-processor transparency status
Record the run. After you have written the artifact, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"compliance-iso27018","workflow":"compliance","phase":1,"project":"<project>","event":"finished","artifact":"01-assess/","note":""}.
Open the artifact with this frontmatter (agent is the agent you run in, or unknown; gate is passed when the gate ran clean and skipped under --skip-checks):
---
skill: compliance-iso27018
workflow: compliance
phase: 1
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
End the artifact with ## Decisions and ## Open questions, in this shape:
## Decisions
- <what was chosen> — <why> — <what was rejected>
## Open questions
- <what the next phase or a reviewer must settle>
End the artifact with this paragraph, verbatim:
Not legal or audit advice. This artifact supports preparation for compliance work; certification, attestation and regulatory conclusions require a qualified auditor or counsel.