Sekit CSF · Privacy · Process
RCF-0365Privacy by design
Privacy by design principles are consistently applied in development
Mapping at a glance
RCF-0365Privacy by designPrivacy · Process
RCF-0365 maps to 7 controls across the published frameworks. +2 more in the table below. Open in the full graph →
Maps to ISO/IEC 27001:2022
Curated mapping with the reasoning, not just the codes.
A.5.34Privacy and protection of personal identifiable information (PII)supportsRunning the privacy check as a routine step in every project keeps privacy by design an actual gate, not a principle stated in policy only.A.8.25Secure development life cyclerelatedThe privacy-by-design process runs a privacy check as a routine step before launch, a parallel discipline to A.8.25's security-by-design requirement rather than the same one.
Maps to NIST CSF 2.0
Curated mapping with the reasoning, not just the codes.
GV.PO-02Cybersecurity policy maintainedPR.DS-01Data-at-rest protectedPR.PS-01Configuration management applied
Maps to ISO/IEC 42001:2023 — Annex A
Curated mapping with the reasoning, not just the codes.
A.6.1.3Processes for responsible design and development of AI systemssupportsRunning the privacy check as a routine project step is the closest existing practice to the data governance stage an AI development process needs.A.6.2.2AI system requirements and specificationsupportsRunning the privacy check as a routine project step supplies the data-governance input an AI requirements record needs before design begins.
Evidence that proves this control
What an auditor, or Sekit's evidence engine, asks for.
DPIA and cross-border transfer records
The privacy impact assessments done before new data processing and the records of personal-data transfers to other countries.
From the Sekit evidence catalog
This topic through the other lenses
All Privacy controls
Ask Sekura: “What evidence proves RCF-0365?”
Also via MCP, free with account