C1 (3 points)
https://knobit.org/id/task/dso-environments-capacity/C1
Also as Turtle · JSON-LD · RDF/XML
| dcterms:license | https://creativecommons.org/licenses/by/4.0/ |
|---|---|
| owl:sameAs | https://bitbucket.org/reffa/ontology/id/task/dso-environments-capacity/C1 |
| rdfs:label | C1 (3 points) en |
| schema:hasPart | dso-environments-capacity C1: production data outside production |
| schema:identifier | C1 |
| schema:position | 1 |
| schema:text | Production data outside production, 1 each. (a) UAT (EV-003) is called masked, but the personal identification code is hashed with SHA-256 and no secret - anyone can hash a known code and find the person - and the IBAN is kept: together the data stays re-identifiable, so it is still personal data (GDPR recital 26). The answer says why the combination, not each field, fails. (b) It fixes it: tokenisation with a secret key held outside the environment (or synthetic accounts for payment tests), and each refresh approved by the data owner (EV-003 has no refresh approval). (c) SIT (EV-002) loads an unmasked production copy: reported and changed to masked or synthetic data. en |
Used by
| has question | Core banking environments and capacity - masking and peaks (environments and capacity anomaly skills) |
|---|---|
| schema:isPartOf | dso-environments-capacity C1: production data outside production |