From the course: Automating Data Quality in Dev Environments
Unlock this course with a free trial
Join today to access over 25,300 courses taught by industry experts.
Make a traceability matrix
From the course: Automating Data Quality in Dev Environments
Make a traceability matrix
- [Narrator] Requirements gathering for security isn't the same as gathering business requirements. Capturing security requirements is complex, comprehensive, and can take time to implement. So it's best to start security requirements gathering as early in your data product process as possible well before beginning a data migration or deploying data to production. Security requirements fall within three categories, confidentiality, controlling who gets to read information, integrity, assuring that information and programs are changed only in a specific authorized manner, and availability, assuring that authorized users have continued access to information and resources. It helps to track these security requirements using a security requirements traceability matrix. This matrix shows security requirements, their implementation schedule, and essential resources you'll need to succeed. VSRTM is a useful tool for your security steward to build and maintain as your products work…
Contents
-
-
-
-
-
(Locked)
Make a plan to govern data throughout the full lifecycle2m 38s
-
(Locked)
Practice data mesh design principles3m 29s
-
(Locked)
Automate federated data QA standards2m 12s
-
(Locked)
Execute data security standards2m 25s
-
(Locked)
Make a traceability matrix2m 45s
-
(Locked)
Scale and automate your data QA standards3m 1s
-
(Locked)
Use feature stores to prevent data drift2m 49s
-
(Locked)
Ship new data as deployable units2m 10s
-
(Locked)
Track ongoing regulation changes3m 10s
-
(Locked)
-