Data classification
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
classify data and attach handling rules to each class.
Planned topics
- Classes for Larkspur: public, internal, confidential, personal, payment.
- Each class gets rules: who may access, where it may be stored, encryption, whether it may leave the platform, whether it may appear in logs or analytics.
- Classify per data set and per field; one order record holds several classes.
- Rules that are not enforced by architecture (tagging, masking, access policy) are only wishes.
Draft outline details
Demonstration
a table: data set, class, system of record, allowed copies, masking rule. Example: customer email = personal; card token = payment-related, no card number anywhere.
Check your understanding
Why classify at field level?
Show answer
One record mixes classes; the email needs different handling from the order total.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.