Those of us involved in information technology have traditionally used the label legacy for applications running on the mainframe accessed via green screens. Many of us can remember the struggles of getting these legacy Web applications upgraded so that desktops and laptops could easily be used. Then we went through a huge shift to develop and deploy applications that could be accessed via a browser on the Internet — the ultimate in thin client experience and portability optimization.
Legacy Apps Aren’t Going Anywhere
Well, many of those Web applications are still around and used within enterprises, and given their age, they can easily now be considered legacy. They’ve endured the test of time and are functional but probably haven’t been upgraded in a while and the personnel who initially developed them may have moved on, as well.
These legacy Web applications were also developed before many of today’s strict privacy rules and regulations were introduced. They may present to users information that they really should not have access to, such as payment card information (PCI), personal health information (PHI), personally identifiable information (PII) and other individual or proprietary corporate information.
I was recently talking with a company that had put together a portal many years ago that drew information from a couple disparate systems for presentation to customer-facing personnel. Though this certainly helped the agents by providing information at their fingertips, it pulled all the customers’ data, including items like their full Social Security number. In their usage, the agents never really need to see the full value; they really only needed the last four digits of that number for validation. Providing that extra information only created risk and the potential for theft.
How Dynamic Data Masking Can Help
This is where introducing dynamic data masking functionality can help provide necessary data privacy protection and extend the life of these legacy applications. A dynamic data masking appliance can integrate with the Web server stack to identify sensitive data elements and decide how to present them back to the end user.
Based on rules, users can be individually identified or put into classifications for the purposes of rules applicability. Then, based on the data element and the appropriate rule applied, sensitive data can be completely or partially masked. This fine level of granularity can provide flexibility in applying the right level of masking while still delivering the content users need.
The bottom line is for organizations to think about these legacy Web applications and evaluate whether there are data privacy gaps in what information is presented back to users. If that’s the case, dynamic data masking could be the ideal solution.
Hi. I’m Designer of Blog Magic. I’m CEO/Founder of ThemeXpose. I’m Creative Art Director, Web Designer, UI/UX Designer, Interaction Designer, Industrial Designer, Web Developer, Business Enthusiast, StartUp Enthusiast, Speaker, Writer and Photographer. Inspired to make things looks better.
0 comments:
Post a Comment