Warehouse load and marts
None of the held texts sets a fixed period on this consumer; every row below reads no period set by the text. Paste one job that feeds this consumer, for example dbt_daily_marts, weekly, and the register reads its period against the clocks below, names the gap in hours, and carries the question for its owner.
Matched on the job name or the consumer column by these words: marts, warehouse, etl, elt, mart build, warehouse load, transform, warehouse load. A backup, replication, feed or return job in this class is expected to name a fallback; a blank one is a finding.
The clock each rule sets
| Regime | Clock | Clause |
|---|---|---|
| GDPR | no clock | GDPR Art. 5 Principles relating to processing of personal data |
| ISO/IEC 25012:2008 named reference | no clock | ISO/IEC 25012 Currentness Currentnessquoted below |
| BCBS 239 named reference | no clock | BCBS 239 Principle 7 Accuracy (Reporting)quoted below |
Named reference beside this class, ISO/IEC 25012 Currentness Currentness: The degree to which data have attributes that are of the right age in a specific context of use; the acceptable age depends on the use, from real time to historical. A data quality requirement, measure or evaluation using the model is categorised under this characteristic (inherent point of view).
Named reference beside this class, BCBS 239 Principle 7 Accuracy (Reporting): Risk management reports should accurately and precisely convey aggregated risk data and reflect risk in an exact manner. Reports should be reconciled and validated.
Questions this page answers
How often does GDPR require warehouse load and marts?
The held text of GDPR Art. 5 (Principles relating to processing of personal data) sets no fixed period: no period set by the text. Process personal data lawfully, fairly and in a transparent manner; collect it for specified, explicit and legitimate purposes and do not process it further in a way incompatible with those purposes; keep it adequate, relevant and limited to what the purpose needs; keep it accurate and up to date, erasing or rectifying inaccurate data without delay; keep it in a form permitting identification no longer than the purpose requires; and secure it against unauthorised or unlawful processing and against accidental loss, destruction or damage using appropriate technical or organisational measures. The controller is responsible for all six principles and must be able to demonstrate compliance with them.
What does the register ask the owner of a warehouse load and marts job?
Which reports read these marts, and do they state the age of the data they show?
The clauses in full
Process personal data lawfully, fairly and in a transparent manner; collect it for specified, explicit and legitimate purposes and do not process it further in a way incompatible with those purposes; keep it adequate, relevant and limited to what the purpose needs; keep it accurate and up to date, erasing or rectifying inaccurate data without delay; keep it in a form permitting identification no longer than the purpose requires; and secure it against unauthorised or unlawful processing and against accidental loss, destruction or damage using appropriate technical or organisational measures. The controller is responsible for all six principles and must be able to demonstrate compliance with them.
What an assessor asks to see: The purpose recorded for each processing activity, stated specifically enough that a later use can be tested against it; Retention schedule per data category with the criteria that set each period, and deletion evidence showing the schedule actually runs; Minimisation analysis per collection point showing why each field is necessary for the stated purpose; Accuracy controls: how inaccurate data is detected, and records of rectification or erasure carried out without delay. Where it usually falls short: Purposes written so broadly, for example business purposes or service improvement, that no later use could ever be incompatible with them
The degree to which data have attributes that are of the right age in a specific context of use; the acceptable age depends on the use, from real time to historical. A data quality requirement, measure or evaluation using the model is categorised under this characteristic (inherent point of view).
What an assessor asks to see: Timestamps and refresh cadence per data set against the use's tolerance. Where it usually falls short: Reference data refreshed yearly for a daily decision
Risk management reports should accurately and precisely convey aggregated risk data and reflect risk in an exact manner. Reports should be reconciled and validated.
What an assessor asks to see: Reconciliation and validation procedures for risk reports prior to distribution; Defined accuracy requirements and validation sign-offs for reports; Documentation of report data sources and calculation methods; Error log and correction process for risk reports. Where it usually falls short: Reports distributed without validation or reconciliation
Requirement text quoted from the standards themselves, published at compliance.theartofservice.com, the same publisher as this register, read against the held text of each standard: our statement of each clause, not the instrument verbatim. Run this job through the register