The product manager will fill out a questionnaire with the legal team and respond to queries they ask about the product, such as what it does, who the lead might be, and a series of questions probing subjects around privacy, patents, security, open source, export controls and other factors. The Information Commissioner's Office (ICO), meanwhile, has been adamant that it wouldn't seek to punish businesses following an incident provided they have shown willingness and co-operation with the new regulations.įor example, for all product releases the company now demands the use of a structured privacy tool configured in a particular way. Research done since GDPR came into force shows a significant portion of organisations still don't consider themselves to be compliant with the toughest set of data protection laws drafted to date. And people are happier with a more standards-based way of proceeding." Compliance is a process and doesn't happen overnight "What I've been interested to see is that the privacy community and the business community, for all of the effort that went in, have taken to it pretty well. "The move to a framework where you need to know what data you're collecting, how you're using it, which vendors you're using to oversight, it gets us back to a manageable place. "For a long time, in Europe, we had national implementing of laws on the directive, we had filings, we had different permissions to obtain in different places," he tells IT Pro. Rather, the consensus has settled in more positive territory for Citrix's chief digital risk officer, Peter Lefkowitz, GDPR has worked much better as an accountability framework than people had expected. 12 months on, however, organisations by-and-large have come to learn that many of the urban myths spread before the GDPR watershed (that regulators would simply scale up fines, for example) have not come to pass.
0 kommentar(er)
