The main purpose of this topic is to discuss the state for affairs of GDPR for a DPO in a typical mid/large enterprise. Furthermore, we are trying to introduce a simple, pragmatic approach and framework that can be used in a typical business scenario.
I would like to welcome Claudio Reyes as a contributor to this blog. He has been a regular guest at Architecture Corner this year and will now write for Disruptive Architecture.
Claudio is a trusted advisory in the field of compliance and information architecture. He gives value to clients by leveraging high performance deliveries in the gap between business and technology.
Disclaimer
The expressed view in this blog is purely his personal view and not in any way related to the company that he work for.
In last article did we talk about individuals and GDPR. We will wait a while before describe how we thing about privacy and instead look at our sales process.
We have defined some of the Business Activities for production of film, video and TV, but it’s only one side of the coin. You also need to describe the information input and output from that activity.
The next step is to describe business activities for the prioritized business events (and needed business services) together with some of the roles. The benefit us that we can re-use a lot from industry standards and best practices in this area.
