Managing and Regulating Third Party Data Loss Prevention Through Enterprise Rights Management

Financial organizations are struggling to meet today’s increasingly complex data governance requirements as the demand for “anywhere-anytime” access to corporate data rises exponentially. The equally rapid expansion of cyber threats and cyber crime introduce an increasingly hostile landscape for those in finance, especially those individuals in charge of moving data.  One aspect of data management often overlooked is in how data leakage can factor into an organization’s compliance plans, in particular third party data, which is where Enterprise Rights Management comes into play. 

Financial organizations need Enterprise Rights Management solutions to control the operational use of documents by internal and external partners, by performing high-level data loss prevention. This meets the PCI DSS requirement of controlling third party data and protecting it from security breaches.

PCI and 3rd Party Data

Data loss prevention (DLP) needs to follow any data that leaves an organization’s network boundaries, whether that is during collaborative efforts, client data exchanges or other data sharing activities in which a financial organization will be involved. Maintaining Enterprise Rights Management policies on all data is a vital part of hitting PCI compliance requirements, which is more difficult to achieve when the data is being used by third parties. Unfortunately, this may not be enough.

According to an interview conducted by Security Week, third party security is by and large a weak point for financial organizations. Many do not verify the data security policy of a third party prior to sharing sensitive data, often times exposing this data to higher risk of breach. The security protection of third parties may introduce new risk factors to your data that can subvert or even cancel out security intelligence implemented on shared financial data.

Thankfully, there is help. The PCI SCC helps those in the financial industry, as well as other PCI-reliant industries, work through the PCI compliance challenges brought forth by third party data sharing. This security guidance shows best practices throughout the data management cycle and covers the steps needed to conduct third party security policy due diligence. 

 

Some of the other facets of this guide touch on:

  • Engaging third parties to prioritize data security
  • Develop written agreements to clearly outline data security policies and assigns security responsibilities
  • Provider monitoring action steps and plans for configuration and remediation

This helps financial institutions share data in collaborative efforts while having a defined data security process in place that aligns with its own security intelligence methods and policies.

Revolving PCI Conflicts With BigFix

With the above action items in place, let’s turn to an actionable, security intelligence tool that will aid and further protect the PCI compliant stature of a financial organization’s data. IBM’s BigFix provides a great add-on call the BigFix Compliance add-on, which provides PCI DSS v3.2 security checklists to be used for endpoint and network data and device monitoring.

A key component I love utilizing with my financial and retail clients is the Security Configuration Management (SCM) module, which provides even further controls to better set, detect and enforce data security policies. The feedback I have received on this has been great; financial organizations using these additional controls find the benefit of real-time reporting and automatic non-compliance remediations a huge regulatory success. I mean, who wouldn’t want instant data security policy enforcement?

But what really brings this home is in how the BigFix compliance add-on in its ability to autodiscover and manage security policies on devices that were previously unknown, an especially important win in today’s collaborative environment. I have seen third parties push back on this, as having someone else’s security policy application on their personal device would be a bit concerning. However, as seamless as it is to enforce security policy on such a device is, it is just as easy to un-enforce the same device once the collaboration or project has ended. Thus, the third party device is left as it was, and the financial organization has successfully maintaining PCI compliance throughout the process.

Third Party DLP At Your Service

It is important for those in the financial industry to maintain PCI compliance on all of its data at all times, including when it leaves an organization’s walls as part of a third party initiative. Establishing and maintaining an appropriate level of security intelligence to ensure PCI compliance and DLP is vital to any financial institution, and Champion is equipped and ready to assist in meeting security intelligence goals.

PREV

Best Practices to Prevent Revenge DDoS in Banking Using QRadar

NEXT

Integration of Security Intelligent ERM Controls Enhances Data Loss Prevention in Banks

WRITTEN BY: