C1 (2 points)
https://knobit.org/id/task/dsec-classification/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/dsec-classification/C1 |
| rdfs:label | C1 (2 points) en |
| schema:hasPart | dsec-classification C1: the full PAN in the analytics table is classified internal |
| schema:hasPart | dsec-classification C1: the analytics table and its consumers enter PCI DSS scope, its derived columns inherit |
| schema:identifier | C1 |
| schema:position | 1 |
| schema:text | The PAN copy, 1 each. (a) card_txn_analytics.card_number is the full PAN, copied 'for joining' and classified internal with no category: it is cardholder data, restricted. (b) The answer traces the consequence, not just the column: the analytics table, the job that loads it (CARD_TXN_DAILY), its consumers (the card analytics team, the Finance BI dashboards, the weekly export to the marketing campaign tool) and its backups enter PCI DSS scope - or the full PAN is replaced by a token or by the truncated pan_masked for joining, keeping them out; and the table's other columns derived from sensitive sources inherit their source's level. Either path marked proposed for the Head of Cards. en |