Topics In Demand
Notification
New

No notification found.

Blog
Privacy & IT Architecture

April 4, 2018

424

0

Building or designing Privacy in IT systems is no different than building Privacy in traditional building & utilities designs. Privacy architecture is the embodiment of the Privacy by Design (PbD) principle, which has been adopted as a privacy standard by privacy regulators worldwide. Which involves the incorporation of privacy principles and features into the basic design of information management processes and system(s).

Privacy architecture is often confused with security architecture, which is quite different. Privacy and security architectures must be coordinated and can be combined, but privacy architecture features are distinct from security architecture features.While a lot is happening in IT world , one thing is common across both sides of equator – ambiguity on role of Solution and Enterprise Architects in privacy related projects (GDPR is just a hot topic, I am saying privacy risk in any compliance or ethics format). Traditional IT architects were bred on security and ease of doing business (service integrity). Privacy emerging as a critical (N/FR – Non/Functional requirements) within IT ecosystem has resulted on questions on what and how architects will approach this situation.

For instance, Enterprise Data Privacy Architecture (EDPA) provides you with the ability to protect in isolation sensitive data fields residing in IT systems such as Web, Application and Database Servers. This architecture ensures all sensitive data in storage is encrypted, and only decrypted when required. The architecture encrypts data as early as possible – for example at Web servers, and provides many benefits including however not limited to:

  • Centralization of encryption keys
  • Separation of duties
  • Granular protection of sensitive data from such users as DBA’s and Root Users
  • Auditing and logging and consistent cryptographic interface to any type of application such as those commonly used in Web, Application and Database servers
  • The protection of any identified sensitive data from internal rogue employees as well as external hackers

One of the finest pair of articles on this, laying out the subtle intricacies on this matter was published by Marc Lankhorst , few months ago, in bizz design forum, without going in details , I would say that its a must read for all you fellow privacy professionals & architects – who either have similar or vested interests on this matter .  The topic was – 7 Things Every Enterprise Architect Needs to Know About the GDPR

 8 Steps Enterprise Architects Can Take to Deal with GDPR

Some other honorable mentions : (Read the following articles)


That the contents of third-party articles/blogs published here on the website, and the interpretation of all information in the article/blogs such as data, maps, numbers, opinions etc. displayed in the article/blogs and views or the opinions expressed within the content are solely of the author's; and do not reflect the opinions and beliefs of NASSCOM or its affiliates in any manner. NASSCOM does not take any liability w.r.t. content in any manner and will not be liable in any manner whatsoever for any kind of liability arising out of any act, error or omission. The contents of third-party article/blogs published, are provided solely as convenience; and the presence of these articles/blogs should not, under any circumstances, be considered as an endorsement of the contents by NASSCOM in any manner; and if you chose to access these articles/blogs , you do so at your own risk.


© Copyright nasscom. All Rights Reserved.